Guide · 14 min read · updated 15 November 2026

On-board diagnostics explained

On-board diagnostics is the vehicle’s ability to detect faults and report data. A scan tool asks the control modules for readings, fault records and test results. Below: every term, grouped by what it does, with where each one is used.

1. Modules and tools

A vehicle contains several computers on shared networks. Each controls one job. Diagnostics means talking to them.

TermDefinition
ECU / module / controllerElectronic control unit: a computer with software, inputs and outputs. The three words are used interchangeably. ECU sometimes means engine control unit specifically.
ECM / PCM / TCMEngine, powertrain (engine + transmission) and transmission control modules.
BCM / ABS / SRSBody control module, anti-lock brake controller, airbag (supplemental restraint) controller.
NodeAnything on a network: a module or a diagnostic interface. One module can sit on several networks.
GatewayModule joining networks. Forwards diagnostic requests, translates addresses and can block access.
Tester / scan toolThe device or app sending requests. The module answering is the server.
Adapter / VCIVehicle communication interface: the hardware between your phone or computer and the car.

2. OBD-II and the connector

OBD-II is the standardized, emissions-focused part of diagnostics: one connector, a few permitted protocols and a common request set. Every manufacturer supports it. Everything beyond emissions (ABS, airbags, body, coding) uses the manufacturer’s own diagnostics. EOBD is the European equivalent. OBD-I means the earlier, unstandardized systems.

DLC pinUse
6 and 14CAN High / CAN Low (standard OBD CAN).
4, 5, 16Chassis ground, signal ground, battery +12 V (live with ignition off).
7 (and 15)K-Line (and optional L-Line) for ISO 9141 / KWP2000.
2 and 10J1850: pin 2 for VPW, pins 2 + 10 for PWM.
1, 3, 8, 9, 11, 12, 13Manufacturer use: GM SWCAN on 1, Ford MS-CAN on 3 + 11, BMW Ethernet activation on 8.

DLC (diagnostic link connector) is the socket, SAE J1962. US cars from model year 1996; EU petrol from 2001, diesel from 2004.

3. Layers: OSI and the three-level model

The OSI model splits communication into seven layers, each with one job. Vehicle protocols fill only some of them. Knowing the layer tells you which terms can be swapped and which can’t: UDS can ride on CAN or Ethernet; ISO-TP only carries, it never interprets.

OSI layerJobVehicle examples
7 · ApplicationWhat the message meansOBD-II services (J1979), UDS (ISO 14229), KWP2000 (ISO 14230), GMLAN diagnostics, J1939-73
6 · PresentationEncoding of valuesScaling and formulas defined by the application layer or ODX/DBC files
5 · SessionDialogue stateUDS sessions (service 10), TesterPresent, KWP StartCommunication
4 · TransportSplitting and reassembling long messagesISO-TP (ISO 15765-2), VW TP2.0, J1939-21 transport, DoIP
3 · NetworkAddressing and routingDiagnostic addressing (7DF/7E0), gateways, DoIP logical addresses, IP
2 · Data linkFrames, IDs, error checksCAN / CAN FD frames, K-Line bytes, LIN frames, Ethernet MAC
1 · PhysicalWires and voltagesCAN High/Low, SWCAN, K-Line, J1850, LIN, 100BASE-T1 Ethernet

In practice three levels cover CAN diagnostics. A request travels down, the reply travels back up.

  1. Level 3 · Meaning (OSI 5–7)

    OBD-II / UDS / GMLAN / KWP2000

    Ask for RPM: 01 0C → answer: 41 0C 1A F8

  2. Level 2 · Delivery (OSI 3–4)

    Addressing and transport, usually ISO-TP

    Pick request/response IDs; split long messages; reassemble replies

  3. Level 1 · Network (OSI 1–2)

    CAN frames, transceiver and wires

    CAN ID + length + data → CAN High / CAN Low → module

Request ↓ · Response ↑
  1. The app asks for RPM: service 01, PID 0C.
  2. The interface sends a CAN frame on functional ID 7DF; ISO-TP adds the length byte.
  3. The engine module replies on 7E8 with 41 0C 1A F8.
  4. 41 = positive reply to 01, 0C = RPM, 1A F8 = raw value → 1,726 RPM.

