CAN Bus vs LIN vs FlexRay vs Automotive Ethernet Compared
By Alec J. Reviewed byJames M.
CAN bus vs LIN comes down to speed, cost and job: CAN is the fast two-wire backbone that carries engine, chassis and body messages, while LIN is a slower single-wire bus for simple switches and motors. FlexRay adds deterministic timing for safety systems, and automotive Ethernet moves the large data loads.
The short version:
- CAN: two wires, up to 1 Mbit/s on classic high-speed CAN, the workhorse for control messages.
- LIN: one wire, 1 to 20 kbit/s, cheap enough for window, mirror and seat modules.
- FlexRay: time-triggered, up to 10 Mbit/s, used where timing has to be guaranteed.
- Automotive Ethernet: 100 Mbit/s over a single twisted pair (100BASE-T1), for cameras and high-bandwidth links.
- Most vehicles mix them, joined by a gateway module.
What is the difference between CAN bus and LIN bus?
The short answer is that LIN is a cheaper, slower helper that sits underneath CAN.
- Wiring: CAN uses a twisted pair (CAN High and CAN Low). LIN uses a single wire referenced to ground.
- Speed: high-speed CAN runs up to 1 Mbit/s. LIN runs between 1 and 20 kbit/s.
- Who talks: any CAN node can transmit when the bus is free. LIN uses one master node that polls its slaves.
- Size: Texas Instruments’ guide to the high-speed ISO 11898 standard gives up to 30 nodes on a 40 m bus at 1 Mbit/s. The LIN specification says a LIN cluster should not exceed 16 nodes.
CAN arbitrates by message priority, so the most important frame always wins when two units start at once (Texas Instruments). That makes it a good fit for engine, gearbox, braking and body data that several modules need at the same time.
LIN was created for jobs that don’t need any of that. Its own specification lists a “low cost single-wire implementation” and “speed up to 20 kbit/s” among its aims (LIN Consortium). A door module, for example, might sit on the CAN bus and then run a small LIN cluster for the mirror motors and window switches. The master decides who speaks and when, which keeps the slave electronics simple.
Where does FlexRay fit in?
FlexRay arrived for systems where “probably on time” isn’t good enough.
CAN is event-driven. A message goes out when something happens, and the arbitration rules decide who waits. That works well, but the exact moment a lower-priority frame gets through depends on what else is on the bus. FlexRay takes the opposite approach. It runs on a fixed, repeating schedule, so every node knows in advance when its slot comes round.
NXP’s FlexRay transceiver data sheet describes the parts as “optimized for time triggered communication systems” with data transfer up to 10 Mbit/s (NXP Semiconductors). That’s ten times the top speed of classic high-speed CAN.
The catch is cost and complexity. FlexRay networks need careful scheduling at the design stage, and the controllers and transceivers cost more than CAN parts. You’ll find it on some vehicles for chassis and driver-assistance functions, but CAN remains far more common across the wider car, van and truck parc.
Why do vehicles now use automotive Ethernet?
Cameras, radar, large infotainment screens and software updates move far more data than CAN or FlexRay were built to carry.
Automotive Ethernet answers that with a physical layer made for vehicles. IEEE 802.3bw, approved in October 2015 and published in March 2016, defines 100BASE-T1: full-duplex 100 Mb/s Ethernet over a single balanced twisted pair (IEEE). One pair of wires instead of the four pairs in office Ethernet keeps weight and cost down.
Ethernet links are point to point, usually through a switch, rather than a shared bus. They tend to carry bulk data between a small number of powerful computers, while CAN and LIN still handle the everyday control signals underneath.
How do CAN, LIN, FlexRay and Ethernet compare?
| Network | Wires | Typical top speed | Access method | Typical jobs |
|---|---|---|---|---|
| High-speed CAN | Twisted pair | 1 Mbit/s | Event-driven, priority arbitration | Engine, gearbox, ABS, body control |
| LIN | Single wire | 20 kbit/s | Master polls slaves | Windows, mirrors, seats, switches |
| FlexRay | Twisted pair | 10 Mbit/s | Time-triggered schedule | Chassis and timing-critical functions |
| 100BASE-T1 Ethernet | Single twisted pair | 100 Mbit/s | Point to point via switches | Cameras, displays, high-bandwidth links |
CAN has also grown. CAN FD (flexible data rate) was introduced in 2012 to carry larger frames at a faster data phase, and work on CAN XL began at the end of 2018 (CAN in Automation). These newer versions narrow the gap with FlexRay and Ethernet for some jobs.
Which network will an installer actually work with?
For almost every aftermarket job, CAN.
Road speed, ignition state, reverse gear, park brake, lighting and door status are all carried as CAN messages on most modern cars, vans and trucks. Those are the signals that trackers, cameras, parking aids, beacons and security systems need. LIN clusters are usually buried inside a door or seat. FlexRay and Ethernet links are mostly reserved for the vehicle’s own safety and multimedia computers.
Two practical points follow:
- Don’t treat every twisted pair as CAN. A twisted pair could be FlexRay or an Ethernet link. Splicing the wrong one can cause faults that are hard to trace.
- Read messages, don’t cut wires. If you need a signal, take it from the network with an interface built for that platform rather than tapping a data line.
If you want a refresher on how messages and arbitration work, start with our guide to what CAN bus is.
Scorpion products across vehicle networks
Scorpion designs and manufactures CAN electronics in the UK. Our CAN bus integration range reads the vehicle network and turns messages into the plain outputs that accessories expect. A multi-output interface supplies speed, ignition, reverse, illumination and park brake from a single connection, with no cutting into the factory loom.
The same network knowledge goes into security. A CAN bus immobiliser such as the X-Series reads the vehicle’s own buttons and holds the car until the right sequence is entered.
Talk to us about integrating with vehicle networks
Not sure which network carries the signal you need? Tell us the vehicle and the job.
- Speak to us about your vehicle and the outputs you need
- CAN bus integration for the full range of interfaces
Frequently Asked Questions
Is LIN bus faster than CAN bus?
No. LIN runs between 1 and 20 kbit/s on a single wire, while classic high-speed CAN runs up to 1 Mbit/s on a twisted pair. LIN is used where low cost matters more than speed, such as window and mirror motors.
Why do cars use both CAN and LIN?
Each suits a different job. CAN carries the shared control messages that many modules need quickly. LIN connects simple local devices to one master module at lower cost, so the expensive CAN hardware is only used where it earns its place.
Is FlexRay replacing CAN?
Not across the board. FlexRay is used for timing-critical functions on some vehicles, with data rates up to 10 Mbit/s, but CAN and its faster CAN FD version remain the most widespread control network in cars, vans and trucks.
What is 100BASE-T1 automotive Ethernet?
It is the Ethernet physical layer defined by IEEE 802.3bw, giving 100 Mb/s full-duplex links over a single twisted pair. Vehicles use it for cameras, displays and other high-bandwidth connections between computers.
Which vehicle network do aftermarket interfaces read?
Almost always CAN. Road speed, ignition, reverse, lighting and park-brake status are broadcast as CAN messages on most modern vehicles, so a CAN interface can provide those outputs without cutting into the factory wiring.
Speak to our team
Questions about vehicle security, tracking or fleet telematics? Our UK team will point you to the right product for your vehicle or fleet.
Related Products
View all products →- CAN bus
- LIN bus
- FlexRay
- automotive Ethernet
- vehicle electronics
Alec J.
Software Engineer at Scorpion Automotive
Alec J., a Software Engineer at Scorpion Automotive in Chorley, covers CAN bus, vehicle electronics and electric vehicles.
Reviewed by James M., Technical Director at Scorpion Automotive