Automated analysis for vehicle communication

Representation of CAN FD in different data layers: Logic layer / Physical Event Layer / Bit Layer

Automated analysis for vehicle communication

Those who design CAN FD networks for automotive applications know about the advantages of the CAN successor: the new system maintains existing CAN concepts such as bus arbitration, frame identification, event control etc., in order that specialists with it do not have to deal with new types of strategies.

Timing diagram of a CAN FD frame

However, the CAN FD development confronts network designers with some additional challenges, mainly attributable to the higher bandwidth in the data phase. CAN FD is noticibly more sensitive to unfavorable network topologies, electromagnetic interference sources and influences as well as wrong termination, for instance.

Front page of CAN FD vehicle communications white paper.

In order to realize robust networks, CAN FD designers must thoroughly deal with these effects which primarily take place on the physical layer.

This article presents a comprehensive solution that establishes a strict time-related reference between logical network analysis and events on the physical layer.

The full article is available here.

By Mirko Donatzer & Peter Decker, Vector Informatik GmbH

Representation of CAN FD in different data layers: Logic layer / Physical Event Layer / Bit Layer

CANoe and CNAalyzer are comprehensive software tools for development, test and analysis of individual ECUs and entire ECU networks. They support network designers, development and test engineers throughout the entire development process – from planning to system-level test.

Option .Scope is an integrated oscilloscope solution achieved by combining a 4-channel PicoScope 5444D with the standard Vector network interface. Up to 2 CAN FD or FlexRay networks or 4 LIN/sensor/IO signals can be simultaneously analyzed. The PicoScope hardware is synchronized with the network interfaces so that all scope measurements have the same time base as CANalyzer.

With bus specific trigger conditions and the CANoe time synchronization, you can find the cause of protocol errors much faster than with a separate network analyzer and oscilloscope.