Contents
StandardISO

ISO 17987 (LIN)

Road vehicles — Local Interconnect Network (LIN)

ISO 17987 defines how low-cost sensors, actuators and their controlling ECU communicate over a Local Interconnect Network (LIN) in a vehicle.

What it is

ISO 17987 is a multipart standards family for Local Interconnect Network (LIN), a vehicle communication bus intended for inexpensive sensors and actuators. Typical applications include small motors, switches and comfort functions whose communication needs fit a centrally scheduled network.

A LIN cluster has a commander that initiates communication and responders that participate in the configured exchanges. Older documents and tools use the terms master and slave. The schedule determines when frames are exchanged, so communication timing is a design responsibility rather than something each application chooses independently.

Who it applies to

The family matters to vehicle manufacturers, ECU suppliers, smart sensor and actuator suppliers, transceiver vendors, and integration or test teams building LIN systems.

It is a technical standard, not a vehicle regulation that automatically makes every part mandatory. The vehicle programme, customer requirements and supply agreement establish which parts and editions apply. Record those choices explicitly: a reference to “ISO 17987” alone is insufficient to define a complete implementation and acceptance baseline.

What it covers

The family addresses several layers of a LIN implementation:

Topic Engineering consequence
General concepts and use cases Establish shared terminology and the intended communication model.
Communication protocol Implement frame exchanges, scheduling, signal handling and protocol behavior consistently.
Transport and network-layer services Carry messages across diagnostic frames where the node supports those services.
Electrical physical layer Design compatible transceiver and bus interfaces.
Protocol and physical-layer conformance testing Check implementations against the applicable requirements.

The transport services support diagnostic communication but do not mean every inexpensive LIN node must provide a full diagnostic implementation. ISO describes their use for extending diagnostic access to suitable nodes on a LIN subnetwork. ISO’s transport-layer overview.

How it fits with other documents

ISO 17987 defines the LIN communication foundation. ISO 14229 provides the Unified Diagnostic Services framework used when a node implements the relevant diagnostic capabilities. LIN transport carries diagnostic messages; it does not by itself define the complete diagnostic application.

AUTOSAR specifications describe software modules and interfaces that can implement LIN communication in an AUTOSAR ECU. A small responder can also implement LIN without AUTOSAR or an operating system.

Programme network descriptions, signal definitions and ECU requirements supply the concrete configuration: who publishes each signal, when frames run, which diagnostics exist and how faults are handled. Safety and cybersecurity requirements must also be established separately; communication conformance alone does not demonstrate either property.

In practice

Start by fixing the applicable parts, editions and customer requirements. Agree the cluster configuration across the commander, responders, software configuration and test equipment.

Build schedules from application timing needs, then account for diagnostic traffic and transitions between communication states. Check what applications do when expected data is absent or stale. On a small node, confirm that local processing can service communication within the required timing.

Verify the electrical interface as well as protocol behavior. Exercise normal exchanges, communication errors, sleep/wake transitions and supported diagnostic paths. Keep conformance evidence alongside integration results: passing component tests does not establish that the assembled cluster meets the vehicle function’s requirements.

What it means for your discipline

  • Networks & communicationCore

    Own LIN cluster design, frame schedules and communication conformance. Translate signal timing needs into schedules that also accommodate diagnostics and power-state transitions.

  • Hardware & siliconCore

    Select LIN transceivers and design the electrical interface against the applicable physical-layer requirements. Verify bus behavior across the programme’s supply, wiring and operating conditions.

  • Base softwareCore

    Implement or configure LIN drivers, protocol handling and transport services. Ensure scheduling, communication status and sleep/wake behavior match the agreed network configuration.

  • E/E architecturePartial

    Decide which functions fit on a LIN cluster and where its controlling ECU connects to the wider vehicle network. Account for communication timing, gateway dependencies and fault behavior.

  • HPC & application softwarePartial

    Design application signal handling around scheduled communication and potentially stale or missing data. Service the LIN interface within its timing constraints, whether the node uses an operating system or a simple main loop.

  • Diagnostics & lifecyclePartial

    Define how diagnostic requests reach supported LIN nodes and how responses return through the controlling ECU. Coordinate transport behavior, node identification and diagnostic scheduling.

  • Functional safetyPartial

    Assess how delayed, missing or incorrect LIN communication affects the function. Specify application monitoring and safe reactions beyond communication conformance.

  • CybersecurityPartial

    Assess access to LIN through gateways, diagnostic paths and physical wiring. Define any required protection at system level rather than treating LIN conformance as a security guarantee.

No direct stake: Software update & OTA