IBus Messages
From HackTheIBus
General Structure
Most ibus message types are device-independent and can be used by all IBus Devices, where they make sense to that device.
Most ibus message types are only used once. Only very rarely will two different IBus Devices use the same message type number. Hence all ibus messages are listed on this page.
Example: many IBus Devices respond to the "Device status request" message. Some exceptions to this rule occur, however the exceptions are not many.
Generally, an odd message is a request, an even message is the reply.
Example 1:
- 0x01: Device status request
- 0x02: Device status ready (responce to 0x01)
Example 2:
- 0x03: "Bus status request"
- 0x04: "Bus status" (response to 0x03)
Example 3:
- 0x79: "Doors/flaps status request"
- 0x7A: "Doors/flaps status" (response to 0x79)
[edit]
List of IBus Messages
Listed in blocks of 16 (0x0F) for clarity.
- 0x01: Device status request
- 0x02: Device status ready
- 0x03: "Bus status request"
- 0x04: "Bus status"
- 0x06: "DIAG read memory"
- 0x07: "DIAG write memory"
- 0x08: "DIAG read coding data"
- 0x09: "DIAG write coding data"
- 0x0C: Vehicle control
- 0x10: "Ignition status request"
- 0x11: Ignition status
- 0x12: "IKE sensor status request"
- 0x13: "IKE sensor status"
- 0x14: "Country coding status request"
- 0x15: Country coding status
- 0x16: "Odometer request"
- 0x17: "Odometer"
- 0x18: Speed/RPM
- 0x19: Temperature
- 0x1A: "IKE text display/Gong"
- 0x1B: "IKE text status"
- 0x1C: "Gong"
- 0x1D: Temperature request
- 0x1F: UTC time and date
- 0x23: Update MID
- 0x24: Update ANZV
- 0x34: DSP Equalizer Button
- 0x38: CD status request
- 0x39: CD status
- 0x40: Set On-Board Computer Data
- 0x41: On-Board Computer Data Request
- 0x48: BMBT buttons
- 0x49: BMBT buttons
- 0x4F: RGB Control
- 0x5A: Lamp state request
- 0x5B: Lamp state
- 0x53: Vehicle data request
- 0x54: Vehicle data status
- 0x5B: Lamp Status
- 0x71: Rain sensor status request
- 0xA0: "DIAG data"
- 0xAA: Navigation Control
(to be continued)
