Contents
StandardISO

ISO 11992

Road vehicles — Interchange of digital information on electrical connections between towing and towed vehicles

ISO 11992 defines how a truck and its trailer exchange digital information for braking, running gear, other equipment, and diagnostics.

What it is

ISO 11992 is a family of standards for digital communication across the electrical connection between a towing vehicle and its towed vehicles. A typical example is a heavy truck exchanging braking information with a trailer.

The family defines both how information travels and what application messages mean. This allows equipment from different manufacturers to interpret the same information consistently. The full standards are paid publications; public catalogue descriptions provide only an overview.

Who it applies to

It is relevant to manufacturers of heavy commercial vehicles, trailers, braking controllers, gateways, and other equipment connected across the vehicle coupling. Its application-layer scope includes road vehicles with a maximum authorized total mass greater than 3,500 kg and their towed vehicles, including communication between towed vehicles.

Network, hardware, and software engineers implement the interface together. Safety engineers evaluate the consequences of communication faults, while diagnostic engineers arrange service access. Vehicle integrators must check that the complete combination works, even when the truck and trailer come from different suppliers.

What it covers

The family separates the communication foundation from the functions using it.

Part Main subject
Part 1 Physical and data-link layers
Part 2 Application layer for brakes and running gear
Part 3 Application layer for equipment other than brakes and running gear
Part 4 Diagnostic communication

Part 1 establishes the electrical and data-link basis of the connection. Part 2 defines application information for electronically controlled braking and running gear, including anti-lock braking and vehicle dynamics control. Part 3 addresses other equipment and includes some lighting information. Part 4 defines diagnostic application requirements and communication profiles.

Together, these documents help engineers agree on the transmitted data and its interpretation. They do not provide a complete vehicle safety argument. The application and diagnostic parts also exclude conformance and interoperability test plans, so projects need their own verification strategy.

How it fits with other documents

SAE J1939 is an important connection: ISO 11992-2 specifies a J1939-based application layer. Engineers familiar with J1939 will recognize concepts such as parameter groups, which organize related information into messages. However, that relationship does not make an ordinary vehicle J1939 interface interchangeable with the truck–trailer interface. The relevant ISO 11992 physical and communication requirements still apply.

Connector specifications and vehicle approval requirements must be considered alongside the communication standard. Where an approval requirement references a particular edition, adopting a newer ISO edition alone does not establish compliance. Likewise, functional safety work must determine whether the system responds acceptably when communication fails.

In practice

Start by recording the required parts and editions in the interface specification. Identify the messages each controller sends and receives, their timing, and the required treatment of unavailable, invalid, or missing information. Assign ownership for the electrical interface, protocol implementation, application behavior, and diagnostics.

For example, a trailer braking controller needs more than correctly decoded braking information. The integration team must establish what happens when the connection is interrupted and how the fault becomes visible to the vehicle and service technician.

Test representative truck–trailer combinations, including different suppliers and supported equipment variants. Exercise connection loss, recovery, unexpected data, and diagnostic access through gateways. Keep evidence linking requirements to implementation and test results; successful communication with one trailer is only an initial interoperability check.

What it means for your discipline

  • Networks & communicationCore

    Own the communication interface between towing and towed vehicles, including the physical link and application messages. Verify interoperability across vehicle and trailer suppliers.

  • HPC & application softwareCore

    Implement message encoding, decoding, timing, and handling of unavailable or invalid information. Connect received signals to braking and other equipment functions.

  • Hardware & siliconCore

    Design the electrical communication interface to meet the physical-layer requirements. Check transceiver selection, wiring, and electrical behavior at the vehicle coupling.

  • E/E architecturePartial

    Define which controllers and gateways exchange information across the coupling. Allocate interface responsibilities and maintain compatibility between vehicle combinations.

  • Functional safetyPartial

    Assess how missing, delayed, or incorrect trailer information affects vehicle functions. Use the interface requirements as input to safety analysis and fault-response design.

  • Base softwarePartial

    Configure communication drivers and supporting services for the dedicated interface. Ensure the software stack supports the required protocol behavior rather than assuming a generic CAN configuration is sufficient.

  • Diagnostics & lifecyclePartial

    Use Part 4 when designing diagnostic access between towing and towed vehicles. Coordinate tester communication and gateway behavior with the supported trailer controllers.

No direct stake: Cybersecurity · Software update & OTA