FAQ

From Jmri

(Difference between revisions)
(RXajBnNenDbG)
 
(22 intermediate revisions not shown)
Line 1: Line 1:
-
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 [http://groups.yahoo.com/group/jmriusers Yahoo group archives]. Hopefully this page will help clear that mist!
+
xw40lo Muchos Gracias for your article.Really thank you!
-
 
+
-
==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!!
+
-
 
+
-
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.
+
-
 
+
-
This message may alsoresult 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 unfortunately. If the program is starting up, but the programming options are 'greyed out' the [[JMRI Preferences setup]] page may be able to help.
+
-
 
+
-
== See Also ==
+
-
* [[Can I try the program without any layout connection? | Instructions for installation without a layout]]
+
-
* [[OsxDtrax | MacOS X with Digitrax]]
+
-
* [[MacOS X with Lenz]]
+
-
* [[ScriptMain | Information on scripting]].
+
-
* Please add others!
+
-
 
+
-
[[Category:FAQ]]
+

Current revision as of 09:29, 20 September 2012

xw40lo Muchos Gracias for your article.Really thank you!

Personal tools