LeCroy Corporation
Creating a Sequence
354
Sierra M6
‐
2 SAS/SATA Protocol Analyzer User Manual
Creating a Sequence
This section gives several examples for creating sequences. Recall that a sequence can
have multiple states, but only one state is active at any time. In other words, at any point
in time, a sequence “waits” for one event (or combined event) and responds with the
corresponding action or set of actions when the event occurs.
A sequence is more powerful than Global Rules, because you can create branching or
looping test logic with a sequence.You can include up to two sequences in a scenario, but
each is completely independent of the other. There is no branching or other interaction
between the two, except through the Restart All Sequences action.
You must follow some simple rules when creating sequences:
TABLE 4.5: Sequence Rules
You
can
use
only
two
branch
actions
per
state.
When you specify actions for a state, you can only use two instances of
Branch
to
an
Existing
State
or
Branch
to
a
New
State
. If you try to use more than two, a red error
message appears in the status area of the application that says “Too Many Actions.”
You
can
use
only
one
restart
sequence
action
per
state.
When you specify actions for a state, you can only use one instance of
Restart
Current
Sequence
or
Restart
All
Sequences
. If you try to use more than one, a red
error message appears in the status area of the application that says “Too Many
Actions.”
You
can
use
a
maximum
of
255
states
per
sequence.
If you try to use more than 255 states, a red error message appears in the status area
of the application.
