Comprehensive Low-speed Serial Data Trigger, Decode, Measure/Graph, and Eye Diagram Capabilities

Teledyne LeCroy’s Trigger(T), Decode(D), Measure/Graph(M or G) and Eye Diagram and Physical Layer(E or P) options are the best in the industry and nearly universally available across our entire oscilloscope product line.

TDME Datasheet
Trigger Decode Measure Graph Eye Diagram
Embedded Computing
Automotive + Industrial
Power Management

Highest Performance Triggers

Designed by people who know the standards, with the unique capabilities you want to isolate unusual events. Conditional data triggering permits maximum flexibility, and highly adaptable error frame triggering is available to isolate error conditions. Frame definition allows grouping of UART or SPI packets into message frames for customization.

Every serial trigger we design exhibits deep knowledge of the standard. Most serial triggers work with digital (MSO) inputs, or the EXT input for the Clock line so as to conserve analog channels. Each serial trigger has some unique aspect for high performance, such as:

  • I2C trigger permits triggering on data in a specific location of an up to 2048 byte I2C EEPROM read or write.
  • UART or SPI bytes can be combined into a single “message frame” - trigger on custom protocols based on UART or SPI byte blocks.
  • UART supports 9-bit “address” or “wakeup” mode triggering.
  • CAN, CAN FD, LIN, FlexRay and MIL-STD-1553 permit conditional ID/Address triggering.
  • CAN and CAN FD permit triggering symbolically using a DBC file.
  • USB 2.0, USB-PD, and MIL-STD-1553 triggers permits complex transaction definition and triggering.

Every Teledyne LeCroy low-speed serial trigger that incorporates DATA trigger permits a conditional (<. <=, =, >, >=, <>, inside a range, outside a range) setup for the DATA condition. This is especially useful in situations where abnormal events should be monitored, such as when a temperature sensor transmitting via I2C exceeds a maximum temperature, or a CAN node broadcasts a low or high engine RPM or coolant pressure. Furthermore, data for triggering can be specifically isolated in very long byte streams to specific bit locations, even those which span data bytes.

Many proprietary serial protocols make use of the common UART (single Data line) or USART (Clock and Data lines, e.g., SPI) byte structures, with multiple bytes grouped into proprietary protocol definitions. Our highly flexible UART byte and SPI format definitions accommodate nearly any customer need, and the UART or SPI bytes can be defined to be part of a single “message frame” through use of our Interframe Setup. Then, the trigger pattern setup can isolate any byte value, e.g., an ID, or a DATA string value, that is part of your proprietary protocol message definition.

The Best Serial Decoder

Decoded protocol information is color-coded to specific portions of the serial data waveform and transparently overlaid for an intuitive, easy-to-understand visual record. All decoded protocols are displayed in a single time-interleaved table. Touch a row in the interactive table to quickly zoom to a packet of interest and easily search through long records for specific protocol events using the built-in search feature.

A transparent overlay with color-coding for specific portions of each protocol and the entire message frame makes it easy to understand your serial data information. Unlike other solutions, with protocol decode information away from the signal, our solution correlates the waveform and the protocol decode directly on the display. As the acquisition length is expanded or shortened, the decode overlay will adjust to show you just the right amount of information.

All decoders provide ability to search through a long record of decoded data by using a variety of search criteria, or values, or simply finding the next occurrence. Pattern Search automatically creates a zoom trace of the acquired waveform and displays the selected location complete with the transparent color-coded overlay.

Turn the oscilloscope into a protocol analyzer with a tabular display of decoded information. Customize the table to show only the data of interest and touch a message in the table to automatically zoom to it and display it on the screen. Export the table for offline analysis. Up to four different decoded signals of any type may be simultaneously displayed in the table.

Measure and Graph Tools for Validation Efficiency

Quickly validate cause and effect with automated timing measurements to or from an analog signal or another serial message. Make multiple measurements in a single long acquisition to quickly acquire statistics during corner-case testing. Serial (digital) data can be extracted to an analog value and graphed to monitor system performance over time, as if it was probed directly. Complete validation faster and gain better insight.

Digital data can be extracted from specific locations in the serial data message using the Message to Value measurement parameter - a serial data DAC. This information can then be displayed as a measurement parameter value(s), or it can be viewed as a time-correlated waveform displaying the measurement value over time - as if you were able to probe and acquire it directly. Use the long acquisition time of the oscilloscope to understand how the data changes over long periods of time, in conjunction with other system behaviors.

Some examples of the usefulness of this capability are:

  • Viewing I2C or SPI temperature sensor data
  • Viewing DigRF 3G radio frequency I and Q modulated signals
  • Viewing CAN wheel speed information used by an ABS
  • Viewing reconstructed analog audio from serial I2S streams

Utilize a serial trigger to isolate a specific message and then measure a cause-effect timing relationship with a subsequent analog signal, or vice versa. But instead of manually measuring the timing with cursors, use these tools to automate the measurement and return thousands of values quickly as your system undergoes stress testing. Automate the measurement and validation of gateway latency times from one serial message to another (e.g. CAN to LIN or low-speed CAN to high-speed CAN, or CAN to FlexRay) without having to manually use cursors or compare values and times in a protocol table. Quickly understand bus latency times or arbitration behaviors by measuring the difference between two messages on a single decoded waveform. Dramatically improve your validation efficiency and time to insight

The bus status measurements Bus Load, Message Bitrate, and Number of Messages, give an overall status of the decode protocol to quickly learn if the bus is over utilized and to verify the bit rate matches expectations.

Eye Diagrams & Physical Layer Testing

Rapidly display an eye diagram of your packetized low-speed serial data signal without additional setup time. Use eye parameters to quantify system performance and apply a standard or custom mask to identify anomalies. Mask failures can be indicated and can force the scope into Stop mode.

Up to four serial data signals can be decoded and displayed as eye diagrams at one time. These can be different protocols, or the same protocol measured at different points (e.g., transmit and receive, different nodes, or different standard-defined test points). Apply a user-defined filter to each eye diagram to only display specific signals in the eye

Quantify physical layer signal quality in the eye by applying parameters for Eye Height, Eye Width, and Number of Mask Failures. Some packages (e.g. FlexRay TDMP) go a step further and include additional measurements defined in the standard.

A user-defined or pre-defined mask may be added to the eye diagram so as to objectively evaluate if the physical layer signal intrudes too far into the eye opening. Apply a filter to include or exclude specific messages from the Eye so as to determine failure source (e.g., messages from a specific node or with a specific ID). Mask failures are indicated with a red circle and can be displayed in a table. Touch the failure table to open a zoom of the failed area for further inspection

Some standards, due to their speed or nodal complexity, provide specific guidance on what eye diagrams or measurements should be made and exactly how they should be performed. FlexRay, and MIPI DPHY are examples. In these cases, the Eye Diagram (“E”) capability is augmented with additional specialized “P” capability (for Physical Layer Measurements), per the standard In these cases, the “E” capabilities previously described are also available.