FREE - TMCC & Legacy Information for MTH's Premium DCS Application!!

That's why I said NOT. The TMCC "Y". 

Barry provided this link in another thread. 

Amazon Y

Thanks Marty.   Found it all on Amazon.   Let's hope it works.

Jim

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.

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.

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.

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? 

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.

Jim,

Did you do as I asked?

"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.

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

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'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.

"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

Mike,

Thank you and a Happy Thanksgiving to you and your family, as well!  

Startup my 0-6-0 steam engine using the DCS App on my iPhone.  Bell works, whistle does not. Go to Soft Keys page, Forward whistle works (two toots), reverse whistle (three toots) works.  Go back to Cab page, whistle does not work.  Bell works, not whistle, the button does not press when touched.

The answer I got was: 

If you will look at the sequence of screen shots from my iOS phone app, which is and always has been at version 2.02,  I can't find anything about a "Playable Whistle".  Can anyone identify that for me.    Thanks.

Jim,

Actually, my remembering was off. The Playable Whistle is on the Engine Settings screen.

That's a mystery because my screen does not have that.  All I have after SMOKE is RESET.  Nothing about Playable Whistle and I am at version 2.02.  Regards, Jim.

Jim,

Since you didn't provide an MTH engine number, I have no way of knowing if the engine has a playable whistle or if it does not.

Does the engine entry in the remote have soft key SPW? If it does, that would indicate that it has a playable whistle.

Negative.  No "SPW" in the DCS remote for that engine.   Has an "STW" and bunch of others but not that.

Jim,

No "SPW" in the DCS remote for that engine.

In that case, there is no playable whistle setting in the app for that engine and that's no the problem. Further, I assume that the whistle works from the DCS Remote. 

You could try doing the following:

• Factory reset the engine from the app. That should also delete it from the app.
• Re-add the engine to the app.
• Try using the whistle.

Success!   I feel pretty dumb about this one.  On a steam engine in the app, you have to pull the whistle lanyard down.   I was just pushing it.   It works just fine when you swipe it down.  I'm having a colonoscopy tomorrow so you won't be able to say I'm full of it.  (:-))

Thanks again for your help.
Jim.

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

Just received a new 50-1032 cable from Amazon today.  Connected it up to the Legacy Base and the Y cable splitter into the TIU and the WiFi Interface.   Everything is working perfectly for TMCC Lash-ups and Locos.   I have to admit the cable is the last place I would have looked as I stated earlier in this thread, but there it is.  The first cable is just dead as a door nail and cost refunded by Winkie's Toy and Hobby. 

Jim.

Hi! I'm sorry if this has been answered already. I have a simple oval Fastrack layout and would like to add some Command Control switches. I just added a WIU and TIU to my command base with 50-1032 cable. Will the DCS app control Fastrack Command switches?

Thank You, Rick

It has been answered.  Here is the link.  You will need an MTH AIU, accessory interface unit.

Fast Track with MTH AIU

Jim Katz posted:

It has been answered.  Here is the link.  You will need an MTH AIU, accessory interface unit.

Fast Track with MTH AIU

Thank you for your reply Jim, but that's not exactly what i want to do. I want to use switches with Command Control built in and use the DCS app to operate them just as it would operate a TMCC engine. Maybe what I'm trying to do isn't possible and you must use an AIU?

Rick,

Maybe what I'm trying to do isn't possible and you must use an AIU?

At the present time, the DCS App's abilities in regards to TMCC and Legacy, are limited to engine and lashup control. In the future this may change, however, I personally don't believe that it will.

If you want to use switch tracks and accessories with the app, they must be connected to AIUs. However, the advantage to doing so is to be able to use MTH's powerful Routes and Scenes functionality with any devices so connected.

Barry Broskowitz posted:

Rick,

Maybe what I'm trying to do isn't possible and you must use an AIU?

At the present time, the DCS App's abilities in regards to TMCC and Legacy, are limited to engine and lashup control. In the future this may change, however, I personally don't believe that it will.

If you want to use switch tracks and accessories with the app, they must be connected to AIUs. However, the advantage to doing so is to be able to use MTH's powerful Routes and Scenes functionality with any devices so connected.

OK good to know. I have a simple floor layout and I'm trying to have as few wires as possible going to it . I guess I still could operate the Command switches with my Cab1 if I don't go the AIU route (no pun intended). Right?

I just got my TIU and WiFi units a few days ago and I'm lovin it. I decided to skip the DCS remote because I think the app is the future. I got stuck on one thing which was moving a TMCC engine out of inactive to active which you cleared up in your addendum. Thank you for that!

Rick,

I got stuck on one thing which was moving a TMCC engine out of inactive to active which you cleared up in your addendum.

Actually, I believe that's within The DCS WiFi Companion 1st Edition, itself, rather than in the TMCC/Legacy addendum.

Barry,

Another thing I noticed is that on the Variable Screen, the speed goes from 0 to 5.0 with nothing in between and visa versa. Is it just me or is that just the way it is. I have the very latest DCS hardware and software but I have the original Cab-1 and Command Base if that means anything.

It's a little problematic for my PS-1 and other conventional powered units.

Thanks again Barry

Rick

Rick,

on the Variable Screen, the speed goes from 0 to 5.0 with nothing in between and visa versa. Is it just me or is that just the way it is.

Neither.

Go to the track settings screen and adjust the Minimum Voltage and Maximum Voltage for the track's variable channel.

This and a whole lot more 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!

Barry Broskowitz posted:

Rick,

on the Variable Screen, the speed goes from 0 to 5.0 with nothing in between and visa versa. Is it just me or is that just the way it is.

Neither.

Go to the track settings screen and adjust the Minimum Voltage and Maximum Voltage for the track's variable channel.

---

Barry,

The Minimum is set at 0.0 Maximum at 22.0 Just for fun I saved both. Made no difference the throttle goes from 0 to 5.0 like before. Maybe the minimum needs to be raised? But then there will be no slow conventional speed.

For the record, my power is a PH-1 PowerHouse 135.

Rick

And even on the Minimum settings screen it starts at 0 then the next setting is 5.0 then 5.5 then 6.0 and so on. Are they all like that?

Rick,

I can affirm that that's how it works. The DCS Remote allows setting starting TIU Track voltage at 1.0 volts.

I'll report it to MTH as a bug.