Capture Modes
The timer mode is the simplest mode of data capture. A pre-defined duration is set by the user and the capture will end once the duration is reached. In the example video below, we set the capture duration to 5s. The recording will stop once 5s is reached.
Timer Mode Capture
The looping mode allows for a continuous recording into a RAM buffer, the size of which can be set by the user. Once the RAM buffer is filled, old data is deleted while new data arrives, and the capture can continue indefinitely in a continuous loop. When the capture ends, the data can be trimmed down to a certain length via the Trim data after stopping setting, keeping the most recent data.
In the example video below, we set the Memory buffer size to 500 MB. Notice that, during the capture, the memory usage does not go above the set Memory value of 500 MB during the continuous recording.
Looping Mode Capture
The trigger mode will continuously record data until a digital trigger is found on a single channel. The four available types of digital triggers are Rising Edge, Falling Edge, High Pulse, and Low Pulse.
Trigger Mode Capture Settings
In addition to the edge/pulse trigger which is set on a single digital channel, you can require other digital channels to be either HIGH or LOW to trigger a capture.
Digital Channel State Conditions for Trigger
In Trigger mode, while waiting for the trigger during a capture, Logic will continue using the PC's RAM in a continuous loop. The Memory buffer size setting limits the amount of RAM usage for this process. Similar to Looping mode, once the RAM buffer is filled, old data is deleted while new data arrives, and the capture will continue indefinitely until the trigger condition is met.
Please make sure to size the "Memory buffer size" appropriately from within the capture settings panel, such that your PC does not run out of memory while waiting for a trigger.
Memory Buffer Size Setting
The data that was captured before the trigger can be trimmed down in length. This allows you to specify how much of the data before the trigger is kept when the capture ends.
Trim pre-trigger data
You can also specify the duration at which the software will continue recording data once the trigger condition is met.
Capture duration after trigger
Two options exist for jumping to a trigger point after your capture is complete:
- Via a keyboard shortcut (On Windows it is Ctrl+J)
- Via clicking on the trigger icon above your capture (shown below)
Clicking on the Trigger icon will jump the view to the trigger point
At the moment, we don't have a way of automatically jumping to trigger point after a capture. If this is a feature you would like added, please vote for it in the idea post here!
Navigate to the "Analyzers" panel and enable "Trigger View." From there, select the protocol analyzer you would like to trigger on, as well as the query value and holdoff time. HLA results can also be triggered on via this method.
Please note that Trigger View is only supported for the analyzers listed in the support article link below (Titled HLA - Analyzer Frame Format). This means that custom analyzers, including pre-installed analyzers that are not listed, will not work with Trigger View.
This is due to our Trigger View relying on a new low level analyzer framing format that we call “frame v2.” Only a handful of analyzers support “frame v2” at the moment, and these are the analyzers that work with Trigger View. We eventually want to extend Trigger View support to all analyzers in the future. Feel free to vote on this feature request here!
Trigger View - SPI Example
Triggering on a protocol frame
Last modified 8mo ago