Roadmap
What the Protocols section is working towards, from understanding every message on the buses to locking the car from a phone, what each goal depends on, and where each stands.
The long-term aim is to understand the car’s buses well enough to add functions that behave as if the factory had fitted them. Each goal below builds on the layers in the Protocols overview. The status says how far the documentation has got, not whether anything works in the car yet.
| Status | Meaning |
|---|---|
| Not started | No page with content yet. |
| Sources only | The pages summarise what Audi documents and the wiring manual say. Nothing has been captured on the car. |
| In progress | Captures or findings exist and are being written up. |
| Done | Documented well enough to build on, with the key points verified. |
1. Understand all buses and messages
Section titled “1. Understand all buses and messages”Know what every message on the drivetrain, convenience and infotainment CAN means, who sends it, and when.
Depends on: the physical layer (where to tap each bus, bus speeds); captures from each bus with the car in known states; the evidence rules on the overview.
| Part | Status |
|---|---|
| Physical buses: CAN, LIN, MOST, Bluetooth (from SSP 238, 269, 286 and the wiring manual) | Sources only |
| K-line and L-line, physical layer | Sources only (in Diagnosis access in CAN bus in the A4 B6/B7 and the K-line and L-line stub) |
| Infotainment CAN messages | In progress: 26 IDs from one B6 (2016 capture), not yet checked on the car |
| Convenience CAN messages | Not started |
| Drivetrain CAN messages | Not started |
| Network management (how modules wake the bus and keep it awake) | In progress: the ring and keep-alive messages of the same capture |
| Text on the cluster display, and the cluster’s character set | In progress: message IDs and the character table from the same author, not yet checked on the car |
2. Diagnostics
Section titled “2. Diagnostics”Know which diagnostic protocol each module speaks, over which wire, and what it can read and change.
Depends on: the diagnosis wiring, which is documented in Diagnosis access in CAN bus in the A4 B6/B7 (K-line and L-line on both generations, plus the drivetrain CAN on the diagnostic connector of the B7); the module addresses in VCDS controller addresses; captures of a tester talking to each module.
| Part | Status |
|---|---|
| Which module is on the K-line, which on the L-line | Sources only (in Diagnosis access in CAN bus in the A4 B6/B7) |
| Which protocol each module speaks | Not started |
| Which modules answer over the drivetrain CAN pins of the B7 | Not started |
3. Immobiliser (IMMO3 / IMMO4)
Section titled “3. Immobiliser (IMMO3 / IMMO4)”Understand how the immobiliser in the cluster recognises the key and what it exchanges with the other modules, to the level needed for legitimate repair and integration.
Depends on: the cluster and its key-reading coil D2 (see Instrument cluster); which generation a given car has (the owner’s notes give Immo 3 for the B6 and Immo 4 for the B7, with forum reports of Immo 3 in some B7s); convenience CAN messages, since SSP 254 says the immobiliser exchanges data with J393 over that bus; diagnostics (goal 2), for key adaptation.
| Part | Status |
|---|---|
| Immobiliser III in the B6 cluster, as SSP 254 describes it | Sources only |
| Immo 4 in the B7 | Not started |
| Messages between the immobiliser and J393 | Not started |
4. Remote key, locking and alarm
Section titled “4. Remote key, locking and alarm”Understand the path from the remote key to the locks: the radio signal and how it is coded (for example whether it uses a rolling code), the receiver, how J393 drives the door control units, and how the alarm arms and disarms.
Depends on: the convenience system as SSP 254 describes it (Convenience system and anti-theft alarm: J393, the remote-control aerial R47, the door control units, the alarm’s arming rules); convenience CAN messages (goal 1); the immobiliser (goal 3), because the alarm checks whether the key is known to it.
| Part | Status |
|---|---|
| Convenience system and alarm, from SSP 254 | Sources only |
| The remote key’s radio signal and its coding | Not started |
| How a key is learnt | Not started |
| Lock and unlock commands on the convenience CAN | Not started |
5. Factory-like integrations
Section titled “5. Factory-like integrations”Add functions through the documented messages, so they behave like factory equipment. The first goal is locking and unlocking from a phone app. Starting the engine and getting past the immobiliser are out of scope.
Depends on: the lock and unlock commands on the convenience CAN (goal 4); how the convenience CAN is woken from sleep and kept awake (goal 1, network management); how the alarm behaves when the car is not locked with the remote, since SSP 254 says it arms only when the car is locked with the remote; a safe way to connect to the bus (see Fault finding in CAN bus in the A4 B6/B7).
| Part | Status |
|---|---|
| Phone lock and unlock | Not started |
Pages for these goals
Section titled “Pages for these goals”Pages that exist now:
- Protocols overview
- CAN bus basics (SSP 238)
- Drivetrain and convenience CAN (SSP 269)
- LIN, MOST and Bluetooth (SSP 286)
Pages for each part (stub pages list what the sources say and the open questions, with no data yet):
- Buses: K-line and L-line (stub)
- CAN messages: how messages are documented; infotainment CAN; convenience CAN (stub); drivetrain CAN (stub); network management
- Display: writing text to the cluster display; the cluster’s character set
- Diagnostics: diagnostic protocols (stub)
- Security: overview; immobiliser; remote key; central locking and alarm (stubs)
- Integrations: phone control (stub)