Trace formats
- PCAPNG, MDF4 and BLF
- The same format in the vehicle, on the bench and in the lab
- Copy stations for fast data offload and encrypted transfer
- Trigger- and event-based trace identification
Technical coverage
What we cover.
This is a coverage list. The exact configuration is agreed with your engineers in the conversation.
Vehicle networks
- Automotive Ethernet
- CAN, CAN FD and LIN
- FlexRay
- A2B audio
Camera and display links
- GMSL
- FPD-Link
- ASA Motion Link
- MIPI CSI-2
- APIX
Analog and digital I/O
- Digital and analog input and output
- Current measurement via shunts
- Contactless current clamps
- Voltage measurement on low- and high-voltage branches
Timing
- Time synchronisation across interfaces
- Audio timing analysis
- Live monitoring during capture
- Event recognition independent of full trace storage
Fleet and remote operation
- Fleet software in use from hundreds to thousands of vehicles
- Remote diagnostics and configuration
- Remote software updates
- Operation in hot and cold climates
Hardware grades
- Automotive-grade equipment for in-vehicle use
- Bench and rack equipment for static setups
- Extended temperature range for in-vehicle deployment
- Same interface coverage in every grade
Working with your stack
- Works alongside your existing tools
- Data usable in your analysis chain
- Vendor-neutral test strategy
- Tool-chain architecture on request
How the pieces fit
Capture, decide, deliver.
Capture converts the vehicle interfaces into standard trace formats.
The costs arise from the decisions behind it: which interfaces, which equipment grade, how much storage, and where the data goes.
We agree those decisions with your engineers before hardware is ordered. That is where most of the cost is saved.
PCAPNGMDF4BLFAutomotive EthernetCAN FDLINFlexRayA2BGMSLFPD-LinkMIPI CSI-2APIXASA Motion Link
Not sure whether your interface is covered?
Send the interface and the format you need. We answer with a yes, a no, or the path that gets you there.