Inline Model Interface Custom Devices
- Updated2025-10-27
- 1 minute(s) read
An inline model interface custom device executes inline with the VeriStand Engine's Primary Control Loop (PCL), which processes data acquired from hardware inputs and sends the processed values to hardware outputs without latency.
You can create an inline model interface custom device from a template in the Custom Device API library.
An inline model interface custom device executes as a state machine, or action-engine. The device contains a Case structure, and the PCL calls each case at a specific time with respect to other components of the VeriStand Engine. Within the device, an uninitialized Feedback Node handles iterative data transfer between states.
The inline model interface custom device is very similar to the inline hardware interface custom device. An inline model interface custom device has one case, or step, that executes within an iteration of the PCL, while an inline hardware interface custom device has two steps that execute within a PCL iteration.
Related Information
- Using the Inline Model Interface Custom Device Driver Template
Use the inline model interface custom device driver template to build the RT Driver VI for a custom device.
- Custom Device API Library
The Custom Device API library is a LabVIEW library that contains type definitions, template VIs, and the LabVIEW API a custom device needs to interact with VeriStand.
- Inline Hardware Interface Custom Devices
An inline hardware interface custom device executes inline with the VeriStand Engine's Primary Control Loop (PCL) and enables you to read and write data from and to a hardware device.