Teledyne LeCroy SAS Suite User Manual - Manual (Page 85)

SASSuite User Manual Version 6.25
LeCroy Corporation
75
Actions Once any event (or set of events) has been
identified, the next step is to define an action (or
a set of actions) that result from the event(s).
There are several actions which can take place,
as shown in the list to the left. (Note: The
actions "Branch to Existing State" and "Branch
to New State" are shown only when building a
sequence, in which multiple states are allowed.
If building Global Rules, these options are not
shown, since Global Rules have only one state.
Trigger
The Trigger action is the most common endpoint of the majority of scenarios. Triggers
work in combination with other settings previously described to determine what data is
actually captured and retained in analyzer memory. Triggers work, in effect, to stop
recording, but depending on the settings for the trigger position, recording may not stop
immediately when the trigger is issued.
The Trigger action has only one parameter, which is the number of time the action must
be called before the trigger is issued. This allows the scenario to trigger, for example, on
the 10th instance that the specific event occurred. The number of occurrences can be
selected from a list of options provided in the drop-down menu.
Branch to Existing State
This action is shown only for sequences, not for Global Rules which can contain only one
state. The Branch to Existing State action provides a means for branching and looping
within a scenario between different predefined states.
The option of an "unknown state" is provided as a temporary means to include a branch
to state which has not yet been defined, but if this option is selected the Triggering/
Filtering screen will identify this as an error in the script until the new state is defined and
the user returns to and corrects this "dead end".
Also note that the option is provided, as with all actions, of the event needing to happen
multiple times before the action actually occurs.