Vector CANalyzer

1. CANalyzer Overview

CANalyzer is a versatile analysis tool for ECU networks and distributed systems. It supports monitoring, analysis, and easy data transmission to supported bus systems. The tool's powerful basic functions and user programmability cater to a wide range of needs, from simple network analysis to complex debugging of intricate problems.

Figure 1: Standard configuration of CANalyzer for CAN system analysis.

1.1 Features/Advantages

CANalyzer offers intuitive operation via a graphical block diagram. It displays bus data flow in various evaluation windows via a PC interface and logs it to files. The system is parameterized within this block diagram. Functional blocks such as filters, generators, and replay blocks can also be inserted and configured here.

1.2 Application Fields

CANalyzer is suitable for all applications. It is ideal for a wide range of uses, from simple network analysis to advanced emulation systems. For example, a replay block can be inserted into the transmit branch to play back bus system data traffic previously recorded. Output filters can also be added to prevent certain data traffic from being transmitted. This creates an ideal test environment for ECU testing.

Other use cases for CANalyzer include:

• Bus module emulation
• Creation of simple remaining bus simulation and test sequences
• Gateway between two buses for message manipulation functions
• Logging of critical phases using programmed triggers
• User-specific online evaluation via text message display
• Verification of simple ECU diagnostic functions

1.3 Bus Systems and Protocols

CANalyzer offers various options and can be combined with different bus systems and CAN base protocols as needed. Supported bus systems include: CAN, CAN FD, LIN, MOST, FlexRay, J1708, Ethernet, K-Line, A429, WLAN, AFDX®. Higher-level protocols for CAN include: J1939, CANopen, CANaero. Please consult for other protocols. Details on options are available on the Vector website.

1.4 CANalyzer Grades

• CANalyzer fun: The fun (Fundamental) version is ideal for simple analysis tasks and provides access to all standard interactive functions. However, programming functions, diagnostic testers, and control panels are not available.
• CANalyzer exp: The exp (Expert) version is suitable for almost any standard application and allows unrestricted use of all functions and extensions, except for creating CAPL programs.
• CANalyzer pro: The pro (Professional) version offers unrestricted use of all functions and extensions. This grade covers all applications, from simple monitoring of bus traffic to complex analysis and stimulus input for multi-bus systems.

1.5 System Requirements

Note: CPU clock speed significantly impacts CANalyzer performance. Virtual OS are excluded. Running on virtual machines is possible but not tested. Virtualization may cause delays in Vector hardware operation.

1.6 Further Information

• Support/Download: Demo versions of CANalyzer are available for download from the Vector website. These demo versions include sample configurations for various applications and help for all CANalyzer functions.
• CANalyzer Function Matrix: For details on CANalyzer grades, channels, and supported bus systems, please refer to the datasheet "CANoe/CANalyzer Function Matrix".

2. Functions

CANalyzer's basic functions support a wide variety of applications. These include:

• Displaying bus data traffic in a trace
• Graphical and text display of signal values
• Interactive transmission of predefined messages
• Transmission of messages recorded in log files
• Diagnostic communication compliant with KWP2000 and UDS, enabling use as a full-fledged diagnostic tester
• Message statistics
• Bus load and bus error statistics
• Replay of message logs or offline evaluation
• Generation of bus errors
• Intuitive interface with flexible docking concepts and a user-friendly menu structure
• Support for new Vector hardware: VN1610 (2-channel CAN), VN1611 (2-channel CAN and LIN/K-Line), VN1630A (4-channel CAN and LIN/K-Line), VN1640A (4-channel CAN and LIN/K-Line).

2.1 Special Functions

Key features of CANalyzer's functions include:

• Simple and intuitive user control concept
• Interactive creation of stimulus input and test sequences using the Visual Sequencer
• User programming with CAPL
• Support for various bus-specific function blocks
• Diagnostic functions: Parameterization of diagnostic communication using ODX 2.0.1/2.2.0, MDX 2.0/3.0, CDD formats. Basic diagnostic editor for defining simple diagnostic services. Support for physical and functional addressing. On-board diagnostic tester for quick execution. Diagnostic observer for UDS and KWP2000 based on parameterizable diagnostic databases. Transport protocol observer for ISO/DIS 15765-2. Support for DoIP and HSFZ.

2.2 Database Support

CANalyzer supports databases based on DBC (CAN), LDF (LIN), XML (MOST), FIBEX (FlexRay), and AUTOSAR System Description (CAN/FlexRay/Ethernet). It also supports diagnostic database files like CDD (CANdelaStudio), ODX 2.0.1/2.2.0 (PDX files), and MDX 2.0/3.0. CANalyzer displays information from these databases as symbols, which can be used in CAPL and other applications.

3. Analysis and Stimulation Input

