The Volvo D2 protocol explained: frames, addresses and services
Put a CAN sniffer on a P1 Volvo while a diagnostic tool is talking and you will see one identifier over and over: 0x000FFFFE. That is D2, Volvo's own diagnostic protocol. Here is how its frames are built, how modules answer, and what the services mean — with frames recorded on a real car.
What D2 is, and where it is used
D2 is the diagnostic protocol spoken by the control modules of Volvo's P1 cars (C30, S40, V50, C70) and, in an older generation, P2 cars. It is Volvo's own design: the framing, the addressing and the service numbers are not those of OBD-II or of UDS.
Strictly speaking, the protocol is a property of each module, not of the car. A module's configuration says which protocol it speaks, on which bus and at which address. On a P1 car practically every module is D2; on P3 cars the modules speak UDS instead, with a separate pair of CAN identifiers each. A tool that decides by platform alone will eventually send the wrong kind of frame to something.
The request frame
Every D2 request, to any module, is sent to the same 29-bit CAN identifier: 0x000FFFFE. What makes it reach the right module is inside the data:
| Byte | Meaning |
|---|---|
| 0 | C8 + the number of meaningful bytes that follow |
| 1 | Address of the target module |
| 2 | Service |
| 3… | Parameters of the service; the rest of the frame is padding |
Take the request in the picture above, which asks the central electronic module for the block containing the VIN:
| Bytes | Meaning |
|---|---|
CB | C8 + 3: three meaningful bytes follow |
50 | Central electronic module, high-speed bus |
B9 | Service: read a block |
FB | Which block |
00 00 00 00 | Padding |
A request with a two-byte identifier and one more parameter is five meaningful bytes, so it starts with CD: CD 11 A6 00 A1 01 00 00 asks the diesel engine module (11) for record 00A1.
Module addresses
The address in byte 1 comes from the module's configuration. These are the addresses for a 2008 C70 diesel:
| Module | Address |
|---|---|
| BCM — brake control | 01 |
| ECM — diesel engine (EDC16) | 11 |
| CCM — climate | 29 |
| CEM — central electronic module | 50 on the high-speed bus, 40 on the low-speed bus |
| DDM / PDM — driver and passenger door | 43 / 45 |
| DIM — instrument cluster | 51 |
| SRS — airbags | 58 |
| TCM — automatic gearbox (AW55) | 6E |
Two things in this table trip people up. The CEM sits on both buses and has a different address on each. And addresses are not fixed per module type: other Volvo engine modules use 7A, and a tool that sends engine requests to 7A on this car gets silence. P3 cars use a different address space altogether, so an address does not tell you the protocol either.
How a module answers
A module answers on its own CAN identifier, not on the shared one. On our test car in October 2026 the modules on the high-speed bus answered from these identifiers:
| Module | Answered on |
|---|---|
| CEM | 0x00400003 |
| TCM | 0x00400005 |
| BCM | 0x00400009 |
| ECM | 0x00400021 |
| EPS — power steering | 0x00400101 |
| SWM — steering wheel module | 0x00400801 |
These are observations from one car, and the module definitions we work from do not list a response identifier for D2 at all. So Volscan does not rely on them. It recognises an answer by what is in it:
- byte 1 is the address of the module that was asked;
- byte 2 is the service that was asked, plus
40. AB9request is answered withF9,A6withE6,AEwithEE.
Once the first matching frame arrives, the identifier it came from is known and can be used to narrow the adapter's filter for the rest of the session.
One detail that matters when decoding: in a short answer the bytes after the stated length are not padding zeros. The power steering module answered a fault-code read with CB 30 EE 1B 01 00 00 91. The length byte CB says three bytes — address, EE, 1B — so this is an empty fault list, and the last four bytes are leftovers to be ignored.
Answers longer than one frame
A CAN frame holds eight bytes, and the VIN alone is seventeen. Longer answers are split across frames, and byte 0 says where each frame belongs:
80set — this is the first frame;40set — this is the last frame, and its low three bits give the number of bytes it carries;- every frame except the last carries seven bytes.
This is also why a single-frame message starts at C8: it is first and last at once (80 + 40), and the low bits hold its length. On the car, a long answer from the CEM started with 97, continued with frames whose first byte ran 11, 12 … 17 and then 10 — a frame number that wraps around — and ended with 55: last frame, five bytes.
This is not ISO-TP, the transport used by UDS, and an adapter's built-in ISO-TP handling cannot reassemble it. The tool has to collect the frames itself and check that the frame numbers arrive in order.
The services
The service byte selects what the module should do. Each module's definition lists the services it supports and how the answer is laid out; these are the ones a read-only tool needs:
| Request | Answer | Used for |
|---|---|---|
A6 <id16> 01 | E6 <id16> … | Read a record by a 16-bit identifier — most live values |
A5 <id8> 01 | E5 … | Read a record by an 8-bit identifier |
B9 <id8> | F9 <id8> … | Read a block — identification, the VIN |
AE 1B | EE 1B + 8 bytes per code | Read the fault-code list |
AE 11 | EE 11 + 2 bytes per code | Read the fault-code list, shorter form |
AE 18 <code> | EE 18 <code> … | Status of one fault code |
The answer is only a row of bytes. What they mean — which bits form a value, how it is scaled, what unit it has — comes from the definition of that record for that exact module variant. The VIN, for example, is a 17-character ASCII field at a fixed position inside the CEM's FB block. Fault codes work the same way: the list gives 16-bit numbers, and the module's definitions turn them into text, as described in Volvo fault codes explained.
There are services that change things as well — activations, routines such as the injector balance test, clearing codes. They follow the same framing, and they are where a tool has to be careful: Volscan is read-only by default and sends such a request only when the module's definition lists it, after a confirmation.
When a module says no
A refusal has its own shape: instead of service + 40, the module sends 7F, the service it is refusing, and a reason code. Two refusals from our test car:
| Frame | What happened |
|---|---|
CC 01 7F B9 12 | The brake control module (01) declined a B9 block read |
7F AF 22 | The engine module declined a request to clear its fault codes |
A refusal is an answer, and a useful one: the module is awake, on this bus, at this address, and understood the request. That is very different from silence, which can mean a wrong address, the wrong bus, a module the car does not have, or a car that has gone to sleep. A tool should show the two differently instead of folding both into "no response".
One reason code is worth handling specially. Workshop software treats 7F <service> 21 as "busy" and sends the same request again rather than reporting a failure.
What this asks of an adapter
D2 is simple on the wire, but it rules out the shortcuts generic tools take:
- Raw 29-bit frames. The adapter must send arbitrary frames to
0x000FFFFEand hand back whatever arrives from the modules' identifiers. Its built-in OBD-II mode is of no use here — see why a generic OBD-II scanner misses Volvo fault codes. - Both buses. The same request identifier is used on the high-speed bus (OBD pins 6 and 14, 500 kbit/s) and the low-speed bus (pins 3 and 11, 125 kbit/s), but a module only hears it on its own bus. On our C70 the door, airbag, climate and instrument modules answered on the low-speed bus; Volvo HS-CAN and LS-CAN explained has the full list.
- A session that stays open. While a diagnostic session is running, workshop software repeats a short frame beginning
D8on the shared identifier every four seconds. A tool that wants modules to behave as they do in the workshop does the same.
Volscan picks the protocol for each module from that module's configuration, builds D2 frames as described here, switches between the two buses, and tells you plainly when a module's protocol cannot be determined instead of guessing. See supported cars and adapters.
FAQ
What CAN ID does Volvo D2 diagnostics use?
Every D2 request is sent to one shared 29-bit identifier, 0x000FFFFE. The module it is meant for is named by an address in the second data byte. Each module answers on its own identifier; on our 2008 C70 the engine module answered on 0x00400021 and the central electronic module on 0x00400003.
Is Volvo D2 the same as UDS?
No. D2 is Volvo's own protocol with its own framing and service numbers (A6, B9, AE and so on), used by modules on P1 and P2 cars. UDS (ISO 14229) is the standard used by P3 modules, with a separate pair of 11-bit CAN identifiers per module and ISO-TP framing.
What does the first byte of a D2 frame mean?
In a single-frame message it is 0xC8 plus the number of meaningful bytes that follow, so CB means three bytes and CD means five. In longer answers the same byte marks the first frame with 0x80 and the last frame with 0x40.
Can an ELM327 adapter send Volvo D2 messages?
The adapter has to send raw 29-bit CAN frames to 0x000FFFFE and pass back frames from the modules' own response identifiers, and it only reaches the modules on the bus it is wired to. Many body modules sit on the low-speed bus on OBD pins 3 and 11, which most plain ELM327 adapters do not connect to.