FAQ

From Jmri

Revision as of 20:42, 21 February 2006 (edit) Admin (Talk | contribs) ← Previous diff		Revision as of 20:56, 21 February 2006 (edit) (undo) Admin (Talk | contribs) (Addded timeout-talking-to-cmd-stn notes/link) Next diff →
Line 15:		Line 15:
	==Timeout talking to command station==		==Timeout talking to command station==
-	Anyone?	+	This message is saying that your command stationand 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 option are 'greyed out' the [JMRI Preferences setup] page may be able to help.

---

Revision as of 20:56, 21 February 2006

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 may help those mists clear!

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.

Timeout talking to command station

This message is saying that your command stationand 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 option are 'greyed out' the [JMRI Preferences setup] page may be able to help.