Skip to main content

The new Premium version of the DCS Application includes control of both TMCC and Legacy engines. However, some of the hardware requirements have changed from what was required to operate only TMCC engines using the DCS Remote.

Further, there are a few caveats regarding TMCC and Legacy engine operation using MTH's Premium version of the DCS Application that may not be readily apparent. This free, 12-page pdf document includes:

  • Specific hardware and cables required to operate TMCC engines, Legacy engines, or both using MTH's DCS Application, depending upon which command bases are being used and how the operator desires to operate these engines.
  • Wiring diagrams for each of the possible connection configurations.
  • Other caveats and considerations regarding operation of TMCC and Legacy engines using the DCS Application.

You don't have to purchase anything to download this free pdf document. While it includes some information not readily available anywhere else, its use requires no additional support.

You can view and/or download the pdf by clicking here!

Enjoy!

Last edited by Barry Broskowitz
Original Post

Replies sorted oldest to newest

Looks good, Barry. Just one comment:

Connecting DCS to both TMCC and Legacy Command Bases

If the DCS TIU is connected to both the Legacy Command Base and also the TMCC Command Base or the Base-1L Command Base, the MTH cable used is MTH item #50-1007 TIU/TMCC 6’ Connector Ca- ble or MTH item #50-1032 TIU/TMCC-Legacy 6’ Connector Cable, and the Legacy-supplied “Y” cable is also required. The following diagram illustrates how the DCS TIU is connected to a Legacy Command Base, and also a TMCC Command Base or a Base-1L Command Base.

You're correct as far as connecting a TMCC Command base as shown. But one should never connect Base-1L to the Legacy base as shown in the diagram. Connecting a Base-1L to the Legacy base won't work, is not supported and even if it did work, would add no additional functionality. 

Otherwise, thanks for sharing this valuable resource.

I apologize if this question is in the wrong thread, but here goes...

When I wired my layout I did not know about MTH's DCS.  I wired for legacy with a single ground bus around the entire layout and 6 isolated 180 Watt Power House power districts.  Since originally wiring my layout I added LCS WiFi with ACS2s and BPC2s.  

Can I add the DCS hardware without having to rewire my layout?  The ability to fully control Legacy engines and DCS engines with one app is very enticing.  Having to rewire my entire layout to accommodate for DCS would be prohibitive.

thank you

Last edited by T4TT

Can I add the DCS hardware without having to rewire my layout?

The short answer is "yes", however, there are a few things of which you should be aware..

DCS is considerably more forgiving of less than ideal wiring schemes than initially thought. Typically, connecting DCS to an existing layout that isn't wired using a star or home run method will yield satisfactory results, however, there may be some issues or trouble spots.

Keep in mind that. although DCS operation will be determined by several factors, not the least of which is DCS signal strength, DCS will generally work satisfactorily with a signal strength of 7 or greater. If you connect DCS to an existing layout and experience problems, there are several remedies that may be easily applied.

It's extremely rare that a major rewiring is required in order to get DCS to work satisfactorily. For example, when I originally introduced DCS to my previous layout, I obtained very good results although signal strength varied between 6 and 8. This was a layout that was a wiring nightmare: solid core wire as opposed to stranded; 18 gauge wire; and true "spaghetti" wiring. It turned out that my use of lighted bumpers and track blocks were a big part of obtaining good DCS control.

Since 2003, DCS has improved exponentially. The current Rev; L TIU is much better at ensuring viable DCS signal strength and light bulbs, as I had in my bumpers, are almost never required.

I'd encourage you to give it a try. Even if your initial results are less than you'd like, there are several quick fixes that can generally get you where you need to be. Also, I'd encourage you to acquire a copy of either The DCSS Companion 3rd Edition or The DCS WiFi Companion 1st Edition, depending upon how you plan to operate DCS, with a. DCS Remote or the DCS Application. This will answer many questions in advance of adding DCS and will help you to avoid some possible mistakes.


DCS Book CoverEverything that you need to know about DCS is all in MTH’s “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 MTH's web store!

DCS Book Cover

Everything that you need to know about DCS WiFi is all in MTH’s “The DCS WiFi Companion 1st Edition!"

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

