Lionel S1 Bluetooth connectivity issue on Christmas Morning......Help!

Do you notice anything binding or sticking when you run it in conventional?….does all seem well?…..if so, try a reset at start over again,….try running it on the remote first, if all seems well, then try the app again…..

Pat

binding from a thrown tire

loose motor mount or driveshaft

maybe even something wrapping around the driveshaft!

just guessing here about your question....

I had a similar issue with a new BNSF ES44C, I ended up turning the engine over and gently turning each wheel set to get any binding issues resolved. 

@Former Member posted:

I had a similar issue with a new BNSF ES44C, I ended up turning the engine over and gently turning each wheel set to get any binding issues resolved.

It would be very unlikely that one could move the wheels on a locomotive when powered off.

@harmonyards posted:

Do you notice anything binding or sticking when you run it in conventional?….does all seem well?…..if so, try a reset at start over again,….try running it on the remote first, if all seems well, then try the app again…..

Pat

Super smooth operation in conventional…no binding whatsoever…only issue is forward movement with app or controller…reverse is fine..scratching my head on this one.

@Engineer-Joe posted:

binding from a thrown tire

loose motor mount or driveshaft

maybe even something wrapping around the driveshaft!

just guessing here about your question....

Would have guessed that too but as reported originally it runs super smooth in conventional.

@Former Member posted:

I had a similar issue with a new BNSF ES44C, I ended up turning the engine over and gently turning each wheel set to get any binding issues resolved.

So yeah did that too…runs super smoothly in conventional though so doesn’t explain Bluetooth problem.

@rplst8 posted:

It would be very unlikely that one could move the wheels on a locomotive when powered off.

Normally with most no…but this one (and a few others from Lionel) no problem.

@Maverick0394, Ok, would it be possible to place a picture of your track, your power supply, and your remotes, and the locomotive? This would help in diagnosing the issue. Another Question, is your power supply plugged directly into the wall outlet, not an extension cord? I’ve been told to plug in power supplies directly into a grounded outlet. Thank you for posting the question, we all learn from others.
PS… please fill out the OGR Forum profile so we would have the state you live in, there could be someone local that could help you….Thank You.
Happy New Year…

@leapinlarry posted:

Another Question, is your power supply plugged directly into the wall outlet, not an extension cord? I’ve been told to plug in power supplies directly into a grounded outlet.

The OP is having trouble with Bluetooth. This has nothing to do with the grounding issues with the TMCC or Legacy command base.

@rplst8 posted:

The OP is having trouble with Bluetooth. This has nothing to do with the grounding issues with the TMCC or Legacy command base.

Really?..

Pat

@leapinlarry posted:

@Maverick0394, Ok, would it be possible to place a picture of your track, your power supply, and your remotes, and the locomotive? This would help in diagnosing the issue. Another Question, is your power supply plugged directly into the wall outlet, not an extension cord? I’ve been told to plug in power supplies directly into a grounded outlet. Thank you for posting the question, we all learn from others.
PS… please fill out the OGR Forum profile so we would have the state you live in, there could be someone local that could help you….Thank You.
Happy New Year…

Yes, power supply is plugged directly into wall. I have tried running the engine on multiple tracks that I have, different power supplies, different remotes.

@Maverick0394 posted:

Yes, power supply is plugged directly into wall. I have tried running the engine on multiple tracks that I have, different power supplies, different remotes.

This sounds like you’ve exhausted all avenues of exploration at this point. If this is still covered under warranty, it may be time to go back to Lionel.

Pat

@harmonyards posted:

Really?..

Pat

Pat, he said he was using the universal controller/remote in the original post. It’s my understanding that it uses Bluetooth to communicate with Legacy engines.

Am I wrong?

@rplst8 posted:

Pat, he said he was using the universal controller/remote in the original post. It’s my understanding that it uses Bluetooth to communicate with Legacy engines.

Am I wrong?

No, I thought he was using a Cab 2, …..I swore I saw cab2 somewhere but I was wrong,….he is using the universal remote , which indeed is Bluetooth,……irregardless, it sounds like it’s a trip back to Lionel.

Pat

Try updating firmware on the universal remote if possible.  Lionel added this capability to fix bugs and expand the types of engines that can be controlled. 

@Long Hair posted:

Try updating firmware on the universal remote if possible.  Lionel added this capability to fix bugs and expand the types of engines that can be controlled.

Will do...trying that now...thanks, will follow up.

@Maverick0394 posted:

Will do...trying that now...thanks, will follow up.

@Long Hair posted:

Try updating firmware on the universal remote if possible.  Lionel added this capability to fix bugs and expand the types of engines that can be controlled.

No dice..same result but thanks

So all signs point to a defective engine.  Your behavior is very programmatic and predictable - it consistently moves 3-4 inches and then blows the whistle.  It seems like some sort of a test mode rather than a real defect.

@Maverick0394 posted:

I received a Lionel Legacy Pennsylvania S1 6-4-4-6 Model #213040 and am having a very strange issue in Bluetooth mode. When powered up it does respond to both the Universal controller and Lionchief app through Bluetooth. When I try to engage the engine to go backwards no problem...when I then try to go forward it starts initially then stops after maybe moving 3-4 inches at which point the whistle blows, when I try again, same issue but it does go backwards with no problem with both the remote and the app. Before anyone asks I did try to run in conventional mode and NO ISSUES, seems strange to me. I do not have legacy control to test it in that mode. Why would an engine in bluetooth mode run fine backwards with no signal issue but continuously stop while trying to go forward?? And run fine in conventional going forward?

Anyone have any ideas? Merry Christmas everyone by the way.

Perhaps Mr. @gunrunnerjohn has some idea or has encountered this phenomenon before. I know you’re not a big fan of Bluetooth but given the facts I posted, any ideas my friend? Thanks so much for your time in advance.