I just re-assembled one loop of track after cannibalizing everything for the Christmas layout. This includes moving my dcs tiu which while older has been relatively problem free, I have a 750 w brick hooked up to the aux input, an a 1000 w brick hooked up to the variable input 1., variable out put one to the track. I do have the fixed and variable inputs jumpered together, although thats unrelated to this issue.
So I wanted to run a longer train, (ie I was too lazy to find a home for everything on the tracks. I planned to use an existing two unit lashup in my dcs controller. I fired up each engine individually to make sure they were responding. Then I scrolled to the inactive engines, found the appropriate existing lashup, selected it, and then started that lash up. The engine noise came back up on the rear engine like it usually does. (I believe I am one rev being in my software updates.) When I gave a forward command the front engine responded and the rear engine did not. Of course this resulted in a string line derailment.
Thinking there was something wrong with the diesel trying to push on the rear I took that engine off, grabbed another steamer that had previously been lashed with the lead steamer. Following a similar method, again everything was fine until I told the lashup to roll forward. Once again the lead engine started rolling, but the rear engine did not.
Am I missing something here, or is my dcs acting screwy? If its the dcs acting screwy can someone remind me how to reset it? Does resetting the dcs mean I will have to re program all my engines into the remote?
- yes I have the dcs companion. No I don't know where it is right now.
- I have run these locos in these configurations before and never had this issue.
- The tiu is a rev I