Table Of Contents

cDAQ-91xx Timing Engines

Version:
    Last Modified: November 16, 2017

    The cDAQ-9132, 9133, 9134, 9135, 9136, 9137, 9138, 9139, 9174, 9178, 9179, 9184, 9185, 9188, 9188XT, and 9189 chassis provide three timing engines for analog input. Multiple timing engines allow those chassis to run up to three analog input tasks simultaneously, each using independent timing and triggering configurations.

    By default, NI-DAQmx automatically selects an available timing engine when reserving the task. Use the DAQmx Timing attribute/property SampTimingEngine to specify the timing engine to use or to determine which timing engine NI-DAQmx automatically selected.

    spd-note-note
    Note  

    You must reserve the task before querying the timing engine unless you explicitly specified the timing engine.

    The SampTimingEngine attribute/property is an integer value corresponding to one of the three analog input timing engines available on the chassis:

    SampTimingEngine Value Timing Engine Used
    0 te0
    1 te1
    2 ai
    On the cDAQ-9132, 9133, 9134, 9135, 9136, 9137, 9138, 9139, 9174, 9178, 9179, 9184, 9185, 9188, 9188XT, and 9189, the Sample Clock and Sample Clock Timebase, as well as the Start, Reference, and Pause triggers, exist on each timing engine. Therefore, the names of the output terminals for those signals include the associated timing engine. If NI-DAQmx automatically selects the timing engine for a task, the timing engine, thus the output terminals for those signals, are undefined until you reserve the task. To reference one of those terminals, such as to share a Start Trigger across multiple tasks, use the Terminal attribute/property associated with each signal to determine the terminal name.
    spd-note-note
    Note  

    You must reserve the task before querying the terminal name unless you explicitly specify the timing engine.

    Counter Input Modules

    The NI 9361 can also use te0 and te1.


    Recently Viewed Topics