Get the free TMCC & Legacy Addendum here!

So, I have a rev I tiu, which has a serial port, but no USB port. Up until now, I ran the wiu into this port.  Now I have acquired a cab 1, which works fine, and the 5018 cable.  Using the cab 1 and cable I was able to add a tmcc engine to my dcs remote.  

The problem is I can only use the serial port for either the cab 1 or the wiu.  I read the attachment, but I don't see any coverage for the older tiu with both the wiu and one of the Lionel devices.  What do I need to make this work? Is there such a thing as a serial port splitter cable, and if so can the tiu handle it?  

I am sure this has been covered somewhere already.  All constructive comments and criticism appreciated.

Thank you,

JHZ563

Last edited by jhz563

We certainly are lucky to have Barry around here to help us with DCS and he is always willing to try and help us as well! Many other forum members are great help to us all as well. Great place to hang out here.

You are also very lucky to have a wife that is good at wiring and that also would really be a great asset. I would say that is pretty rare in the model train hobby and you are very lucky! Get her a dozen roses and be extra nice to her!! 

Last edited by rtr12

This information is nothing short of FANTASTIC !!!! Thanks to Barry and the rest of this well respected group of fans.

I do have a question .is it necessary now to buy the mth Wi fi device any more?

looks like the wiring drawing does not show it ,so getting the premium app and the Lionel wifi plus the legacy base and upgraded to 6.0 TIU and remote will do the job?

thanks a lot to all of You in this great forum

jorge

Thanks Barry,your knowledge is always appreciated .so let me put it this way and you can tell me if it is correct please.

in order for me to run lionel legacy and tmcc trains in my lay out I need:

DCS REMOTE VERSION 6.0

TIU UPDATED TO VERSION 6.0

LIONEL 6-81326

LEGACY COMMAND BASE

MTH WIU

MTH PREMIUM APP

A BUNDLE OF CABLES

LOTS OF MONEY

OF COURSE YOUR NEW BOOK WITH ADDENDUM

AM I right or missing  Something 

thanks a lot Barry,my best regards.

jorge

By now I'm sure a lot of people have bought the SER2 and necessary cables to run Legacy engines in Legacy mode using the MTH premium app. Can anyone, even a single user, say that they have been able to get Legacy diesels to automatically ramp RPM's in response to throttle adjustments using the IPHONE version of the app?  I just can't get RPM ramping to work unless I do so with manual adjustments. All other features like quilling horn work perfectly. Am I the only one with this issue?

GregR posted:

By now I'm sure a lot of people have bought the SER2 and necessary cables to run Legacy engines in Legacy mode using the MTH premium app. Can anyone, even a single user, say that they have been able to get Legacy diesels to automatically ramp RPM's in response to throttle adjustments using the IPHONE version of the app?  I just can't get RPM ramping to work unless I do so with manual adjustments. All other features like quilling horn work perfectly. Am I the only one with this issue?

From @Railsounds from a post in July...  Rudy is Lionel's sound engineer and works with JonZ and is a resident of Dr. ZW's home for Legacy Users.

 

In Legacy mode, the locomotive only ramps RPM when it gets an absolute Legacy run level command. This command is separate and unique from Legacy absolute speed commands. (TMCC gives you a different result because in that mode, the same relative throttle up/down messages cause changes to both speed and sound.)

It would be my guess that the current MTH support for Legacy products sends absolute speed commands, but never sends absolute run level commands. On a related note, I would be interested to know if Legacy steam locomotives change their chuff laboring in the TIU/WIU environment, or if they sound at a fixed labor.

Absolute run level commands and engine laboring commands are sent from the CAB2 and also from from Apps like Lionel iCab and HighRail. Perhaps MTH will add this functionality in a future version--the commands are published in freely available Legacy command protocol document.

Rudy Trubitt

Thanks Marty. I remember that post and it sounds like a good explanation for why this issue is occurring. I was wondering if I'm the only one with this problem. If it's just me, that might explain why MTH hasn't fixed the bug (although they have many other bugs on their to do list which haven't been corrected either). Hopefully a version 2.01 will be released to address these things. 

Okay....following this with interest.  Novice in this area   Hopefully I'm on base here...........?

