Teledyne LeCroy Sierra M6-1 SAS_SATA Protocol Analyzer User Manual - Manual (Page 251)

Sierra M6‐1 SAS/SATA Protocol Analyzer User Manual 249
Scenario Actions Teledyne LeCroy
 State per sequencer X 256
 Action Register per state X 8
Usage of Action Register:
 Each Counter in Global Rules = 2
 Each Counter in State = 3
 Each Timer in Global Rules = 2
 Each Timer in State = 3
 Other Actions = 1
4.6.2 Using Counters in Events and Actions
Many of the events and actions supported by InFusion also support counters that can
control functions.
Within events, counters determine how many times the event must occur before the
associated actions are triggered. Event counters typically have two properties:
 Count Randomly: Can be set to “Yes” or “No” (default value is “No”). 
If set to “Yes”, the event repeats a random number of times (between 1 and the
value set in the property Max Random Count, which replaces the property
Counter Value when “Yes” is selected), before the action is triggered.
 Counter Value: Number of repeats required when Count Randomly is set to
“No”. The default value is 1.
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 number 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.