CDDriverExecMode Enumeration
- Updated2023-02-21
- 3 minute(s) read
Specifies the execution mode, or device type, of a custom device. The execution mode defines how the device interacts with the VeriStand Engine.
Namespace:
NationalInstruments.VeriStand.SystemDefinitionAPIAssembly: NationalInstruments.VeriStand.SystemDefinitionAPI (in NationalInstruments.VeriStand.SystemDefinitionAPI.dll) Version: 2013.0.0.0 (2013.0.0.0)
| Member name | Description |
|---|---|
| Asynchronous | The device executes asynchronously, or in a separate, parallel loop to the VeriStand Engine's Primary Control Loop. Asynchronous custom devices use RT FIFOs to exchange channel data with the rest of the NI VeriStand system. |
| AsynchronousTimingAndSync | The device executes as an asynchronous custom device that also can function as the hardware synchronization master device, which drives the RTSI 0 line. In NI VeriStand, the device appears as a Timing and Sync device. |
| InlineHWInterface | The device executes inline with the VeriStand Engine's Primary Control Loop (PCL) and can read and write data from and to a hardware device. Inline custom devices contain a Case structure and execute as state machines. In inline hardware interface devices, two of the cases (Read Data from HW and Write Data to HW) are called on each iteration of the PCL. |
| InlineModelInterface | The device executes inline with the VeriStand Engine's Primary Control Loop (PCL). Inline model interface devices can process data acquired from hardware inputs and send the processed values to hardware outputs with no latency. Inline custom devices contain a Case structure and execute as state machines. In inline model interface devices, one case (Execute Model) is called on each iteration of the PCL. |
| InlineTimingAndSync | The device executes as an inline hardware interface custom device that also can function as the hardware synchronization master device, which drives the RTSI 0 line. In NI VeriStand, the device appears as a Timing and Sync device. |