I just received a brand new Lionel J3 Hudson and after running it on TMCC I attempted to link it to my DCS system with no luck.    I have five other TMCC engines working on my DCS system with no problems.  I used a programming track as advised so the issue of other engines on the track is not a problem.  If anyone has an answer for me I would greatly appreciate the help.

Bob R

Original Post

The only thing you need to turn on is the remote. The layout itself can be off. Doesn’t matter if the engine itself is on the layout.  I hadn’t done this for a while so I just tried it.

Turn on the DCS remote.

Hit Menu, Engine Setup, Add engine, Add TMCC Engine.

Now give it a name and hit the D on the end when done.

Now enter the TMCC address assigned to the engine.

Now select the TIU number the TMCC base is plugged into. Count the blinks on the TIU when you turn it on if your not sure.

The engine will come up on your inactive list.

Move it to the active list. Select it and hit start up.

When I once was running everything with the DCS remote. I entered all my TMCC engines watching TV.

Exactly what happens when you try the engine?

Dave has nicely covered the process. I’ll emphasize to Make sure the TMCC address number is the same as the TMCC engine ID number. If it’s still the default “1,” that’s the TMCC address for adding it to DCS. If you have changed the TMCC ID number then the “TMCC address” in the DCS remote should be that number. Say you changed the TMCC ID to “5”. AssignTMCC Address 5 when adding it to the DCS remote. (By the way I think Legacy engines still default to a factory assigned ID of 1 for TMCC operation). 

Unless something is different about Legacy engines, you don’t need a programming track to add a TMCC equipped engine to DCS. In fact the engine doesn’t even need to be powered up. TMCC engines don’t actually participate in the process of adding to the DCS remote. All you are doing when adding a TMCC engine is configuring the remote to send commands to the assigned TMCC  ID number. As Dave says, you can add them while watching TV. In another state....

I have a dim memory of some EOB engines not responding to the DCS remote in 132 speed step mode unless that mode was specifically selected with the DCS throttle  if it’s not responding to speed commands check that too.

RM

Thank you for the replies but neither of the options offered so far work.  I have been using the MTH and Lionel systems for at least 15 years and while the programming that you recommend may work on the older engines, it does not on appear to work on the Legacy engine.  I may have older software versions in both the DCS and the TMCC controllers so I will see what I can find out.  I will post the answer whether someone offers up a solution or I figure it out.  I really appreciate what has been sent so far and thank you for the process you have used. 

 

Bob Rimm

As they asked, when you changed the engine number using the TMCC equipment, that is the engine number that you used when entering it into the DCS system correct? (I don't recall being able to update the TMCC software at all) As asked, what does the DCS controller show after you've entered the engine? 

That is correct.  I tried using the same number in the DCS system to no avail.  In the past I found that an older Lionel worked with number that was different that the TMCC number.  I have tried to program it both ways, one that is the same and one that is different.  What bothers me is that the problem only involves the new Legacy engine.  I was hoping that I am not the first to run into this issue but I am still trying to resolve the problem.  If I do, I will document how I solved it and Post it on this forum. I do appreciate any input I can get.

 

Thanks!

Bob

BOB RIMM 030717 posted:

That is correct.  I tried using the same number in the DCS system to no avail.  In the past I found that an older Lionel worked with number that was different that the TMCC number.  I have tried to program it both ways, one that is the same and one that is different.  What bothers me is that the problem only involves the new Legacy engine.  I was hoping that I am not the first to run into this issue but I am still trying to resolve the problem.  If I do, I will document how I solved it and Post it on this forum. I do appreciate any input I can get.

 

Thanks!

Bob

You aren't confusing the MTH DCS handheld engine list number for the Lionel TMCC/Legacy engine number are you?   

The number that I am referring to is the digital "Address" that is set when you program an engine to be controlled by the DCS or TMCC controller.   The "List Number" is simply the list location that it is displayed on the controller screen and is meaning less in the digital control side.  

Bob

 

 

Well if the locomotive works from the TMCC Cab-1 it should work from the DCS remote, provided the TMCC address in the DCS remote is correct. All the remote does for TMCC locomotives is send a command to the TIU, which in turn sends a command to the TMCC base through the cable connected to the TIU. 

Santa Fe, All the Way

Santa Fe, All the Way:   I agree with you!  The problem is all the more daunting to me as I am a retired Electronics Engineer.  I understand that it doesn't make sense that it's not working but I've invested several hours trying different ways to link the engine to the DCS system.  I believe that it could be "operator malfunction" but without a way to look at the data stream it has be be done with the "trial and error" process.  I'll be attempting to program it again later today and pass on the results.

Thanks

Bob R.

 

 

BOB RIMM 030717 posted:

Santa Fe, All the Way:   I agree with you!  The problem is all the more daunting to me as I am a retired Electronics Engineer.  I understand that it doesn't make sense that it's not working but I've invested several hours trying different ways to link the engine to the DCS system.  I believe that it could be "operator malfunction" but without a way to look at the data stream it has be be done with the "trial and error" process.  I'll be attempting to program it again later today and pass on the results.

Thanks

Bob R.

 

 

Try programming the locomotive to engine number 5 (or whatever you have free) with the Cab-1. See if works with the Cab-1. If so go to edit engine in the DCS remote, edit TMCC engine, edit address, change address number to 5. Once it's saved try running it with the DCS remote. Either running the engine with the DCS remote or Cab-1 it's still responding to the TMCC base.

My guess is there is an issue with the address for that particular locomotive in the DCS remote, especially since the other TMCC locomotives work fine with the DCS remote.

I run all my DCS and TMCC locomotives from the DCS remote. I'm often running a DCS and TMCC locomotive at the same time so it just makes my life easier. 

Santa Fe, All the Way

BOB RIMM 030717 posted:

The number that I am referring to is the digital "Address" that is set when you program an engine to be controlled by the DCS or TMCC controller.   The "List Number" is simply the list location that it is displayed on the controller screen and is meaning less in the digital control side.  

Bob

Since the DCS system is just sending a command to the Lionel base, and you say the engines all respond flawlessly to the Lionel commands using the Lionel hand held, there has to be an issue with this particular engine in the DCS remote. The engine doesn't know if the command is coming from a Cab1, Cab1-L Cab2, DCS remote, or laptop software to the base. Curious, what Lionel engine address number are you using for it?

 Can you try this. You have other TMCC engines working fine with the DCS remote. You mentioned your new engine runs fine using Cab 1 in command. Remove one of your TMCC engines from the layout. Give your new engine the same TMCC ID as the one you removed. Confirm it runs with the new ID with Cab 1. Now try running your new engine with the DCS remote using the name and info from the engine you removed. All DCS knows is that it is sending the TMCC signal to a certain engine #.  The name you give it in the remote is just for your convenience. The fact that it’s a Legacy engine doesn’t make any difference. Mine work with both the DCS remote and wifi.

To all of those that gave me advice on my Hudson issue, I want to say thank You!  After reviewing all of my notes and then trying Dave C's approach, I finally got it to work.  For whatever reason my information instructed me to turn the program switch to "on" when I programmed the DCS system into the Hudson.  My DCS manual is a very early edition and my DCS remote also advised me to turn on the programming switch.  My testing the process that Dave recommended  and not activating the program switch, the DCS now can control the Hudson with no problems. Thanks again for all who helped!

Bob R

Add Reply

Post
OGR Publishing, Inc., 1310 Eastside Centre Ct, Suite 6, Mountain Home, AR 72653
330-757-3020

www.ogaugerr.com
×
×
×
×
×