Skip to content

Search is only available in production builds. Try building and previewing the site to test it out locally.

Network management

How the cluster, the RNS-E and the phone kit announce themselves on the infotainment CAN of one A4 B6: the ring messages on 0x428, 0x436 and 0x43A and the keep-alive on 0x6C4/0x6C5. Frames as captured, meanings not yet checked.

Applies to: B6 onlyCommunity write-upFrom an owner’s write-up or forum thread. Not checked against factory documentation.

The 2016 capture of one A4 B6 shows two sets of messages that the source describes as modules finding each other: ring messages between the instrument cluster (KI, J285), the RNS-E and the phone kit, and a keep-alive request and answer between the cluster and the phone. This matters for anything added to the bus, such as a box that writes to the cluster display or a phone interface: it may have to take part in the same exchange.

Bytes counted from 0. The descriptions are the source’s own, translated.

ID Frame DLC Source’s description
0x428 16 01 00 00 00 00 00 00 8 “Ring-ID, KI looks for RNS-E. Reply with: 436 [1A] (on phone), or 428 [08] 01 00 00 00 00”
0x436 1A 01 00 00 00 00 00 00 8 “Ring-ID, KI is looking for phone. Reply with: 43A [08] 01 00 00 00 00”
0x436 16 02 80 00 00 00 6 “RNS-E first sign on the ring”
0x43A 1A 02 80 00 00 00 6 “Phone initial notification on the ring”

The replies in the description column are quoted as printed. The source does not say what the square brackets mean, or why a reply to a frame on 0x428 would also be on 0x428.

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 on 0x428 starting with 08. The brackets could also mark something else, such as the length (DLC) or a node number, so the length and content of the replies are open.

The source gives two frames of different length on 0x436, one described as the cluster looking for the phone and one as the RNS-E’s first sign on the ring. It does not say which module sends which.

ID Frame DLC Source’s description
0x6C4 A0 0F 8A FF 4A FF 6 “Keep alive request from KI for phone”
0x6C5 A3 1 “Answering keep alive request phone to KI”

The source does not describe the individual bytes of either frame, or how often they are sent.

All five IDs are in the infotainment catalogue with their notes: 0x428, 0x436, 0x43A, 0x6C4, 0x6C5.

  • Which module sends each ring frame, in particular the two frames on 0x436?
  • What do bytes 1 and 2 of the ring frames mean (01, 02 80)?
  • How often are the ring and keep-alive frames sent, and what happens when a module stops answering?
  • Does a module that writes to the cluster display (0x261 to 0x267) have to join the ring or answer the keep-alive first? See Writing text to the cluster display.
  • How do the bytes of 0x6C4 relate to the answer A3 on 0x6C5? Is the answer always the same?
  • Is there a ring on the convenience and drivetrain CAN as well, and how does the bus wake from sleep? SSP 269 says the convenience and infotainment buses go to sleep when not needed after ignition off (Drivetrain and convenience CAN), but gives no messages.
  • Is any of this the same on a B7?

Log the infotainment CAN unfiltered, with timestamps, from before the key goes in until the radio and phone are fully up, and again while switching off. Repeat with the phone kit unplugged, and with the RNS-E unplugged, to see which frames belong to which module. Follow the checklist in Contributing a capture.

Parts in the wiring data

CodeNameModelsLocation
J285Control module with indicator unit in instrument panel insertB6 and B7Behind display unit

Sources

  • Known CANID's (janssuuh, 18 March 2016) — janssuuh
    Every frame and description on this page. Read from a screenshot of an English machine translation of the Dutch post; the original could not be retrieved to check against the screenshot.