Skip to content

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

Protocols

Every bus and protocol in the A4 B6/B7 in one place: the physical buses, the messages on them, diagnostics, the security systems and integrations built on top. Each finding says how sure it is.

Applies to: B6 and B7Work in progressIncomplete. Some steps or details are missing.

This section collects what is known about how the modules in the A4 B6/B7 talk to each other and to the outside world: the buses, the messages on them, diagnosis, and the security systems (immobiliser, remote key, central locking and alarm). The aim is to document the car well enough to add things that behave as if the factory had fitted them, such as locking and unlocking from a phone.

Most of this is still to be worked out. This page summarises what the existing articles already say, and sets the rules for adding to it. What the section is working towards, and what each goal depends on, is in the Roadmap.

From CAN bus in the A4 B6/B7 and LIN, MOST and Bluetooth:

Bus Speed Generations What is on it
Drivetrain CAN 500 kbit/s B6, B7 Engine, gearbox, ABS/ESP and airbag modules, and the cluster. Data about the running car such as road speed, engine speed and coolant temperature.
Convenience CAN 100 kbit/s B6, B7 Central convenience control unit J393, the door control units, climate control, parking aid, tyre pressure, seat memory, central locking.
Infotainment CAN 100 kbit/s B6, B7 Radio, navigation, telephone interface. SSP 254 calls it the “display bus”.
K-line and L-line – B6, B7 Workshop diagnosis. The K-line and the L-line each connect their own group of modules to the diagnostic connector.
Drivetrain CAN on the diagnostic connector 500 kbit/s B7 only Pins 6 and 14 of the diagnostic connector go straight to the drivetrain CAN splices. On the B6 they are empty.
LIN – B7 only One single-wire link from J519 to the rain/light sensor G397.
Short point-to-point pairs – some cars The B6 navigation bus, the B7 cornering-light bus and the link between the twin engine control modules of the B7 4.2 FSI. See Other buses in the wiring manual in CAN bus in the A4 B6/B7.

There is no separate gateway module (no J533) and no diagnosis CAN: the gateway that joins the three CAN buses is built into the instrument cluster J285 (The gateway is in the instrument cluster in CAN bus in the A4 B6/B7). The A4 manual has no MOST bus. Bluetooth appears only as the antenna R152 on the telephone transceiver in the phone-preparation diagrams.

The drivetrain CAN works differently from the other two electrically. On the A4 the convenience and infotainment buses stay powered from terminal 30 and can keep running on one wire after a fault; SSP 269 adds, for VW Group cars in general, that these buses go to sleep when they are not needed after the ignition is switched off. See Drivetrain and convenience CAN.

Each layer builds on the one before it. Pages go in the subfolder for their layer.

Layer What it covers What the wiki already has
1. Physical bus Wires, pins, splices, speeds, signal levels, which module sits on which bus The three bus explainers under Buses (from SSP 238, 269 and 286), and CAN bus in the A4 B6/B7 for the A4’s own wiring
2. Messages CAN identifiers, what each byte means, who sends and who receives; text on the cluster display The infotainment CAN messages of one B6 (2016 capture, not yet checked), network management and the cluster display
3. Diagnostics How a tester talks to each module over the K-line, the L-line and (B7) the drivetrain CAN The wiring of the diagnosis wires and the diagnostic connector in Diagnosis access in CAN bus in the A4 B6/B7
4. Security Immobiliser, remote key, central locking and alarm, and the messages between them What SSP 254 says, in Instrument cluster and Convenience system and anti-theft alarm
5. Integrations Adding functions to the car through the documented messages, for example locking from a phone Nothing yet

