-
Notifications
You must be signed in to change notification settings - Fork 331
/
Errors.shtml
224 lines (183 loc) · 7.96 KB
/
Errors.shtml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
"http://www.w3.org/TR/html4/strict.dtd">
<html lang="en">
<head>
<meta name="generator" content=
"HTML Tidy for Mac OS X (vers 31 October 2006 - Apple Inc. build 15.17), see www.w3.org">
<!-- Copyright Bob Jacobsen 2008 - 2016 -->
<title>JMRI Setup - Error Messages and Codes</title>
<!-- Style -->
<meta http-equiv="Content-Type" content=
"text/html; charset=us-ascii">
<link rel="stylesheet" type="text/css" href="/css/default.css"
media="screen">
<link rel="stylesheet" type="text/css" href="/css/print.css"
media="print">
<link rel="icon" href="/images/jmri.ico" type="image/png">
<link rel="home" title="Home" href="/">
<!-- /Style -->
</head>
<body>
<!--#include virtual="/Header.shtml" -->
<div id="mBody">
<!--#include virtual="Sidebar.shtml" -->
<div id="mainContent">
<!-- Page Body -->
<h1>JMRI Setup: Error Messages and Codes</h1>
<!-- Copy any new content below from page http://jmri.org/help/en/manual/DecoderPro3/Error.shtml, another copy is in tools/programmer/ -->
<hr>
<p>Various things can go wrong when JMRI tries to work with
your DCC command station to program a DCC decoder. This page
lists the error message that can result, and describes what
they mean.</p>
<h2><a href="../html/setup/Errors.shtml">JMRI Error
Codes</a></h2>
<dl>
<dt><strong>301 - no locomotive detected</strong></dt>
<dd>The command station has reported that it doesn't see a
locomotive on the programming track.</dd>
<dd>
<p>This can happen if the locomotive isn't making good
electrical contact or if there's a wiring fault in the
locomotive.</p>
</dd>
<dt><strong>302 - programmer busy</strong></dt>
<dd>
<p>The command station has reported that it's busy doing
something else, and can't do any programming right now.
This usually means that some other part of the DCC system
is doing a programming operation, e.g. a hand-held
throttle.</p>
</dd>
<dd>
<p>Some DCC systems can't do ops-mode programming
(programming on the main) while also using the service
mode programming track, in which case they'll return this
error message.</p>
</dd>
<dt><strong>303 - requested not implemented in command
station</strong></dt>
<dd>
<p>This means that JMRI has requested the command station
do something that it doesn't support.</p>
</dd>
<dd>
<p>This is not supposed to happen, as JMRI should disable
programming modes that the command station can't provide.
If you do see this message, please report the
circumstances on the <a href=
"https://groups.io/g/jmriusers">JMRI
users Group</a>.</p>
</dd>
<dt><strong>304 - aborted by user</strong></dt>
<dd>
<p>The user has requested that the read or write
operation stop early.</p>
</dd>
<dd>
<p>This is considered an error, because the program
doesn't know whether the decoder actually saw the
operation complete or not.</p>
</dd>
<dt><strong>305 - confirm failed</strong></dt>
<dd>
<p>Some command stations allow you to "confirm" the
content of a CV, rather that read the value from it. In
general, this is faster than doing a complete read. If
the value in the CV doesn't match the expected value,
this message is issued. It's considered an error because
if the values don't match, we know that we don't know the
correct value for the CV contents.</p>
</dd>
<dt><strong>306 - timeout talking to command
station</strong></dt>
<dd>
<p>The program did not hear back from the command station
when it expected to.</p>
</dd>
<dd>
<p>This is by far the most common error message when
people first start using JMRI. In that case, it usually
means that the connection to the command station isn't
correct. This could be a problem with the cable(s) making
the connection, or a problem with how the preferences are
set. Picking the wrong serial port is particularly
common.</p>
<p>Once JMRI is working properly, this error may
occasionally happen due to a transient error. DecoderPro
generally will retry it successfully in that case.</p>
</dd>
<dt><strong>307 - Unknown error</strong></dt>
<dd>
<p>An error has happened, but JMRI doesn't know enough
about it to be able to report more detail.</p>
</dd>
<dd>
<p>In general, JMRI is pretty good at deciphering what
went wrong, and this message isn't very common. If you do
see this message, please report the circumstances on the
<a href=
"https://groups.io/g/jmriusers">JMRI
users Group</a>.</p>
</dd>
<dt><strong>308 - No acknowledge from
locomotive</strong></dt>
<dd>
<p>At the end of a CV read or write operation, the
locomotive replies ("acknowledges") to the command
station using a pulse of current.</p>
</dd>
<dd>
<p>If that pulse isn't seen, some command stations
provide this error message. It could be due to poor
electrical connections to the programming track or within
the locomotive. It could also be that the decoder doesn't
support readback.</p>
<p>Some decoders, particularly certain sound decoders,
draw so much current that the reply pulse isn't detected
by the command station. In that case, one of the various
"programming boosters" may solve the problem.</p>
</dd>
<dt><strong>309 - Short Circuit on Programming
Track</strong></dt>
<dd>
<p>The command station has reported seeing a short
circuit on the programming track. That prevents
programming operations.</p>
<p>Check the electrical connections to the programming
track, and also within the locomotive.</p>
</dd>
<dt><strong>310 - Sequence Error</strong></dt>
<dd>
<p>For some reason, the programming operation ended early
and the command station returned to normal mode (left
service mode) before it should have.</p>
<p>This error can occur when some operations are performed
in JMRI durring programming. Turning track power on durring
a programming operation on an XpressNet is one example of how
to create this error.</p>
<p>If you haven't performed any operations durring your
programming sequence, this error, might indicate that
you've selected the wrong command station type in the
preferences. Check that. If that's correct and it's still
happening, ask for help on the JMRI users list.</p>
</dd>
<dt><strong>311 - Communcation Error Between PC and Command Station</strong></dt>
<dd>
<p>The data between the PC and the Command Station was
corrupted and the corruption was detected before the
Command Station processed the request.</p>
<p>If this error occurs frequently, this error might
indicate a problem with the connection between your
computer and the command station or an issue with your
system interface. Wireless connections are more prone
to this issue than connections with physically connected
cables.</p>
</dd>
</dl>
<hr>
<!--#include virtual="/Footer.shtml" -->
</div><!-- closes #mainContent-->
</div><!-- closes #mBody-->
</body>
</html>