Skip to main content

Hi Forumites!

I have two CSX engines on my DCS layout and I had one parked and shut down on a siding while I ran the other. When I put my genset in reverse, my GP38 came to life and started running in reverse, spinning its wheels like mad against the bumper, I cut power to the layout and removed the engine. I know one fix for this is to insulate the siding, and I do plan on doing this. Is there another fix I make within the DCS software to avoid what I am assuming is cross-communication? I assume it has something to do with the fact that the engine names are similar as the system couldn't find the genset when I first bought and it was because the GP38 was on the track at the same time. If it helps, I use the DCS app on my Android tablet, I don't have a remote

Thankfully no damage that I can tell, but I would have for something like this to happen again!



Last edited by Ken S
Original Post

Replies sorted oldest to newest

Actually, it's because you have two engines with the same engine number, it has nothing to do with the name of the engine.  This frequently happens if you have more than one remote, the engine can be in different remotes with different numbers.

thank you for pointing me towards the app. I included some screenshots, the most concerning thing is that the runaway engine starts up at high speed. Would it be safer to move the engine to the inactive list when it's not in use?

Thanks for all your support!


Images (3)
  • Screenshot_2020-11-22-15-37-47
  • Screenshot_2020-11-22-15-38-03
  • Screenshot_2020-11-22-15-38-13


    Starting in high speed sounds to me like the engine is going into conventional mode. You can lock the engine into a conventional neutral with the 1 horn 3 bells procedure.  I would also check to make sure your battery is OK or charged by turning off track power and see if the engine sounds play for at least 6 to 7 seconds.

I have experienced that problem, rarely, even though no two of my locos have the same ID.  When I would send a signal to a specific loco, an engine 10 numbers down in the ID would also repond.  Only those two locos, out of my stable of 26, did this, and I cured it by changing the ID of the higher-numbered loco.

A brief short, as from the wheels of a moving train, will also cause this to happen.  Given what you describe, I don't think a conventional reset is needed.

[ Given what you describe, I don't think a conventional reset is needed.]

Not sure you are referring to the 1 horn, 3 bells , ( 2 horn blasts, confirms it took) , I wrote above, but that is to lock the engine in direction (in this case neutral) so the engine doesn't move if it goes into conventional full speed from whatever reason.

1 horn, 5 bells, (2 horn blasts confirms the reset took) is the conventional reset.

I didn't understand where you were going, Joe.  Problem with qny of those sequences is that they have to be done without a DCS signal on track, from trasformer not remote.  This prolongs the procedure when you want to use or kill a loco.

Th situation I experienced was odd:  When I' activate the loco in #23, the loco in #13 sometimes would react.  I exchanged these 2 IDs with 2 from kther locos, and never had the problem again.

A derailment spark causes engines to start up all over the layout

Add Reply

The DCS Forum is sponsored by
OGR Publishing, Inc., 1310 Eastside Centre Ct, Suite 6, Mountain Home, AR 72653
Link copied to your clipboard.