The LIN bus: half the car that never appears at the diagnostic port

A question everyone who buys an adapter reaches eventually: “why does the scanner see the engine and ABS but say nothing about the mirror that stopped folding?”

The answer is that a car has more than one network. And the one carrying most of the small electrics is not connected to the diagnostic port at all.

Two networks, two jobs

CAN is fast, robust, with arbitration and error checking. Two twisted wires, up to 1 Mbit/s, and any node may start transmitting on its own. Expensive per node.

LIN is a single wire, up to 20 kbit/s, with a strict master-slave hierarchy. A slave never speaks unprompted; it answers only when the master asks. Cheap to the point of indecency.

The split is obvious once you see it. Brakes need milliseconds and guaranteed delivery — that is CAN. A mirror actuator needs to receive “fold” once every few minutes — paying for CAN there makes no sense whatsoever.

CAN fundamentals, if you want the groundwork, are in their own article.

What lives on LIN

The list is longer than you expect:

• Window motors and mirror actuators.
• Rain and light sensors.
• Climate control flaps and actuators.
• The alternator regulator — yes, on modern cars a module decides the charging voltage, not the alternator.
• The battery state sensor on the negative terminal.
• Seat heating and seat adjustment.
• Steering wheel buttons.
• Door lock actuators.
• Humidity and air quality sensors.

In total, a typical modern car carries 10 to 30 nodes on LIN.

Why the OBD port cannot see them

The reason is architectural rather than a matter of equipment quality.

The diagnostic connector is physically wired to CAN. LIN does not reach it. Each LIN segment hangs behind its own master module: climate behind the climate module, mirrors behind the door module, the alternator behind the body control module.

So to learn what is happening on LIN, you have to ask the master. It is the only one that was there.

And there the limit appears: such a request is not described by OBD-II. The standard obliges vehicles to expose emissions-related data, and the state of a mirror actuator is not that. The mechanics of that limit are in supported PIDs.

What a LIN fault looks like from outside

The most common scenario: a symptom with no code.

• The mirror will not fold — no codes.
• Climate air comes from the wrong vents — no codes.
• The rain sensor stopped detecting rain — no codes.

Occasionally the master does report losing contact with a slave, and then a U-series code appears — usually in the body control module, U0140. But that is a secondary indication: the code says “my subordinate is silent”, and which one and why has to be established with other tools. Network codes are covered in the body control module guide.

The most useful practical case: the alternator

Here LIN affects even people who do not care about mirrors.

On modern cars the alternator’s voltage regulator is commanded over LIN. A module decides how much to supply right now: during acceleration charging is reduced for performance, during braking it rises to 15 V for recuperation, and with a full battery it drops to 12.5 V to save fuel.

The practical consequence: 13.2 V on a warm engine can be entirely normal. That is not an undercharging alternator, that is a module’s decision at that moment.

Which means diagnosing the charging system on such cars by voltage alone is wrong — you have to read it together with the driving state. The system is covered in battery and alternator diagnostics.

How LIN fails

With a single unshielded wire there are few weak points, but they are consistent:

• A break or corrosion in a connector. Most often in door conduits, where the harness flexes constantly.
• A short to ground or to power. This kills the whole segment: not one device stops working but every device behind that master.
• A dead slave node dragging the line low. The symptom is identical to a short.
• Moisture. A single unshielded wire strongly dislikes water in a connector.

The signature of a bus problem rather than a device problem: an entire group of devices failed at once. Not one mirror, but both mirrors plus the windows. One device suggests the device; a group suggests the bus or the master.

What this means in practice

Realistic expectations for consumer diagnostics:

• Engine, transmission, ABS, airbags — available, because CAN.
• Small body electrics — largely not.
• U-codes in the master module — the only hint that reaches the connector.

This is not a shortcoming of a particular app or adapter but a boundary of the architecture itself. Working with LIN needs equipment connected to the right segment and factory documentation.

The practical takeaway for an owner: if the symptom concerns comfort features and small electrics and the scanner is silent, the scanner is not broken. It is a different network.

In short

• A car has at least two networks: fast CAN and cheap LIN.
• The diagnostic connector is wired to CAN only.
• LIN carries small electrics: mirrors, windows, climate, alternator, rain sensor.
• The typical fault picture is a symptom with no code.
• A whole group of devices failing at once points at the bus, not the device.

Download the app — codes from every CAN system, network U-codes from master modules included, are read with an ELM327 adapter over Bluetooth SPP on Android.