LIN Bus, FlexRay, and Automotive Ethernet

CAN bus is the dominant vehicle network but it is not the only one. Modern vehicles use multiple network types optimized for different purposes. Understanding these networks helps you diagnose communication faults that do not involve the main CAN bus at all — and prevents you from wasting time testing CAN when the fault is on a completely different network.

Local Interconnect Network is a single-wire, low-speed network used for simple body functions — power mirrors, rain sensors, seat position motors, ambient lighting, and window switches. LIN is a master-slave system — one master module (usually the BCM) controls communication with multiple slave devices. Data rates are much slower than CAN — up to 20 kilobits per second compared to CAN's 500 kilobits. LIN signals are a single wire referenced to ground, swinging between 0 and 12 volts (battery voltage). Because LIN is single-wire and low-speed, it is cheap to implement but cannot handle the data volume or timing precision that CAN provides.

A LIN bus fault typically affects a single subsystem — one mirror stops adjusting, one window switch stops communicating, the rain sensor stops working. Because LIN is master-slave, check whether the master module (BCM) is communicating with the slave. Use a scope on the LIN wire — you should see digital pulses swinging between 0V and battery voltage. A flat line at battery voltage means the bus is stuck recessive — the master may not be sending commands. A flat line at 0V means the bus is shorted to ground — a slave device or the wiring is pulling the line down.

FlexRay is a high-speed deterministic network used in premium vehicles for safety-critical systems — active suspension, advanced braking, and steer-by-wire. It operates at 10 megabits per second — twenty times faster than high-speed CAN. FlexRay guarantees message delivery within a fixed time window, which CAN cannot do. This makes it suitable for systems where a delayed message could cause a safety hazard. FlexRay uses two channels for redundancy and is relatively rare compared to CAN — found primarily in BMW, Mercedes-Benz, and some premium platforms.

Automotive Ethernet is rapidly replacing CAN for high-bandwidth applications — ADAS camera data, surround-view systems, infotainment streaming, and over-the-air software updates. A single ADAS camera can produce 1 to 3 gigabits per second of data — impossible on CAN's 500 kilobit bus. Automotive Ethernet uses a single unshielded twisted pair at 100 megabits per second (100BASE-T1) or 1 gigabit (1000BASE-T1). Diagnosis requires understanding that Ethernet communication faults can cause ADAS failures, camera blackouts, and display malfunctions without setting traditional U-codes because the Ethernet network may not be monitored by the same diagnostic infrastructure as CAN.

A modern vehicle may have high-speed CAN for powertrain and chassis, a second CAN for body systems, LIN sub-networks for individual subsystems, and Ethernet for ADAS and infotainment. A gateway module translates data between networks — the powertrain CAN bus shares engine RPM with the body CAN bus through the gateway so the instrument cluster can display it. When diagnosing communication faults, identify which network the affected module lives on. A U-code from the ABS module while the engine and transmission communicate normally means the fault is on the chassis CAN bus or at the gateway — not the powertrain CAN bus. Knowing the vehicle's network architecture prevents you from testing the wrong bus.