Infotainment CAN messages
26 message IDs from the infotainment CAN of one A4 B6 with RNS-E and phone kit, captured in 2016 by janssuuh: cluster text, speed, rpm, time, buttons, ring and keep-alive messages. Frames as captured, meanings not yet checked.
These are the CAN identifiers one person found on the infotainment CAN of their own A4 B6, with an example frame for each and what they took it to mean. They are the starting point for the infotainment bus, not a checked reference.
How the entries are written (bytes counted from 0, hex, byte order, evidence levels) is on CAN messages. The ring and keep-alive messages (0x428, 0x436, 0x43A, 0x6C4, 0x6C5) are explained on Network management, and the text messages (0x261 to 0x267, 0x627, 0x6C0, 0x6C1) on Writing text to the cluster display.
Messages
Section titled “Messages”0x261 FIS text, line 1 Meaning: interpreted
Source: "First line of content on FIS". Sender not stated.
Example frames
54 45 53 54 20 20 20 20as text:“TEST ”"TEST" padded with four spaces (0x20)
Signals
| Signal | Position | Byte order | Encoding | Values | Evidence |
|---|---|---|---|---|---|
| Text Byte order does not apply: each byte is one character. Read from the example "TEST ". | bytes 0, 1, 2, 3, 4, 5, 6, 7 | unknown | 8 characters, one byte each, in the cluster's character set (FIS character table); first character in byte 0 | interpreted |
0x263 FIS text, line 2 Meaning: interpreted
Source: "Second line of content on FIS". Sender not stated.
Example frames
54 45 53 54 20 20 20 20as text:“TEST ”"TEST" padded with four spaces (0x20)
Signals
| Signal | Position | Byte order | Encoding | Values | Evidence |
|---|---|---|---|---|---|
| Text Byte order does not apply: each byte is one character. Read from the example "TEST ". | bytes 0, 1, 2, 3, 4, 5, 6, 7 | unknown | 8 characters, one byte each, in the cluster's character set (FIS character table); first character in byte 0 | interpreted |
0x265 FIS text, line 1 (high priority) Meaning: interpreted
Source: "First line of content on FIS (high priority / used by phone)". The source says the phone uses it; it does not say which module sends it.
Example frames
54 45 53 54 20 20 20 20as text:“TEST ”"TEST" padded with four spaces (0x20)
Signals
| Signal | Position | Byte order | Encoding | Values | Evidence |
|---|---|---|---|---|---|
| Text Byte order does not apply: each byte is one character. Read from the example "TEST ". | bytes 0, 1, 2, 3, 4, 5, 6, 7 | unknown | 8 characters, one byte each, in the cluster's character set (FIS character table); first character in byte 0 | interpreted |
0x267 FIS text, line 2 (high priority) Meaning: interpreted
Source: "Second line of content on FIS (high priority / used by phone)". The source says the phone uses it; it does not say which module sends it.
Example frames
54 45 53 54 20 20 20 20as text:“TEST ”"TEST" padded with four spaces (0x20)
Signals
| Signal | Position | Byte order | Encoding | Values | Evidence |
|---|---|---|---|---|---|
| Text Byte order does not apply: each byte is one character. Read from the example "TEST ". | bytes 0, 1, 2, 3, 4, 5, 6, 7 | unknown | 8 characters, one byte each, in the cluster's character set (FIS character table); first character in byte 0 | interpreted |
0x271 Ignition key position Meaning: interpreted
Source: "Position of the ignition key; 10 means key out of ignition". Other values not given.
Example frames
10key out of the ignition
Signals
| Signal | Position | Byte order | Encoding | Values | Evidence |
|---|---|---|---|---|---|
| Key position | byte 0 | – | Only one value is given in the source |
| interpreted |
0x351 Road speed and direction Meaning: interpreted
Bytes 3, 6 and 7 are not described in the source.
Example frames
00 6E 10 AE 09 76 75 05forwards, 21 km/h (the source's own decoding)
Signals
| Signal | Position | Byte order | Encoding | Values | Evidence |
|---|---|---|---|---|---|
| Direction | byte 0 | – | Source: "00 ahead / 01 backwards" |
| interpreted |
| Road speed | bytes 1, 2 | little-endian (LSB first) | Swap byte 1 and byte 2, read as hex, decimal / 200 = km/h (0x106E = 4206, / 200 ≈ 21 km/h)raw × 0.005 = km/h | interpreted | |
| Wheel pulses Printed in red in the original post. A search-engine summary of that post says red marks IDs whose meaning is not exactly known; the post itself could not be retrieved to confirm this. Byte order not stated in the source. | bytes 4, 5 | unknown | Source: "Byte 4 and 5 wheel pulse; calculate distance travelled". How to calculate is not given. | interpreted |
0x353 Engine speed and coolant temperature Meaning: interpreted
Bytes 0, 4 and 5 are not described in the source.
Example frames
20 F5 0C 65 80 6F829 rpm (the source's own decoding)
Signals
| Signal | Position | Byte order | Encoding | Values | Evidence |
|---|---|---|---|---|---|
| Engine speed | bytes 1, 2 | little-endian (LSB first) | Swap byte 1 and byte 2, read as hex, decimal / 4 = rpm (0x0CF5 = 3317, / 4 ≈ 829 rpm)raw × 0.25 = rpm | interpreted | |
| Coolant temperature The source gives no example value. In the example frame byte 3 is 0x65 = 101, which by this rule is 101 °F ≈ 38 °C. To verify on the car. | byte 3 | – | Degrees Fahrenheit, according to the source: (x − 32) / 1.8 = °C | interpreted |
0x428 Ring message: cluster looks for the RNS-E Meaning: interpreted
Source: "Ring-ID, KI looks for Rns-e. Reply with: 436 [1A] (on phone), or 428 [08] 01 00 00 00 00" (KI = instrument cluster; "zoekt" = looks for, "of" = or). The replies are quoted as printed. Interpretation: the bracketed value may be byte 0 of the reply, which would make "428 [08] 01 00 00 00 00" a 6-byte frame; the source does not say, and the brackets could also mark something else, such as a length or a node number. See the network management page. Sender: the wording "KI looks for Rns-e" reads as the cluster (J285) sending this frame; no capture establishes it, so the sender is left unknown.
Example frames
16 01 00 00 00 00 00 00
Signals
No signals worked out yet.
0x436 Ring message (two frames in the source) Meaning: interpreted
Source, first row: "Ring-ID, KI is looking for phone. Reply with: 43A [08] 01 00 00 00 00". Second row, a 6-byte frame on the same ID: "16 02 80 00 00 00", "Rns-e first sign on the ring". The data file holds one length per ID, so the 6-byte frame is kept here in the notes. Sender not established for either frame: the wording "KI is looking for phone" reads as the cluster sending the first frame, and "Rns-e first sign" as the RNS-E sending the second. See the network management page.
Example frames
1A 01 00 00 00 00 00 00"Ring-ID, KI is looking for phone"
Signals
No signals worked out yet.
0x43A Ring message: phone's first announcement Meaning: interpreted
Source: "Phone initial notification on the ring". See the network management page. Sender: the wording reads as the phone kit sending this frame; no capture establishes it, so the sender is left unknown.
Example frames
1A 02 80 00 00 00
Signals
No signals worked out yet.
0x461 RNS-E buttons Meaning: interpreted
Source: "Up button Rns-e", "Down button Rns-e" and so on, one row per button. Bytes 0 to 2 are 37 30 01 in every frame and are not described. The source names the buttons as RNS-E buttons but does not say which module sends the frame. The frames with no button pressed are not given.
Example frames
37 30 01 40 00 00Up37 30 01 80 00 00Down37 30 01 00 40 01Left37 30 01 00 20 01Right37 30 01 01 00 00Previous37 30 01 02 00 00Next37 30 01 00 10 00Select (big round knob)37 30 01 00 02 00Return37 30 01 00 01 00Setup
Signals
| Signal | Position | Byte order | Encoding | Values | Evidence |
|---|---|---|---|---|---|
| Button (byte 3) | byte 3 | – | One value per button, from the example frames; 0x00 in the frames of the byte-4 buttons |
| interpreted |
| Button (byte 4) | byte 4 | – | One value per button, from the example frames; 0x00 in the frames of the byte-3 buttons |
| interpreted |
| Byte 5 | byte 5 | – | Not described in the source; values from the example frames |
| interpreted |
0x5C0 Multifunction steering wheel buttons Meaning: interpreted
Source: "Passive state multifunction steering wheel", "Left button multifunction steering wheel" and so on. Sender not stated.
Example frames
39 00passive state (no button)39 02Left39 03Right39 04Up39 05Down3A 1CMode
Signals
| Signal | Position | Byte order | Encoding | Values | Evidence |
|---|---|---|---|---|---|
| Byte 0 | byte 0 | – | Not described in the source; values from the example frames |
| interpreted |
| Button | byte 1 | – | One value per button, from the example frames |
| interpreted |
0x602 TV/video option in the RNS-E Meaning: interpreted
Source: "Activates the TV/Video option in your RNS-E". Which byte does what is not described. Sender not stated.
Example frames
89 12 30 00 00 00 00 00
Signals
No signals worked out yet.
0x604 Unknown, constant Meaning: interpreted
Printed in red in the original post. A search-engine summary of that post says red marks IDs whose meaning is not exactly known; the post itself could not be retrieved to confirm this. Source: "Always stays the same". The frame itself was captured as shown.
Example frames
81 00 00 00 00 00 00 00
Signals
No signals worked out yet.
0x621 Door and engine lid; counter while the ignition is off Meaning: interpreted
Printed in red in the original post. A search-engine summary of that post says red marks IDs whose meaning is not exactly known; the post itself could not be retrieved to confirm this. Both rows for this ID are red. The frame itself was captured as shown. "Engine lid" is the machine translation; it probably means the bonnet.
Example frames
10 49 3C
Signals
| Signal | Position | Byte order | Encoding | Values | Evidence |
|---|---|---|---|---|---|
| Driver's door and engine lid Printed in red in the original post. A search-engine summary of that post says red marks IDs whose meaning is not exactly known; the post itself could not be retrieved to confirm this. | byte 0 | – | Source: "Byte 0 responds to driver's door and engine lid". Values not given. | interpreted | |
| Counter Printed in red in the original post. A search-engine summary of that post says red marks IDs whose meaning is not exactly known; the post itself could not be retrieved to confirm this. "Contact" is Dutch for the ignition, so this probably means the value rises while the ignition is off. What it counts and how fast is not stated. | bytes 1, 2 | little-endian (LSB first) | Source: "Byte 1 and 2 increases when contact is passive. LSB, MSB". In the example 0x3C49 = 15433. | interpreted |
0x623 Time and date Meaning: interpreted
Source: "Time / Date: xx HH MM SS DD MM YY YY". The source does not say the bytes are BCD; that the hex digits read directly as the decimal time and date is an interpretation of the example. Sender not stated.
Example frames
00 14 25 54 12 03 20 16read as BCD (interpretation): 14:25:54, 12 March 2016
Signals
| Signal | Position | Byte order | Encoding | Values | Evidence |
|---|---|---|---|---|---|
| Byte 0 | byte 0 | – | "xx" in the source: not described | interpreted | |
| Hours | byte 1 | – | HH (source). BCD reading (interpretation): 0x14 = 14 | interpreted | |
| Minutes | byte 2 | – | MM (source). BCD reading (interpretation): 0x25 = 25 | interpreted | |
| Seconds | byte 3 | – | SS (source). BCD reading (interpretation): 0x54 = 54 | interpreted | |
| Day | byte 4 | – | DD (source). BCD reading (interpretation): 0x12 = 12 | interpreted | |
| Month | byte 5 | – | MM (source). BCD reading (interpretation): 0x03 = 3 | interpreted | |
| Year Byte order not stated in the source; big-endian follows from the BCD reading of the example. | bytes 6, 7 | big-endian (MSB first) | YY YY (source). BCD reading (interpretation): 0x20 0x16 = 2016 | interpreted |
0x627 Driver's door and FIS status Meaning: interpreted
Printed in red in the original post. A search-engine summary of that post says red marks IDs whose meaning is not exactly known; the post itself could not be retrieved to confirm this. All three rows for this ID are red. The frame itself was captured as shown. Machine-translation terms: "tm" = t/m (up to and including), "standaard" = default.
Example frames
80 3A 3A 3A 3A 28 28 28printed in lower case in the source: 80 3a 3a 3a 3a 28 28 28
Signals
| Signal | Position | Byte order | Encoding | Values | Evidence |
|---|---|---|---|---|---|
| Driver's door Printed in red in the original post. A search-engine summary of that post says red marks IDs whose meaning is not exactly known; the post itself could not be retrieved to confirm this. The source says only "byte 0"; that it is the first (high) hex digit is read from the next row, which calls the FIS status the second digit. | byte 0, bits 4–7 | – | Source: "Byte 0 responds to driver's door, 0 closed / 8 open" |
| interpreted |
| FIS screen status Printed in red in the original post. A search-engine summary of that post says red marks IDs whose meaning is not exactly known; the post itself could not be retrieved to confirm this. | byte 0, bits 0–3 | – | Source: "Byte 0 (2nd digit) responds to status FIS screen: 0 default, 1 registration FIS, 4 is P (gear)" |
| interpreted |
| FIS activity Printed in red in the original post. A search-engine summary of that post says red marks IDs whose meaning is not exactly known; the post itself could not be retrieved to confirm this. Byte order does not apply: the source describes each byte on its own. | bytes 1, 2, 3, 4, 5, 6, 7 | unknown | Source: "Byte 1 up to and including 7 default 28. 1 up to and including 4 becomes 3A when FIS is active. All 00 when no FIS activity" | interpreted |
0x635 Lighting and dash dimming Meaning: interpreted
Byte 0 is not described. Sender not stated.
Example frames
39 00 10
Signals
| Signal | Position | Byte order | Encoding | Values | Evidence |
|---|---|---|---|---|---|
| Lighting 0x64 is 100 in decimal. | byte 1 | – | Source: "Relief, byte1; 00 from / 64 at". Probably a machine translation of verlichting (lighting), uit (off) and aan (on). |
| interpreted |
| Dash lighting dimming | byte 2 | – | Source: "Byte 2; dash lighting dimming percentage". Whether the raw value is the percentage itself is not stated (the example 0x10 is 16). | interpreted |
0x651 Unknown, constant Meaning: interpreted
Printed in red in the original post. A search-engine summary of that post says red marks IDs whose meaning is not exactly known; the post itself could not be retrieved to confirm this. Source: "Always the same position". The frame itself was captured as shown.
Example frames
C0 14 61 20 14 40
Signals
No signals worked out yet.
0x653 Unknown, constant Meaning: interpreted
Printed in red in the original post. A search-engine summary of that post says red marks IDs whose meaning is not exactly known; the post itself could not be retrieved to confirm this. Source: "Always the same position". The frame itself was captured as shown.
Example frames
01 01 14
Signals
No signals worked out yet.
0x661 RNS-E on, mode Meaning: interpreted
Source: "Rns-e On, byte 2 (37) indicates the mode, in this case VIDEO". Other modes not given. Sender not stated.
Example frames
83 01 12 37 00 00 00 00mode VIDEO (source)
Signals
| Signal | Position | Byte order | Encoding | Values | Evidence |
|---|---|---|---|---|---|
| Mode The source says byte 2, but in the example 0x37 is byte 3 counted from 0 (byte 2 is 0x12). Placed at byte 3 here because the value 0x37 is named. To verify on the car. | byte 3 | – | Source: "byte 2 (37) indicates the mode, in this case VIDEO" |
| interpreted |
0x665 Phone activity Meaning: interpreted
Source: "This message is sent to indicate phone activity". Which byte does what is not described. Sender not stated.
Example frames
6F 20 00 00 30 00 20
Signals
No signals worked out yet.
0x6C0 RNS-E to FIS display Meaning: interpreted
Source: "Used for Rns-e to FIS screen (explained in other post)", with DLC 8 and ASCII yes but no example data. No frame is given, so the frames are not observed here: the ID, the DLC and the ASCII mark come from the author's description. The other post has not been found, so the protocol is not documented here. Sender and receiver: the wording reads as the RNS-E sending to the cluster, which contains the FIS display; no capture establishes it, so both are left unknown.
Example frames
No example frames.
Signals
No signals worked out yet.
0x6C1 RNS-E to FIS display Meaning: interpreted
Source: "Used for Rns-e to FIS screen (explained in other post)", with DLC 8 and ASCII yes but no example data. No frame is given, so the frames are not observed here: the ID, the DLC and the ASCII mark come from the author's description. The other post has not been found, so the protocol is not documented here. Sender and receiver: the wording reads as the RNS-E sending to the cluster, which contains the FIS display; no capture establishes it, so both are left unknown.
Example frames
No example frames.
Signals
No signals worked out yet.
0x6C4 Keep-alive request, cluster to phone Meaning: interpreted
Source: "Keep alive request from KI for phone" (KI = instrument cluster). Which byte does what is not described. See the network management page. Sender and receiver: the wording "from KI for phone" reads as the cluster (J285) sending to the phone kit; no capture establishes it, so both are left unknown.
Example frames
A0 0F 8A FF 4A FF
Signals
No signals worked out yet.
0x6C5 Keep-alive answer, phone to cluster Meaning: interpreted
Source: "Answering keep alive request phone to KI". See the network management page. Sender and receiver: the wording "phone to KI" reads as the phone kit answering the cluster (J285); no capture establishes it, so both are left unknown.
Example frames
A3
Signals
No signals worked out yet.
Worked decoding examples
Section titled “Worked decoding examples”These follow the source’s own decoding. The arithmetic is checked here; the meaning is not.
Road speed, 0x351
Section titled “Road speed, 0x351”Frame: 00 6E 10 AE 09 76 75 05.
- Byte 0 is
00: forwards (01would be backwards). - Bytes 1 and 2 are
6E 10. The source says to swap them, which gives0x106E: byte 2 is the high byte, so the value is little-endian. 0x106E= 4206 in decimal. 4206 / 200 = 21.03, so about 21 km/h.
The source does not give the resolution beyond “/ 200”, so one step of the raw value is 0.005 km/h if the formula holds across the range.
Engine speed, 0x353
Section titled “Engine speed, 0x353”Frame: 20 F5 0C 65 80 6F.
- Bytes 1 and 2 are
F5 0C. Swapped, they give0x0CF5. 0x0CF5= 3317. 3317 / 4 = 829.25, so about 829 rpm.
Time and date, 0x623
Section titled “Time and date, 0x623”Frame: 00 14 25 54 12 03 20 16. The source labels the bytes xx HH MM SS DD MM YY YY and says nothing more.
Interpretation: the hex digits read directly as decimal digits (binary-coded decimal, BCD): 14 25 54 is 14:25:54, 12 03 is 12 March, and 20 16 is 2016. A date six days before the post was published fits. The source does not say the bytes are BCD; a frame with a value that is not valid BCD (such as 0x1A) would rule it out.
To verify on the car
Section titled “To verify on the car”The source makes these claims, or leaves these gaps, and they need checking before anything is built on them:
- Coolant temperature in °F (
0x353byte 3). The source says degrees Fahrenheit, converted with (x − 32) / 1.8. The example byte0x65= 101 would be 101 °F ≈ 38 °C. Log byte 3 from a cold start to full temperature against the gauge or a VCDS reading. - Mode byte of
0x661. The source says “byte 2 (37) indicates the mode”, but in the example83 01 12 37 00 00 00 00,0x37is byte 3 counted from 0, and byte 2 is0x12. The catalogue puts the mode at byte 3 because the value0x37is named. Check which byte changes when the RNS-E changes mode, and record the other modes. - Counter in
0x621bytes 1 and 2 (red in the source). The source says it rises when “contact is passive”, read here as ignition off, little-endian (LSB, MSB). What it counts, how fast, and whether it resets are unknown. Byte 0 “responds to driver’s door and engine lid”, with no values given. - Byte 0 of
0x627(red). Which hex digit is the driver’s door and which the FIS status is read from the wording of two rows; check by opening the door with the display in a known state. - Speed and wheel pulses in
0x351. Check the speed formula at several speeds against GPS. Bytes 4 and 5 (red) are “wheel pulse; calculate distance travelled”, with no byte order and no formula. - Lighting and dimming in
0x635. Byte 1 is00off and64on (0x64= 100). Whether byte 2 is the dimming percentage as a plain number is not stated. - Buttons in
0x461and0x5C0. The frames with no button pressed for0x461are not given, nor whether holding a button repeats the frame. Which module sends0x461is not stated: the buttons are on the RNS-E, but the source does not say that the RNS-E transmits the frame. 0x436has two frame lengths in the source: 8 bytes (1A 01 00 00 00 00 00 00) and 6 bytes (16 02 80 00 00 00). The catalogue keeps the 8-byte frame and puts the 6-byte one in the notes. Check the DLC of each on the bus.0x602“activates the TV/video option in your RNS-E”. It is not known whether the frame has to be sent once or repeatedly, or by which module.- Constant messages
0x604,0x651and0x653(red): the source says only that they always stay the same. - Repetition times. The source gives none for any message.
- B7. None of this has been seen on a B7.
- The original post. Compare every byte here with the Dutch original once it can be retrieved.
Related
Section titled “Related”Parts in the wiring data
| Code | Name | Models | Location |
|---|---|---|---|
J285 | Control module with indicator unit in instrument panel insert | B6 and B7 | Behind display unit |
Sources
- Known CANID's (janssuuh, 18 March 2016) — janssuuhEvery frame and description on this page. Read from a screenshot of an English machine translation of the Dutch post, supplied by the owner. The original could not be retrieved to check against the screenshot.