The core of CANalyzer's analysis is the data flow from the data source to its display and logging. Filters can be integrated to define which data to consider during analysis and which to ignore. Various stimulation options allow for checking data traffic.

Key Features:

• Easy analysis window setup via drag-and-drop. Messages and signals can be copied or moved between analysis windows.
• Multiple instances of the same window type (e.g., Graphic Window) can be used in the data flow for simultaneous analysis.
• Logging can be started and stopped directly from the status bar with a mouse click.

3.1 Analysis Windows

CANalyzer includes the following windows and blocks:

3.1.1 Measurement Setup

The Measurement Setup allows graphical configuration of the data flow. This includes defining data sources (online/offline), inserting analysis windows, inserting CAPL program nodes, inserting filters, inserting trigger conditions, and data logging.

Figure 2: Measurement setup using an online data source.

3.1.2 Trace Window

The Trace Window lists bus activities like message and error frame transmissions. It displays individual signal values for each message. Features include inserting filters, hiding unchanged data, highlighting events, setting markers, displaying statistics, and logging data.

Figure 3: Trace Window with block filter active and markers set.

3.1.3 Graphic Window

The Graphic Window displays signals, environment data, and diagnostic parameters as curves. It supports measurement markers, difference markers, setting markers, displaying measurement statistics, and X/Y mode. Data can be logged directly from the Graphic Window.

Figure 4: Graphic Window with markers set.

3.1.4 Scope Window

The Scope Window graphically displays bus-level measurements and is used for protocol error analysis. It supports trigger settings, measurement analysis, signal comparison, data logging, measurement cursors, global markers, and eye diagrams.

Figure 5: Scope Window displaying an eye diagram.

3.1.5 Data Window

The Data Window displays signal values, system variables, and diagnostic parameters in various formats. It supports displaying raw or symbolic values, exponential notation, and min/max values. Data can be logged to MDF binary format.

Figure 6: Data Window displaying values in various display types.

3.1.6 Statistics Window

The Statistics Window displays statistical information about measurement bus activities (CAN, LIN, FlexRay). It shows bus load, burst counters/rates, frame counters/rates, and controller status. Users can view statistics for individual channels or all channels and adjust the update interval.

Figure 7: CAN Statistics Window displaying statistics for one channel (CAN 1).

3.1.7 Output Window

The Output Window displays system messages and user-defined output from CAPL. It allows filtering output by source, logging output to files, and copying to the clipboard. It also notifies of warnings and error messages.

Figure 8: Output Window displaying system messages and CAPL output.

3.1.8 Map Window

The Map Window integrates GNSS information with maps, supporting Car2x information when the Car2x option is used. It displays GNSS data and maps in analysis windows and allows offline replay of recorded GPS data. The map window displays the vehicle's position and the target route on the map, enabling analysis of measurement data considering geographical conditions.

Figure 9: Map Window.

3.1.9 Interactive Generator

The Interactive Generator allows defining messages and setting corresponding signal values, facilitating bus stimulus. Messages can be defined manually or via databases. Signals within messages can be modified, and signal curves can be defined using the integrated signal generator. It supports Layer 7 protocols like J1939 and GMLAN.

Figure 10: Interactive Generator displaying configured messages and their signals.

3.1.10 Trigger and Filter

Triggers and filters react to specific bus events, reducing the amount of data displayed or logged. Examples include error states, messages, signals, and signal changes. Complex system states can be combined using logical operators. Filters can be used in measurement setup, trace windows, and at the hardware level (acceptance filters).

3.1.11 Logging/Replay

CANalyzer allows data logging for later analysis and replay. Replay blocks can be used to replay recorded measurement sequences. Log blocks record bus traffic in BLF and ASCII formats, enabling offline replay.

3.2 Data Interpretation

CANalyzer includes an observer for the ISO/DIS 15765-2 transport protocol, interpreting transport protocol messages and displaying them in the Trace Window. It also supports diagnostic interpretation based on KWP2000, UDS, or OEM-specific databases like CANdelaStudio (CDD), ODX/PDX, and MDX files. Basic diagnostic descriptions defined in CANalyzer can also be used for diagnostic interpretation. In addition to the Trace Window, individual diagnostic parameters can be displayed in the Graphic Window and Data Window.

Figure 11: Trace Window displaying diagnostic data using analysis filters and diagnostic database files.

3.3 Offline Evaluation

Logged message traffic can be evaluated in offline mode using all CANalyzer functions. This facilitates analysis of extensive recordings, even from a desk. Multiple log files can be used, combined chronologically based on timestamps. Log files can be imported directly into the Trace Window for immediate analysis. Offline mode directly supports log file formats from Vector's GL1000/GL2000/GL3000/GL4000 loggers and CANlog, reducing pre-analysis conversion steps.

3.4 Export Function