I have the MTH WIFI installed and working well.

I have a Lionel Sensor track installed with an SER 2.

The 9 pin serial port on the TIU is of course available.  (My TIU is new - Rev L)

However, I have a TPC 400 using the 9 pin serial port on the SER 2.

Therefore I cannot hook up the TIU 9 pin to the SER 2 - 9 pin.

I believe an MTH 50-1032 is recommended between the TIU and the SER 2.

How would I solve this?

Thanks Guys

Dave

 

 

 

Soo Line posted:

Okay....following this with interest.  Novice in this area   Hopefully I'm on base here...........?

I have the MTH WIFI installed and working well.

I have a Lionel Sensor track installed with an SER 2.

The 9 pin serial port on the TIU is of course available.  (My TIU is new - Rev L)

However, I have a TPC 400 using the 9 pin serial port on the SER 2.

Therefore I cannot hook up the TIU 9 pin to the SER 2 - 9 pin.

I believe an MTH 50-1032 is recommended between the TIU and the SER 2.

How would I solve this?

Thanks Guys

Dave

 

 

 

Get a second SER2 for the TIU or use the screw connections for the TPC and 9pin for the TIU.  The SER2 is the least expensive LCS module so that may be the easiest route.  Just add it to the PDI buss.

From the Lionel Manual for the SER2...

You may use either the three screw terminal connector or the DB9 connector
on one SER2. You may use both the DB9 and the comm/output screw terminals
simultaneously. However, if your configuration requires using the SER2's INPUT
screw terminal as well as the output, you cannot simultaneously use the DB9
connector. In this case, add an additional SER2 module to your layout.

Last edited by MartyE

Thanks Marty and Barry.......there are screw connections on the SER 2 so I guess it would not hurt to try that first while waiting for another SER2 and cable.

I would like to know how well you find control of Legacy engines with the MTH Wifi.

My searching does not seem to yield info on this.

Do you have the Legacy Quillable whistle and Labour Up with especially steam?

Thank You

 

Soo Line posted:

Thanks Marty and Barry.......there are screw connections on the SER 2 so I guess it would not hurt to try that first while waiting for another SER2 and cable.

I would like to know how well you find control of Legacy engines with the MTH Wifi.

I've found it very good and intuitive.  It works very well.  MTH did a nice job on it.

My searching does not seem to yield info on this.

Do you have the Legacy Quillable whistle and Labour Up with especially steam?

The whistle does quill.  Most of the Legacy functionality is there.  You can labor up but I believe at this point you have to do this manually as there isn't a "Train Brake" control but Barry can comment better as I have had limited exposure to the app so far as Legacy is concerned.

Thank You

 

 

Last edited by MartyE
IMG_2378MartyE posted:
Soo Line posted:

Thanks Marty and Barry.......there are screw connections on the SER 2 so I guess it would not hurt to try that first while waiting for another SER2 and cable.

I would like to know how well you find control of Legacy engines with the MTH Wifi.

I've found it very good and intuitive.  It works very well.  MTH did a nice job on it.

My searching does not seem to yield info on this.

Do you have the Legacy Quillable whistle and Labour Up with especially steam?

The whistle does quill.  Most of the Legacy functionality is there.  You can labor up but I believe at this point you have to do this manually as there isn't a "Train Brake" control but Barry can comment better as I have had limited exposure to the app so far as Legacy is concerned.

Thank You

 

 

Actually, within engine settings, within the speed control category, there is a labor bias setting that seems to have a similar effect to a train brake in enhancing labor effects on a loco. 

Attachments

Images (1)
  • IMG_2378
Last edited by GregR

At the risk of having missed something blatant.... on page 10 the diagram seems to indicate that the "one wire" for digital signal comes off the AC brick for the 6-81499. I looked through the document for other references to "AC" or the use of "one wire" in section two but came up short. Looking at the pictures of the 6-81499 I don't see any indicator of where I could pull the digital signal off of. (And kinda feel like it would be a bad idea anyways. Can one of you learned gentlemen (and ladies of of course) tell me what I overlooked?

Hi Barry,

