LIN Bus: how it works and how to diagnose it correctly
LIN (Local Interconnect Network) is a low-cost, single-wire serial network used for sensors and actuators that do not require CAN bandwidth. Its simplicity does not make diagnosis automatic: you need to know who starts communication, what the waveform should look like, and which power supplies each node depends on.
LIN is not CAN: one wire, different diagnostic logic
LIN normally uses one data conductor referenced to ground. It is designed as a low-cost, low-speed network with rates up to about 20 kbit/s. BMW training material commonly shows 2.4, 9.6 and 19.2 kbit/s depending on the system.
Do not look for CAN-H and CAN-L. Do not expect two 120 Ω termination resistors or a 60 Ω equivalent reading. BMW specifically notes that CAN-style terminating resistors are not used on LIN because of its lower data rate. LIN uses pull-up biasing and single-wire transceivers instead.
Commander and responders: who talks, and when
Current ISO 17987 terminology uses commander and responder. Older BMW and workshop documentation often uses master and slave/secondary. The operating principle is the same: one main node schedules traffic and one or more subordinate nodes respond.
The commander/master begins each exchange by transmitting a header. The header contains the Sync Break, Sync Field and a Protected Identifier (PID). The response follows with up to 8 data bytes and a checksum. If you see a valid master header but no response after a specific identifier, focus on that responder, its power, ground, branch wiring or configuration.
What the LIN signal should look like electrically
The idle state is recessive: bus high, normally near system supply voltage. The active state is dominant: bus low, near ground. LIN is not a fixed 5 V logic signal; the high level follows the electrical system and transceiver design.
Recessive / idle / logic 1: line high, near VBAT.
Dominant / logic 0: line low, near GND.
Normal activity: bursts of pulses pulling the line from the high state toward ground.
A multimeter only shows an average value. Seeing 7 V, 9 V or 11 V while the network is active does not by itself prove the bus is healthy or faulty. Frame structure, amplitude, rise time and intermittent errors require an oscilloscope.
Sleep and wake-up: no activity may be normal
LIN is designed for low-power operation. A cluster can enter sleep and leave the line idle. A responder can issue a wake-up sequence to request activity again; BMW also documents this ability on subordinate LIN nodes.
Before concluding that the bus is dead, activate the correct system: open a door, command a mirror, move an HVAC flap, wake the relevant terminal state or run an actuator test in ISTA as appropriate. Testing a sleeping network and calling it faulty is a common diagnostic mistake.
Power and ground first; network diagnosis second
A LIN responder cannot reply if it is missing B+, wake/enable power or ground, even when the LIN wire itself is perfect. Before decoding traffic, verify:
- Battery condition and system voltage.
- Fuse and power supply to the commander/master.
- Power supply to the non-communicating responder.
- Ground voltage drop under load.
- Continuity of the LIN wire according to the wiring diagram.
- Shorts from LIN to ground or B+.
Voltage-drop testing still applies: seeing 12 V with no load does not prove the component can receive adequate current while operating.
Oscilloscope: the test that separates “voltage present” from “communication present”
With an automotive or isolated oscilloscope, reference the measurement to a known-good ground and observe the LIN conductor. A healthy active network should show a stable high level at idle and bursts of low-going pulses during communication.
Look for a line stuck low, no activity, insufficient amplitude, low level that does not approach ground, slow return to the recessive state, noise, distortion or missing responses after repetitive headers. The header Sync Break is intentionally longer than a normal data byte and helps identify the beginning of a LIN frame.
What common fault patterns mean
LIN stuck near 0 V
Possible short to ground, damaged wiring, or a transceiver/node holding the bus dominant. Isolate branches or responders according to OEM documentation.
LIN high with no pulses
Could be normal idle, a sleeping commander, missing commander power/enable, or an open circuit between the probe point and the source.
Headers visible, no response
The master is attempting communication. Check responder power, ground, branch wiring, coding/configuration and the responder itself.
If normal bus activity returns when one faulty responder is disconnected, that is strong evidence that the node or its branch is collapsing the network. Disconnect modules only when the OEM procedure allows it, especially around safety systems.
BMW application: do not assume every “data wire” is LIN
BMW uses LIN across many subsystems: HVAC actuators, door/mirror electronics, rain/light/solar sensors and other devices depending on chassis. On F01 training documentation, for example, IBS data is sent to the DME over LIN.
But architecture changes by generation. On E70 training material, BMW shows the IBS, generator regulator, oil condition sensor and electric coolant pump on BSD, not LIN. This is a critical diagnostic point: identify the exact bus in the wiring diagram for the exact vehicle before testing.
Recommended diagnostic order
1) identify the vehicle, commander and responders; 2) read DTCs and module topology; 3) check the battery; 4) verify B+ and grounds; 5) study the wiring diagram and branches; 6) wake/activate the system; 7) use the multimeter only as a preliminary check; 8) inspect the waveform with an oscilloscope; 9) decide whether headers or responses are missing; 10) isolate the suspect node/branch using OEM procedures; 11) repair, clear DTCs and verify communication again.
Common mistakes to avoid
- Looking for 60 Ω as if LIN were High-Speed CAN.
- Condemning a responder without checking its power and ground.
- Treating a multimeter average as proof of a correct waveform.
- Testing a sleeping network and concluding there is no communication.
- Using a conventional test lamp directly on a data line.
- Disconnecting safety-related modules without OEM procedure.
- Assuming the IBS, alternator or sensor uses the same protocol on every BMW generation.
Conclusion
Professional LIN diagnosis separates three questions: does the node have power, is the commander producing headers, and is the responder answering? Once each question is verified with electrical measurements and an oscilloscope, a vague LIN fault becomes a demonstrable root cause.
Technical sources: ISO/LIN 2.2A and LIN-CIA; Microchip LIN physical-layer and data-link documentation; BMW Technical Training material covering LIN systems and network architecture. Electrical values described here are operating references; the vehicle wiring diagram, protocol version and OEM specification always take priority.