Contents
SpecificationLIN Consortium

LIN 2.2A

LIN Specification Package, Revision 2.2A

LIN 2.2A defines how inexpensive automotive sensors and actuators communicate over a shared, centrally scheduled bus.

What it is

LIN Specification Package, Revision 2.2A, is a coordinated set of specifications for the Local Interconnect Network. LIN supports economical communication between automotive controllers and relatively simple sensors or actuators, such as those used in doors, seats and climate systems.

The package brings together communication rules, electrical requirements, software interfaces and configuration formats. This helps teams integrate separately developed nodes using a shared technical baseline.

Who it applies to

It applies to vehicle manufacturers, ECU suppliers, smart sensor and actuator suppliers, and tool developers working on a cluster specified against LIN 2.2A. It is a technical specification; its project obligations come from the agreed requirements and supply contract.

The document uses the terms master and slave. The master controls communication scheduling; a slave responds when the relevant header arrives. For a smart slave node, application developers need to understand how their command and status interface depends on that schedule, even when a supplied stack handles communication.

What it covers

The package connects several engineering concerns:

Concern What it establishes
Communication Signals, frames, scheduling, error handling, sleep and wakeup
Platform integration Software interfaces and communication status
Configuration Node addressing, identification and configuration services
Diagnostics Transport behavior and diagnostic classes
Engineering data LIN Description File and Node Capability File formats
Hardware Electrical bus-interface requirements

A LIN Description File, or LDF, describes the cluster. A Node Capability File, or NCF, describes a slave’s capabilities for integration. These files support configuration and tooling, but application-specific signal meanings still need agreement between the participating teams.

How it fits with other documents

LIN 2.2A is a legacy consortium baseline. ISO 17987 carries subsequent international standardization of LIN. A project should name the required baseline explicitly and assess differences before substituting an ISO requirement for a LIN 2.2A requirement.

SAE J2602 provides related automotive LIN implementation requirements. Apply it when the customer or project specifies it, and check the applicable edition rather than assuming every LIN implementation meets that profile.

AUTOSAR specifications govern integration within an AUTOSAR software platform. The LIN package provides the underlying network baseline; platform configuration and application requirements complete the implementation contract. Diagnostic service requirements likewise need to be reconciled with the node’s supported diagnostic class.

In practice

For a smart actuator, begin with the agreed interface: which commands it receives, which status values it publishes, and how quickly those values must reach the application. Review those needs against the controller’s schedule before selecting or configuring the stack.

Record the required revision, node capabilities and diagnostic expectations in the supplier interface agreement. Keep the LDF, generated configuration and application signal definitions consistent as changes arrive.

During integration, test normal commands alongside missing communication, power cycling, sleep/wake transitions and diagnostic access. A successful frame exchange alone does not show that the actuator responds within the function’s required time. Review bus behavior and application behavior together, using the project’s acceptance criteria.

What it means for your discipline

  • Networks & communicationCore

    Owns cluster configuration, frame schedules and communication compatibility. Uses the specified revision to resolve timing and interoperability questions.

  • Base softwareCore

    Implements or configures the LIN stack, signal access, node configuration and communication status handling. Checks that generated configuration matches the node's supported capabilities.

  • Hardware & siliconCore

    Selects and validates the transceiver and bus interface against electrical and timing requirements. Investigates physical communication faults and sleep/wake behavior.

  • HPC & application softwarePartial

    Maps application commands and status to LIN signals. Accounts for scheduled updates, communication failures and startup behavior in application logic.

  • Diagnostics & lifecyclePartial

    Defines supported diagnostic behavior within the node's diagnostic class. Coordinates addressing, identification and diagnostic access with the cluster controller.

  • E/E architecturePartial

    Allocates functions to LIN nodes and their controlling ECU. Checks that communication timing and integration constraints suit the intended vehicle function.

No direct stake: Cybersecurity · Functional safety · Software update & OTA