Skip to content

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

Convenience CAN messages

Stub. The message catalogue of the convenience CAN of the A4 B6/B7, which has no documented messages yet.

Applies to: B6 and B7StubOnly a starting point. Contributions welcome.

The messages seen on the convenience CAN: identifier, length, sender and receivers, what each byte means, and how sure we are of it (the evidence levels). How messages are written down is on the CAN messages page.

No messages documented for this bus yet. How to contribute a capture

  • The bus runs at 100 kbit/s on the A4. High is orange/green, low is orange/brown, joined at splices A146 (high) and A147 (low) in the instrument panel harness. At the cluster it is on blue T32 pins 17 (high) and 18 (low). See CAN bus in the A4 B6/B7.
  • Modules on it include the cluster J285, J393, J519, J527 and the door control units J386 to J389 (full list under Which modules are on which bus in the same article).
  • Some functions are named as messages, without identifiers: J519 sends a bulb-failure message to the cluster, J527 sends stalk positions to J519 and the key (S-contact) information to the cluster (CAN bus in the A4 B6/B7). The immobiliser in the cluster and J393 exchange data on this bus (Convenience system and anti-theft alarm).
  • On the A4 the bus is powered from terminal 30, and SSP 269 says it goes to sleep when not needed after ignition off (Drivetrain and convenience CAN). In sleep mode, with no traffic, CAN-Low sits at battery voltage and CAN-High at 0 V.
  • No message identifier or byte layout for this bus is in the sources of this repo.
  • Which identifiers are used, and which module sends each one?
  • Which messages carry the lock and unlock commands, and the state of each door lock (see Central locking and alarm)?
  • Which message carries the remote key’s button presses from J393 to the rest of the bus?
  • What wakes the bus, and which message keeps it awake? Is there a network-management pattern as on the infotainment CAN (see Network management)?
  • What does the cluster, as gateway, forward between this bus and the others, and does it change the identifiers?
  • Do B6 and B7 use the same identifiers? Nothing has been captured on either.
  • Passive listening only. Use a CAN interface set to listen-only at 100 kbit/s, connected at a point the wiring data gives: the splices A146/A147, or the cluster’s blue T32 pins 17 and 18. Never connect the convenience bus to another CAN bus.
  • Log with timestamps and record the ignition state: key out, key in, ignition on, engine running, and the wake-up moment. Note each action in the car with a time (door opened, central locking button, remote key button).
  • The bus is powered when the car looks switched off. Disconnect the battery before any resistance measurement, as the fault-finding article says.
  • Transmit nothing on a live bus unless you know what each message does.

Parts in the wiring data

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

Sources