The export function in Log and Trace Windows, as well as the Graphic Window, allows converting recorded log files or window content into other file formats (e.g., *.csv). When exporting log files, individual signal information is extracted from message-oriented logs.

3.5 Integrated Desktop

CANalyzer often involves many open analysis windows. To manage this, it features an integrated desktop function allowing switching between virtual desktops via page tabs. Open windows can be distributed across multiple desktops, and analysis information can be classified by work process or topic.

3.6 Start Values

The Start Values Window allows pre-assigning values to system variables at the start of a measurement. Start value lists can be exported to or imported from files, enabling easy assignment of simulation parameters using diverse start value sets.

Figure 12: Start Values Window.

3.7 Symbol Mapping

The Symbol Mapping dialog allows mapping system variables. When the source value changes during a measurement, the corresponding variable's value is automatically set. Linear conversion formulas can also be applied.

Figure 13: Mapping dialog.

4. Diagnostics

CANalyzer can transmit predefined standard diagnostic services for KWP2000 or UDS. Diagnostic parameters can be defined and assigned Local IDs (LIDs). ECU information can be quickly and easily read from the diagnostic console.

Supported concepts and functions include:

• Support for diagnostic database formats for KWP2000 and UDS (ISO 14229): ODX 2.0.1/2.2.0 (PDX files), MDX 2.0/3.0/4.0, CANdelaStudio (CDD).
• Diagnostic/ISO-TP configuration dialog allows modifying key diagnostic communication parameters (transport layer and diagnostic layer).
• Basic diagnostic editor for quickly defining simple diagnostic services when diagnostic database files are unavailable (supports CAN, LIN, FlexRay, Ethernet, K-Line).
• Interactive diagnostic tester using the diagnostic console and fault memory window with security DLLs.
• Interactive variant coding window for reading, writing, and comparing variant coding data, considering security mechanisms.
• Diagnostic parameter window for sending periodic or interactive diagnostic requests and displaying parameters from diagnostic responses.
• Configured OBD-II tester and diagnostic console/fault memory window for OBD-II.
• Support for multiple addressing methods (Normal, Extended, Normal Fixed, Mixed) and addressing types (Functional/Physical).
• Analysis of service and parameter-level diagnostic communication in Trace Window, Data Window, and Graphic Window (symbolic display based on diagnostic database files).
• Display of protocol errors in the Trace Window.
• Panel-based display of diagnostic parameters and stimulus input to ECUs.
• Support for major automotive network types: CAN, LIN, FlexRay, Ethernet, K-Line.
• Support for DoIP, HSFZ, DoSoAd.
• Recording and replay of diagnostic sequences using macros.

Figure 14: Diagnostic Console and Fault Memory Window. Figure 15: Diagnostic Parameters Window.

Figure 16: Basic Diagnostics Editor. Figure 17: OBD-II Window.

Figure 18: Diagnostic/ISO-TP Configuration. Figure 19: Trace Window for diagnostic communication.

5. Programming

5.1 CAPL Interface

The CAPL (Communication Access Programming Language) programming language significantly extends CANalyzer's capabilities. CAPL features:

• Easy to learn, based on the C programming language.
• Complete event control on behalf of the user during operation.
• Symbolic access to all data information, including messages and signals, with physical values available.
• Language extensions via special functions for quick problem-solving in various scenarios.
• Flexible extension with external libraries.

5.1.1 C-like Syntax

Standard scalar data types and arrays are supported (1, 2, 4, 8-byte types, and 8-byte floating-point types). Assignment, arithmetic operators, and loop flow control adhere to C syntax.

5.1.2 Event-Driven Control