The phone-to-adapter link (USB, Bluetooth, Wi-Fi) sits outside this stack. It carries instructions to the adapter, which speaks CAN.

4. CAN: frames and IDs

CAN (Controller Area Network, ISO 11898) is a shared two-wire bus. Every module hears every frame; each picks the ones it needs.

TermDefinition
FrameOne CAN message: ID, length, up to 8 data bytes (64 on CAN FD), CRC.
CAN ID / arbitration ID11-bit (standard) or 29-bit (extended) label on a frame. Lower ID wins when two nodes transmit at once.
Classic CANUp to 8 data bytes per frame, typically 500 kbit/s powertrain, 125–250 kbit/s body.
CAN FDFlexible Data-rate: up to 64 bytes and a faster data phase. Needs CAN FD hardware.
Bitrate vs baudBitrate is bus speed; baud rate is the serial speed between computer and adapter.
DLC (in a frame)Data Length Code: the frame’s payload length field. Same letters as the connector, different thing.
CRC / ACK / bus-offError check; receipt by any node; a controller disabling itself after too many errors.
SignalA value packed into a broadcast frame (wheel speed, coolant), with bit position, scale and unit.
HexBase 16, digits 0–9 and A–F. One byte = two hex digits (00–FF). 0x is a notation prefix.

7F7 in an ID column is CAN ID 0x7F7 (decimal 2039). Its meaning comes from that vehicle’s address map: often a manufacturer diagnostic request or reply ID. 7F as the first payload byte is something else: the UDS negative response.

5. Addressing and ISO-TP

ISO-TP (ISO 15765-2) carries diagnostic messages longer than one CAN frame: it adds length and sequence bytes, flow control and reassembly.

Frame typeJob
Single Frame (SF)A complete short message, up to 7 bytes on classic CAN.
First Frame (FF)Starts a long message and gives its total length.
Flow Control (FC)Receiver says continue, how many frames per block and the spacing.
Consecutive Frame (CF)The next piece, numbered in sequence.
AddressingDefinition
FunctionalOne request to every emissions module. OBD on 11-bit CAN: 7DF.
PhysicalOne request to one module. Engine: 7E0 → reply 7E8; transmission: 7E1 → 7E9.
29-bit OBD18DB33F1 functional; replies on 18DAF1xx, where xx is the module address.
Extended addressingAn extra address byte inside the data (used by BMW). Separate from 29-bit IDs.

Reply = request + 8 holds for standard OBD pairs. Manufacturer modules use their own maps.

6. Message types

TypeDefinition
RequestTester asks for a service: service ID plus a PID, DID, subfunction or arguments.
Positive responseSuccess plus data. Service ID + 0x40 (01 → 41, 22 → 62).
Negative responseStructured refusal or delay: 7F, the refused service, a reason code.
No response / NO DATANothing arrived in time: wrong address, ignition off, unsupported, filtered.
Broadcast / periodicFrames modules send on their own, repeatedly. Normal vehicle traffic.
Event-drivenFrames sent when something changes.
PollingTester asks again and again. This is what most ‘live data’ is.
Passive monitoring / sniffingListening to traffic without sending requests.
Service / subfunction / maskOperation; its variant; flag filter that selects records.
PayloadThe message data inside the frame.

More channels means slower updates: the adapter splits a fixed request rate among them.

7. PIDs, DIDs and definitions

TermDefinition
PIDParameter ID: one value within an OBD service. Service 01 PID 0C = RPM.
DIDData Identifier: two-byte UDS value ID, read with service 22. F190 = VIN; most others are manufacturer-defined.
User / custom PIDA definition you add to an app: request, address, reply bytes, formula, unit. Usually wraps a manufacturer DID.
OBDbOpen database of vehicle signal definitions: how to request and decode each value per vehicle.
ScalingByte positions, sign, byte order, factor and offset that turn raw bytes into units.
Supported-PID bitmapPIDs 00, 20, 40…: a module’s list of the PIDs it answers.
PID (tuning)Proportional–integral–derivative controller, used for idle and boost. Unrelated to OBD PIDs.

Confirm a new definition against a known reading: a believable value can still be wrong.

8. OBD services (modes)

Mode and service mean the same thing here. Numbers are hex. Defined in SAE J1979; newer cars use J1979-2 (OBDonUDS).

