It would be nice for a tuner to find out which map a controller is using:
Suppose for some odd reason a setup has one map that specifies 4 cylinders and another map that specifies 6, or 8, meaning the user didnt bother setting up another map, or some other finicky reason. What happens when program tries to convert tick count into rpm using a wrong cylinder number? Either an incorrect read out, or if its checking ranges an exception will be thrown.
Second, a tuner program displays a tracker, or call it whatever you will, over a table, 2D or 3D, indicating which cell and its associated value is used, so if user flipped a switch during a runtime session, things wouldnt display right.
Of course ignition table is pulled every time runtime is started, but what if switch is flipped during the session?
Possible solution could be leaving everything as is and accept unstable behavior, or a bit in timing value could be flipped to indicate which map is used, that way program could check for that. Or, when switch is flipped it could prevent state data from being pulled, for five seconds, that way a tuner will automatically disconnect, and then when S is available again, it will automatically connect and retrieve state data.
It will be nice to know which map is used, A or B, 1 or 2.. I personally favor flipping a bit in timing value, it allows for backward compatibility and gives you an idea which map is used, plus you can determine on the fly if switch was flipped.
Now if we can update a desired table via software, i.e. no need to flip the switch, that will be awesome. Flip another bit in U.
)