I have a situation that has happened to me a few times so far that I find annoying to say the least.I have ten DCC operated locos (9 Digitrax,1 Lenz) and every once in a while one stops operating completely without any sign of malfunction other than stopping.Putting them on the computer programming track,I then find out that the decoder has returned to its factory set adress of 03.I’m told by other club members that this is normal as it happens to them occasionally.Does someone have any clue as to what causes this?
some decoders are sensitve to shorts on the track, not all the time and not every one.
if the short is exactally the right length, or frequecny it will scramble the decoders brains.
older decoders seem to scramble more, and the short is generaly caused by another loco, or metal wheeled car.
quick trip to programming track sets it all good again.
Check your manual and see if you can “lock” your decoder. I recently had a similar problem with a TCS decoder, reset 2 cv’s so that they are now unaffected and locked, and have been happy as a clam ever since.
If I remember correctly, there are some forum members that could tell you off the top of their heads what cv it is. I’m still only on my 1st cup of coffee, cant quite remember what cv’s,need more caffiene![:p]
Better check the manuals!![;)]
I had a digitrax that did this and my LHS finaly told me that certain old decoders did that and sold me a newer decoder. It fixed that problem. I did install a sound decoder in an old brass engine and its trick is to forget how fast it should be going and stops. If I turn the knob it starts going again, but it is frustrating. I am so new to DCC these things are still novelties. I hope I can get used to them, because what I read is that these things are the quirks of DCC and we need to learn to live with them.
Decoder Lock CV’s are typically CV 15 and CV16. Although not yet a standard, manufacturers such as Digitrax, TCS and Throttle Up! (Soundtraxx) have adopted the idea. It is recommended to set CV16 (the ID of the decoder to be locked) to 1 for light/motor decoder, 2 for sound decoder, 3 for accessory decoder (especially if you have more than one decoder in the unit.
Set CV15 for something other than 0, 1, 2, or 3 and the decoder is locked. To unlock the decoder, set CV15 to equal the ID number (CV16’s value).
The Tsunami has the lock feature as decribed by Carl however you must first program CV30 bit 0 to 1 (lock enable) A 0 for bit 0 is normal operation with no lock feature. That way you can’t accidentally lock your decoder without knowing it. I am not sure if Digitrax has this lock enable feature or not,. I just happened to be programming my Tsunami and came acrossed it.
Terry[8D]
Great point Terry! I forgot that one![8D]
It sometimes helps to disable the DC operation.
Jerry - I had heard that before but was never given a reason why? Any idea?
Terry[8D]
Disabling the DC feature helps to eliminate ‘strange behavior’ from decoders when the loco encounters dirty sections of track. The behaviors include:
-
stopping then becoming non-responsive to commands; lifting one side of the unit off the track the setting down may resolve the issue.
-
As number 1 but to resolve the problem, you have to reset and reprogram the decoder.
-
unit responds to the default address (#3) instead of the address you programmed.
-
Lighting effects do not work as expected, i.e., MARS lights stay on constantly, ditch lights do not flash alternately, etc.
In most cases, setting CV29 to 34 (4 digit addressing, NDOT is forward, no speed table, DCC mode only) or to 6 ( 2 digit addressing the difference compared to above) will set this mode.
Thanks Terry, I knew someone would have a little more oxygen to his brain than I had at the time of my last post! [|)]
One other idea to pass along. Older DH120’s have a problem where the loco will shake and jerk when commanded to run , or run,then stop and quiver, then take off again. 2 of my Maryland Midland GP9’s did this right in the middle of a module deplyment! (Yeah, the 2 in my sig pic) Rather than replace them, NCE system owners (and other I assume) can go into command station programming and change the number of stop packets that the command station sends out, from 1 to 9. Evidently DH120’s forget [D)]thier last command, then get confused [%-) ]when a new command comes along.
Kudos to Jim Scorce at NCE for answering an email during one of our club shows with the answer to this problem.[bow]