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.
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.