CAN FD's higher data-phase bit rates make a network faster, but they also make it far less...
Turning CAN Traffic Into Answers: A Practical Vehicle Data Logging Workflow With Raptor VeeCAN 320 and Kvaser Tools
Reliable vehicle data capture comes down to one question: can your logger survive the environment it's deployed into and still hand you clean, decodable signal data afterwards? At EMB Power, as New Eagle's exclusive UK and EU partner for the Raptor toolchain and a Kvaser qualified sales representative, we build CAN data acquisition workflows for automotive, EV, marine and off-highway engineering teams across the UK. Here's a practical, field-tested workflow combining the Raptor VeeCAN 320 data logger with Kvaser CAN interfaces — from in-vehicle capture to post-process analysis.
Why Reliable CAN Data Capture Matters
CAN remains the backbone of vehicle communication, and as control networks grow more complex, data capture has to do more than catch the occasional fault. Engineering teams need it for characterising system behaviour, validating component changes, and refining embedded controls algorithms — not just troubleshooting after the fact. That means the tools doing the capturing need to be tunable, repeatable and scalable across a development programme, whether the platform is ICE, hybrid, fully electric or autonomous.
What the Raptor VeeCAN 320 Brings to the Workflow
The VeeCAN 320 is built for in-vehicle deployment rather than bench-only use. Per New Eagle's published specification, it offers a 3.5-inch, 320×240 colour display rated to 700 NIT brightness, two CAN channels, 7 analog inputs, 2 digital inputs and 4 outputs, with a USB port that supports onboard data logging. It's rated for -40°C to 70°C operation in a rugged, environmentally sealed enclosure, and is programmed through the Raptor-Dev environment — the same toolchain used for the rest of a Raptor-based controls project. New Eagle's product page doesn't publish a specific logging storage capacity or ingress-protection rating, so confirm those details with EMB Power against your current build if they're critical to your application.
The live 3.5" screen is the detail engineers notice first in the field: it lets you confirm a test setup and spot gross communication errors before committing to a long test cycle, without needing a laptop tethered to the bench.
Where Kvaser Interfaces Fit: Leaf Light R v2 and USBcan Light 4xHS
The VeeCAN 320 covers autonomous, in-vehicle logging well, but bench-based and interactive diagnostic work is usually faster with a dedicated PC interface. Kvaser's tools are the standard here.
- Kvaser Leaf Light R v2: a rugged, single-channel USB-to-CAN interface, IP65-rated and specified for -40°C to 70°C operation, supporting High Speed CAN (ISO 11898-2) at up to 1 Mbit/s. It's a strong fit for lab debugging and shakedown testing where the interface itself needs to survive a harsher environment than a typical desktop accessory.
- Kvaser USBcan Light 4xHS: a 4-channel high-speed CAN interface on a single connector (with a splitter cable for four separate connections), galvanically isolated, supporting 50–1000 kbps and rated IP40 for -20°C to 70°C. The 4-channel count makes it well suited to projects running separate drivetrain, body and diagnostic CAN networks side by side.
Both interfaces run on Windows and Linux, and ship with Kvaser's free CanKing analysis software and the CANlib SDK, which supports C, C++, C#, Delphi and Visual Basic alongside a DBC Editor for decoding proprietary vehicle signals and J2534/RP1210C libraries used by common calibration tools. Neither currently lists CAN FD support, so a mixed CAN/CAN FD network needs that checked against your specific channel requirements before specification.
A Five-Step Workflow for Field Data Capture and Analysis
The same basic sequence applies whether you're running a short bench session or a multi-week fleet trial.
- Define objectives and select gear. Identify which CAN signals or networks matter — battery SoC, inverter temperature, HVIL status, torque commands — and confirm whether single or dual-channel logging is required. Use the VeeCAN 320 for autonomous in-vehicle logging, and a Kvaser interface for direct PC capture or interactive diagnostics.
- Install safely. Connect the logger to the vehicle's CAN harness with automotive-grade connectors, mount it securely, and always power down the vehicle before connecting new hardware to live network lines.
- Configure channels and DBC files. In Raptor-Dev, set up the project and specify which CAN channels, ID ranges and periodic signals to record. Load the correct DBC files to decode proprietary signals into engineering units, and set sampling rates appropriate to the signal (commonly 10–500 Hz for control signals, lower for diagnostics).
- Log and export. For road testing, the VeeCAN 320 logs autonomously via its USB-connected storage, with live signal viewing on its display for immediate validation. For short or interactive sessions, capture directly to a laptop with a Kvaser interface. Export in standard formats such as .csv or .asc for post-processing.
- Decode and analyse. Load the captured data into your analysis tools and decode with your DBC files. Engineers can plot trends — motor current against temperature, for example — flag fault-code triggers, or script custom filtering, with MATLAB or Excel commonly used for bespoke validation work.
Technical Specifications at a Glance
| Device | Role | Key specs |
|---|---|---|
| Raptor VeeCAN 320 | In-vehicle autonomous logging + live display | 3.5" 320×240 display, 2 CAN channels, USB logging, -40°C to 70°C, Raptor-Dev programmable |
| Kvaser Leaf Light R v2 | Bench / shakedown PC interface | 1 channel, up to 1 Mbit/s, IP65, -40°C to 70°C |
| Kvaser USBcan Light 4xHS | Multi-network bench capture | 4 channels, 50–1000 kbps, galvanically isolated, IP40, -20°C to 70°C |
Specifications based on published New Eagle and Kvaser product data as of November 2026; confirm current specification and lead times with EMB Power before finalising a design.
Practical Example: Diagnosing a Drivetrain Communication Fault
Consider a recurring drivetrain communication error on a prototype hybrid vehicle. Logging both the drivetrain and body CAN networks with the VeeCAN 320, then decoding with a Kvaser interface and DBC file, lets you graph transmission requests against actual torque outputs side by side. Timing mismatches or dropped packets that would otherwise take days of blind troubleshooting to isolate become visible in a single comparison — and give you a documented basis for an ECU or calibration adjustment.
Why EMB Power is Your Partner for Vehicle Data Capture
Specifying the right logger or interface is only half the job. As New Eagle's exclusive UK and EU Raptor partner and a Kvaser qualified sales representative, EMB Power supplies this hardware alongside the engineering support to get it working correctly the first time: channel and DBC configuration in Raptor-Dev, calibration workflow setup, and integration testing against the rest of your control system. Our engineers bring OEM automotive controls backgrounds to that integration work, across automotive, marine, commercial vehicle and off-highway projects.
Talk to EMB Power About Your Data Acquisition Workflow
If you're specifying a CAN data logging and analysis workflow for an EV, hybrid or autonomy programme, get in touch with EMB Power for current pricing, lead times and integration support on the Raptor VeeCAN and Kvaser ranges.