Trigger on packet content such as start of packet, specific addresses, specific data content, unique identifiers, etc. on popular serial interfaces I2S/LJ/RJ/TDM.
Provides a higher-level, combined view of the individual signals (clock, data, chip enable, etc.) that make up your bus, making it easy to identify where packets begin and end and identifying sub-packet components such as address, data, identifier, CRC, etc.
Tired of having to visually inspect the waveform to count clocks, determine if each bit is a 1 or a 0, combine bits into bytes, and determine the hex value? Let the oscilloscope do it for you! Once you’ve set up a bus, the 3 Series MDO will decode each packet on the bus, and display the value in hex, binary, signed decimal (I2S/LJ/RJ/TDM) in the bus waveform.
In addition to seeing decoded packet data on the bus waveform itself, you can view all captured packets in a tabular view much like you would see in a software listing. Packets are time stamped and listed consecutively with columns for each component (Address, Data, etc.). You can save the event table data in .CSV format.
Search (serial triggering)
Serial triggering is very useful for isolating the event of interest, but once you’ve captured it and need to analyze the surrounding data, what do you do? In the past, users had to manually scroll through the waveform counting and converting bits and looking for what caused the event. You can have the oscilloscope automatically search through the acquired data for user-defined criteria including serial packet content. Each occurrence is highlighted by a search mark. Rapid navigation between marks is as simple as pressing the Previous (←) and Next (→) buttons on the screen.