FAQ
From Jmri
This FAQ should be the first place to check for answers to your questions. Many times the answer is hidden in the mists of our Yahoo group archives. Hopefully this page will help clear that mist!
Contents |
How can I upgrade?
Every release of JMRI is carefully tested to try and ensure compatability with previous releases. To quote Bob:
"Backups are always good!!"
On MacOS X ,your config files, roster, etc, are stored in ~/Library/Preferences/JMRI (That's your own Library folder, in your home directory) If you make a copy of that, you've got everything that might get damaged if something Really Bad happens. But nothing like that is _supposed_ to happen; since JMRI 1.0 all formats have been (and will be, I hope) backward compatible. Note that they're not _forward_ compatible; if you create a new panel in N+1, you might not be able to read it in version N (or you might, there are just no guarantees)
For upgrades go to http://jmri.sourceforge.net Save and run the version appropriate to your computer.
No Loco Detected
With thanks to Paul Bender for the following notes:
Basically, the error "no loco detected" means that the decoder didn't respond when the command station sent out the programming request. On a Lenz system, this is the same as getting an "Error 2" when programming from a hand held throttle.
One possible cause of this is that the CV requested isn't actually defined in the decoder. See if you can read the problem CV using a hand held throttle. If you get the same result on the handheld, then the CV may not actually be defined.
When using Digital plus by Lenz ® systems, you can change CVs 1 to 999 with PoM, while "Programming on the programming track" is currently used for CVs 1 to 256.
This means reading CVs greater than 255 on a Lenz system will result in a No Loco Detected error (Common with SUSI variables as these are CVs 897 to 1024)
This message may also result from a bad connection betweeen the locomotive and the track --(dirty track, dirty wheels). Try moving the loco by hand to determine if the problem will resolve itself. Clean the track and clean the loco wheels.
Timeout talking to command station
This message is saying that your command station and JMRI are not communicating. Typical causes are incorrect 'com' port settings, baud rate, and other arcane H/W stuff that is discussed in, at present, various different places. If the program is starting up, but the programming options are 'greyed out' the JMRI Preferences setup page may be able to help.
NCE Systems
(Info taken from Bob Jacobsen's email to the mailing-list http://groups.yahoo.com/group/jmriusers/message/16702)
Common causes of 'Timeout talking to command station '
- Wrong cable
- Make sure that cable is "straight through", not "null modem". If you have an ohmmeter, you can confirm this by making sure that pin 2 on one end is connected to pin 2 on the other end.
- Wrong speed (mismatch from end to end)
- 9600 baud is the default speed for the PowerHouse Pro, however it could have been changed by mistake or sometimes it can get confused and report that it is set to 9600 even when it is not. See Setting / Resetting the Baud rate below..
- EPROM update
- If you have installed the EPROM update and not followed the NCE system reset instructions completely, you should follow the instructions above about changing the speed (baud rate) . This is because the NCE system memory needed to be reloaded when the EPROM was installed; if not done just right, the speed displayed isn't the speed actually being used. By changing it and changing it back, you ensure it's the right value. See Setting / Resetting the Baud rate below.
- Wrong com port
- Sometimes COM1 is a modem, fax connection, etc. if there are others listed, try each of them in turn in the DecoderPro preferences.
USB Connections on Windows PCs
DCC Systems connected to a Windows PC via USB (e.g. SPROG II, locoBuffer II) often use Virtual COM Port or VCP drivers in order to emulate an old fashioned serial COM port. A common problem is not setting the connection preferences to reflect the virtual COM port that has been assigned to your hardware.
After installing all of the required drivers, aqnd with the hardware connected and powered up, ascertain the COM port assignment by opening the Device Manager (Right-click "My Computer" then select Properties -> Hardware -> Device Manager. Expand the list of Ports (COM & LPT) and note the COM port assigned to your hardware. Enter this in the layout connection preference in DecoderPro, PanelPro, etc. [AC June 16, 2006]
Setting / Resetting the Baud rate
- Go to the menu item for setting the speed
- Set it to something other than 9600
- Set it back to 9600
