Also, let me explain something because based on the conversation so far, I'm not sure you have this TMCC and Legacy thing quite down yet.
First understanding that the engine has a program and run switch and we need to program the engine to listen for a specific ID. Typically that ID, I recommend using the first 2 or last 2 digits of the engine number. This way, you can easily pick an engine off the shelf and within 2 tries guess the correct address even if you do not know it. Example engine 4413, you could choose 44, or 13 as your engine ID. So back to programming, again, we have to have the engine in program mode via the switch, and then with the remote, we set an ID hitting the ENG button then the 2 digit number, and then at the bottom of the remote pressing the "SET" button. By doing this, we just sent a command with that ID number plus the set command, while the engine was powered and in program mode. It should respond with a whistle toot or horn after seeing the set command. Now the engine knows to listen for any command with that ID number. You set the engine to run as the last step of that process so that again, it now listens and is ready to run.
However, we are not done yet. OK, so now we just used an ID memory slot in the Legacy system. Now we need to configure what and how the legacy remote and base are going to send commands and use that ID slot. Yes, we can name it and add the engine name and engine number to help us identify and find it later. This is where once you selected the engine ID (Eng+ ID number) then we hit the info key from the previous post and again, we now see 4 tabs of information and settings specific to that engine address in the Legacy system. What I'm saying is, those settings on those tabs- type (example steam, diesel, switcher, crane, passenger, freight, etc), the control type tab sets the flavor of commands sent (CAB, TMCC, R100, Legacy) and last, the railsounds tab.
What I'm getting at is, there are 2 things.
The engine programming process sets the ID it will listen for all future commands.
Then, that same ID slot in the list of engines in the Legacy system- you then have to configure that ID options to match the type of equipment now at that ID to get the correct Icons and settings to get maximum control of that engine. By default, the Legacy engine IDs start off with CAB mode, the lowest feature mode. This is so that during the engine or accessory program sequence, we send the TMCC version of the SET command for compatibility reasons. Example if it defaulted to Legacy mode, a TMCC only engine would never hear the SET command because it was sent a Legacy command and it only reads the TMCC commands. So knowing this, this is why you have to know what the engine or equipment is capable of, and selecting the more advanced control types so that those icons are displayed, and that flavor of command is sent out. Again, if you send an engine a higher command set like Legacy and it's capable of only TMCC style of commands it never follows or acts upon the commands. However, a Legacy item is backwards compatible and does listen to lower commands like TMCC or CAB, however, obviously there are limited commands in that method.
And yes, the sensor track can update some or much of that when working, but as a fundamental, to use and own these engines, to at least be able to choose the correct type, control type, and sounds type for an engine is a skill you need to be able to do. Not everything is going to be capable of auto updating via sensor, and many things may not have the old way with the memory modules either.
Again, the senor track can be a good thing and does make life easier when working, but understanding the Legacy structure, the concept that an ID slot in the database then has associated settings and details, and that how to make those decisions on what is correct for an engine is important to then be able to access the full features of that engine.
