Most general-purpose controllers force a trade-off: enough I/O to be useful, or fast enough...
Bridging CAN and LIN in EV and Hybrid Architectures: A Practical Integration Playbook
Most hybrid and electric vehicle architectures don't run on one network protocol — they run on at least two. CAN handles the mission-critical, high-speed traffic; LIN handles the low-cost, low-bandwidth subsystems; and the integration work sits in between. Get that bridge wrong and you end up with duplicated wiring, scattered microcontrollers, and a gateway that's harder to service than the vehicle it's installed in. Get it right, and one controller can do the job of several.
At EMB Power, as the exclusive UK and EU partner for New Eagle's Raptor platform, this is engineering work we do every week for automotive, marine, commercial vehicle and off-highway clients. Here's the practical playbook we use.
Why CAN and LIN Still Split the Vehicle Network
Hybrid and EV platforms rely on distributed control: dozens of electronic control units across the powertrain, battery system, body electronics and user interface all need to talk to each other, but not all of them need to talk at the same speed or cost.
- CAN is the high-speed, error-resilient backbone. Classic CAN (ISO 11898-2) runs up to 1 Mbit/s, which is why battery management, traction control and charging controllers depend on it for real-time, mission-critical data.
- LIN is the low-cost, lower-bandwidth option — up to 20 kbit/s under ISO 17987 — built for simple actuators and sensors like interior lighting, seat modules and climate control, where flexibility matters more than raw throughput.
The practical problem is that almost no modern vehicle runs one protocol end to end. Efficient system integration depends on bridging the two cleanly — not bolting them together after the fact.
Where CAN/LIN Integration Actually Breaks Down
Three issues come up on almost every programme we support:
- Inter-network communication. CAN-dominant and LIN-dominant sub-systems aren't protocol-agnostic. Message structure, timing and priority differ between them, and each domain has its own rules for error handling and update rates.
- Scalability. Projects that move from prototype to production tend to grow — two CAN buses become four, a new LIN sub-network gets added for a feature that wasn't in scope six months ago. If the architecture can't expand without a redesign, that growth gets expensive fast.
- Development effort. Hand-written embedded code and manual calibration don't scale well across multiple protocol domains. Teams need a way to accelerate the work without losing control of it.
| Protocol | Typical role | Max speed |
|---|---|---|
| CAN (ISO 11898-2) | Battery management, traction control, charging | 1 Mbit/s |
| LIN (ISO 17987) | Lighting, seating, climate actuators | 20 kbit/s |
How EMB Power Bridges the Two with Raptor Hardware
The Raptor suite of control modules — supplied and supported exclusively in the UK and EU by EMB Power — is built for exactly this scenario. The Raptor BCM48 body control module, for example, ships with multiple CAN and LIN interfaces on one unit, so a single gateway can bridge both domains instead of running separate hardware for each.
In practice, that means:
- Multi-bus support on one module, cutting wiring complexity and the error risk that comes with it.
- Automotive-grade ruggedness — the same hardware carries a project from early R&D through to production, so there's no re-spec at the point where it matters least.
- Pre-configured harnesses and connector kits, such as the Raptor Power CAN1 Harness and the Raptor Programming Harness for BCM48, which take the labour-intensive wiring and setup work off your engineers' plates.
- Configurable gateway logic, so message routing, translation and security can be tailored to the specific vehicle programme rather than forced into a generic template.
Building the Gateway Logic in Raptor-Dev
Hardware is only half of it. Raptor-Dev is where EMB Power's controls engineers build the gateway logic itself, in a model-based MATLAB/Simulink environment rather than hand-written code:
- Drag-and-drop CAN and LIN blocks to map, filter or merge messages between protocols, cutting the manual coding errors that creep in with hand-rolled gateways.
- Generated, production-intent code that can be flashed and calibrated in the workshop or over the air.
- Built-in UDS and J1939 diagnostics, so field diagnostics, emissions compliance and aftersales servicing slot into the same workflow rather than needing a separate toolchain.
The net effect is faster iteration and more confidence in both safety and reliability, without the lead time a fully hand-coded gateway usually demands.
A Practical Example: Climate Control Meets the Traction Battery
Take a plug-in hybrid with climate control and cabin comfort functions on LIN, and propulsion and battery management on high-speed CAN. A Raptor controller with both CAN and LIN interfaces can bridge the two directly — for example, letting cabin pre-conditioning logic activate heater or fan nodes over LIN in response to CAN commands from the traction battery system. That removes the duplicated wiring and scattered microcontrollers that a split architecture would otherwise need, and condenses the logic into one manageable, serviceable gateway.
Bench Tools That Make Integration Easier
Hardware and gateway logic still need to be tested before they go anywhere near a vehicle. The Kvaser Hybrid 2xCAN/LIN interface is a USB device built for exactly that: two channels that can each be configured independently as CAN or LIN, supporting CAN up to 1 Mbit/s (or 5 Mbit/s for CAN FD on a properly implemented physical layer) and LIN 2.2A up to 20 kbit/s — letting engineers simulate and debug both protocol domains from one device rather than juggling separate interfaces on the bench.
Power delivery matters just as much as data integration. A Multiplexed Power Distribution Module (MPDM) simplifies how power is distributed, protected and monitored across distributed ECUs — it's a smaller detail than the gateway logic, but just as important to a robust overall design.
Best Practices for a Smooth CAN/LIN Integration
- Map the network at project inception. Decide CAN and LIN domain boundaries before committing to hardware, so wiring constraints, latency and gateway needs are predictable rather than discovered late.
- Use production-grade, multi-bus hardware from the start. Modules that support both prototyping and final assembly avoid a costly re-spec partway through the programme.
- Iterate gateway logic in software, not hardware. Version-controlled model-based development lets the system evolve as requirements shift, without a hardware respin every time.
- Validate on the bench before the vehicle. Tools like the Kvaser Hybrid 2xCAN/LIN let you simulate and debug communication flows ahead of in-vehicle deployment.
- Plan for service and expansion up front. Choose harnesses and accessories that make it straightforward to service ECUs and add features later, rather than only solving for day one.
Why Work with EMB Power
As the exclusive UK and EU partner for New Eagle's Raptor and OpenECU toolchain, EMB Power pairs production-ready hardware with engineering support from a team that works across automotive, marine, commercial vehicle and off-highway programmes — not just one sector. Whether you're scaling an EV development programme, moving to modern embedded controls, or need help bridging CAN and LIN cleanly on your next build, get in touch with our engineering team for a tailored integration plan.