Keysight PXIe Chassis Family User Guide 87
Chassis Trigger Lines Configuring the PXI Trigger Bus
Some multi-slot PXI instruments, such as the Keysight M9381A PXIe Vector
Signal Generator, use peer-to-peer (module-to-module) triggering to function. If
you install these modules on the same trigger bus segment, no routes are
needed. But if you install them on different trigger bus segments, you must
configure trigger routes.
Persistent Versus Volatile Reservations
Volatile (dynamic) reservations will not persist through restarting (rebooting) the
host controller or the chassis. The PXIe Family Chassis Driver KtMTrig utility
creates volatile reservations and routes.
Persistent reservations, except in certain cases of conflicting reservations;
Persistent (or Static) reservations persist through restarting the host controller or
the chassis. Keysight IO Libraries Suite Connection Expert creates persistent
reservations and routes.
You can interactively create or remove persistent trigger reservations and routes
in Connection Expert's Chassis Triggers view. No changes are actually made to
the system until you click ACCEPT.
When you click ACCEPT, your changes are communicated to the underlying
Trigger Manager and thus to the chassis. At the same time, your changes are
also saved as persistent reservations. This means that they will be automatically
restored following a system restart (PC reboot or chassis power cycle).
Example: Persistent Versus Volatile Reservations
Suppose your system includes the reservations and routes shown below. The
Keysight Persistent reservations were made in the IO Libraries Suite Connection
Expert, and therefore they are Persistent reservations. The
AgM9018IviDriver_DefaultClient reservations were made programmatically and
are therefore volatile.
Figure 39 Trigger Routing with Persistent and Volatile Routing
To Next Page
Loading...