Skip to content

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

Diagnostic protocols

Stub. The diagnosis wires and module addresses are documented; which protocol each module speaks is mostly an open question.

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

For each module of the car: which wire a tester uses, which diagnostic protocol the module speaks, what can be read (fault memory, measured values) and changed (coding, adaptation), and what a tester’s frames look like on the wire.

  • Diagnosis uses two wires, K and L, not a separate diagnosis CAN. See K-line and L-line and Diagnosis access in CAN bus in the A4 B6/B7.
  • On the B7 the drivetrain CAN is also wired to the diagnostic connector (T16 pins 6 and 14). On the B6 those pins are empty (B6 vs B7 electrical differences).
  • Address 19 (CAN gateway) is not present on either generation; the gateway and the immobiliser are in the cluster, address 17. Central locking, windows, mirrors and the alarm are under address 46, not 35 (VCDS controller addresses).
  • That page lists, from Ross-Tech, which addresses are reached by the K-line, the second K-line, or “CAN or K” depending on engine and transmission, and says KWP-2000 for addresses 01, 02 and 15 and KWP-1281 and KWP-2000 appear on its B6 info page. It does not say, for the other modules, which protocol they use.
  • SSP 254 says that during diagnosis the cluster checks communication with every module on the CAN and stores communication faults. Current bus status is in its measured-value blocks (Instrument cluster).
  • SSP 286 describes a separate diagnosis CAN to a J533 gateway on the A8 ’03; it does not exist on the A4 (LIN, MOST and Bluetooth).
  • Which modules use KWP 1281 and which KWP 2000? The sources name KWP-2000 only for a few addresses.
  • Which transport does a B7 module use when it answers over CAN on T16 pins 6 and 14 (for example whether it is the VW TP 2.0 transport)? The repo’s sources do not name it.
  • Which B7 modules answer over CAN and which only over the K-line?
  • How does a tester pick a module on the shared K-line (addressing, wake-up, baud-rate negotiation)?
  • Does the cluster relay any diagnostic traffic between the K-line and the CAN buses, or is that done only by fault logic?
  • What does the second K-line (L-line) carry on the B6 compared with the K-line?
  • Is the diagnostic connector’s terminal-15 pin (pin 1) used for anything beyond power?
  • Read-only first: VCDS auto-scan, then the measured-value blocks of the cluster for bus status, writing down the address, block and values. Do not code or adapt anything while investigating.
  • Passive capture: a logic analyser on T16 pin 7 or 15, or on the B7 a listen-only CAN interface on pins 6 and 14, while the tester scans. Record the car, interface and software versions, the ignition state and which module was being addressed.
  • Do not send your own diagnostic requests until you know what the request does: some requests write (coding, adaptation, key learning).

Parts in the wiring data

CodeNameModelsLocation
J285Control module with indicator unit in instrument panel insertB6 and B7Behind display unit
J527Steering Column Electronic Systems Control ModuleB6 and B7At steering column

Sources