Teledyne SierraNet M408, Руководство пользователя, Страница: 214 / 248

Teledyne LeCroy InFusion Scenarios
206 SierraNet M408 Protocol Analyzer User Manual
4.6.21 Synch Jammer Scenarios with Jammer Internal Triggers
By design, each Jammer port pair runs its own independent scenario, and each one can be
controlled independently. However, there may be advanced cases where you would need to
synchronize the Jammer operation of 2 or more port pairs. For example, you might want to
create a setup in which you jam both directions of a single link; you can achieve this by looping
the link through P1/P2 and P3/P4 with external cabling, running separate scenarios on each of
P1/P2 and P3/P4, and synchronizing those scenarios with the Jammer Internal Triggers.
Jammer Internal Triggers are pairs of events and actions that enable cross ‐ port signaling;
these events and actions are manipulated like any other event and action. The Internal
Trigger Action allows one port pair to signal an Internal Trigger Event on a different port
pair. Note that the Internal Trigger Action will NOT signal an Internal Trigger Event on the
same port pair. There are four independent Jammer Internal Trigger event/action pairs
available
For supporting this feature, a specific signal between different paths should be added,
such that one scenario will be able to notify the scenarios of other paths.
Thus, firstly, it is needed to add a new Action for notifying other paths and secondly,
adding a new event for waiting on any notify signal that is raised on other paths. This will
be implemented as bellow:
1. Adding ‘Internal Trigger’ action to notify all other paths :
a. Internal Trigger Action 1
b. Internal Trigger Action 2
c. Internal Trigger Action 3
d. Internal Trigger Action 4
2. Adding ‘Internal Trigger’ event to wait for others’ notifications
a. Internal Trigger Event 1 which is corresponded to Internal Trigger Action 1
b. Internal Trigger Event 2 which is corresponded to Internal Trigger Action 2
c. Internal Trigger Event 3 which is corresponded to Internal Trigger Action 3
d. Internal Trigger Event 4 which is corresponded to Internal Trigger Action 4
Example
For example, the user would like to insert a new frame on P1/P2 path (ACTION1) when
there is a specific symbol on P3/P4 path (EVENT1), this scenario will be implemented in 2
different scenarios as below:
1. In the first scenario for P1/P2, in the global state define a condition that waits for
EVENT1 and then raise ‘Internal Trigger’ action.
2. In the second scenario for P3/P4, in the global state define a condition that waits for
the same ‘Internal Trigger’ event and the does ACTION1.