The 3 Most Common CANalyzer Examples with Tips for Users
There are different possible application areas of CANalyzer. To simplify your work, we guide you here through 3 of the most common application examples. You will get simple yet effective tips:
- Typical pitfalls & how to avoid them
- What your optimal CANalyzer tool environment might look like
Let´s start: What is your task?
1. Analysis and Monitoring of Network Traffic
You monitor the network traffic and make use of the comprehensive analysis possibilities of CANalyzer, such as the Trace Window or Graphics Window or Logging. You might be interested not only in CAN but also in other network systems such as LIN, FlexRay or Ethernet.
Avoid these pitfalls:
Data of different network types are not time-synchronized because they originate from different tools. To put this data into a sequential context is time-consuming and error-prone.
Data from different tools exist in proprietary data formats.
What your Vector solution looks like:
Make use of the multi-bus capability of CANalyzer, which correlates all measured events with respect to simulation time – independent of the respective network type.
2. Implementation of Higher Protocols and Analysis of Log Files
- You implement higher protocols such as ISO Transport Protocol, KWP 2000, or UDS in your ECU.
- You analyze log files of test drives.
Avoid this pitfall:
Time-consuming and error-prone analysis of protocol traffic based on raw data.
What your Vector solution looks like:
Make use of the various protocol observers of CANalyzer. They prepare the protocol traffic and represent it symbolically in the analysis windows. This also works when recorded log files are played offline.
3. Development of ECUs
You develop an ECU and test its software by putting the ECU into a defined state. You would like to bring your system to its limits. To do so, you increase the bus load incrementally. You would like to evaluate the signal quality of your CAN or LIN frames or debug and validate conformity tests.
Avoid these pitfalls:
Using different tools for the different tasks leads to complex system setups that are prone to errors.
It takes time to manually synchronize data and measurement results of different tools and the result is prone to error.
What your Vector solution looks like:
Besides comprehensive analysis possibilities, CANalyzer also provides various types of stimulation of network traffic. Use its Visual Sequencer, the Interactive Generator, or CAPL programs for this. For the analysis of frames on the physical level, on the other hand, the CANalyzer Option .Scope, which time-synchronizes all events, is ideal.
Play the Easy Ball !
