Skip to main content

I had a very incident happen last night that I thought worth sharing. I have been trying to get an Atlas TMCC diesel locomotive (GP-60 Rio Grande) to run on my layout that runs Legacy and MTH DCS engines. I wasn't having much luck using the Legacy CAB - I couldn't get the start speed slow enough with the 128 step and momentum features. I also couldn't get any brake squealing sound in the no or 32 step EOB feature. And lastly the engine would change direction just by rotating the red thumbwheel to zero. Since the front head light wouldn't go off, I never knew what direction the engine was going to start up in. This is a beautiful locomotive (brand new right out of the box) and you can't find any GP-60's around anymore so I really wanted to get this thing running.

So I tried loading it into my DCS remote and initially I was very pleased with the control and performance. However when I ran the engine into a yard which used the same block of power, all of my other MTH engines started up. Initially I didn't know what was happening so I quickly killed all power. I reset everything and tried it again - I had to go through this yard to get to my turntable. Once again all of my MTH engines started up and kinda went wild. Then I noticed that I couldn't start up any of my MTH engines - I kept getting 'not on track' messages. All of my Legacy engines in the same yard started up and ran just fine.

After some troubleshooting, I found that I had lost all access to the MTH engines I had programmed in the remote. I could see them on the display but none of them would start up. So I ended up having to delete them from the remote and reinstall all of them. I even had to recreate all of my lash ups. Additionally I noticed that I did not have access to the previous addresses I had assigned to these engines - I had to use new ones. I haven't been able to figure out why the previously assigned addresses aren't showing up on my remote - maybe I need to do some sort of reset.

Original Post

Replies sorted oldest to newest

A lot of weird stuff happening there.   I'm not sure but this one might be the craziest . Are you going to try it  again or leave it alone after re-installing everything.  You may have to reset the remote  to get back any lost IDs.

We know some TMCC engines will degrade the DCS signal but...

I'm not sure if a dcs engine sitting on a powered track (dark & silent) will come to life immediately if the dcs signal  is turned off.   (perhaps by the  TMCC engine.) good luck.

 Software version??

Last edited by Gregg

As far as the brake squeal not working. I don't believe EOB had that feature. Early on with using DCS to run TMCC engines. The MTH remote only had 32 speed steps. All Lionel TMCC had 32. EOB with more steps was gaining in popularity at the time and many were using their new DCS remote to run these. TA Studios workaround to the problem of accessing all the steps was for every push of the boost button. It would increase one speed step. Same thing by tapping the brake button except it would decrease one step. 

Almost certainly this was a problem with one or more of the TMCC engines causing the DCS signal to degrade. As far as the rest of it - losing the original DCS ID#'s - that could easily have  also been caused by a degraded DCS signal, if the TMCC engine was powered up and on the tracks when the DCS engines were deleted and subsequently re-added.

At this point I'd suggest a reset of the DCS Remote and re-enteruing all of the DCS engines while the TMCC engine is not powered up or sitting a powered track. Then, assuming all is well, resolve the problem by inserting an RF choke in the wire between the TMCC engine's pickup rollers and its electronics.


DCS Book CoverThis and a whole lot more is all in “The DCS Companion 3rd Edition!"

This book is available from many fine OGR advertisers and forum sponsors, or as an eBook or a printed book at OGR’s web store!

Add Reply

Post
×
×
×
×
Link copied to your clipboard.
×
×