Teledyne LeCroy USB Protocol Suite User Manual (Voyager_Advisor T3_Mercury) - Manual (Page 297)

USB Protocol Suite User Manual 297
Recording Rules ‐ USB 2.0 Teledyne LeCroy Corporation
Within actions, counters determine how many times the system calls the action before it
acts. Action counters typically have two properties:
 Random: Can be set to “Yes” or “No” (default value is “No”). If set to “Yes”, the
action triggers a number of occurrences before the action takes place. That num‐
ber ranges randomly between 1 and the value set in the property At least every
Nth occurrence, which replaces the property Every Nth occurrence when “Yes” is
selected.
 Every Nth occurrence: Number of times the system calls the action before it
acts.
Note that there is some overlap in the way these counters can be used. For example, in
the simple case of a single event leading to a single action, it makes no difference whether
you specify the event to require five repeats before triggering the action, or the action to
require five occurrences before it acts.
However, in the case of combined events and/or actions, the separate counters provide
flexibility in designing test cases. For example, consider the case where Event_1 OR
Event_2 leads to Action. If Event_1 has a counter of 5, then the Action triggers either
when Event_1 has repeated five times or when Event_2 happens the first time, whichever
occurs first.
But if the event counters are set to 1 and the Action counter is set to 5, then the Action
happens after five occurrences of EITHER Event_1 or Event_2.
Number of Analyzer Counters and Timers
The Analyzer includes one event counter and one time counter (timer). If you try to assign
more, you get a warning.
Packets
You must assign a packet, event, or logical expression to a counter and/or timer.
Using a Counter
To use a counter:
1. Click an event to display an arrow.
2. Click a counter. This causes the counter to attach itself to the bottom of the event.
An arrow automatically connects the counter to the Trigger button.
Note:
For Timers, do NOT use a timer as the first event in a sequence, since this first “event” will be the
start of recording, and this is not a precise or predictable point in time from which to start
timing. Use timers only AFTER the first event.