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.
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.
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.
Three issues come up on almost every programme we support:
| 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 |
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:
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:
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.
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.
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.
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.