I'm about to hook up DCS wifi and replace my TMCC with Legacy.  Also going to add Lionel wifi.  Thanks for your Companions and the addendum, they are always very helpful.  I'm a little confused regarding the AC block in figures A9 and A10 in the addendum.  I couldn't find any reference in the addendum to define AC.  Is that the Legacy power adapter or is it the train transformer ?   Maybe I missed the reference.  Also the "one wire" shown in the figures I presume is the Legacy signal wire coming from the Legacy Command Base post ?  Should the figures show the "one wire" coming from the Legacy Command Base instead of AC ?   Thanks for the help.

shorling posted:

Hi Barry,

I'm about to hook up DCS wifi and replace my TMCC with Legacy.  Also going to add Lionel wifi.  Thanks for your Companions and the addendum, they are always very helpful.  I'm a little confused regarding the AC block in figures A9 and A10 in the addendum.  I couldn't find any reference in the addendum to define AC.  Is that the Legacy power adapter or is it the train transformer ?   Maybe I missed the reference.  Also the "one wire" shown in the figures I presume is the Legacy signal wire coming from the Legacy Command Base post ?  Should the figures show the "one wire" coming from the Legacy Command Base instead of AC ?   Thanks for the help.

The "one wire" should come from the Legacy Base binding post to the outside rail  or common directly.  The AC block looks like it does represent the LCS power supply and has no connection to the track only to the 9 pin base connection and the PDI buss for LCS.  I suspect that the drawing could be in error and the line to the outside rail should be shown going to the Legacy base direct.

Below is how I suspect Barry meant to illustrate page 9.  If Barry finds it in error he can contact me and I'll remove this.  It shows the "one wire" going from the outside rail directly to the Legacy Base binding post. I believe the error came from page 5 possible copy and paste.  This should also be correct for page 10 minus the LCS WiFi module.

DCS

Attachments

Images (1)
  • DCS
Last edited by MartyE
MartyE posted:
shorling posted:

Hi Barry,

I'm about to hook up DCS wifi and replace my TMCC with Legacy.  Also going to add Lionel wifi.  Thanks for your Companions and the addendum, they are always very helpful.  I'm a little confused regarding the AC block in figures A9 and A10 in the addendum.  I couldn't find any reference in the addendum to define AC.  Is that the Legacy power adapter or is it the train transformer ?   Maybe I missed the reference.  Also the "one wire" shown in the figures I presume is the Legacy signal wire coming from the Legacy Command Base post ?  Should the figures show the "one wire" coming from the Legacy Command Base instead of AC ?   Thanks for the help.

The "one wire" should come from the Legacy Base binding post to the outside rail  or common directly.  The AC block looks like it does represent the LCS power supply and has no connection to the track only to the 9 pin base connection and the PDI buss for LCS.  I suspect that the drawing could be in error and the line to the outside rail should be shown going to the Legacy base direct.

Below is how I suspect Barry meant to illustrate page 9.  If Barry finds it in error he can contact me and I'll remove this.  It shows the "one wire" going from the outside rail directly to the Legacy Base binding post. I believe the error came from page 5 possible copy and paste.  This should also be correct for page 10 minus the LCS WiFi module.

DCS

Thanks MartyE !!  Your revised drawing looks more like I would expect with the "One Wire" coming off the Command Base binding post and the LCS AC power adapter feeding the Command Base.  I think Figure A10 also needs similar revision.

Well I received the last piece of the network and am presently running a Legacy diesel via my tablet and MTH WIFI.  Easy to load and basic systems are running fine.  Horn is quillable.  I have not gone into any deeper actions yet.....you have to play with it. 

My first question.....AUX 1 on this system does not start Sequence Control. 

Anyone know how or if this can be done?

Thanks

Dave

Thanks Rudy

I have Legacy and am familiar with the extended press of Aux 1 for Sequence.

While attempting Sequence on the tablet using MTH WIFI.....an extended press of Aux 1 does not activate Sequence.....I've also tried several other wild guesses to no avail.

Maybe Sequence is not available via the MTH WIFI way?

Dave

Understood..............Holding the Aux 1 down for extended time does not activate Sequence.

I tried "tapping" it several times but that does not work either.  All it does is change the screen.....sort of like Aux 1 "off" - Aux 1 "on" and so forth.

We need a manual........................ 

