Lionel locomotive ID different on Bluetooth.

@Brennenr05 posted:

Hello all. This isn't a huge issue but it's odd. I have a brand new in box UP 1943 6-85315 I bought from Eastside trains last year. Always have ran it with legacy via my 990. I wanted to run 2 different trains on both loops so I decided to run this unit with the Bluetooth app. The engine appears as a Tacoma Rail 7002 SD70ACE. Pretty odd. Not the end of the world but just annoying. Can this be addressed or is it stuck like this? It was purchased brand new in box.

Interesting! Do you have one of those funky reader tracks? If so, what does it come up as? If they were produced the same year Lionel could have installed the incorrect chip or software. Haven't run anything using Bluetooth so I've guessed the info.is in the engine?

@BobbyD posted:

Interesting! Do you have one of those funky reader tracks? If so, what does it come up as? If they were produced the same year Lionel could have installed the incorrect chip or software.

I don't have anything else to read the locomotive other than the app. Looks like they were both introduced in 2018 so I assume it's got the incorrect chip in it. Heck, I had no idea it was even that old.

I believe the BT app supplies the locomotive ID, try updating or deleting/reinstalling the BT app.  I had a similar issue where they would just show up as a generic engine, reloading the app got it's mind right.

Let's go over how the Lionchief app ACTUALLY works (or reality- doesn't work).

Each engine has a numeric ID as part of the bluetooth connection. The Lionchief app when adding the engine for the first time is supposed to compare that BT ID with the local info in your phone or tablet from PREVIOUS sessions where you used other bluetooth engines AND- important here- it queried the Lionel server API via the internet.

So, your assumption right now- is the ID number- that then correlates in a database, results in a given incorrect ID (picture, roadname, and other details).

Given this circumstance, I would clear all app data (possibly removing the app and reinstalling) and then knowing the phone or tablet had internet, then attempt to add this engine again. If this time it gets the incorrect ID again, then we have another data point the bluetooth module might be incorrect.

However, another test is just load the fresh Lionchief app onto a new device not previously used before for Lionchief, then add the engine and see what happens.

Again, there are a couple of factors here:

#1 the Lionchief app first uses the local database info of previously added engines on your phone or tablet. It's possible for a duplicate or mistake locally.

#2 only after not finding it locally, does it then try the internet service back to Lionel. If your data plan for a phone or tablet, or say it's not on wifi- it might not actually reach Lionel's API server and update the app data.

@Brennenr05 posted:

I don't have anything else to read the locomotive other than the app. Looks like they were both introduced in 2018 so I assume it's got the incorrect chip in it. Heck, I had no idea it was even that old.

I'll say it again, one instance or session instance of the wrong engine listed in the Lionchief app does NOT mean it has the wrong BT module.

It just means the app is flaky and as a system there are problems with the entire concept of how it works or is "supposed to work".

Until you can prove it is the wrong module with multiple instances of the app on different phones or tablets after fresh reloads, you just encountered a known Lionchief app glitch.

And if it was actually the wrong BT module programming (not being under warranty), it would cost you about $45 ($10 shipping) from Lionel for the part to fix it.

https://www.lionelsupport.com/...-SD70-685315-UP-1943

Before ordering parts I agree with BobbyD having the engine checked on a Legacy system with the Track Sensor to see what it comes up as in the event the OP ever gets Legacy and the LCS Sensor stuff running.  This way you are aware of the full extent of the issue, or if it is just the App or BT module Vernon referenced.

Jim