EasyManua.ls Logo

Keysight Technologies M9010A - 8 Configuring the PXI Trigger Bus

Keysight Technologies M9010A
154 pages
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
PXIe Chassis Family
User Guide
83
8 Configuring the PXI Trigger Bus
Trigger management provides a systematic way for multiple applications to
share the eight PXIe backplane trigger lines without interfering with each other.
See the CAUTION below.
A generic trigger utility, KtMtrig (see page 101), is installed as part of the PXI
Chassis Family Driver for programmatic control of trigger management. It is a
“wrapper” around the PXI-9 Trigger Manager DLL specified in the PXI-9 Trigger
Management Specification. This is managed by the PXI Systems Alliance.
PXI-9-compliant trigger managers provide a way for applications, including
Keysight Connection Expert (part of the IO Libraries Suite), to dynamically query
to see if a trigger line is reserved, and if not, reserve it for use by that application.
In this way, multiple applications can coordinate their use of the shared chassis
trigger resources. It is the application programmer's responsibility to ensure that
all applications requiring trigger resources secure reservations and routes for
each client, and while in use, configure the instrument module drivers properly
so that only a single trigger source is driving any configured trigger line.
Many chassis backplane trigger lines don’t span the entire backplane, but
instead are split into two or three Trigger Bus Segments. Chassis with a
segmented trigger bus support the ability to route a trigger line from one
segment to another. This may be necessary if an application operates modules in
slots residing in multiple trigger bus segments. Trigger management provides a
way for applications to manage both trigger reservations and routes between
trigger bus segments.
- Ensure all your applications acquire trigger reservations prior
to asserting trigger events on a trigger line.
- Trigger signals can be generated by multiple modules, but
when multiple signals are placed on a trigger line
simultaneously, it can result in hardware damage. The user is
responsible to ensure that multiple modules do not assert
triggers onto the same trigger line.
- When a trigger route is created in the chassis, the chassis
hardware drives the trigger line in the destination segment of
the route. Hardware damage can occur if modules in that
destination segment attempt to drive that same trigger line.
- The PXI-9-compatible chassis trigger manager makes it
possible to recover trigger reservations from other clients.
Improper use of this feature may take trigger lines away from
client applications that are depending on them.

Table of Contents

Related product manuals