Thanks Guys

 

 

 

 

 

 

 

 

Soo Line posted:

Well I received the last piece of the network and am presently running a Legacy diesel via my tablet and MTH WIFI.  Easy to load and basic systems are running fine.  Horn is quillable.  I have not gone into any deeper actions yet.....you have to play with it. 

My first question.....AUX 1 on this system does not start Sequence Control. 

Anyone know how or if this can be done?

Thanks

Dave

Dave, 

I see you are one of the few people actually running a Legacy diesel using a tablet and the MTH app. Do your diesel RPM's ramp up and down automatically? If this function does work correctly, are you using the Android version of the app? This function does not work on the iphone version of the app.

Greg

Last edited by GregR

Greg

I'm using Android and no, I have to manually ramp up if I choose to.

As well, Sequence does not work and the Braking Sounds do not come on when using the MTH network.

I'm sure there are other missing effects that will come to light as we all "tinker" with this setup.

I hope MTH plans to upgrade the APP.  Maybe Barry will have some news for us after York.

For now.....I really like this method of operating my Legacy engines.  I no longer need to switch from MTH to Lionel remotes!

My next thing to try will be the Lionel TMCC Crane and Boom car.

Most recently I tried the Lionel Tie Jector car and it works nicely using the "smoke" button to activate the disposal of the ties.

Overall at this point.....very pleased I took this route.

Dave

Barry,

Thank You for your help. My Laptop is acting up a little, so I downloaded this file to my work computer and printed the same.

And, just in case, I deleted the file after I e-mailed the same to my Laptop.

Now, I have to wait for the new Printed & E-Mail Version of the 2nd. Edition of the DCS Companion with the

 WiFi Information added.

Wally,

Which system is best for me at this stage?  A TMCC setup or Legacy?

If you don't plan on getting Legacy engines down the road, or if you believe that you'll be happy running Legacy engines as if they were TMCC engines, without the Legacy-only features, then get TMCC. Otherwise, I'd suggest that you purchase a Legacy system. 

I guess I'm a little late to this party, but I don't see how you connect the Lionel Legacy Base and the WIU to share the TIU RS-232 Serial Port?   Nowhere in the Addendum is the WIU even pictured.  What cable or combination of cables do we use for that?

Pictured below is my 14 year collection of cables.  The top one worked well to run TMCC Cab-1 with DCS back in the day.  The bottom cable was supposed to let Cab-1 and Legacy play with DCS but I could never get it to work properly.  I could not run TMCC trains with my DCS remote using the Legacy for TMCC control.

IMG_2006

Attachments

Images (1)
  • IMG_2006
Last edited by Jim Katz

That is the cable pictured at the bottom of my photo.  That was designed to connect CAB-1 and Legacy and the TIU so you could use both the Cab-1 and Legacy remotes.  Problem is the pin out on that is not a direct path to each connector.  Some of the pins are dead ends.    I cannot find any type of three-way DB-9 serial connector on Amazon or in Google.   I could make one, but should I really have to do that?  Do you have a link you could share?

Jim,

Let's hope it works.

As long as you just the Y cable's male end into the TIU's serial port, and the MTH #50-1032 cable into one of the female ports and the WIU's serial to USB cable into the other female port, I can pretty much guarantee that it will work.

That's the same Y cable that I purchased from Amazon and use on my layout to connect my 3 WIUs to their respective TIUs.

" I can pretty much guarantee that it will work."

It didn't.  First off, I connected the 50-1032 cable into my Legacy base, then into the "Y" connector into the DCS TIU, then from the "Y" connector to the WIFI DCS Hub.   The Premium APP works (with MTH engines with many glitches I will discuss later) but as I expected, TMCC Engines on the DCS Remote have no response at all.  They do nothing.  There was one brief moment when my first attempt with a lash-up started to work but died and I have had nothing since.  So I can add another cable to my junk heap.  It worked when made our own cables for TMCC back in 2003.  I should have kept that one I guess.

Is it just possible my TIU cannot do this because it has something wrong with it?

Jim,

So I can add another cable to my junk heap.

Unless the cable is physically defective, the problem is elsewhere.

