0 Members and 1 Guest are viewing this topic.
DecoderPro is just a user interface to a DCC system. Which DCC system (or interface) are you using? Digitrax DB 150 and DCS 100 with many DT400 and 402 forgot what they are calling it Super Chief or ...Sounds like you are able to read the CV values from the decoder and modify them. Correct? Yes I said I could put back factory settingsAre you doing the programming on the main or on programming track (I assume on programming track, since you don't know the locos address)?Programming track and I know the loco address since the lights work front and rear on demandNo matter which system you are using, try using it directly to program the decoder (do not use DecoderPro). The only thing I change with my DT400 is the loco address , then all CV are change using Decoder Pro, I did 3 other locos this afternoon doing so , only this one is "doomed" it all started on address 03 , factory condition then I changed to cab number , all the others were ok Write value of 8 into CV8 (that is the factory reset which you probable already tried through DecoderPro). Then try running it (and/or turning the headlights onor off) on shoer address 03. That's what I did 03 and every other addresses I tried , the headlights are still operating fine , no motor respond but still working fine on pure DC ... But I should add I discovered this morning it's working ( motor and lights ) on address 00 like a loco without a decoder Write the following values into CVs and verify that those values were actually written:CV19 = 0CV29 = 6CV1 = 3Will try to reprogram like that tomorrowNow try run and to control headlights using short address 03. Can you either control the headlights or the motor? Place another (known working) locomotive, addressed for short address 03 alongside of the non-working loco to make sure that address 03 control packets are being sent through the rails.
But I should add I discovered this morning it's working ( motor and lights ) on address 00 like a loco without a decoder
I will reopen it just in case one of the motor brush cap is touching one side of the half frames , maybe ...
This is one of the negatives of using DCC: if you start fooling around with programming, you can easily do just what you did. I don't remember the details but I think that if you send main track programming instructions to address 0 then you are sending that command to all the models with decoders on the track. From what I can see, there is no easy way to magically restore things to normal. You need to reprogram each locomotive separately (hopefully on the programming track). Programming on main should really only be used to change things like motor control parameters (things that need to be tuned dynamically while you are trying to speed match or tune a running locomotive).Since you do use DecoderPro, if you saved the decoder settings for your locomotives, your job of reprogramming all of them will be much easier than doing it from scratch.
You were probably programming on the main to address 00. That's the broadcast address that all NMRA compliant decoders must respond to. They won't actually run when address 00 is selected on a throttle. That's zero stretching and no commands are actually being put in the rails to the 00 address. Decoders will respond to commands sent to address 00 including programming commands. That's how a global stop is sent to the layout.
There is still about 6 locos to reprogram I will try to see on which address they are .
What we are trying to say is that if you send programming commands on the main track to address 00, that is a special broadcast address, and the programming command will be accepted by all the locomotives sitting on the track on your layout. By doing that you are programming all the locos at the same time. So, whatever address you programmed at the time all your locomotives got messed up, that should be the same address programmed into *all* the locomotives.
I would say with about 90% certainty that this is the problem. A short between a motor lead and the correct side of the frame won't cause a problem in DC. It just becomes a parallel path for the current, which may also flow or return through the decoder. The problem only manifests itself in DCC.