K-line Default ID / address for DCS configuration

When you added that locomotive to your TMCC/Legacy system you gave it an engine number.  Whatever that number was is the number you need to add it to DCS.

Thanks Dan. I just ended up going with the default number from the factory number 1 address and it has fired up and running. Thanks for the prompt reply.

I am noticing the application interface is not as accurate and dialed in with the Lionel TMCC locomotives in comparison to the MTH’s DCS. Speeding up and slowing down does not match what’s displayed in relation to actual performance of the locomotive.

Is anyone else having the same issue?

It’s been a while since I have run K-Line engines. The K-Line cruise has 32, 128 and 256 for speed steps. I believe the default setting is 128. On the soft keys on the DCS remote it will show 32 and 128. I believe if you are in 32 on the remote and the engine is in 128 you will only see 32 steps. In other words. The remote should match up with the engine. The display is only showing speed steps in TMCC. Not SMPH like DCS..

@awp34 posted:

Thanks Dan. I just ended up going with the default number from the factory number 1 address and it has fired up and running. Thanks for the prompt reply.

I am noticing the application interface is not as accurate and dialed in with the Lionel TMCC locomotives in comparison to the MTH’s DCS. Speeding up and slowing down does not match what’s displayed in relation to actual performance of the locomotive.

Is anyone else having the same issue?

Of course it won't match. DCS engines with PS2 or PS3 have a feedback based tachometer on the motor and firmware that that then translates RPM to scale miles per hour. Many MTH PS3 engines are capable as slow as 3 Scale MPH and it maxes out at 120 Scale MPH.

From this topic, here is a linked chart to Lionel speed steps and Scale MPH, however, this may not be accurate for your K-line, just trying to point you at what data is out there. https://ogrforum.com/topic/39722753779307012

@MartyE posted:

Compliments of Mr. Hikel...

Speed Conversion Chart for Legacy, TMCC and DCS

Additional key info specific to those K-line Tank engines.

Your specific engine used K-line Cruise and that module also generates the chuff sound trigger. Just a key thing to know about. https://ogrforum.com/...33#81537088427983433

More information about setting the speed step options in that loco

https://ogrforum.com/...-and-256-speed-steps

@GregM posted:

I'm not sure who was being asked but here are the directions for setting the speed steps on K-Line cruise.

quote:From the K-Line "Steam Locomotive Instruction Sheet"

The number of speed steps can be adjusted by pressing the following sequence on the CAB-1:  DIR, BELL, AUX1, then either 1, 2, or 3.  Each button should be held for one full second.  This sets the number of steps between stopped and full speed.  Press the Bell button again to turn off the bell.

32 STEPS:  DIR, BELL, AUX1, 1  (factory setting)

128 STEPS:  DIR, BELL, AUX1, 2

256 STEPS:  DIR, BELL, AUX1, 3

@awp34 posted:

Thanks Dan. I just ended up going with the default number from the factory number 1 address and it has fired up and running. Thanks for the prompt reply.

I am noticing the application interface is not as accurate and dialed in with the Lionel TMCC locomotives in comparison to the MTH’s DCS. Speeding up and slowing down does not match what’s displayed in relation to actual performance of the locomotive.

Is anyone else having the same issue?

I would not leave the locomotive address as 1 or you will have a problem with your next Lionel locomotive since they will both respond.  You really don’t want to be like George Forman - when you enter “George” everyone responds.

As Vernon said, you will not get the scale miles per hour display.  MTH has patented that so Lionel can’t use it.

Am I able to change the address through the DCS interface?

@awp34 posted:

Am I able to change the address through the DCS interface?

I think no and here is why. In order to change the ID in a TMCC/Legacy engine, you first must on the engine flip the program/run switch to program. Now the engine is listening and ready to program. Then you send the ID and a special command "set" button that causes the engine to then store that ID. You then have to switch the engine back to "run" in order for it to now listen for commands using the new ID.