Questions:

  • Do TMCC engines work with the app?
  • If you remove the Y cable and just connect the 50-1032 cable directly between the TIU and the command base, do TMCC engines work using the remote? If so, the Y cable is defective.
  • Is the 50-1032 connected correctly? If reversed, it will not work. The ends are marked for which end is connected to which device.
  • You say: "The Premium APP works (with MTH engines with many glitches I will discuss later)". What are the glitches?
  • You say: "but as I expected, TMCC Engines on the DCS Remote have no response at all". Why did you expect failure?

If your setup is correctly connected and your assignment of the command base is to the correct TIU #, the system works just fine.

Last edited by Barry Broskowitz
  • Do TMCC engines work with the app?No.
  • If you remove the Y cable and just connect the 50-1032 cable directly between the TIU and the command base, do TMCC engines work using the remote? If so, the Y cable is defective. No they don't work.
  • Is the 50-1032 connected correctly? If reversed, it will not work. Connected properly.
  • You say: "The Premium APP works (with MTH engines with many glitches I will discuss later)". What are the glitches?
  • 1. Running an MTH lashup at startup the (9 dot) page is gone.  Tap increase 4 or 5 times and speed goes to 100% throttle.
  • 2.  Startup my 0-6-0 steam engine. Bell works, whistle does not.  Go to (9 dot) page, Forward whistle works, reverse whistle works.  Go back to Cab page, whistle does not work.
  • 3. I will have more once I get my TMCC problem resolved.  There are definitely others.
  • You say: "but as I expected, TMCC Engines on the DCS Remote have no response at all". Why did you expect failure? Previous experience of never having gotten TMCC to work on DCS since 2004.  Back when we made our own cables and used CAB-1 Base, it worked.  You saw the picture of my two previously purchased official MTH cables.
Last edited by Jim Katz

Jim,

First, the "9 dots" screen is the Soft Keys screen.

Second, if the TMCC engines don't work with either the app or the remote, regardless of whether the Y cable is connected, one of the following is wrong:

  1. The 50-1032 cable is defective.
  2. The command base is defective.
  3. The cable is installed reversed.
  4. The TMCC ID# of each TMCC engine is not the same as what you told the DCS Remote or the app they are.
  5. The TIU number that you provided when you added each TMCC engine is not the actual number of the TIU.

If you have a Cab-1 remote and you can operate your TMCC engines with it, then you can rule out it item number 2.

Running an MTH lashup at startup the (9 dot) page is gone.

If your Soft Keys screen shows no soft keys for lashups, you aren't using the latest version of the DCS App.You should update to the latest version.

Tap increase 4 or 5 times and speed goes to 100% throttle.

You have the TMCC engines set up with a speed control mode of "Default", which is the equivalent of the "big red wheel". Change it to TMCC 32.

2.  Startup my 0-6-0 steam engine. Bell works, whistle does not.  Go to (9 dot) page, Forward whistle works, reverse whistle works.  Go back to Cab page, whistle does not work.

 

 
That's most likely because you need to turn on the the Playable Whistle in the engine's Soft Keys screen. Also, there's a bug in the process that was corrected in the latest release of the app, which I believe that you do not have.
Before you do anything else, make sure that you update your DCS App to the latest version. For iOS, that's 2.0.2. For Android, it should be either that or higher.

Jim,

First, the "9 dots" screen is the Soft Keys screen.

Second, if the TMCC engines don't work with either the app or the remote, regardless of whether the Y cable is connected, one of the following is wrong:

  1. The 50-1032 cable is defective.
  2. The command base is defective.
  3. The cable is installed reversed.
  4. The TMCC ID# of each TMCC engine is not the same as what you told the DCS Remote or the app they are.
  5. The TIU number that you provided when you added each TMCC engine is not the actual number of the TIU.

If you have a Cab-1 remote and you can operate your TMCC engines with it, then you can rule out it item number 2.

Running an MTH lashup at startup the (9 dot) page is gone.

If your Soft Keys screen shows no soft keys for lashups, you aren't using the latest version of the DCS App.You should update to the latest version.

Tap increase 4 or 5 times and speed goes to 100% throttle.

You have the TMCC engines set up with a speed control mode of "Default", which is the equivalent of the "big red wheel". Change it to TMCC 32.

