0 Members and 1 Guest are viewing this topic.
Another thought.. If you did the Zephyr Command to Empire Booster to getaround the short issue.... The Zepher could power the Ops Mode Programming track only, and the Booster runs the rest of the layout. (Turn off the booster when programming)~Ian
You wont notice the short issue until you get 2-3 sound locos in the same booster at the same time.. (and maybe Digitrax finally fixed the issue) and I think its unique to the Super Chief.. So you may not notice it with a Zephyr or Empire Builder. If your doing Ops mode Programming.. your programming the locomotive with live track power ...sound loco would be running the whole time... like your running the layout (not through the programming track outputs on the Zephyr).The biggest issue with Ops mode.. Is you need to know the address.. since your directing the commands to Loco #### (likely 03 until you change the #).. so if you have multiple 03s on the layout, the all get programmed (which is why the on off switch is important)..But the program track booster may be the better option.. for address recovery and things like that.~Ian~Ian
If you haven't noticed it, dont worry about it.. ~Ian
Here is a good description and history of what I'm referring to.https://tonystrains.com/news/a-brief-history-in-dcc-inrush-current/With new decoders and DCC systems.. it may be fixed.. ~Ian
The initial shorts may be equipment/track related, but the failure to restore power was likely system related..~Ian
Fortunately that has not once occurred on the RGS...unless I just jinxed myself.
The main challenge of Digitrax sound programming is the amount of Power that Digitrax sends to the programming track is not enough to 'wakeup' the sound decoder. (You would need a Programming Track Booster to solve this.. )
Increased power output to the programming track makes it easier to program sound decoders and decoders with "keep alive" circuitry. On the DCS50 and DCS51 this is accompished using "Blast Mode". On the DCS52, DCS210 and DCS240, this is standard behavior on the programming track.