running TMCC And DCS engines with DCS handheld

You need to edit the engine number in the DCS remote for the TMCC engine.  It MUST match the TMCC ID for the engine in question.

I realize you read the DCS book (I assume you mean Barry's book), but are you sure the cable is connected between the TIU and the TMCC base?  DCS sends a signal from the TIU to the TMCC base via a serial cable (I apologize if you already knew this and had set it up, some people think that the DCS talks directly to the TMCC engine, it doesn't).

The other thing could be as another thread recently had, check the address on the tmcc engines and make sure you are using the same address in the DCS hand held when trying to address the engines. My first thought would be to reconnect the cable between the TIU and the TMCC base, then check the engine addresses using the Cab 1 remote and verify that DCS has the same addresses for the engines.

@bigkid posted:

I realize you read the DCS book (I assume you mean Barry's book), but are you sure the cable is connected between the TIU and the TMCC base?  DCS sends a signal from the TIU to the TMCC base via a serial cable (I apologize if you already knew this and had set it up, some people think that the DCS talks directly to the TMCC engine, it doesn't).

Since commands are getting to the Legacy command base, this seems clearly to be an addressing configuration issue with the individual engines and not an issue with the DCS/TMCC cables or configuration.

This is a different, user, John, this guy is saying none of his engines work with the DCS-TMCC hookup, hence my comment. It could still be addressing, but in this case none were working (and this is a different poster). He said the engines work using TMCC Cab1, but don't work at all in DCS.

I won’t go through the whole scenario. But you must be getting to this screen if the info is in the DCS remote.

I’m going to enter Rutland #37.

  Select the letter D in the 2nd line up for Done.

Since your engines are already running with TMCC. Scroll with the thumbwheel and select the TMCC number. In my case 37.

Press the thumbwheel. The next screen will ask which TIU has the TMCC cable plugged into it. I have 3. So I select #2. If you only have one. I’m guessing it will be the only one on the screen.

After you select the TIU it will tell you the engine has been added and will go to your inactive list. Scroll down to your engine and select it using the thumbwheel. That will put it on the active list. Select it again with the thumbwheel and you should be good to go.

The #10 is the slot that it resides in the remote. Nothing to do with the TMCC address. If you have multiple engines to do. You don’t need to have the layout powered up.

@bigkid posted:

This is a different, user, John, this guy is saying none of his engines work with the DCS-TMCC hookup, hence my comment. It could still be addressing, but in this case none were working (and this is a different poster). He said the engines work using TMCC Cab1, but don't work at all in DCS.

Yep, I edited my reply right after I posted it since I saw I was in the wrong thread.  However, my comment still applies, he's seeing activity on the Legacy command base when working on the DCS remote.  That indicates the commands are getting to the Legacy system, the obvious issue would still be TMCC address of the engines don't match what is in the DCS remote.

I took your info and re entered the "ID". I reentered the "ID" in the legacy system using "14" I then took the DCS handheld and went through adding a TMCC engine. I got the screens that you show got to select the TMCC engine from the inactive list it came up  as TMCC #14 I selected it and turned up the thumb wheel it registered on the screen but the engine did not move would not start-up. I did notice the red signal on the legacy unit lit but for an instant it seems to stay lit longer when using the CAB1 if that means anything. I appreciate your help I don't know what to do next. Could it be a TIU error I am using rev 15 which works fine with DCS engines.

You re entered the I.D.  In the Legacy System as 14. Not sure why you needed to do that.  Just to be clear. When you run the engine with Cab 1.You hit  Engine 14 and Aux or Boost and it starts up.
You have mentioned both Cab 1 and Legacy.  Do you use both on the layout ?  I know you can with a cable. Just curious if you are doing this. How are you attaching the cable to the TIU ?

I know they have sold a few different TIU cables over the years for TMCC and another for Legacy.  If you are entering the info. correctly. Just wondering how the components are linked together.

I remember one poster a few years back had this issue with his tmcc-legacy engines not responding to his dcs system. It turns out he was using the "old" TIU/ TMCC connector cable #50-1018. That one doesnt work with the Legacy system, so when he got the newer #50-1032 TIU/TMCC-LEGACY cable, BOOM, everything worked like it's supposed to. Just sayin' make sure u got the correct 50-1032 cable between the TIU Legacy. except for the little tag, they look identical.

@Penn-Pacific posted:

Just sayin' make sure u got the correct 50-1032 cable between the TIU Legacy. except for the little tag, they look identical.

Excellent point!   We sometimes assume all the parts are correct, not always the case.

I am using 50-1032 cable

Dave C,

I re-entered the "ID" to make sure it was correct in both handheld units. I am trying to run TMCC engines on my

DCS Layout I have a legacy unit w/CAB1 but I prefer to use only one handheld.

I'm coming up blank at this point.

I did a quick test.  I can confirm that the flashes on the Legacy base are shorter for serial commands coming from the TIU than from the TMCC/Legacy remotes, so that seems right.