User`s guide

320
Logic Analyzer Reference
The Analyzer Trigger Menu
As the analyzer executes the trigger specification, it searches for a
match between the resource term value and the data. When a match is
found, that part of the sequence statement becomes true and the
sequencing continues to the next part of the statement or the next
sequence level.
Eventually a path of "true" resource terms leads to your trigger
command. If timers or occurrence counters are used, the analyzer
waits or counts occurrences of a specified value before continuing.
The following examples illustrate the use of resource terms,
occurrence counters, timers, branching, and store qualification. You
will use them in your trigger specification either by themselves or
combined with each other.
Using bit patterns, ranges, and edges
Bit patterns are set to match specific data values, and ranges are set to
match a range of bit patterns. In the Timing Acquisition mode, edges
are set to match specific edges of a timing pulse.
Using storage qualification
Store qualification lets you store all data, no data, or just selected data,
before trigger occurs.
Setting < and > durations (Timing only)
When a resource term is found during a timing sequence evaluation,
you can dictate how long the term must remain before it actually
becomes true. When less than (<) or greater than (>) duration is
assigned, the secondary branching (Else on) is not available.
> field. When greater than (>) is used, the analyzer continues
sequence level evaluation only after the resource term has been true
for greater than or equal to the amount of duration specified.
< field. When less than (<) is used, the analyzer continues sequence
level evaluation only after the resource term has been true for less than
or equal to the amount of duration specified. Using less than requires
four sequence levels.