This content is not available in your preferred language.
The content is shown in another available language. Your browser may include features that can help translate the text.
Disclaimer: To be able to configure routes in LabVIEW you will need to install the NI-DAQmx driver.
With PXI Platform Services version 20.0 the T&S Upgrade will show up in NI-MAX with the following indicators when selecting the chassis:
7. T&S Upgrade Indicators in NI-MAX
Another way to confirm that the extension is working is the following:
8. PFI Ports of the T&S Upgrade in LabVIEW
In the dropdown menu for the NI Terminal type, the DSUB PFI ports always show up when a T&S Upgrade is installed. When a chassis connect on the other end of the cable that isn’t part of the host system (i.e. a multi-host system), the “PortX/TrigY” endpoints show up.
9. Trigger Lines in a Multi-Host System
These are hidden when MXI’ed chassis connect (i.e. a single-host system). This is because users are encouraged to route between modules or, when that isn’t possible, between chassis backplanes. Routing infrastructure will determine a path across the cables.
"National Instruments drivers such as NI-DAQmx must be used to route triggers between chassis dynamically; routing triggers between chassis using static routes defined in MAX is not supported."10. Quote From the Manual of the PXIe-1095
If possible use dynamic routes, this is because the dynamic route declaration binds the route to the operation that’s leveraging it, providing the best usability and maximizing our ability to manage routing resources automatically, including cleaning them up.
As a first step, make sure that the trigger settings of the PXI chassis are set to "Dynamic" for all the trigger busses that you are intending to use for cross chassis triggering. You can set this in NI-MAX by clicking on the PXI chassis and locating the Triggers tab on the bottom of the window. With this the routes are left unconfigured and available for National Instruments products to perform programmatic or automated routes to connect devices.
11. PXI Chassis Trigger Settings
Some NI drivers support implicit trigger routings, like NI-DAQmx, NI-DCPower, and NI-XNET (to see if your driver supports automatic route creation, please refer to the specific driver Help documentation).Implicit - A concrete trigger source can be specified from different hardware/card which also can be in a different chassis. Example: The start trigger of the analog input on the DAQmx card (Dev1/ai/StartTrigger) can be configured for the trigger source in the "input terminal" of the DCPower Configure Trigger VI .This is always supported for the above-mentioned drivers, including the case when the T&S Upgrade is used:
12. Dynamic Trigger Route Creation With Implicit Declaration
Many other drivers that are commonly used like NI-DMM, NI-RFSA, NI-RFSG, etc. use explicit trigger routing.Explicit - The device can only specify the PXI trigger bus line to export or import a trigger signal to or from. Example: The NI-RFSG Export Signal VI can only specify the PXI_Trig0 line for trigger signal exportation.The PXI trigger bus naming can differ for some of the drivers when using the trigger configuration VI(PXI_Trig0, TTL0, RTSI 0) but all of them refer to the same PXI trigger lines from 0 to 7.
13. Trigger Configuration VI
When working with these drivers, it is possible to implement them in a dynamic route fashion with the help of the DAQmx Connect Terminals VI. This is needed since the majority of the drivers can only specify the PXI trigger bus to listen on for a trigger signal and cannot refer to a specific signal on a specific device, as seen before in case of the DAQmx, DCPower and XNET.To connect together the intermediate connections between the PXI trigger busses, which were defined for the drivers, the DAQmx Connect Terminals VI should be used. In this case too, the cards can be in different chassis.
14. Partially Specified Route With DAQmx Connect Terminals VI
The defined terminals are connected together automatically by the DAQmx driver, so the programmer does not have to define each subpart of the signal path but this connection also has to be disconnected programmatically with the DAQmx Disconnect Terminal VI at the end of the measurement session.
15. Disconnecting Trigger Route With DAQmx Disconnect Terminal VI
Collaborate with other users in our discussion forums
A valid service agreement may be required, and support options vary by country.