• Symbolic trigger setup, decode, and data extraction and graph setup using (customer-supplied) DBC file
• Error-frame red color decode highlight
• DATA trigger pattern setup can be less than full bytes/nibbles and can be spread across bytes
• Conditional ID definition (<, <=, =, >, >=, <>, IN RANGE, OUT of RANGE)
• Supports 29-bit GM CAN Priority ID, Source ID, Parameter ID trigger and decode

CAN and CAN FD Symbolic decode options both support use of a customer-supplied DBC file for signal selection for triggering and CAN to Value serial data DAC setup. Additionally, the decode annotation is in Symbolic format as well, with complete message and signal structures described.

Symbolic (DBC) File Support

CAN remains the most used vehicle serial data bus. Many vehicle bus software architectures are very message dense, and data for a single message is spread across multiple data bytes. The hexadecimal and measurement toolsets permit isolation of specific bit-level data patterns in one or more data bytes, e.g., data location in bits 17-28 in data bytes 3, 4, and 5. This provides significant advantages in isolating the exact information or behavior you need. Symbolic message/signal setup is even simpler.

Trigger Flexibly Across Data Bytes