Have you tried resetting the decoders as suggested? Try that before going through the hassle of returning the command station.
Dante
Thanks for all the input. It appears the programming of my DCS50 is out to lunch. I also tried other modes of programming and none of them work either.
Digitrax recommends Direct Mode on the programming track.
I've only used the page mode, never tried any other mode.
Mark
Which program mode are you isning? The display will say Po, Pd, Pr, or Pg. Po is Ops Mode, will not work on the program track. Pr is Register mode, left over for compatibility with some old early decoders that didn;t exactly have CVs as we know them today. You should be using Pd for Direct mode, or Pg for Page mode.Most decoders support both, but some prefer one over the other.
--Randy
Modeling the Reading Railroad in the 1950's
Visit my web site at www.readingeastpenn.com for construction updates, DCC Info, and more.
All decoders are being programed on a program track.
Those two messages mean different things. d-nd means no decoder detected as in none. d-na means no acknowledgement from decoder. Make sure the track is clean. Wheels are clean, track is connected to the program A and B terminals. (they are not next to each other). page mode or direct mode programming selected. Direct works best.
Martin Myers
wjstix Some decoders have a CV setting that "locks" the settings in place. Until you unlock the decoder, I think it even blocks you from reading the CVs. It may be that your decoders were locked, and doing the factory re-set unlocked your decoders. Not sure if it was a TCS one, but seems to me early on in my DCC days (daze?) I accidently locked a decoder, or locked it and forgot I had done it. Eventually I got it fixed.
Some decoders have a CV setting that "locks" the settings in place. Until you unlock the decoder, I think it even blocks you from reading the CVs. It may be that your decoders were locked, and doing the factory re-set unlocked your decoders.
Not sure if it was a TCS one, but seems to me early on in my DCC days (daze?) I accidently locked a decoder, or locked it and forgot I had done it. Eventually I got it fixed.
Yes, I was aware of that possibility, but it didn’t apply to my problem. In any event, reset did the trick.
A decoder is a falliable object, Electrons zap around in it, things get dislocated. heppens with every brand from time to time. Reset is the obvious solution, until that does NOT work with a particular decoder, no harm, no foul.
There are all kinds of things that can cause this issue. Just reset and don't sweat it.
Mike Lehman
Urbana, IL
Well ...... try resetting. All my decoders but 2 are TCS. Most of them worked well without resetting. Now they all work well.
P.S. If that doesn't work, e-mail Digitrax. If you have different brands that are not working, they cannot realistically blame the decoders, especially if they once worked.
I've checked everything several times and it has not made a difference. The only thing I've not done was to try reseting the decoders. I have a few different brand decoders and it is not isolated to any one brand.
davidmbedardWhich decoders?
TCS DP2X-UK (2 of them), DP2X, T-1 (2 of them) and A4X. But I also had locos with the same model decoders that could be read! I should also mention that after I had reset the decoders and read the CVs, I was able to reset CV 29 to disable DC and stop the surging.
Before I did the resets, TCS did offer to take them back and check them under warranty. Before I went through that hassle, I tried the resets.
I cleaned the programming track and checked the wheels. All the decoders were new. The situation did not correct until I reset the decoders to factory defaults. After I could read the CVs, I set them to what I wanted vs. factory settings (where applicable). I can still read the CVs.
That's a REALLY wierd one, because I have had 0 issues with TCS decoders and they are the only ones I use. I wonder who did what to them before you got them. Every single loco I have that did not come with a sound decoder has a TCS in it, mostly T1.
Even slightly dirty track or wheels can sometimes give a cannot read error. Often, just a shove of a couple of inches down the track is enough to get a good connection.
Try to reset the decoders in question to factory default. I have the Zephyr Extra and some of my decoders could not be read (I also tried the resistor trick). By resetting to factory default, the decoders could then be read. You might have to attempt the reset a few times because the reset didn't always "take" the first time or two. The problem was not restricted to a particular model decoder; also, some decoder models could be read while other units of the same model could not. They are all by TCS.
Another characteristic of the locos with the decoders in question was that the locos would surge a few inches whenever the track was powered. Resetting CV29 to disable DC operation did not work until I was able to reset to factory defaults and then read all the CVs.
P.S. I first inquired of both the decoder manufacturer and Digitrax. Each said the other's product was responsible!
Sure you have the program track connected correctly? The terminals on the back of the Zephyr have PGM A, Ground, and PGM B - so there should be an empty screw connection between the two wires going to the program track.
I currently have the older Zephyr and it will not read decoders when the loco's are placed on the programming track. I've tried several of my loco's and either get the d-nd or the d-na error. I've had this unit for several years and never had any issues, i also tried the resistor trick but that did not work Any ideas?
Thanks, Mark