What file stores Engine info stored in DCS remote for PS3.0 Engines

@Steam Loco Greg posted:

All, I have an engine that displays the incorrect engine # for a PS 3.0 Steam Locomotive.  Planning on reflashing the code for it.  Is the engine info displayed in the remote stored in the Sound file, Chain file or some other location.  Thanks for everyones insight!

Greg

Problem is, it's multiple places.

The engine in the serial number data file has the displayed name and road number. You the consumer cannot change this using consumer loader. When you add an engine, the remote gets the name info during the 2 way data exchange and then names that engine in the remote. Key point- your remote is where your list of engines is stored- not in the TIU. However, you have the option to rename any engine you want. That does it ONLY in that remote as it's just changing the displayed name VS the previous info it got from the engine during the initial add engine.

As with anything- there is an exception to this. upgrade kits- both PS2 and PS3 have a special chain file set that allows renaming to ALSO get saved in the engine.  It's an added feature specific to the upgrade kits. So an upgrade board is blank with no name, when you first add it, and then you edit the name in the remote and that changes both the name displayed in the remote and because of the special firmware- the board saves it too. The problem is, a reset to factory defaults of the board- also wipes this edited name.

Again, bottom line, with consumer loader, you cannot change the name in a factory board. You can in the remote or app edit the displayed name, but that is just in that remote or that instance of the app. The engine- when added to another remote- will send it's original data and display that name in any new add engine sequence.

The reason I wanted to highlight that your naming and engine database is stored in the remote in MTH DCS or in the app when using the wifi DCS, is that is a fundamental difference to the Lionel system

Lionel legacy stores the database in the base. The CAB2 connects to the base and that is how it displays the info on the screen, it's coming from the base.

That's why between a home and club layout- you bring your engine to someone else's layout if it's MTH bring your DCS remote because the info is stored in the remote. If it is a Lionel engine, bringing your CAB2 to a new location and thus legacy base- your info is in your base at home not with you in the remote.

FWIW, this was my motivation to work through my dealer to get a service account and service tech. All I wanted to do was be able to properly rename a used board transplanted into a new engine as an upgrade or repair given the lack of boards and upgrade kits.

Vernon,

Thanks for the insight on this I very much appreciate it.  I was aware of the engine data stored in the remote for DCS and in the base for Legacy (have used the computer to organize the database a time or 2).  I can understand your motivation and I may be similarly motivated.  I have spent over 25 years of my career in the auto industry as a powertrain/propulsion calibrator and have done a lot of programming and reflashes.  I should seek out doing some tech work as yourself.

Thanks again for the excellent description!

Greg