If OpSw 39 actually does fix it for a while - it probably is the battery, especially if it is 12 years old and never replaced.
Or someone is fat-fingering the throttle when they select that loco. You have to deliberately press the Edit key to get into status edit mode, so it shouldn;t be accidental. It's even on the opposite side and up a row from Enter, which IS something you might hit.
--Randy
Modeling the Reading Railroad in the 1950's
Visit my web site at www.readingeastpenn.com for construction updates, DCC Info, and more.
Thanks MisterBeasly and Randy for you input.
Randy this particular Super Chief system is over 12 years old and an OpSw 39 will fix the problem for a short time only. It could be the battery, as you say, I don't know if it was ever replaced. We will replace it and see.
Jack W.
It has nothign to do witht he decoder, it's in the system. Status editing is in the command station, to allow there to be a default setting (out of the box it's 128SS) but also have an override for some specfici addresses to use a different format, liek that old loco you haven't gotten around to putting a modern decoder in so it only does 14SS.
First thing to try is a complete reset of the DCS100. Make a note of any non-standard settings (like if the slots were expanded to 120 - the DCS comes from the factory set for 22) and follow the instructions in the back of the manual for OpSw 39 reset. This will reset the DCS100 to factory secs, which is 128SS for all newly selected locos. If that clears it, great. If not, you will probably have to call Digitrax. Also, how old is the system? Was the battery ever replaced? There's a CR2032 battery inside that keeps the config memory when the power is off, usually good for 5 years tops, although sometimes a brand new one lasts half that. When it dies compeltely, it's obvious - system settings revert to defaults once the power is shut off. But in that in-between state it's been known to cause wierd issues when it sort of keeps the memory but not fully - allowing wierdand sometimes invalid settings to be stored.
I looked up the definition of "Decoder Lock" in the NMRA Spec:
http://www.nmra.org/standards/DCC/standards_rps/rp922.html
The stated purpose of this is to allow you to program decoders individually even if they have the same address. However, the description indicates that you can use CV16 as a lock, by setting it to anything other than zero. So, try setting CV16 to 1. This should effectively block any unwanted changes to the decoder. To release the lock, set CV15 to 1, and then set CV16 to zero.
The spec does say that this is an optional feature, so it may not work with these decoders.
It takes an iron man to play with a toy iron horse.
CSX Robert,
I should have said it was on a Super Chief System. Calling Digitrax will be my last resort as my English pronunciation leave much to be desired.
There are lot of knowledge on this list I am hoping someone experienced that problem.
jalajoie... is it the decoders or the system at fault?..
It is the system, not the decoders. I am going o guess that he has a Zephyr because there have been reports of this problem with some Zephyrs. I don't know of any fix for it. I would contact Digitrax and see if they would be willing fix or replace it.
Some decoders have a feature that allows them to be "locked" so that they will not accept further changes to CVs. If you want to do a change, you need to unlock them first. Check the documentation with the model numbers to see if this is possible.
A member of the club on his own Digitrax layout has 2 decoders ( OneTsunami and One TCS) that keeps changing from 128 speed step to Trinary status. A status edit will change it to 128 but it is temporary only.
Any idea how to make the edit permanent and is it the decoders or the system at fault?
Thanks in advance.