Trying to add a TMCC to my DCS using WIU. I am using a older 9 pin TIU, but it has got the latest software update on it. Because it’s older TIU I have to use the “Y” 9 pin connector to connect the TMCC base and the WIU. When I use my phone or pad the WIU seems to be communicating with the TMCC base because the lights are flashing when commands are given. Problem is the engine does not respond. The engine is a Legacy but from my understanding it should not make a difference. Unless I am I am not adding it to the list right I am kinda at a lost as to why it’s not responding. Oh yeah I did try different TMCC engines.
Replies sorted oldest to newest
Is your base TMCC or Legacy? For TMCC use the 50-1018 cable; for Legacy use the 50-1032.
I am using a 50-1032, so the TMCC base is Model base 1. So is my problem, I should be using a 50-1018?
Do you have the wire connected from the base to the track common? If the base lights flash it is receiving the command input.
Dan's question is interesting. We have both cables, bought over time, but have never hooked them up.
MTH says your cable is the one to use: 50-1018 TIU/TMCC DB-9 6' Connector Cable (DISCONTINUED - Use Item 50-1032)
"The TIU/TMCC-Legacy Connector Cable is used to connect the DCS Track Interface Unit (TIU) to the Lionel Command Base or Lionel Legacy Command Base for users wishing to use the DCS Remote Control Handheld to run TMCC and/or Legacy equipped locomotives."
That’s interesting, I did not see the 50-1018 being discontinued. I do have the TMCC base wire connected and the base is getting signals from the WIU. It’s just not making it to the engine. So now with what was said about the 50-1018 that’s leaves even more confusion on my part.
What type of track? Do you have a TMCC handheld? Have you tried it with the output connected to one piece of track rather than the entire layout?
It’s atlas track and it does work with the TMCC Handheld. I did try it on a small little oval just to check.
a1hobo posted:It’s atlas track and it does work with the TMCC Handheld. I did try it on a small little oval just to check.
Did you try the DCS on that same test? Did you try the layout with the TMCC Cab1?
Yes, DCS works fine, TMCC CAB 1 works fine. Maybe I am putting in a wrong address when it ask for a address? Just for test sake I have been using 2.
What address is your Lionel engine for TMCC?
DCS will give that a different MTH engine number, though you must use the Lionel address in the setting up a Lionel engine.
Forgive my ignorance here on the address. I do not know. I thought you had to set it between 1-90 when filing in the address box when adding the engine?
What engine address number do you use when you run it with the TMCC handheld?
Well the answer to that is... I do not know. I have just followed the programming directions and it has never asked for it. That’s where when it comes to plugging it in on the DCS I am more or less in the dark being a amateur at this. I just remember reading TMCC engines are I think between 1-90 or there about.
The Lionel engines come from the factory as "1" IIRC. Reprogram them to a new engine number using the Cab1, write it down, use that number when setting them up in DCS. You have to know the TMCC address before the engine will respond. If you can't control them with the Cab1 you won't be able to do so in DCS.
I finally got it! When originally programming using cab1 I was putting in the cab # which was way out of the 1-90 addresses available, but it always worked just fine with the cab1 handheld. So I went back and instead of putting in the cab number, I just put a two digit number in. Then I went to the DCS and put that in for the address. It worked (at least for now anyway) stay tuned you never know.
Thank you all for your help.
Great! My guess is the Cab1 and TMCC were not paying attention to the two extra digits and since you entered it the same every time it worked.
Danr posted:Is your base TMCC or Legacy? For TMCC use the 50-1018 cable; for Legacy use the 50-1032.
FYI the only cable currently available is the 50-1032 cable. It works with both the Legacy base and the TMCC base.
a1hobo posted:I finally got it! When originally programming using cab1 I was putting in the cab # which was way out of the 1-90 addresses available, but it always worked just fine with the cab1 handheld. So I went back and instead of putting in the cab number, I just put a two digit number in. Then I went to the DCS and put that in for the address. It worked (at least for now anyway) stay tuned you never know.
Thank you all for your help.
TMCC/Legacy uses 2 digit addresses. So when you put in 4 digits and pressed set the locomotive was actually set to the last 2 digits you entered. Now that you have the locomotives address correctly entered in the DCS app it will work fine pretty much indefinitely.
This post just saved my bacon! I have a MTH control system. About a year ago I picked up a Lionel Legacy 1L- base station the SER2 and other required cables. While I had it all wired up I did not have any Lionel engines to test it with. Santa surprised me with a very nice Lionel Legacy GP9. I kept trying to add it and while every thing was lit up and flashing the engine would not move! I was thinking I had to go out and and by a new Lionel base or something like that.
So here is my question, I don't have a Lionel remote, I don't have any remotes I just use my phone and I have been very happy with that. IF I get a second Lionel Engine is there any way I can change its address , with out a legacy remote?
P.S.
I may have figured this the answer to my addressing question. I never thought of entering 01 when assigning the address. The manual says uses address 1-99, it dose not say use two digits! I am going to try removing the legacy engine and re-adding using a 2 digit number.
This is why I was drawn to MTH over Lionel, the control system is so much simpler, it simply works. I put my engine on the track open the app and BOOM there it is. No addressing no silly f codes, no hand held remote that I need a Post Grad to understand. As an IT guy I like things that just work or instructions that are easy to follow. I know Lionel is the king to a lot of people but things like this are very discouraging to new people in the hobby.
Well I am a rookie at all this. What I did to run 2 Legacy C420’s with my DCS was when it asked for a address just put in a different number for each loco. It has to be between 1and 90 I think . Someone else may know for sure. They come from the factory with #1 as default address. I believed I address them as 7, 8. You just need to write it down somewhere for future reference. You will need it if you lash them up.
If someone else reads this that knows way more please correct me.
After my test the other night I was able to remove my Leglacy engine and re add as 08.
ITS NOT 1-90. Its 01-90 that little 0 makes all the difference in the world!!!!
The MTH app will show you what address each added engine is so hats off to them. BUT wag of the finger as well because again they show 1, 5, 4 ... WHEN IT SHOULD BE 01, 02, 03....
The need for the zero is an MTH DCS thing, not a TMCC/Legacy thing. It's amusing to hear DCS being described as simpler than TMCC. Not most people's reality and experience over the last couple of decades. When in doubt, you need a TMCC/Legacy remote to trouble shoot the problems with DCS's implementation of TMCC. When something works with the TMCC remote but not with the DCS remote/app, the problem is with your implementation of DCS control, which helps identify the problem, as above. I would not advise folks to buy just the command base, since it's (a) usually used and not under warranty and (b) without the remote you cannot effectively troubleshoot TMCC/DCS problems in many cases.
Thanks for the info on the “0” having to be added. I run both DCS and TMCC. Even though I have finally got a grasp on using DCS to run TMCC, I have found for me that just using the Cab1 remote for TMCC works better. It’s no problem for me to have both systems hooked up.