开云体育

Rodney,


Wow, thank you for this, I will put this great advice to use immediately! I didn't realize I could change that within CATS - I thought I had to do it in the JMRI SE8c interface.


I absolutely do know how to get flashing red in hardware and that was how I used to do it, until I installed CATS. I don't use approach lighting. I used software flashing because I thought the CATS manual said to do that. But YOU are the author/guru on that! So I'll change to hardware flashing.


Thank you so much for supporting (and creating!) the CATS CTC software. I like it so much, I wrote a series of articles in the OPSIG journal, the "Dispatcher" on using CATS and JMRI for signal control.


Sincerely,


Steve Davis
KCS 3rd Sub

Is there a way to program a function key to control volume?

I'm not party to to inner working of frog juicers, but it seems to me you can't suddenly limit the current to less than the offending locomotive needs, or you'll have an operating hiccup.

Andy

Hi,
I think I have found what could be a bug between 4.8 and 4.9.1. It will only show up if a new user is installing a new copy on a Windows 10 computer that has never does not already have a copy of 4.8 (or earlier) installed. Here is how I discovered this:

I had recently purchased an Azulle Quad Core 4GB Ram 32GB ssdd Windows 10 Home v1607 compute stick and it arrived the other day. I hooked it up with an ethernet cable to my network and an HDMI cable to my monitor and an attached usb keyboard and mouse. I powered it up and it came up and walked me through the initial new Windows 10 configuring process. Once done, I adjusted the display setting to 1600x1200 to get the entire Windows image on my screen.

Now I was ready to start installing other applications. I downloaded JAVA 1.8.0_131(en_US) and installed it and followed with another restart of the Windows environment. I next downloaded JMRI 4.9.1 and installed it with all users and all three checkboxes set for PanelPro,DecoderPro,and SoundPro.
Once completed, I did another restart and then launched 4.9.1. The splash screen came up followed by the help screen and then JMRI sat there for a few seconds and then blew up with a error dialog box on the screen and when I hit the OK button it and everything else related to JMRI went away. I tried it again and got the same result.

I then went in and uninstalled 4.9.1 and deleted the JMRI folders under Program Files(x86) and Users/"username"/ so no residule data would exist.

I then download 4.8 and repeated the whole process. This time when I launced JMRI the preference dialog opened after the splash screen and I was able to enter the required info for the connections. This followed with the save and restart and everything came up and ran as it should.

Having done this without uninstalling 4.8, I reran the 4.9.1 install and on completion, JMRI 4.9.1 came up and ran with no problems. I am assuming if found what it need to launch because of the residule files left by 4.8. Therefore, I suspect something is not being included in the 4.9.1 install which will only trip it up if it's a brand new install.

I will send the jpg image capture of the error screen to Bob, George, and Randall since I do not know how to get yahoo to accept a jpg attachment. Anyone else that wants to see the jpg can send me you direct email address so I can send you the attachment.

=gerry=

Sam,



Most thumb drives have low read/write speeds. You would have to monitor this
using the task manager or other tools to see what speed you are getting.



I would not suggest that configuration. Putting the data on the thumb is one
thing but the program should be installed in the C drive like normal
programs.



-Ken Cameron, Member JMRI Dev Team

www.jmri.org

www.fingerlakeslivesteamers.org

www.cnymod.com

www.syracusemodelrr.org

Scott,



Inspect the console log to see if it provides clues. I can't remember when,
but there was an issue with the storing of the node configuration data and
that may need resetting. With the latest versions, 4.8 or 4.9.1 the serial
support has changed from 4.6 to a newer library. So there is a chance of a
conflict depending on what hardware you are using for your connection to
CMRI.



-Ken Cameron, Member JMRI Dev Team

www.jmri.org

www.fingerlakeslivesteamers.org

www.cnymod.com

www.syracusemodelrr.org

Hi Sam,

When you say "all data is stored in thumb drive", do you mean that you actually installed JMRI to the thumb drive?

If so, then as Dave H already explained, that is most likely the cause of your poor performance.

Your thumb drive will be 10 to 100 times slower than the main hard drive of your computer.

Even if only your JMRI user files are on the thumb drive, it will still slow things down.

You need to install JMRI to the c: drive.

Thanks Nick. I do have an SMINI but haven't installed it yet. This is just one SUSIC with 24 bit I/O cards which it appears doesn't care what is started first. I'll remember this though when I get started on the SMINI.

Scott

Bob,

I believe the problem may lie with the initialisation .

The SUSIC is set up with 24 bit cards in the following format:-


OOOO OOII IIII


My interpretation of the initialisation sequenece is ua=0, Type= N, NS=3, CT = aa 5a 55


I have checked via the CMRI monitor for this sequence and have found that for 4.6, 4.7.4 & 4.8 the sequence is ua=0, Type=N, NS=16, DL=10, CT= 3 aa 5a 55 ????? I would have expected NS to be 3. It appears to have added the correct NS to the CT sequence. The baud rate on the SUSIC matches the preferences entry and there is only one entry for the CMRI.


I should have been clearer on the fast flash - this is not the amber and red send/rec LED's but the Green which should indicate a slow flash if the SUSIC is successfully initialised. I get the slow flash for 4.6 but once upgraded to 4.8, I get the fast flash.


Under 4.6 I can use the CMRI diagnostics on one output card located in slot 0 and can see the successfull result of the test sequence. 4.7.4 & 4.8 as mentioned won't initialise even for just one output card.


For all three versions I tested, I get ua=0, Type=N, NS=1, CT = x for output cards in slots 0 to 3. As soon as I add a 5th card as a second card set, it appears to add the NS as the first digit for the CT sequence followe by the correct CT numbers.


