Use the following techniques to troubleshoot errors you might encounter while routing trigger signals and connecting trigger terminals:

  • Ensure that the source and/or destination terminals you selected are compatible with one another. Refer to Trigger Terminal Connections for a list of compatible terminals.
    Tip You can also check for possible trigger routes in Measurement & Automation Explorer (MAX) by selecting your device and clicking the Device Routes tab.
  • Ensure that the source and/or destination terminals you selected physically exist on your hardware. Refer to your hardware documentation for specific information on its terminals and connections.
  • Ensure that the source and/or destination terminals you selected are not already in use by another application. You can do this in MAX by selecting your device, opening the Test Panels window, selecting the Measure tab, and clicking Update Line State. Occupied lines are green, unoccupied lines are gray.
    Note
    • The Measure tab is not available on every timing and synchronization module.
    • Whenever you use niSync Connect Trigger Terminals, you must disconnect the terminal route using niSync Disconnect Trigger Terminals before you can use the terminals for another trigger route.
  • Ensure that you set a value in the synchronization clock terminal of niSync Connect Trigger Terminals if you are using the optional parameters update edge and invert. You must connect the source and the destination terminals synchronously for these parameters to work.
  • If you are using PXIe_DStar triggers, ensure that you are using the right trigger line for the module you are trying to connect to. Refer to your chassis documentation to see a map of your chassis' differential star triggers.
  • Ensure that your chosen trigger line is receiving a signal. You can determine the status of a line in two ways:
    • niSync Measure Frequency VI—Use this VI to return the frequency of a clock or trigger signal on a specific line. This VI does not work for time-based modules like the 6683(H).
    • niSync Property Node—Use the Trigger State Properties to confirm that future time events are activating and to confirm that triggers and clocks created with niSync Create Clock are firing on a specific trigger line. Refer to Displaying the State of a Trigger Line as an Array for more information.