ServiceProvides
01 · Current dataLive readings (RPM, coolant, trims, MAP), readiness, supported-PID lists.
02 · Freeze frameSnapshot of readings taken when an emissions fault was stored.
03 · Stored DTCsConfirmed emissions trouble codes.
04 · ClearErases codes, freeze frames and readiness.
05 · O2 sensor testsOxygen sensor results on pre-CAN cars.
06 · Monitor resultsOn-board test results with measured value and min/max limits.
07 · Pending DTCsFaults seen this or last drive cycle, awaiting confirmation.
08 · ControlCommands a few on-board tests, such as an EVAP leak test.
09 · Vehicle infoVIN (InfoType 02), calibration IDs, CVNs, ECU name.
0A · Permanent DTCsCodes only the ECU clears, after it verifies the repair.
TermDefinition
ReadinessWhether each emissions monitor has finished its self-test since the last clear.
Mode 06 MID / TID / CIDMonitor, test and component IDs that label each test result.
Drive cycleThe temperatures, speeds and times needed for monitors to run.
VINVehicle identification number, 17 characters.
CALID / CVNCalibration ID names the software; calibration verification number checksums it.

9. One request and reply, byte by byte

Request   CAN ID 7DF   data 02 01 0C 00 00 00 00 00
Response  CAN ID 7E8   data 04 41 0C 1A F8 00 00 00

02 / 04  = ISO-TP Single Frame length
01       = request current data
41       = positive response to 01
0C       = engine RPM PID
1A F8    = A and B: decimal 26 and 248
RPM      = (256 × A + B) / 4 = 1,726
Trailing 00 = padding

On an ELM327 you type 010C and get 41 0C 1A F8: the adapter adds and strips the framing.

10. DTCs

DTC (Diagnostic Trouble Code, SAE J2012) records a failed self-test. It names the test that failed; the cause can be the part, its wiring, power, ground or a mechanical fault.

TermDefinition
P / B / C / UPowertrain, body, chassis, network. P0xxx generic, P1xxx manufacturer.
PendingSeen once, awaiting confirmation.
Confirmed / storedMet its confirmation criteria and saved.
Active / currentFailing right now.
History / intermittentFailed earlier, passing now.
PermanentEmissions record only the ECU clears after verifying the repair.
MIL / CELMalfunction indicator lamp, the check-engine light.
Failure type byteExtra detail after a dash (P0123-1C), used by UDS and GM.
Status byteUDS bit flags: test failed, pending, confirmed, warning lamp requested, and more.
Extended dataMileage, counters and conditions stored with the code.

Save codes and freeze frames before clearing.

11. UDS

UDS (Unified Diagnostic Services, ISO 14229) is the modern manufacturer diagnostic language: reading data and faults, routines, coding and programming. Runs on CAN (via ISO-TP) or Ethernet (via DoIP).

ServicePurpose
10 · Session controlSwitches ECU state: default, extended or programming.
11 · ECU resetRestarts the module.
14 · Clear DTCsErases fault memory.
19 · Read DTCsReads codes, status, snapshots and extended data.
22 · Read by identifierReads a DID.
27 / 29 · Security / authenticationSeed-key unlock (27) or certificate login (29) before protected actions.
2E · Write by identifierWrites a DID, changing configuration.
2F · I/O controlTemporarily drives an output: the basis of actuator tests.
31 · Routine controlStarts, stops or reads a built-in procedure.
34 / 36 / 37 · DownloadRequest, transfer and finish a flash.
3E · Tester presentKeeps a non-default session open.
Request:   22 F1 90
Positive:  62 F1 90 [VIN bytes]
Negative:  7F 22 31

22 = ReadDataByIdentifier, F190 = VIN DID
62 = positive response to 22
7F = negative response, 22 = service refused, 31 = requestOutOfRange
NRCMeaning
11Service not supported
12Subfunction not supported
13Wrong length or format
22Conditions not correct (engine running, speed, etc.)
31Request out of range: identifier unavailable here
33Security access denied
78Response pending: wait, the answer is coming

P2 / P2* are the reply time limits; S3 is the session timeout.

12. Bidirectional

In scan-tool marketing, bidirectional means the tool can command the car: run a fan, cycle a solenoid, start a routine.

