Serge NOEL
118 lines
5.8 KiB
Plaintext
118 lines
5.8 KiB
Plaintext
<!DOCTYPE html>
|
|
<html lang="en">
|
|
<head>
|
|
<meta name="generator" content="HTML Tidy for HTML5 for Apple macOS version 5.8.0">
|
|
<title>JMRI: DecoderPro Frequently Asked Questions</title>
|
|
<!--#include virtual="/help/en/parts/Style.shtml" -->
|
|
<!-- FAQ-Head -->
|
|
|
|
<script type="text/javascript">
|
|
/*<![CDATA[*/document.documentElement.className="hasJS";/*]]>*/
|
|
</script>
|
|
<link rel="stylesheet" type="text/css" href="/web/css/faq.css" media="screen"><!-- /FAQ-Head -->
|
|
</head>
|
|
<body>
|
|
<!--#include virtual="/help/en/parts/Header.shtml" -->
|
|
|
|
<div id="mBody">
|
|
<!--#include virtual="Sidebar.shtml" -->
|
|
|
|
<div id="mainContent">
|
|
<h1>JMRI: DecoderPro User Guide</h1>
|
|
|
|
<h2>Frequently Asked Questions</h2>
|
|
|
|
<p>This page is the JMRI DecoderPro "frequently asked questions" list. Items get listed here
|
|
if they're asked a lot, even if they're also available somewhere else. See also the <a href=
|
|
"../../FAQ.shtml">JMRI general FAQ.</a></p>
|
|
|
|
<dl class="faq">
|
|
<dt class="on" id="newdecoder">How can I get a new decoder type defined?</dt>
|
|
|
|
<dd>
|
|
A completely new decoder needs a new or updated decoder configuration file. You can
|
|
<a href="CreateDecoder.shtml">create your own</a> or ask on <a href=
|
|
"https://groups.io/g/jmriusers">JMRI users</a> for somebody to create one for you.<br>
|
|
<br>
|
|
In many cases, you can use an existing decoder that's "close enough". For example, a
|
|
decoder from the same manufacturer that has a different size or current rating might have
|
|
the same configuration CVs, so its decoder definition would work fine.
|
|
</dd>
|
|
|
|
<dt id="newfile">What do I do with this new decoder file?</dt>
|
|
|
|
<dd>
|
|
For DecoderPro to use the definition of a decoder type in a new decoder file, the new
|
|
file has to be included in DecoderPro's index of decoder types. To do this:
|
|
<ul>
|
|
<li>In your JMRI install directory, you should find a directory named "xml". Under that
|
|
directory, there should be one named "decoders". You should put your new file in
|
|
there.</li>
|
|
|
|
<li>Now start up DecoderPro, and open the "Debug" menu. Select the "Rebuild Decoder
|
|
Index" option.</li>
|
|
|
|
<li>The computer will run for a minute or two with the selection highlighted. As soon
|
|
as that goes away, the new definition should be available to you.</li>
|
|
</ul>
|
|
Please make sure that the new configuration file has been contributed to the project so
|
|
it will be included in future releases, and so you won't have to remake the index each
|
|
time you update.
|
|
</dd>
|
|
|
|
<dt id="update">How can I get the latest decoder definitions?</dt>
|
|
|
|
<dd>
|
|
The easiest way to update really is to download a new version of the program. This is
|
|
unlikely to cause problems, and automatically installs the latest versions of that have
|
|
been contributed to DecoderPro.<br>
|
|
<br>
|
|
Updates occur continuously between versions of the program. As files are contributed, we
|
|
make them available on our <a href="../../../../../xml/decoders/">collected decoder
|
|
definitions</a> web page. You can download them from there, but note that most web
|
|
browsers will not let you directly view them; you really do have to download them.<br>
|
|
<br>
|
|
While people are working on decoder definitions, they often put their draft definitions
|
|
in the <a href="https://groups.io/g/jmriusers/files">"Files" area of JMRI users</a> (log
|
|
in to access). You can <a href=
|
|
"https://groups.io/g/jmriusers/files/Decoder%20files">download them from the Decoder
|
|
Files folder</a>.<br>
|
|
<br>
|
|
Note that as an anti-spam measure, you will have to <a href=
|
|
"https://groups.io/g/jmriusers/join">join the group</a> to be able to download the files.
|
|
</dd>
|
|
|
|
<dt id="errormsg">What does it mean to get Error 301 or Error 306 or any other errors?</dt>
|
|
|
|
<dd>
|
|
JMRI will display various errors when it finds something wrong in attempting to
|
|
communicate with your DCC command station. In particular, Error 301 means that DecoderPro
|
|
doesn't see a locomotive on the programming track when it is trying to program a decoder.
|
|
If you do have an engine on the track (only one!), clean the wheels and the track and try
|
|
again. Error 306 means that JMRI is not getting the expected signal from the command
|
|
station. If this happens when you are first setting things up, check your wiring,
|
|
connections, and com port selection. This <a href="../Errors.shtml">list of all error
|
|
messages</a> also provides some suggestions about how to clear them.
|
|
</dd>
|
|
|
|
<dt id="lb-xp">Why does my LocoBuffer-II not work in Windows XP?</dt>
|
|
|
|
<dd>With Windows XP, your serial port parameters might not be properly set for hardware
|
|
flow control. To fix this, right-click on My Computer and select Properties. Go to the
|
|
Hardware tab and click on Device Manager. Open up the section that says Ports (COM & LPT).
|
|
Right-click on the serial port you have the LocoBuffer hooked to and select Properties. Go
|
|
to the Port Settings tab and set the options to: <em>19200, 8, None, 1, Hardware</em>.
|
|
Click <em>OK</em>. Close the Properties panel. Restart JMRI and verify your connection
|
|
settings.</dd>
|
|
</dl>
|
|
<!--#include virtual="/help/en/parts/Footer.shtml" -->
|
|
</div>
|
|
<!-- closes #mainContent-->
|
|
</div>
|
|
<!-- closes #mBody-->
|
|
<script src="/js/help.js"></script> <!-- FAQ-Tail -->
|
|
|
|
<script src="/web/js/faq.js"></script><!-- /FAQ-Tail -->
|
|
</body>
|
|
</html>
|