Protocols
Vehicle communication and diagnostic protocols across K-Line, CAN and other networks.
Recently updated
-
Vehicle diagnostics protocols
Illustrated guide to vehicle networks, diagnostic transport and services, and scan-tool software interfaces.
-
CleANopen for municipal vehicles
CANopen application profile for refuse-collection vehicle bodies, including lifters, compactors, weighing units and truck gateways.
-
MiC 4.0 BUS for construction attachments
J1939-based CAN interface connecting construction machines with attachments, including addressing, machine-specific integration and current draft status.
-
J1939 collision-avoidance interface for earth-moving machinery
ISO/TS 21815-2 describes an on-board J1939 interface for connected collision-warning and collision-avoidance equipment on mobile machines.
-
CANopen in forklift trucks
A sourced example of CANopen in forklift traction and hydraulic drive systems, with the important distinction that forklifts do not share one universal CAN profile.
-
CANopen profiles for construction machinery
CANopen application profiles CiA 436 and CiA 415 for construction machines and road-building or earthmoving sensors.
-
ISO 11992 truck-trailer CAN
CAN-based communication between heavy towing and towed vehicles, with a separate standardized part for trailer diagnostic communication.
-
Volkswagen convenience CAN
Older Volkswagen Group convenience CAN generations, rates, gateway relationship and evidence limits for CAN IDs and diagnostic examples.
-
VAG KWP1281
Legacy Volkswagen/Audi KWP1281 diagnostics over K-line, session outline, ECU addressing and a read-only fault-code example.
-
BMW K-bus
BMW single-wire K-bus electrical and data-rate overview, its distinction from diagnostic K-line, and evidence limits for legacy frame IDs.
-
Mercedes-Benz CAN-B and CAN-C
Architecture and speed of Mercedes-Benz interior CAN-B and engine-compartment CAN-C, with model-specific limits on IDs and diagnostic examples.
-
Mercedes-Benz D2B optical bus
Mercedes-Benz D2B optical ring architecture, participating infotainment modules and service-level checks; no unsupported raw diagnostic frames.
-
GM GMLAN diagnostics
High-speed and single-wire GMLAN, with 29-bit BCM traffic, E38 identifiers and read-only BCM diagnostic examples.
-
Volkswagen CAN diagnostics
Volkswagen PQ and MQB CAN identifiers, with a captured TP 2.0 identification read and an MQB UDS example.
-
Ford MS-CAN
Ford medium-speed CAN wiring, selected body-network identifiers and read-only tyre-pressure requests.
-
Service-oriented vehicle diagnostics (SOVD)
ISO 17978 describes service-oriented vehicle diagnostics. An SOVD client works with resources and capabilities exposed by a diagnostic server, including software and vehicle entities.
-
SAE J2534 PassThru
SAE J2534 defines a PassThru API used by vehicle applications to communicate through compatible interfaces. The application selects the vehicle procedure while the adapter provides the supported link.
-
Diagnostic D-Server
ISO 22900-3 specifies the diagnostic server API. A server can use diagnostic descriptions to map application-level requests to the required vehicle messages and interpret results.
-
FlexRay
FlexRay schedules traffic in repeating communication cycles. The static segment gives configured messages fixed transmission slots. The dynamic segment permits a different scheduling mechanism for traffic with varying demand.
-
BMW D-CAN, K-CAN and PT-CAN
BMW diagnostic, body and powertrain CAN networks, with MK60E5 diagnostic request examples and a community-decoded K-CAN broadcast.
-
RP1210 vehicle interface API
TMC RP1210 defines a software interface used by heavy-duty vehicle diagnostic applications and communication adapters. It can expose links such as J1939 or J1708 through a vendor driver.
-
Open Test Sequence Exchange (OTX)
ISO 13209 defines Open Test Sequence Exchange. OTX represents diagnostic and test procedures in a portable form, including control flow, calls and result handling.
-
D-PDU API
ISO 22900-2 defines an interface between diagnostic software and the vehicle communication interface. It lets the application use communication modules and logical links through a common programming interface.
-
WWH-OBD
World-Wide Harmonized On-Board Diagnostics uses the ISO 27145 series for standardised access to emissions-related diagnostic data.
-
UDS over CAN
How Unified Diagnostic Services use ISO-TP on CAN, with links to diagnostic CAN addressing and transport framing.
-
OBD-II emissions diagnostics
Legislated OBD uses standardised access to emissions-related data. A generic scan tool can retrieve supported monitor status, live parameters, freeze-frame records and diagnostic trouble codes.
-
KWP 2000 on CAN
Some vehicles carry KWP 2000 diagnostic services over CAN. The service payload and CAN transport are distinct. A trace may use ISO-TP or a vehicle-specific transport depending on the application.
-
Volkswagen TP 1.6 and TP 2.0
Volkswagen Group’s TP 1.6 and TP 2.0 are legacy CAN transport protocols. TP 2.0 negotiates a logical channel and communication parameters before transferring diagnostic messages.
-
KWP 2000 on K-Line
Keyword Protocol 2000 over K-Line (ISO 14230), covering the diagnostic layers, tester requests and ECU responses.
-
ISO-TP on CAN
How ISO 15765-2 splits a diagnostic message across CAN frames: single, first, consecutive and flow-control, and the separation time the sender has to keep.
-
SAE J1708 and J1587
SAE J1708 describes serial communication used in older heavy-duty vehicles. SAE J1587 supplies message conventions used over that link. A truck can expose J1708 alongside a separate J1939 network.
-
SAE J1850 vehicle diagnostics
SAE J1850 was used for legacy vehicle diagnostics. The PWM and VPW forms use different signalling. A matching connector alone does not establish that a tester supports the required electrical interface.
-
ISOBUS
ISO 11783 defines a CAN-based network for agricultural machines and implements. A Universal Terminal can present an implement’s interface using descriptions supplied by the implement.
-
CAN FD
CAN FD increases payload capacity to 64 bytes and can switch to a higher bit rate for the data phase. Nodes must agree on the nominal rate used during arbitration and the configured data-phase rate when bit-rate switching is used.
-
CAN XL
CAN XL adds a frame format for payloads up to 2,048 bytes while retaining CAN-style arbitration. Its header distinguishes arbitration priority from information used by higher-layer protocols.
-
K-Line diagnostics
A single signal wire carries bidirectional serial diagnostic traffic between the tester and control units. The vehicle interface uses automotive electrical levels, so a suitable K-Line transceiver sits between the line and the tester hardware.