For diagnostic services and message framing, see UDS over CAN and ISO-TP on CAN.
Legislated emissions diagnostics and manufacturer enhanced diagnostics share the physical diagnostic connector on modern vehicles, using either 11-bit standard or 29-bit extended CAN arbitration identifiers carried over ISO-TP (ISO 15765-2).
Legislated 11-bit OBD-II CAN IDs (ISO 15765-4)
ISO 15765-4 reserves 17 eleven-bit CAN identifiers for legislated emissions diagnostics at 500 kbit/s or 250 kbit/s. Functional requests address all emission-related controllers simultaneously; physical requests address a single ECU, whose response identifier is always Request ID + 0x08.
| Hex ID | Decimal | Direction & Addressing | Assigned ECU / Role | Notes |
|---|---|---|---|---|
0x7DF | 2015 | Tester → All ECUs (Functional) | Functional broadcast request | All legislated OBD ECUs listen and reply on their own response ID |
0x7E0 | 2016 | Tester → ECU #1 (Physical) | Engine Control Module (ECM / DME) | Strongly recommended by ISO 15765-4 |
0x7E8 | 2024 | ECU #1 → Tester (Physical) | Engine Control Module response | 0x7E0 + 0x08 |
0x7E1 | 2017 | Tester → ECU #2 (Physical) | Transmission Control Module (TCM / TCU) | Strongly recommended by ISO 15765-4 |
0x7E9 | 2025 | ECU #2 → Tester (Physical) | Transmission Control Module response | 0x7E1 + 0x08 |
0x7E2 | 2018 | Tester → ECU #3 (Physical) | Legislated OBD ECU #3 (e.g. Hybrid / ABS) | Manufacturer-assigned within OBD pool |
0x7EA | 2026 | ECU #3 → Tester (Physical) | Legislated OBD ECU #3 response | 0x7E2 + 0x08 |
0x7E3 | 2019 | Tester → ECU #4 (Physical) | Legislated OBD ECU #4 | Manufacturer-assigned within OBD pool |
0x7EB | 2027 | ECU #4 → Tester (Physical) | Legislated OBD ECU #4 response | 0x7E3 + 0x08 |
0x7E4 | 2020 | Tester → ECU #5 (Physical) | Legislated OBD ECU #5 | Manufacturer-assigned within OBD pool |
0x7EC | 2028 | ECU #5 → Tester (Physical) | Legislated OBD ECU #5 response | 0x7E4 + 0x08 |
0x7E5 | 2021 | Tester → ECU #6 (Physical) | Legislated OBD ECU #6 | Manufacturer-assigned within OBD pool |
0x7ED | 2029 | ECU #6 → Tester (Physical) | Legislated OBD ECU #6 response | 0x7E5 + 0x08 |
0x7E6 | 2022 | Tester → ECU #7 (Physical) | Legislated OBD ECU #7 | Manufacturer-assigned within OBD pool |
0x7EE | 2030 | ECU #7 → Tester (Physical) | Legislated OBD ECU #7 response | 0x7E6 + 0x08 |
0x7E7 | 2023 | Tester → ECU #8 (Physical) | Legislated OBD ECU #8 | Manufacturer-assigned within OBD pool |
0x7EF | 2031 | ECU #8 → Tester (Physical) | Legislated OBD ECU #8 response | 0x7E7 + 0x08 |
Legislated 29-bit OBD-II CAN IDs (ISO 15765-4)
Vehicles using 29-bit extended identifiers (commonly Honda/Acura legacy buses, heavy-duty vehicles, and some FCA/J1939-derived architectures) use ISO 15765-2 normal fixed addressing with priority 0x18 (6) and tester source address 0xF1.
| Hex ID | Decimal | Format / Byte Layout | Role |
|---|---|---|---|
0x18DB33F1 | 417018865 | Priority 0x18, Type 0xDB (Functional), TA 0x33, SA 0xF1 | Functional broadcast request from external test equipment |
0x18DAxxF1 | 416940273 + (xx × 256) | Priority 0x18, Type 0xDA (Physical), TA xx, SA 0xF1 | Physical request from tester (0xF1) to ECU address xx (e.g. 0x18DA10F1 for ECM 0x10) |
0x18DAF1xx | 417001728 + xx | Priority 0x18, Type 0xDA (Physical), TA 0xF1, SA xx | Physical response from ECU address xx to tester (0xF1) (e.g. 0x18DAF110) |
Manufacturer UDS and Enhanced Diagnostic CAN IDs
Outside the legislated 0x7DF–0x7EF pool, ISO 14229 (UDS) does not mandate fixed CAN identifiers; OEMs assign request/response pairs per module or route requests through a central gateway. Common documented ranges include:
- 11-bit OEM UDS pairs (
0x700–0x7FF): Many OEMs (such as Ford, Mazda, Hyundai/Kia, Toyota, Volvo, VAG, and GM) place non-OBD module UDS pairs in0x700–0x7DFwith responses atRequest + 0x08(for example, Volvo CEM0x726/0x72E, PSCM0x730/0x738, FSM0x764/0x76C; Hyundai/Kia & Toyota ADAS/ABS modules). - VAG legacy transport: Pre-UDS Volkswagen Group CAN modules use VW TP 2.0 (channel setup on
0x200 + logical address) before migrating to ISO-TP / UDS on later PQ35/PQ46 and MQB platforms. - BMW UDS / KWP over CAN: E-series and F-series gateways use extended or structured addressing (for example
0x6F1tester requests with target-address byte in byte 0, and module replies in0x600 + source address).
Sources
- ISO 15765-4: Road vehicles — Diagnostic communication over Controller Area Network (DoCAN) — Part 4: Requirements for emissions-related systems, Tables 3, 4 & 5 (11-bit and 29-bit legislated OBD CAN identifiers).
- OpenECU ISO 15765-2 Addressing Reference. Accessed 2026-11-17.
- Rust can crate OBD identifier constants. Accessed 2026-11-17.