Unable to change engine ID on New LioneChief+2.0 Dockside (2032030)

Wow Ed, you've been having lousy luck with your engines lately.  Will it run under name #51?  If so, I'd leave it.  I have a few with the same engine number, and they all do run fine...

I have.  That’s what I’ll do. Thanks.

Ed,

    I do not have any Lionchief, Lioncheif+, or Lionchief+2.0 equipment so I am guessing here. I do have a couple Legacy engines that also run on Bluetooth using the LCS apt. From what I can tell changing the engine ID number only effects running the engines in Legacy or TMCC. When you use the apt the engine is identified in the apt so if the engine’s cab # is 151 the apt recognizes the engine as 151 not 51 or 15 which you may of used when setting up the engine in Legacy/TMCC.

    Please do not take this as fact it is just the way I understand the systems. Good luck with your new engine.

JohnB

JohnB, thanks for your comment.  I'll explore that angle, however, the engine's Cab # is "76."  What I remember happening is while it was running fine with assigned ID# 76, when I opened my LCS app to run it, the roster showed  #51  assigned to my trackmobile.  That  is when it would no longer respond to 76 but when I reassigned the Dockside to "51", viola, it woke up. What is puzzling is why it will not permit a reprogramming to a different ID.  Well.  as Ted said...go with it.  I do know some folks  have multiple engines with the same ID (Eric of Ericstrains mentioned he does).  I've not run it in BlueTooth mode...that's next...should be interesting.

Ed,

    What command system are you using to change the engine’s ID # TMCC Cab 1 or Legacy Cab 2? Changing iD #s is basically the same for both, Put the Program/Run switch in program, enter the ID# 76 in your case, press the set button and you will hear the whistle blow if done correctly. When running you engine using TMCC or Legacy the engine will respond to ID# 76.

     When you use the LCS apt you are using Bluetooth. The engine should show as #76 Bethlehem Steel 0-6-0T. If you did assign the legacy ID as say engine # 7 and if you have Legacy or TMCC active the LCS system will operate the engine as #76 and the LCS Bluetooth apt will override the Legacy or TMCC system. When you mentioned engine # 51 I thought that maybe one of the other 0-6-0T engines that was cataloged was that number but the closest one was # 15 which was a BEDT switcher.

    Again good luck with your engine.

JohnB

You do realize that the CAB2 defaults to Legacy protocol, and if you try to change using that setting, it'll ignore you.  I just experienced that when I was re-addressing my new docsiders, and then noticed I was at the Legacy setting.  Change it to TMCC or R100 (the dockside uses back-EMF cruise), and see if the setting works.

Johns, B and Gunrunner, thank you.  I was so used to running in Legacy mode and the few TMCC engines I have I programmed years ago and forgot.  Once I set the mode TMCC it reprogrammed to #76.  Lesson relearned. Thanks again.  It's a sweet little runner....

@Quarter Gauger 48 posted:

Wow Ed, you've been having lousy luck with your engines lately.  Will it run under name #51?  If so, I'd leave it.  I have a few with the same engine number, and they all do run fine...

Ted, as with so much in life...turns out to be "operator error"   See the exchanbe with JohnB and Gunrunnerjohn. 

Try the R100 protocol, it'll give you 100 speed steps instead of 32 speed steps.  Makes things run a little smoother.

Thank John, will do.

@ToledoEd posted:

Johns, B and Gunrunner, thank you.  I was so used to running in Legacy mode and the few TMCC engines I have I programmed years ago and forgot.  Once I set the mode TMCC it reprogrammed to #76.  Lesson relearned. Thanks again.  It's a sweet little runner....

Ed,,

    Good news congratulations and continued luck with your engine.

JohnB

Gents, I changed it to RS100. It ran OK.  Then I shut it down...but after a few minutes I noticed smoke was still wafting out. I looked down the stack and sure enough the element was red hot.  I shut off smoke via the switch...still glows.   I can't imagine there is some system setting that would tell it to keep that element hot even with the switch off.   It seems to me if it's still on even with the switch in the off position there is nothing I can do and it's back to Lionel.  Is that your advice as well? Thanks.  I think this engine hates me.

The smoke is a bit odd, you have to poke the - sign multiple times to truly turn the smoke off.  The smoke switch should kill the smoke, that's wrong and sounds like it may be a problem.  There's no reason the smoke should continue to function with that switch off.

Thanks John. You confirmed my assessment, it should not be on with switch off. Ha. I sound like Cpt. Obvious. I’m waiting for a response from the vendor.

Ed, I was just about to say Congratulations on the correct settings. and finally you can enjoy the engine.  Shame it has to go back'... but that's best' I think'...

@ToledoEd posted:

Gents, I changed it to RS100. It ran OK.  Then I shut it down...but after a few minutes I noticed smoke was still wafting out. I looked down the stack and sure enough the element was red hot.  I shut off smoke via the switch...still glows.   I can't imagine there is some system setting that would tell it to keep that element hot even with the switch off.   It seems to me if it's still on even with the switch in the off position there is nothing I can do and it's back to Lionel.  Is that your advice as well? Thanks.  I think this engine hates me.

Weird I had a old conventional one that did that. It smoked GREAT for 5 minutes I saw red down the stack and shut it off and never to bee seen from again. Bummer this one didn’t shut off. Obviously no thermistors in these smoke units 😜

First thing this morning, well, first thing after the first cup'o java, with smoke switch off...turned on track power and within a few seconds smoke and the heating element glowed red. Back to Lionel.  Thanks for your help fellas.