Fundamentally, the problem has been there was no "set" button or command from DCS.

So based on the lack of being able to send a specific command sequence with a "set" button, that's why you cannot change a TMCC engine ID.

https://ogrforum.com/...ines-with-dcs-issues

Sorry always quoting @gunrunnerjohn but it's a very good answer to the question at hand and he deserves the credit.

From this topic "running-tmcc-engines-with-dcs-issues" https://ogrforum.com/...ines-with-dcs-issues

@gunrunnerjohn posted:

If you're going to run TMCC stuff, I "strongly" recommend you have at least one TMCC remote as well.  There are certain operations that can't be done through the DCS remote.

Actually, the one operation you can do with the DCS is change the TMCC ID.

Although they don't have a separate emulation of the SET key, when you go through the TMCC engine setting procedure on the DCS remote, they send the SET keystroke to properly change the locomotive ID.  Why they didn't have a separate emulation of the SET key so you could use it for stuff like setting stall speeds is a whole other conversation.

So unless I have the DCS remote I cannot change the TMCCID through the app correct?

I honestly never tried the DCS app, but I presume they should have carried that specific sequence over to the app, only way to know is to try it.  Remember, you have to set the TMCC locomotive to PGM before doing the TMCC locomotive add to the DCS system.

@awp34 posted:

So unless I have the DCS remote I cannot change the TMCCID through the app correct?

In your original post you indicated that you have a Legacy controller, so changing the locomotive address should be easy.  The DCS controller, or the app, cannot change a Lionel address. To run Lionel equipment, it mimics Lionel commands via the TIU and serial cable connected to the Lionel base (TMCC or Legacy) which is addressing the engine.

@Danr posted:

The DCS controller, or the app, cannot change a Lionel address.

Yes it can, but it's a bit of a kludge.  You can edit engine address of a TMCC engine, set the PGM/RUN switch to PGM, and it'll change the address.  The issue is sometimes it screws up the engine type, I did it and it changed the address, but the engine had no sound!  I fixed it with the CAB1L.

@gunrunnerjohn posted:

Yes it can, but it's a bit of a kludge.  You can edit engine address of a TMCC engine, set the PGM/RUN switch to PGM, and it'll change the address.  The issue is sometimes it screws up the engine type, I did it and it changed the address, but the engine had no sound!  I fixed it with the CAB1L.

Somewhat unreliable and you still wind up with a Lionel control to fix it.  Yep, kludge.

Wow, I thought I had read MTH left out the Program feature on the app - so there is no way to change the TMCC engine address. I have tried to change the address using the app. The app happily takes engine ID and does nothing with it. I got my engine to respond by using the factory default of 01 for the engine. Worked fine once I figured out which sequence needed to be entered. Its not obvious until you do it right. @Mark Boyce  straightened me out on this.  I just picked up an old (new) cab1 remote so I can change the engine address. Also am curious to see how the engine performs with the remote. 

On the other question - the app is not the greatest for running TMCC engines particularly if you are used to the 7/8 circle which brings the DCS engines from a stop to full speed.  As I remember I had to crank the speedometer in more than a full circle in order to get the engine to move. And remember to run full voltage to the rails to get decent engine performance. I initially was running 14 volts off my Z4000- that was not working well. IMO this is just programming an interface, MTH could have done a way better job of it.

I am not trying to dispute @gunrunnerjohn 's statement above especially with his deep tech knowledge. This is the first I've read its possible although 'Kludgy" and having attempted to do it with the app and having no success, I am obviously missing the magic step.  I would love to know the exact sequence to get this done using the app not the MTH remote. Of course now that I have the CAB1 remote there is no need to attempt this and risk screwing up the engine type.

My test was editing the TMCC engine # after it was in the remote.  I failed in changing the TMCC ID of the engine when adding it, that didn't work.  I know it was supposed to work, so maybe I did something wrong in the process.

The fact that it apparently changed the engine type was a very undesirable side-effect, that would seem to render this technique mostly useless.