Short of removing all traces of Java and JMRI from my laptop and reinstalling, I'm not quite sure of any other diagnostics I can try. In the longer term, I am planning to replace my laptop so perhaps if it is driver related, that may help.


Scott

Thanks Bob


I have done a little Python Programming and will have a look.


Peter

If you have installed the JMRI software on a thumb drive rather than the C: drive, that will cause a massive performance loss. Thumb drives are incredibly slower (10-100 times slower)

This will affect all aspects of JMRI performance.

You should install the JMRI software on your C: drive.

You can then change your User Files Location (see below) so only your user data is stored on the thumb drive. But even then reading and saving will be severely affected.

A better backup/sharing option is to use Dropbox (or similar) to ensure your files are backed up and shareable between computers (you will need to connect your computer to the Internet at least occasionally to backup the files.

This is used so commonly we have prepared a document or two:
<>
<>

This document is equally applicable whether you use your USB drive or your local Dropbox folder for storage (but Dropbox will be around 100 times faster).
--
Dave in Australia

I'm having the same issue as well. Wonder if it is a Java thing. I had one of the 4.6 variants installed on my current machine and it just took for ever to do anything. Opening and closing. As a matter of fact when I would close and reopen, it would say JMRI was still running and would I like to start another instance. I upgraded to the latest version 4.9.1 and still seems to have the same issue. Panel Pro does not seem to be as bad, but Decodor Pro 3 is unusable for me now. Plus I am trying to trouble shoot a Lenz issue which was the reason for checking the group tonight. Normally I connect to an NCE command station and use a Lenz system for programming. Both are connected to JMRI. NCE using a network connection and Lenz using a LI101F. My Lenz issue is anytime the LI101F is connected to the Xpressnet, it get a emergency stop on the LH100.


Greg McCartney

Wow, that was quite the reply, thanks. I'm running a newer HP machine windows-7 3.3ghz 4 gig ram, loading takes a lot longer than that, saving preferences as an example, lock up the program for up to 2-3 minutes then it comes back and says - (must restart program to take effect).

If I have multiple windows open, "Monitor loconet" etc. it's sometimes worse. My old XP machine I could understated, very slow anyway and too little memory.

The only other thing is that all data is stored in thumb drive, nothing on the "C" drive so I can take the program and data files to another PC if I want to or if the hard drive goes bad I'm safe.

Hope that helps..

Sam

Thanks for the response- Yes, i got a newer HP machine running (7) 64 bit and 4 gig of memory 3.3ghz processor. Runs everything else fine, but I found that especially when I change preferences and hit save, the program freezes and I could walk away for five minutes before it comes back and says- "must restart the program to take effect"

I'm not sure what the issue is as at times I have to close and restart the program and then it's fine...

I think you are onto something as I think Java has a problem on my computer. I'm going to follow your lead snd see what I can come up with
Thanks for the heads up
Cheers,
Richard



Sent from my Verizon, Samsung Galaxy smartphone

Ken and Richard,

I ran the JMRI InstallTest and discovered that there was an error with Java. I tried updating Java from the Start window but it - along with any of the Java programs - would not even run.

I went to Control Panel and saw that Java 8 Update 131 AND Update 141 were both installed on the tablet simultaneously. I deleted Update 141 then ran JMRI and it booted up just fine. I then updated Java 8 to Update 141 and it also booted up without mishap.

From Control Panel, Java 8 updated itself to Update 141 yesterday. However, for whatever reason, it didn't delete the prior version. When I updated to Update 141 manually this time around, Java detected and deleted the prior version (Update 131) before it completed the installation.

So, it appears that everything is copacetic now. Maybe that's the same issue you are running into, Richard.

Tom

You can get a signal to JMRI by replacing the indication LED with the input side of an optoisolator, connecting the other side to whatever electronics you use to get inputs. The 6N137 is a convenient part for this, as it produces a logic output (that’ll work with lots of systems) when the juicer would light the LED.

Bob

On Jul 25, 2017, at 5:29 PM, dave@... [jmriusers] <jmriusers@...> wrote:

A cool change to the circuit would be an output to JMRI so that a locomotive running onto a frog the 'wrong way' could be detected and used to trigger the point to change. This would be really useful in a DCC fiddle yard where you could drive any train out of the yard and have the points set for it without needing additional sensors!

--
Bob Jacobsen
rgj1927@...

If you are running DCC and have a crossover across three tracks with points/switches on the two outer tracks and a crossover in between then if you trace through the rails you should find that the two sharp frogs in the crossover should be wired to change in exactly the same way as the two frogs on the outer points/switches.

You should therefore be able to wire one crossover frog to one of the point frogs and the other to the other.

I happen to have frog juicers on the outer two points in my crossover and since there are no other points nearby I use the four channels in a quad juicer to cover the four frogs in the points and crossover.

BTW there is no 'short' in a frog juicer. When the wheel runs onto the frog the circuitry supplying the frog sees an increase in current and switches the frog. The circuitry limits the current to ensure there is no spark at the wheel and the switching is performed before the controller gets chance to see there is a short on the track. A cool change to the circuit would be an output to JMRI so that a locomotive running onto a frog the 'wrong way' could be detected and used to trigger the point to change. This would be really useful in a DCC fiddle yard where you could drive any train out of the yard and have the points set for it without needing additional sensors!

No problem. What brand and model of DCC system are you connecting to, what computer will you run JMRI on, and what interface will you use between the computer and DCC?

I use one of my my $9 computers (CHIP, running Jessie Debian Linux) at the club, and the other at home, both using Digitrax PR3s to connect. The WiThrottle is setup to automatically start.
Sometimes I use one of my Windows laptops (XP, 7, or 10). I don't have a MAC (tongue held tightly).

So post your plans, and we can help get it all connected and working.

Phil in gorgeous Young Harris, Georgia, USA