CAPL is an event-driven programming language. Compared to C, CAPL uses predefined event handlers (event procedures) that execute when specific events occur (e.g., timer events triggered by hardware or CANalyzer's internal timer).

Examples of event handlers:

5.1.3 Symbolic Access

Signal values are accessed based on physical values, independent of the message's data content, as configured in the database.

5.1.4 Application-Specific Language Extensions

CANalyzer offers various functions tailored to daily development tasks. It can be used for online or offline analysis of measurement results. Simple tasks include counting event occurrences or performing calculations based on signal content.

5.1.5 CAPL Browser

The CAPL Browser serves as more than just a CAPL program editor; it supports building advanced development environments. Features include code writing assistance (auto-complete, syntax check), configurable syntax highlighting, distinct tabs for syntax, collapsible tree view for event handlers and function references, search and replace functionality, online help for functions, and direct navigation from errors to source text. Database objects are also accessible via the CAPL Browser.

Figure 20: CAPL Browser displaying CAPL program, event procedures, and network symbols from the database.

5.2 Visual Sequencer

The Visual Sequencer allows graphical configuration of behavior sequences without programming. It enables setting variables and signals, sending CAN/LIN frames or diagnostic commands, waiting for specific events, checking values, and defining repetitive structures. It is ideal for testing heterogeneous systems and stimulating ECUs.

Figure 21: CANalyzer's Visual Sequencer for creating simple test and stimulus sequences.

6. Panels

Panels are used to graphically display signal or variable values and modify them using controls like sliders or pointers. They can also display analysis data from CAPL programs or transfer values to control CAPL programs. The Panel Designer allows easy creation of panels, linking symbols and controls via drag-and-drop, and configuring individual panels and controls using the Properties Window. Various layout functions are available for optimal arrangement.

Figure 22: User-defined panel displaying signal and variable values.

7. Software Interfaces

A unified COM (Component Object Model) server allows external applications to control measurement sequences and exchange data for analysis and evaluation of observed bus traffic. Commonly used programming/scripting languages include Visual Basic, Visual Basic for Applications, C++, and C#. CANalyzer's COM interface provides functions for simulation control, starting/stopping measurements, loading/creating configurations, adding databases/blocks, accessing CAPL functions, and compiling CAPL nodes.

Example Visual Basic Scripts are provided for starting measurements and opening configuration files.

8. Network Interfaces

CANalyzer supports all network interfaces provided by Vector, including PCMCIA, USB 2.0, PCI, PCI-Express, and PXI interfaces, along with bus transceivers, enabling optimal bus access for all use cases.

Figure 23: Overview of Vector hardware.

9. Option Scope

Option Scope is a high-performance USB oscilloscope hardware solution integrated with CANalyzer. It displays as an analysis window within CANalyzer, featuring views for setup, bus level, and protocol decoding. Supported hardware includes Vector PicoScope 5444B-034 and 5242B-034, offering multiple input channels for CAN/CAN FD/FlexRay and LIN. Synchronization with Vector's network interfaces ensures accurate triggering.

9.1 Application Fields

The combination of USB oscilloscope hardware and CANalyzer enables efficient protocol error analysis. Bus-specific triggers and CANalyzer's time synchronization help discover protocol error causes much faster than traditional oscilloscopes.

Figure 24: Detailed analysis of CAN FD frames/errors at the physical and logical levels using the Scope Window.

9.2 Key Features

• Compact, portable oscilloscope solution using USB-connected hardware.
• Simple bus connection via Vector Scope Bus Probe.
• Oscilloscope functions optimized for bus analysis, including predefined triggers for bus errors and specific events, synchronized bus and I/O signal recording, and protocol error (CAN error frame) decoding.

9.3 Supported Protocols

Supports bus systems: CAN, CAN FD, FlexRay, LIN.

9.4 Supported Oscilloscope Hardware

• Vector PicoScope 5444B-034: 200MHz bandwidth, 500MS/s sampling rate, high-precision USB oscilloscope with 4 bus signal input channels (CAN/CAN FD/FlexRay x 2 or LIN x 4).
• Vector PicoScope 5242B-034: 60MHz bandwidth, 500MS/s sampling rate, high-precision USB oscilloscope with 2 bus signal input channels (CAN/CAN FD/FlexRay x 1 or LIN x 2).
• Connection via Vector Scope Bus Probe and D-Sub connector.
• Vector Scope Y-Trigger Cable enables internal triggering via sync lines of Vector network interfaces, as well as external triggering.

9.5 Oscilloscope Software

In CANalyzer, Option Scope is displayed as a new analysis window including setup, measurement, bus level, and protocol decode views. Features include easy sampling rate setting based on bit rate, automatic adjustment of waveform acquisition time, adjustable pre/post trigger times, and support for multiple oscilloscope devices.

9.5.2 Trigger Functions

Supports single/repeat trigger modes, manual triggers via toolbar or CAPL functions. Simple triggers include frame-based (ID or ID range) and protocol error-based triggers. Complex triggers can be defined using AND/OR conditions, external signal edge/pulse triggers, and CAPL COM interface for trigger condition settings.

9.5.3 Analysis Functions

Detailed decoding of frames with protocol errors at the bit level. Display of timestamps and voltage values at each sampling point. Synchronized trace view (data link layer logic) and diagrams (waveforms), with diagrams showing trace view signal encoding. Time synchronization with Trace Window, Graphic Window, and State Tracker.

9.5.4 Offline Functions

Even without an Option Scope license, Scope Window functions are available in offline mode for displaying and analyzing measured data. Features include overview and management of scope measurement data, automatic display of new measurement data, eye diagram analysis with user-configurable bit masks, and export/import of scope measurement data in various formats (binary *.csf, ASCII *.csv, MATLAB *.mat), and eye diagram export/import (*.ceye).

10. Training

Vector offers training courses for CANalyzer, including on-site training at customer locations. For details and schedules, please visit the Vector website: https://vector-academy.com/vj_training_jp.html