What the existing articles say about layers 3 and 4:

  • Diagnostics. SSP 254 says the A4 uses two diagnosis wires, K and L. The cluster, as the gateway, checks communication with every module on the CAN during diagnosis and stores communication faults. The VCDS controller addresses list which address reaches which module. The manual does not say which modules answer a tester over the drivetrain CAN pins of the B7.
  • Immobiliser. SSP 254 says the launch cluster contains immobiliser III, which reads the key through the coil D2 around the ignition lock and exchanges data with J393 over the convenience CAN. The owner’s notes give Immo 3 for the B6 (RB4 cluster) and Immo 4 for the B7 (RB8 cluster); forum reports say some B7 clusters are Immo 3. See Owner’s notes: RB4 and RB8 clusters in Instrument cluster.
  • Remote key, locking and alarm. Radio remote control is standard on the B6. The remote-control aerial R47 feeds J393, which runs central locking through the door control units. The alarm arms only when the car is locked with the remote. See Convenience system and anti-theft alarm.

Every message, signal and claim on a Protocols page carries one of these levels:

Level Meaning
observed Seen on the bus, values as captured.
interpreted The meaning someone gave to observed data, not checked.
verified Checked on the owner’s car, with the date and method.
documented Stated in an Audi/VW document.

Rules that go with them:

  • A capture from someone else’s car is observed for the frames and interpreted for the descriptions. Nothing becomes verified until it has been checked on the owner’s car, and the page then says when and how.
  • A reading of raw data (for example that some bytes look like a date) is written down only as interpretation, with the data it is based on.
  • Every finding says which car, model year and equipment it came from, and which bus. A finding from one car is not extended to the other generation or to another bus without a capture that shows it.
  • Where nothing is known, the page says so and lists the open question.

A capture is only useful if someone else can tell what was happening when it was taken. A good capture includes:

  • The car: generation (B6 or B7), body, model year, engine code, and the equipment that matters for the bus: cluster type (lowline or highline), head unit, phone kit, alarm, navigation.
  • The bus and where it was tapped: drivetrain, convenience or infotainment CAN, K- or L-line, with the connector and pins (for example the cluster’s T32 or T32a, see Cluster CAN pins in CAN bus in the A4 B6/B7) and the bus speed used.
  • The tool: the interface and the software, with versions, and any filter that was set.
  • The ignition state: key out, key in, ignition on, engine running; and whether the buses were awake or just waking.
  • The raw frames: the unfiltered log with timestamps, in the tool’s own format (candump log, SavvyCAN CSV or similar). Decoded tables are welcome as well, but not instead of the raw log.
  • What was done in the car while capturing, with times: which button was pressed, which door was opened, which menu was selected. Without this, a frame cannot be tied to a function.

When tapping a bus, follow the cautions in Fault finding in CAN bus in the A4 B6/B7: never join the drivetrain CAN to the convenience or infotainment CAN, keep the pair twisted, and keep added wiring on the drivetrain CAN short.

The CAN messages are kept as hand-written structured data in site/src/data/protocols/can-messages.json, one entry per message with its evidence level and source, so the same data can later feed other tools. A new finding goes in there, or on the page for its layer, with its evidence level and a citation for the capture or document it comes from.

Buses (layer 1):

Planning:

  • Roadmap: the reverse-engineering goals and what each depends on

Messages, display, diagnostics, security and integrations (layers 2–5). Pages marked stub list what the sources say and the open questions, with no data yet:

Parts in the wiring data

CodeNameModelsLocation
J285Control module with indicator unit in instrument panel insertB6 and B7Behind display unit
J393Central control module for comfort systemB6 and B7At sill panel, front left
J519Vehicle Electrical System Control ModuleB6 and B7Behind driver's storage compartment
J527Steering Column Electronic Systems Control ModuleB6 and B7At steering column
D2Induction Coil of Anti-theft ImmobilizerB6 and B7Steering column, around the ignition lock
R47Central Locking and Anti-theft Alarm System AntennaB6 and B7Routed from the Comfort System Central Control Module -J393-
G397Rain/Light Recognition SensorB7 onlyIts wires run through T17g (Connector station - left A-pillar)

Sources