CapabilityDefinition
ReadReadings, identity, codes, test results.
Clear / resetErases stored diagnostic state.
Active testDrives an actuator temporarily.
Adaptation / relearnResets or relearns stored values (throttle body, injector codes).
Coding / configurationChanges module options.
Flashing / programmingReplaces calibration or firmware.

13. Manufacturer implementations

Every maker speaks OBD-II for emissions and its own diagnostics for everything else.

MakerOlder networksManufacturer diagnosticsNewer
GMJ1850 VPW (Class 2), ALDLGMLAN (GMW3110), SWCAN body busUDS on Global B / VIP
FordJ1850 PWM, UBPUDS on HS-CAN and MS-CAN (pins 3 + 11)UDS, CAN FD, DoIP
Stellantis (Chrysler)J1850 VPW, SCIKWP2000 / UDS on CANUDS behind the Secure Gateway
VW groupK-Line KW1281, KWP2000KWP2000 over VW TP2.0UDS on ISO-TP (MQB on), DoIP
BMWK-Line DS2KWP2000 / UDS on D-CAN with extended addressingUDS over DoIP (ENET), F-series on
MercedesK-Line KWP2000KWP2000 / UDS on CANUDS, DoIP
Toyota / Honda / NissanISO 9141, KWP2000 on K-LineProprietary services on CANUDS
Trucks / heavy dutyJ1708 / J1587J1939J1939, UDS on newer

GM

TermDefinition
GMLANGM’s network family and its diagnostic language (GMW3110). Close to KWP2000 with GM services.
Class 2GM’s pre-CAN network on J1850 VPW, 10.4 kbit/s.
High-speed GMLANTwo-wire 500 kbit/s CAN for powertrain and chassis.
SWCANSingle-Wire CAN (SAE J2411), 33.3 kbit/s, GM body bus on DLC pin 1. Needs a single-wire transceiver.
Global AGM electrical architecture, roughly 2007–2019, using GMLAN diagnostics.
Global B / VIPSuccessor architecture with UDS and a security gateway.
A9GMLAN service 0xA9, ReadDiagnosticInformation: reads DTCs by status mask (subfunction 81).
A9 framingA9 replies arrive as unsolicited frames (UUDT) on a separate ID, one DTC per frame, ending with a terminator.
USDT / UUDTSegmented (ISO-TP) vs unsegmented single-frame diagnostic transfers.

VW group

TermDefinition
KW1281VW’s original K-Line protocol, 1990s.
VW TP2.0VW Transport Protocol 2.0: opens a channel to a module on CAN with negotiated IDs, acknowledgments and timing, then carries KWP2000. Roughly 2004–2012.
Measuring blocksNumbered groups of readings (block 001 = RPM, coolant…) per module and firmware.
Module addressesTwo-digit hex: 01 engine, 02 transmission, 03 ABS, 17 instruments.

Older shared protocols

TermDefinition
K-LineSingle-wire serial link on DLC pin 7. Physical layer for ISO 9141-2 and KWP2000.
ISO 9141-2Early OBD-II protocol on K-Line, 10.4 kbit/s, slow init. Common on Asian and European cars.
KWP2000Keyword Protocol 2000 (ISO 14230): diagnostic language, on K-Line or on CAN. UDS’s predecessor.
5-baud / fast initK-Line wake-up sequences before talking.
J1850 VPW / PWMSAE pre-CAN networks: VPW 10.4 kbit/s (GM, Chrysler), PWM 41.6 kbit/s (Ford).

14. Description files

A protocol defines how to ask. A description file defines what one ECU’s requests and replies mean.

FormatDescribesUsed with
CDDAn ECU’s diagnostic services, DIDs, DTCs and variantsVector CANdela tools
ODXSame, in open XML (ASAM MCD-2 D / ISO 22901)OEM and dealer tools
PDXA ZIP package of ODX filesODX tools
DBCBroadcast CAN frames and their signalsSniffing and logging
A2LECU memory map for calibrationXCP / CCP tools
VariantOne module + software + configuration combinationAll of the above

15. J1939 (heavy duty)

SAE J1939: trucks, buses, tractors and generators. 29-bit CAN, 250 or 500 kbit/s, mostly broadcast.

