Skip to main content

Which is exactly why all my Bluetooth equipped locomotives also have standard Legacy or TMCC command control, and that's the way they get run.  My layout is fully wired for Legacy/TMCC and DCS, so no need for the stinkin' unreliable Bluetooth link.  It would be nice if it were more reliable, I can see situations where it would be handy to have.  However, I've adjusted to the fact that the current Lionel Bluetooth is simply not ready for prime time.

IMO, in order to be reasonably useful, the Bluetooth link should have a reliable range of at least 25 feet or more.  Oddly, the older LC and LC+ stuff that wasn't using Bluetooth had a much better range using their dedicated remotes or the Universal Remote.  I never looked into exactly what radio technology they were using, but when they shifted to Bluetooth, they should have at least tried to match that range and reliability!

Following this thread and something just came to mind.  I have a thermoWorks bluetooth probe monitor on my smoker, works ok if I set the receiver on the kitchen island, line of sight through the window out to the deck/smoker.  They have another little device, smoke gateway, that connects the probe monitor to the house wifi, 2.5 but that's fine everything else in the house is 5 or ethernet gig.  Bottom line is when the gateway is connected to the bluetooth probe and I'm connected to my network I can be anywhere and on any on my devices and see what the smoker is doing and approximately when I will be enjoying my latest creation.  This gateway seems to be quite reliable, easy to setup, and I have never had a security issue with it.  So why couldn't the same be added to the Lionel bluetooth as an add on, put it in/on the train somewhere.  

@Jim Sandman posted:

Any estimate for the fix for the Andorid App?  Version 2.6.25 dated Dec 1, 2021 finds and initially connects just fine but as soon as you get back to the main page and try to do anything it drops, over and over again.  Apple app & Orange remote works fine.  I personally tried 2 different phones, and 1 Android tablet - all exact same issue.

I'm a service center and multiple engines have came in for repair, but I end up explaining its the LionChief App not the engine that is the issue.

Jim

Did @Dave Olson ever respond to this?  I have the same problem after I accidentally updated the app.  Can't do anything with that new Lionel Verdana Turbine I got.  I feel like if Lionel is going to market a product they should adequately support the product.  I'm suspect that new CAB3 for Android may suffer the same issues.  My feeling is that they need to hire decent Android developers.

Anthony

Last edited by A. Wells
@Jim Sandman posted:

@A. Wells

I don't recall ever seeing a response from Dave O.  Funny thing is I'm working on a Polar Express Bluetooth engine on the work bench currently, and it seems to work fine on this one.   Same 2.6.25 version.     I did upgrade phones at Christmas.  Your mileage may vary.

Jim

This is where I am very concerned with this new way they are heading. There is different hardware and phones running android out there and they need to make there software function on them all properly or they will fail especially making people pay for it. I work in IT for a cell phone company. Companies that rely apps for there the lifesblood should make sure it works flawlessly or quickly fix the bugs.

@Shaun posted:

I found a solution - but it is not what I had hoped for.  Putting it in the gondola wasn't even reliable enough.

Bluetooth fix picture

Shaun, I had to pull this same fix last year at one of our module group setups. I quickly stopped using my BT option after that. After I get my Cab2 back from Lionel I'll just be sticking to that and conventional for a bit.

This is where I am very concerned with this new way they are heading. There is different hardware and phones running android out there and they need to make there software function on them all properly or they will fail especially making people pay for it. I work in IT for a cell phone company. Companies that rely apps for there the lifesblood should make sure it works flawlessly or quickly fix the bugs.

Shawn - ESU gets around this issue by including an Android mobile control unit with their CAB Control.  I just got mine today.  Looking forward to trying it out. Anthony

Ok,

For what it's worth, I have 3 or 4 BT locos that operate fine on a 8 x 12 layout. Recently, I tried running a Legacy SP Atlantic Daylight colors w/ BT in Conventional Mode with a CW80. Ran great with whistle steam effect.

Tried run in BT mode with Android Phone. BT connects to Lionchief App with no whistle confirming connection and no response to any commands

Tried unstalling and reinstalling app. No change. Also, Tried with Apple IPAD, NO CHANGE! NO BT SWITCH ON LOCO OR TENDER! What am I doing wrong!?

Joe Gozzo

Ok,

For what it's worth, I have 3 or 4 BT locos that operate fine on a 8 x 12 layout. Recently, I tried running a Legacy SP Atlantic Daylight colors w/ BT in Conventional Mode with a CW80. Ran great with whistle steam effect.

Tried run in BT mode with Android Phone. BT connects to Lionchief App with no whistle confirming connection and no response to any commands

Tried unstalling and reinstalling app. No change. Also, Tried with Apple IPAD, NO CHANGE! NO BT SWITCH ON LOCO OR TENDER! What am I doing wrong!?

Joe Gozzo

Here is my experience and I hope it helps you. With these modern Bluetooth enabled Legacy engines, especially recent releases like the 20 and 21 cataloged engines, because there are multiple boards inside the engine each with a processor, I have seen them get hung up on the first cold boot of the day. By that I mean if the engine is suddenly powered up, the boards don't all boot and power at the same time and order and so the system goes into a wonky state. The fix is, power down, wait a 3 count, power back up. This causes the system to reboot but more likely now in correct order sequence.  I know it sounds crazy but I have seen this a lot with these recent engines. I have several including the daylight and again, I have absolutely seen this wonky star on first power up after being unpowered- example first time you power it that day. My home setup is a Z4000 with Z4K remote so I soft power on the track and bring up the voltage and wondered if that is part of the cause, but again, I've seen this both at the club and at home. Power cycling the track solves it every time.

Last edited by Vernon Barry

Here is my experience and I hope it helps you. With these modern blueotoh enabled Legacy engines, especially recent releases like the 20 and 21 cataloged engines, because there are multiple boards inside the engine each with a processor, I have seen them get hung up on the first cold boot of th day. By that I mean if the engine is suddenly powered up, the boards don't all boot and power at the same time and order and so the system goes into a wonky state. The fix is, power down, wait a 3 count, power back up. This causes the system to reboot but more likely now in correct order sequence.  I know it sounds crazy but I have seen this a lot with these recent engines. I have several including the daylight and again, I have absolutely seen this wonky star on first power up after being unpowered- example first time you power it that day. My home setup is a Z4000 with Z4K remote so I soft power on the track and bring up the voltage and wondered if that is part of the cause, but again, I've seen this both at the club and at home. Power cycling the track solves it every time.

Thanks for your reply. I will give it a whirl. I am not sure if it matter, however I think my loco was in the 2019 Catalog

Joe Gozzo

Add Reply

Post
This forum is sponsored by Lionel, LLC

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