2.  Startup my 0-6-0 steam engine. Bell works, whistle does not.  Go to (9 dot) page, Forward whistle works, reverse whistle works.  Go back to Cab page, whistle does not work.

 

 
That's most likely because you need to turn on the the Playable Whistle in the engine's Soft Keys screen. Also, there's a bug in the process that was corrected in the latest release of the app, which I believe that you do not have.
Before you do anything else, make sure that you update your DCS App to the latest version. For iOS, that's 2.0.2. For Android, it should be either that or higher.
  1. The 50-1032 cable is defective. Really I could be that unlucky.
  2. The command base is defective. No, works for everything else.
  3. The cable is installed reversed. No, tried it both ways incase they labelled it wrong.
  4. The TMCC ID# of each TMCC engine is not the same as what you told the DCS Remote or the app they are.  No, my ID's work with the TMCC remote.
  5. The TIU number that you provided when you added each TMCC engine is not the actual number of the TIU.  TIU gives one blink red light on power up.  Remote Addr =1, TMCC ADDR = 59, remote says "TIU = 2 ADDED"  That's pretty strange.  How do I change that to say TIU = 1 ADDED?  

Jim,

TIU gives one blink red light on power up.  Remote Addr =1, TMCC ADDR = 59, remote says "TIU = 2 ADDED"  That's pretty strange.  How do I change that to say TIU = 1 ADDED?  

You need to be more specific. Where does this happen? In the remote or the app? Exactly what sequence of events causes exactly what messages?

Are you using the very latest DCS App release? Based on your previous information, I don't think so. If you aren't you must update your DCS App before we go any further.

To learn the DCS App version, tap: More.../App Settings and look at "VERSION"

Sorry for the confusion.  I am not using the app for this setup test.  That will come later, but I am at version 2.02.  I am using only the dcs remote to add a tmcc engine that has been set as I’d no. 59.  I have run the loco with tmcc and it works fine.  After adding it in the dcs remote I am hoping that it runs with dcs.  But when adding it in dcs I get the message on the remote that said TIU = 2 ADDED as the last step in the ADD TMCC ENGINE dialog.   Both the tiu and the remote are address 1.   Shouldn’t  the remote say  TIU =1 ADDED? 

Last edited by Jim Katz

Jim,

It states "TIU #1" because, whether you know it or not, that's what you told it. Make sure that TIU #1 is highlighted when you press the thumbwheel.

You should now delete your TMCC engines and re-add them to the remote, being sure to enter each engine's TMCC ID# correctly and to always ensure that you enter the command bases's location as TIU #1.

I got the remote and tiu both set as number 1.   Added the TMCC engine and still get no response.   Keep in mind, I have a Cab 1 and a Legacy Base, I have two complete DCS setups.  So I can test every combination of remote, TIU, and TMCC Base.  The only item I don't have a duplicate of is the 50-1032 cable.   And you're going to say;  "that must prove it's a bad cable".   Well that may be.  I guess I'll just have to buy another one...some day.

 

 

"always ensure that you enter the command bases's location as TIU #1"

That is not an option you get to enter if you have only one TIU.  I can't say if that's true if you have more than one, but I know if you have only one, you have no choice.   If it comes up as TIU 2 and you only have one and your TIU is TIU 1 (one blink),  you must do a complete factory reset of the TIU and the Remote before attempting to add the TMCC engine to make sure the engine is added to the TIU number you have.

Now I have to order a new cable.  Not saying it's going to work, but to have a chance that is my last hope.   As I said early on in this thread, my lash-up did start with the cable I have and then died and would never start again.  I feel the cable blew itself out with the very first start, which is where things usually go bad with electrical stuff.  I don't know what's in the little black box in the cable.  Probably a diode or a resistor.  When we made our own cables back in the day, I think is was a 1N4001 diode.

Last edited by Jim Katz

Jim,

Now I have to order a new cable.

Are you certain that your cable is #50-1032 and not an earlier model? Also, make sure that only one Lionel Command Base is powered on and connected to the outsider rails. Which command base are you using, TMCC or Legacy? I believe that you have both. Regardless, it's very unlikely that your cable is defective. Before you go any further, see below.

