I’m trying to add an Atlas engine to a recently updated DCS remote. In the old remote, it locked in at 18 when adding an engine. When trying to do so now, it will not seek out 18 but instead has set on 15 or 16. It will start up, with lighting and sounds, but will not move in either direction. I'll delete it and try to re-add with the same results.
Thoughts on what I'm overlooking?
Two things: First, when adding it to the DCS remote, one of the steps requires you to assign the engine a “TMCC Address” number. That number has to correspond to whatever number the engine has been programmed to recognize in TMCC. If that number is still the factory default “1” you have to assign TMCC Address “1” when adding the engine to the DCS remote. When you finish adding the engine, the remote will then show it in the engine list with whatever number is available. That’s just a list of your added engines, whether TMCC or Protosound 2 or 3. That number doesn’t matter to TMCC operation. You just use it to select and call up the engine in the remote. For example in my remote No. 52 is “ATSF B-40-8W #572”. But it’s TMCC address is “72,” the number I reprogrammed it to when I got it. That’s the number it recognizes with a Cab 1.
Second I recall that some EOB equipped TMCC engines don’t respond to the DCS controller if the right speed setting isn’t selected. I think when programmed to the 128 speed step mode these engines don’t respond to the DCS default 32 step throttle setting. You have to use the seed setting soft key to specifically select the 128 mode. Try that if you think the engine is set to the 128 step mode.
By the way it’s not necessary for either the engine or track to be powered to add a TMCC engine to the DCS remote. As long as you assign the correct TMCC address in the remote, it’ll work.
Good luck,
RM
Access to this requires an OGR Forum Supporting Membership