TermDefinition
PGNParameter Group Number: the message type, taken from part of the 29-bit ID.
SPNSuspect Parameter Number: one value or fault subject.
FMIFailure Mode Identifier: how it failed (high, low, open circuit…).
Source address / address claimA node’s one-byte address and how it claims it; NAME is its 64-bit identity.
DM1Active DTCs and lamp status, broadcast every second.
DM2Previously active DTCs, on request.
BAM / RTS-CTSJ1939 transport for messages over 8 bytes: broadcast or handshake.

16. Other networks and protocols

TermDefinitionUsed for
DoIPDiagnostics over IP (ISO 13400): UDS over Ethernet, with discovery and routing activationFast diagnostics and flashing on newer cars
LINSingle-wire, up to 20 kbit/s, one commander schedules the restSwitches, mirrors, window motors
SOME/IPService-oriented messaging over automotive EthernetInfotainment, ADAS data
CANopenHigher-layer CAN protocol with object dictionary, PDOs and SDOsIndustrial, e-bikes, forklifts
CCPCAN Calibration Protocol: read and tune ECU memory liveECU development
XCPCCP’s successor (ASAM), on CAN, Ethernet, USB; uses A2L filesECU development and tuning
MQTTPublish/subscribe messaging through a broker over IPSending readings to dashboards or servers

17. Adapters and connections

TermDefinition
ELM327OBD-to-serial interpreter chip. You send text commands, it handles the vehicle protocol and returns text. Most cheap adapters are ELM clones.
AT commandsELM setup commands: protocol, headers, timeouts, filters (ATSP6, ATH1).
STN / ST commandsScanTool.net chips (OBDLink): ELM-compatible plus ST commands, faster, with SWCAN and better buffering.
J2534Pass-through standard: a PC API for flashing and dealer software.
USB / serialWired link to the adapter. May need an OS driver.
Bluetooth Classic vs BLETwo different Bluetooth types. Classic uses SPP serial; BLE uses GATT services.
Web SerialBrowser API for serial ports (USB adapters). Chrome and Edge on desktop.
Web BluetoothBrowser API for BLE adapters. Chrome on desktop and Android.
CLICommand-line interface: text-based control of software.

18. Diagnostic workflow

  1. Note the complaint and when it happens. Check battery voltage, power and grounds.
  2. Connect and read identity, stored, pending and permanent codes, and readiness.
  3. Save the report, freeze frames and extended data.
  4. Watch a few relevant live values under the fault’s conditions.
  5. Test wiring and the mechanical side with the manufacturer’s procedure.
  6. Run active tests once you know what they move. Keep clear of fans and belts.
  7. After the repair, clear, drive the conditions again and recheck.

Symptom → check

SymptomCheck
Adapter connects, car silentIgnition, protocol, wiring, timing
Generic OBD works, a module doesn’tGateway, module address, its diagnostic language
Module answers, a value doesn’tDID support, firmware variant, session, definition
Short reads work, VIN or codes failMulti-frame transport, flow control, filters, adapter buffer
Slow updatesFewer channels; adapter speed
Negative responseDecode the NRC before retrying

19. The efi2000 scanner

The efi2000 OBD2 scanner runs in Chrome or Edge with an ELM327 or STN adapter, no account needed. It reads live data, readiness, stored, pending and permanent codes, freeze frames and vehicle info, and finds what each module speaks: UDS, GMLAN, KWP2000 or VW TP2.0.

References

TopicStandard
ConnectorSAE J1962
OBD servicesSAE J1979 / J1979-2
DTCsSAE J2012
CANISO 11898
CAN transport / OBD on CANISO 15765-2 / -4
UDSISO 14229
KWP2000ISO 14230
J1850SAE J1850
SWCANSAE J2411
DoIPISO 13400
LINISO 17987

Questions

How do CAN and OBD-II relate?
CAN carries frames. OBD-II defines the emissions requests and data sent in them. Since 2008 every US car runs OBD-II on CAN.
What is 7F7?
A CAN ID, 0x7F7, used by some makers for module diagnostics. A 7F byte at the start of a payload is a UDS negative response.
What does a custom PID do?
It tells the app how to request and decode a value the module already supports.
What does clearing codes do?
Erases stored codes, freeze frames and readiness. Permanent codes stay until the ECU verifies the repair.
What do bidirectional scanners do?
Command the car: actuator tests, relearns, coding. Flashing is a separate capability.