Yes, if you only have one TIU, then DCS selects the TIU for you. However, it will always select the TIU that the remote has in its TIU list.

Proceed as follows:

  • First, power-on the TIU and count how many times the red LED blinks before coming on steady.
  • Second, do a READ on the remote and copy down exactly what it reports
  • Third, press Menu/System/TIU Setup/Edit TIU Address
  • There will be a list of TIUs consisting of all TIUs of which the remote is aware.
  • If all is well, the only TIU in the list will be the same number TIU as the one that is selected when you add the TMCC engine.
  • Press ENG. to leave the Menu system without changing anything>

Questions:

  • How many times did the TIU blink before coming on steady?
  • What did the READ report?
  • What TIUs were in the list of TIUs in the remote that you saw when you followed the process above?
  • What DCS version is in the TIU and in the remote? The remote tells you its version on power-on. To learn the TIU's version, press: Menu/System/TIU Setup/TIU Version
Last edited by Barry Broskowitz

I am able to run TMCC with the DCS remote using the Cab-1 TMCC Base and the original cable that MTH released in 2004.   This proves that my hardware and software is configured properly.  That 2004 cable will not work with the Legacy base at all.  The cable I purchased last week will not work at all.   That tells me that I may have a bad TIU/TMCC Legacy Cable.

I am going to order a replacement 50-1032 cable.

Jim,

I am able to run TMCC with the DCS remote using the Cab-1 TMCC Base and the original cable that MTH released in 2004.   This proves that my hardware and software is configured properly.

Then why did you tell us that you had problems running TMCC in the first place?

That 2004 cable will not work with the Legacy base at all. 

If that's a #50-1018hat's completely correct. That cable will only work with a TMCC base, not with a Legacy Base.

That tells me that I may have a bad TIU/TMCC Legacy Cable.

No, that's not necessarily the case. Further, you still haven't determined why you say that your TIU is #1 and that the DCS Remote thinks that the command base is attached to TIU #2.

I am going to order a replacement 50-1032 cable.

I'd be surprised if the current #50-1032 cable is at all defective. If it is, it would be the first one of which I've ever heard, let alone encountered.

Regardless, I'm done attempting to assist you. You insist on not answering my questions or performing the troubleshooting steps that I've provided. I also suspect that there may be one or more things that you haven't disclosed that could get to the root cause of the issues that you've described.I can't help you if you won't provide the required information and I've grown tired of trying to help you if you won't help me, to help you.

I sincerely wish you the best of luck with your DCS. However, please take your issues to a different thread rather than hijacking this one.

Last edited by Barry Broskowitz

"Then why did you tell us that you had problems running TMCC in the first place?"

I told you this because it did not work with the 50-1032 using the Legacy Base.

"That 2004 cable will not work with the Legacy base at all."

Ok, but the 50-1032 cable does not work with the Legacy Base either.

"Regardless, I'm done attempting to assist you. "

I sincerely thank you for the help you have provided.  It has stimulated in me a strong desire to try and solve this problem using techniques I have used through out my life to deal with problems as they are encountered.   

Sometimes life gets in the way of trains.  Today was an especially crowded day for me and sometimes taking a step back is a good thing.  I have been a member of this forum on and off for only 15 years and while I have not written a bunch of pamphlets on the subject, I have used trains, and over the years helped many others in this space to use them as well.  If you wish to no longer communicate with me I am sorry you feel that way and I apologize for whatever you perceive I have done to cause you to feel this way.  

Sincerely,

Jim

 

Barry, 

I am not one to jump in and add to a fire, but if everyone will leave you alone, the Next Generation of the DCS Companion Book will

 have all of the answers that everyone will be waiting for.

Besides, I cannot wait to increase your retirement fund(s) by buying two of the newest DCS Companion Books, and the

 on-line version as well.

So, with this said, I leave You and Your Wife and Family with a wish for a Very Happy Thanksgiving.

God Speed, Michael 'Santa Fe Mike' Sudlow

Add Reply

Post
The DCS Forum is sponsored by

OGR Publishing, Inc., 1310 Eastside Centre Ct, Suite 6, Mountain Home, AR 72653
800-980-OGRR (6477)
www.ogaugerr.com

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