Configures the properties commonly required for the TClk synchronization of device sessions with homogeneous triggers in a single PXI chassis or a single PC.

Use the niTClk Configure For Homogeneous Triggers VI to configure properties for the Reference Clocks, Start Triggers, Reference Triggers, Script Triggers, and Pause Triggers.

If the niTClk Configure For Homogeneous Triggers VI cannot perform all the steps required for the given sessions, it returns an error. If the niTClk Configure For Homogeneous Triggers VI returns an error, use the instrument driver VIs and properties, along with the following NI-TClk properties, for signal routing.


icon

Inputs/Outputs

  • c1dgenclassrn.png sessions —

    sessions specifies the array of session references that are being synchronized. Obtain session references from the instrument driver by using the <driver name> Get Session Reference VI, where <driver name> is the name of the instrument driver, for example, the niScope Get Session Reference VI.

  • cerrcodeclst.png error in (no error) —

    error in (no error) describes error conditions that occur before this node runs. This input provides standard error in functionality.

  • i1dgenclassrn.png sessions out —

    sessions out passes the array of session references to the next VI.

  • ierrcodeclst.png error out —

    error out contains error information. This output provides standard error out functionality.

    • Details

    Configure For Homogeneous Triggers Details

    Reference Clocks

    The niTClk Configure For Homogeneous Triggers VI configures the Reference Clocks if they are needed. Specifically, if you use the internal Sample Clocks or internal Sample Clock timebases, and the Reference Clock Source is either not configured or is set to None (no trigger configured), the niTClk Configure For Homogeneous Triggers VI configures the following:

    • PXI—The Reference Clock Source on all devices is set to be the 10 MHz PXI backplane clock (PXI_CLK10).
    • PCI—One of the devices exports its 10 MHz onboard Reference Clock to RTSI 7. The Reference Clock Source on all devices is set to be RTSI 7.
    Note If the Reference Clock Source is set to a value other than None, the niTClk Configure For Homogeneous Triggers VI cannot configure the Reference Clock Source.

    Start Triggers

    If the Start Trigger is set to None (no trigger configured) for all sessions, the sessions are configured to share the Start Trigger. The VI performs the following actions to share the Start Trigger:

    • Implicitly exports the Start Trigger from one session
    • Configures the other sessions for digital edge Start Triggers with sources corresponding to the exported Start Trigger
    • Sets the Start Trigger Master Session property to the session that is exporting the trigger for all sessions

    If the Start Triggers are set to None for all except one session, the niTClk Configure For Homogeneous Triggers VI configures the sessions to share the Start Trigger from the one excepted session. The VI performs the following actions to share the Start Trigger:

    • Implicitly exports the Start Trigger from the session in which the Start Trigger is not set to None
    • Configures the other sessions for digital edge Start Triggers with sources corresponding to the exported Start Trigger
    • Sets the Start Trigger Master Session property to the session that is exporting the trigger for all sessions

    If the Start Triggers are configured for all sessions, the niTClk Configure For Homogeneous Triggers VI does not affect the Start Triggers. Start Triggers are configured for all sessions if either of the following conditions is true:

    • No session has a Start Trigger set to None
    • One session has a Start Trigger set to None, and all other sessions have Start Triggers other than None. For the session in which the Start Trigger is set to None, the Start Trigger Master Session property must be set to this session, indicating that the session itself is the Start Trigger master

    Reference Triggers

    For sessions that support Reference Triggers, if the Reference Triggers are set to None (no trigger configured) for all except one session, the niTClk Configure For Homogeneous Triggers VI configures these sessions to share the Reference Triggers sessions. The VI performs the following actions to share the Reference Triggers:

    • Implicitly exports the Reference Trigger from the session in which the Reference Trigger is not set to None
    • Configures the other sessions that support the Reference Trigger for digital-edge Reference Triggers with sources corresponding to the exported Reference Trigger
    • Sets the Reference Trigger Master Session property to the session that is exporting the trigger for all sessions that support the Reference Triggers.

    Calling the niTClk Configure For Homogeneous Triggers VI will not affect the Reference Triggers if either of the following conditions is true:

    • No session has a Reference Trigger set to None
    • One session has a Reference Trigger set to None, and all other sessions have Reference Triggers other than None. For the session in which the Reference Trigger is set to None, the Reference Trigger Master Session property must be set to this session, indicating that the session itself is the Reference Trigger master

    Reference Trigger Holdoffs

    For acquisition sessions, the niTClk Configure For Homogeneous Triggers VI configures the holdoff attributes, which are instrument driver specific, on the Reference Trigger master session so that the session does not recognize the Reference Trigger before the other sessions are ready. This condition is only relevant when the Sample Clock rates, Sample Clock timebase rates, sample counts, holdoffs, and/or any delays for the acquisitions are different.

    Script Triggers 0, 1, 2, and 3

    Note This section applies to each of Script Triggers 0, 1, 2, and 3.

    For sessions that support Script Triggers, if the Script Triggers are set to None (no trigger configured) for all except one session, the niTClk Configure For Homogeneous Triggers VI configures these sessions to share the Script Triggers. The VI performs the following actions to share the Script Triggers.

    • Implicitly exports the Script Trigger from the session with the Script Trigger that is not set to None.
    • Configures the other sessions that support the Script Trigger for digital-edge Script Triggers with sources corresponding to the exported Script Trigger
    • Sets the Script Trigger Master Session property to the session that is exporting the trigger for all sessions that support Script Triggers

    If the Script Triggers are configured for all sessions that support Script Triggers, the niTClk Configure For Homogeneous Triggers VI does not affect Script Triggers. Script Triggers are configured for all sessions if either of the following conditions is true:

    • No session has a Script Trigger set to None
    • One session has a Script Trigger set to None and all other sessions have Script Triggers other than None. The session with the None trigger must have the Script Trigger Master Session property set to itself, indicating that the session itself is the Script Trigger master

    Pause Triggers

    For sessions that support Pause Triggers, if the Pause Triggers are set to None (no trigger configured) for all except one session, the niTClk Configure For Homogeneous Triggers VI configures the generation sessions to share the Pause Triggers. The VI performs the following actions to share the Pause Triggers:

    • Implicitly exports the Pause Trigger from the session with the Pause Trigger that is not set to None
    • Configures the other sessions that support the Pause Trigger for digital-edge Pause Triggers with sources corresponding to the exported Pause Trigger
    • Sets the Pause Trigger Master Session property to the session that is exporting the trigger for all sessions that support Pause Triggers

    If the Pause Triggers are configured for all generation sessions that support Pause Triggers, the niTClk Configure For Homogeneous Triggers VI does not affect Pause Triggers. Pause Triggers are configured for all sessions if either of the following conditions is true:

    • No session has a Pause Trigger set to None
    • One session has a Pause Trigger set to None and all other sessions have Pause Triggers other than None. The session with the None trigger must have the Pause Trigger Master Session property set to itself, indicating that the session itself is the Pause Trigger master
    Note TClk synchronization is not supported for Pause Triggers on acquisition sessions.