Contents

LIN — Local Interconnect Network

A cheap single-wire master/slave bus for simple sensors and actuators like mirrors, seat motors and HVAC flaps — slow, deterministic and good enough.

Why it exists

Using CAN for every window switch or mirror motor would be overkill. LIN was created by car makers around 2000 as a much cheaper sub-bus for simple devices, controlled by a “master” ECU.

What it is

  • Single wire (plus supply and ground), up to 20 kbit/s.
  • One master and up to 16 slaves.
  • Schedule-based: the master sends a header for each frame in a fixed schedule; the addressed slave (or the master) fills in the response.
  • Payload up to 8 bytes per frame.
LIN frame: header from the master, response from one node
Break≥ 13 bitswakes up attention
Sync0x55slaves adjust their clock
Protected ID6 + 2 bitsframe ID + parity
Data1–8 bytessent by the slave (or master) that owns this ID
Checksum1 byte

The master sends every header according to its schedule table, so timing is fully predictable.

How it is used

A zone controller or body ECU acts as LIN master and talks to door modules, mirror and seat motors, HVAC flap actuators, rain/light sensors or ambient lighting. Because the schedule is fixed, timing is fully predictable.

When to use it

For low-cost devices with small, slow data. When an edge device needs more bandwidth, security or richer diagnostics, consider CAN FD or 10BASE-T1S instead.

Best practices

  • Keep schedules simple and verify worst-case response times.
  • Validate commands in the master — slaves trust whatever they receive.
  • Use LIN node configuration to avoid part-number variants of the same slave.

Common pitfalls

  • Treating LIN wiring as unreachable — physical access in doors and bumpers is easy.

What it means for your discipline

  • Networks & communication Core

    Designs LIN schedules, frame IDs and master/slave assignments; keeps schedules deterministic.

  • Hardware & silicon Core

    LIN slaves are tiny MCUs or ASICs with integrated transceivers — cost per node is the main driver.

  • Base software Partial

    The LIN master runs in an ECU or zone controller (AUTOSAR LinIf/LinSM); slaves often run minimal firmware.

  • Cybersecurity Partial

    LIN has no security. Slaves are protected by keeping LIN wiring internal and by the master validating commands.

  • Diagnostics & lifecycle Partial

    LIN supports simple diagnostics and node configuration through the master.

No direct stake: E/E architecture · Functional safety · HPC & application software · Software update & OTA

Where it sits in the software stack

Generic layered software of a central HPC (application processor with hypervisor, plus a safety island) and of a classic MCU-based ECU (AUTOSAR Classic). Highlighted modules matter for this topic. Click any module to open its page.

HPC · application processor (MPU) and safety island (MCU)
  • Classic RTE & COM — Runs LIN interface and state management when the safety island acts as a LIN master.
  • MCAL — Drives the LIN controller to send scheduled headers and exchange responses with local sensors and actuators.
MCU-based ECU · AUTOSAR Classic
  • ECU abstraction — LinIf executes schedule tables and connects upper communication layers to the LIN driver.
  • Microcontroller abstraction (MCAL) — Controls LIN frame transmission, reception and hardware sleep and wake-up operations.
  • Application layer — Validates actuator commands and interprets sensor values exchanged with LIN nodes.