Example : 0x0F8B00
Meaning : A unique hexadecimal number chosen by the OEM to be ID for this controller type.
Example : 0
Meaning : The number of times the firmware on the controller has been re-programmed since the initial programming/manufacturing date.
Example : 13
Meaning : The number of Firmware Sections in the programming memory of this Controller. The scan will normally list all the sections with their Type, Firmware ID and Firmware version.
Example : 0x3039 (12345)
Meaning : A hexadecimal number (optionally followed by the decimal equivalent on K24 chassis bikes) chosen by the OEM to be the ID for this fault condition.
Example : 2
Meaning : The number of times this fault code has occurred without being cleared.
Example : 40
Meaning : The number of times the controller has to be power cycled without the fault re-occurring before it will be cleared automatically. 0 implies it will never be cleared.
Example : 2
Meaning : The index count of the group of environmental variables that were recorded when last this fault code occurred.
Example : 5254235
Meaning : A timestamp generated from an internal counter on the bike counting the number of seconds since the counter has wrapped. The counter is started during manufacturing and wraps roughly every 194 days.
Meaning : Unavailable responses generally means that the controller did not respond to a command or responded with a NACK (Negative Acknowledge). Invalid or Unknown responses could either not be resolved to a logical response or found in a corresponding reference lookup table. ??? is sometimes reported when the response is shorter than expected and the meaning could thus not be calculated or resolved at the required offset address.
