--- title: "CANbus Intelligence for EV Controls: 5 Practices That Separate Resilient Architectures From Fragile Ones" description: Five CANbus practices that keep EV and hybrid control architectures diagnosable and safe, using Raptor ECUs and Kvaser tools, from EMB Power's engineering team. --- [Skip to content](https://blog.emb-power.com/canbus-intelligence-for-ev-controls-5-practices-that-separate-resilient-architectures-from-fragile-ones#main-content) ![EMB\_Power\_Logo](https://blog.emb-power.com/hs-fs/hubfs/EMB_POWER_logo-16x9-tp-1.png?width=250&height=140&name=EMB_POWER_logo-16x9-tp-1.png) Open main navigation Close main navigation - [Contact us](https://www.emb-power.com/contact-us) [Contact us](https://www.emb-power.com/contact-us) Oct 9, 2026, 10:15:32 AM # CANbus Intelligence for EV Controls: 5 Practices That Separate Resilient Architectures From Fragile Ones [EMB Power Team](https://blog.emb-power.com/author/emb-power-team) Share: [facebook-f icon](http://www.facebook.com/share.php?u=https://blog.emb-power.com/canbus-intelligence-for-ev-controls-5-practices-that-separate-resilient-architectures-from-fragile-ones) [linkedin-in icon](http://www.linkedin.com/shareArticle?mini=true&url=https://blog.emb-power.com/canbus-intelligence-for-ev-controls-5-practices-that-separate-resilient-architectures-from-fragile-ones) [Twitter icon](https://twitter.com/intent/tweet?url=https://blog.emb-power.com/canbus-intelligence-for-ev-controls-5-practices-that-separate-resilient-architectures-from-fragile-ones) [pinterest-p icon](http://pinterest.com/pin/create/link/?url=https://blog.emb-power.com/canbus-intelligence-for-ev-controls-5-practices-that-separate-resilient-architectures-from-fragile-ones) [envelope icon](mailto:?body=https://blog.emb-power.com/canbus-intelligence-for-ev-controls-5-practices-that-separate-resilient-architectures-from-fragile-ones) A CAN network that merely carries traffic isn't enough for a modern EV or hybrid programme — it needs to be diagnosable, fault-isolating and scalable from the first prototype build. At **EMB Power**, New Eagle's exclusive UK and EU partner for the Raptor toolchain, we build that intelligence in from the start of a controls project, pairing Raptor ECUs with Kvaser's CAN tools. Here are five practices we apply on every programme, and why each one matters. ## 1. Segment the Network Before You Need To A single flat CAN bus is the easiest network to wire and the hardest one to fault-find once a vehicle is in the field. Isolating critical domains — traction, battery management, safety systems — onto separate buses limits how far a fault can propagate and makes troubleshooting tractable later. A multi-bus module such as the **Raptor RCM112** is built for this: it offers 5 CAN FD channels, 2 LIN channels and Broad-R-Reach 2-wire Ethernet, so a dense, high-bandwidth architecture doesn't need a rack of separate gateway boxes to implement. Getting the segmentation plan right, and the bus loading and termination sums done properly, is worth doing at the architecture stage rather than retrofitting after the first bus-off event. ## 2. Build Diagnostics and Functional Safety In, Not On CANbus intelligence is about insight, not just connectivity. Raptor ECUs carry native support for UDS (Unified Diagnostic Services) and J1939-based diagnostic protocols, so fault management follows an established standard rather than a bespoke scheme that only one engineer understands. Equally important are the less visible safety features — watchdogs, safe-state outputs and secure bootloaders — that are part of the module rather than bolted on afterwards. Where the control strategy is developed in Simulink through **Raptor-Dev**, diagnostic logic can be built from the same native blocks as the rest of the model, which keeps it in the same review and test process as everything else. ## 3. Validate on the Bus Before You Trust It in the Field A well-specified ECU still depends on the team's ability to see what's actually happening on the network, particularly during bench validation and early field trials. This is where Kvaser's interfaces do the work: a **Kvaser Mini PCI Express 2xHS** or one of Kvaser's current Mini PCI Express CAN FD interfaces gives direct access to raw bus traffic, fault frames and payload content, for both development debugging and end-of-line checks. Kvaser's software suite logs that data automatically, which matters most on long-running field trials where diagnosing an intermittent fault depends on having the trace from when it happened, not just a description of the symptom after the fact. ## 4. Plan for Over-the-Air Updates and Automated Testing From Day One A modern EV controller is never really finished — calibration changes, feature updates and field fixes keep coming after the vehicle is in test or in service. Running **Raptor-Test** cycles against the compiled model as it evolves catches regressions while they're still cheap to fix, rather than after they've shipped. Raptor service dongles support in-field recalibration and diagnostics without pulling a module from the vehicle, and secure boot and authenticated firmware update mechanisms matter in their own right, since they're what stops an update path from becoming an attack surface. None of this replaces proper validation; it just means validation doesn't stop on the day a vehicle leaves the bench. ## 5. Don't Treat the Operator Interface as an Afterthought A well-architected network is wasted if nobody can read it at the point that matters. The **Raptor VeeCAN display range** — the compact VeeCAN 320 for bench and in-vehicle monitoring, and the touchscreen VeeCAN 800 for a full operator-facing HMI — puts live diagnostics, warnings and controls in front of the person who needs them, wired straight into the same CAN network. Blink CAN keypads add a tactile control surface alongside a display where a driver or technician needs physical controls rather than a touchscreen, without adding separate wiring runs. Specifying the interface alongside the control architecture, rather than after it, avoids the display becoming the one component that doesn't quite fit the rest of the system. ## RCM112 Communications Snapshot | Interface | Raptor RCM112 | | --- | --- | | CAN FD channels | 5 | | LIN channels | 2 | | Ethernet | Broad-R-Reach, 2-wire | | Safety rating | ASIL D capable | Specifications based on New Eagle's published RCM112 data as of 2026; confirm current specification and availability with EMB Power before finalising a design. ## Why Engineering Teams Work With EMB Power EMB Power is New Eagle's exclusive UK and EU supplier of Raptor control hardware and the Raptor-Dev model-based development toolchain, and now of the OpenECU range following New Eagle's 2026 acquisition of Pi Innovo. That gives UK and EU controls teams direct access to current Raptor and OpenECU hardware, engineering support from people who work with the toolchain daily, and the Kvaser interfaces needed to validate the network once it's built, rather than a generic reseller handoff. ## FAQ ### Do I need a separate CAN interface if my ECU already has diagnostic tools built in? Yes, in most cases. An ECU's native diagnostics confirm what the module itself is doing; an independent CAN interface such as a Kvaser device lets you see the raw bus traffic between modules, which is what you need when the fault is in the network rather than in a single node. ### Is network segmentation worth the extra wiring complexity on a smaller prototype programme? It scales down as well as up. Even a single-vehicle prototype benefits from isolating safety-relevant traffic from general telemetry, and a multi-channel module like the RCM112 means segmentation doesn't require extra gateway hardware. ### Can the VeeCAN displays and Blink keypads be added after the control architecture is already built? They can, but it's more work than specifying them alongside the architecture. Retrofitting usually means finding free CAN bandwidth and I/O for the interface after the fact, rather than allocating it as part of the original design. If you're architecting a CAN network for an EV, hybrid or off-highway controls programme, [contact EMB Power](https://emb-power.com/contact) to talk through the right mix of Raptor hardware and Kvaser tools for your project. [ECUs](https://blog.emb-power.com/tag/ecus), [Rapid Prototyping](https://blog.emb-power.com/tag/rapid-prototyping) [facebook-f icon](https://www.facebook.com/embpowerltd) [linkedin-in icon](https://www.linkedin.com/company/emb-power-limited/) [instagram icon](https://www.instagram.com/restomods_uk/) - [Products](https://www.emb-power.com/all-products) - [Hardware](https://www.emb-power.com/hardware) - [Controllers](https://www.emb-power.com/controllers) - [Displays](https://www.emb-power.com/displays) - [Data Loggers](https://www.emb-power.com/data-loggers) - [Telematics](https://www.emb-power.com/telematics) - [I/O Devices](https://www.emb-power.com/io-devices) - [Software](https://www.emb-power.com/software) - [Services](https://www.emb-power.com/services) - [Resources](https://www.emb-power.com/resources) --- [![EMB\_Power\_Logo](https://blog.emb-power.com/hs-fs/hubfs/EMB_POWER_logo-16x9-tp-1.png?width=250&height=140&name=EMB_POWER_logo-16x9-tp-1.png "EMB_Power_Logo")](http://www.emb-power.com) Ash Lea, Alderley Road, Chelford, Macclesfield, SK11 9AP UK Copyright © 2026, EMB Power Limited ```json { "@context" : "https://schema.org", "@type" : "BlogPosting", "author" : { "@type" : "Person", "name" : "EMB Power Team", "url" : "https://blog.emb-power.com/author/emb-power-team" }, "dateModified" : "2026-10-09T09:15:32.936Z", "datePublished" : "2026-10-09T09:15:32.000Z", "headline" : "CANbus Intelligence for EV Controls: 5 Practices That Separate Resilient Architectures From Fragile Ones", "mainEntityOfPage" : { "@id" : "https://blog.emb-power.com/canbus-intelligence-for-ev-controls-5-practices-that-separate-resilient-architectures-from-fragile-ones", "@type" : "WebPage" }, "publisher" : { "@type" : "Organization", "logo" : { "@type" : "ImageObject", "url" : "https://blog.emb-power.com/hubfs/EMB_POWER_logo-16x9-tp-1.png" }, "name" : "EMB Power Limited" } } ```