Skip to main content

The last time I ran my trains, I decided it was time to change the order of the locomotives in the remote. Today, when I ran them, one wouldn't respond. It sat on the track dark and silent. The remote said Engine Not On Track. So, I went to the DCS Companion 3RD Edition and soon found the answer. It would appear that the battery in that locomotive is low. When it was first added to my layout it was ID#7. During the last operating session I changed it to ID#3. To correct this problem, I cleared the locomotive from the remote and then added it back in. It added as ID#7 even though ID#3 and ID#4 are not used. I haven't verified the low battery because my TIU is 2.21 software. This is a 3 volt PS2. For those that aren't familiar with this occurrence; the ID# is permanently written into the locomotive memory when power is removed. But, if the battery is weak, the new ID# will be lost and the locomotive will continue to use the previous ID#. The remote still has the new ID#.

Last edited by Oman
Original Post

Replies sorted oldest to newest

Close,  If the battery is low, the new ID can not be written so the old one remains.  The easy test is power up the track, start the engine up so sounds are playing.  Turn off power to the track.  IF the engine plays a full shutdown sequence the battery is adequately charged.  If it immediately shuts off, or abruptly shuts off after only a few seconds with out completing the shutdown sequence the battery is too low, or possibly can no longer hold an adequate charge.  There for DCS setting will not write to memory, nor will the train be able to come out of neutral in conventional.   G

George,

Keith wrote:

For those that aren't familiar with this occurrence; the ID# is permanently written into the locomotive memory when power is removed. But, if the battery is weak, the new ID# will be lost and the locomotive will continue to use the previous ID#. The remote still has the new ID#.

You then wrote...

Close,  If the battery is low, the new ID can not be written so the old one remains.

... implying that Keith's statement was not completely correct, which it absolutely was.  Why did you feel Keith's statement wasn't 100% accurate?

Adding additional information is fine and admirable, however, please let's not confuse the issue.

Last edited by Barry Broskowitz

I thought the term "permanent" and "new ID Lost" were a little vague.  Thought what I said was just a little more accurate to what is actually happening.   More than just ID will not transfer.  Any setting changes like smoke off, or volume changes will not be written to memory either.  Which I know you know.  G

Last edited by GGG

Add Reply

Post
The DCS Forum is sponsored by

OGR Publishing, Inc., 1310 Eastside Centre Ct, Suite 6, Mountain Home, AR 72653
800-980-OGRR (6477)
www.ogaugerr.com

×
×
×
×
Link copied to your clipboard.
×
×