NI does not recommend calling functions in hardware driver DLLs directly from TestStand. Instead, NI recommends that you create a code module from a supported application development environment (ADE) to interface with the driver and acquire data. You can then call this code module from a step in a TestStand sequence.

NI recommends this approach for the following reasons:

  • Writing a code module in a supported ADE provides access to driver wrapper code, such as the LabVIEW NI-DAQmx Library, which is fully documented and supported.
  • Using a code module can help modularize components of the test system and reduce unnecessary complexity in a TestStand sequence. For example, instead of creating multiple TestStand steps that interact directly with a hardware driver, you can create a single code module that configures the hardware, acquires measurement data, and returns a numeric result to TestStand for evaluation.