Use 64-bit TestStand to Execute 32-Bit LabVIEW Code Module

Updated Aug 3, 2023



  • TestStand
  • LabVIEW
  • LabWindows/CVI

  • How can I call 32-bit LabVIEW VIs from 64-bit TestStand?
  • How can I configure my code modules to execute on separate processes from my TestStand process?

The steps below show you how to configure LabVIEW and LabWindows™/CVI™ code adapters to execute code modules out-of-process. This is accomplished by configuring the adapter to use the LabVIEW Development System or the LabWindows/CVI development environment to execute code modules, which allows the code modules to access a separate memory space from the TestStand process itself.

Since the LabVIEW Development System is a separate process from TestStand, it is also possible to use a 32-bit version of the LabVIEW Development System to execute 32-bit VIs from 64-bit TestStand.
  1. In TestStand, select Configure»Adapters...

The Adaptor Configuration dialog box appears, in which you can change settings that apply to each adapter.
  1. Enable the Selected button next to the adapter you want to configure. Click the Configure… button.

The Configuration dialog box for the adapter appears.
  1. For LabVIEW, select LabVIEW Development System and specify which version. If you want to execute 32-bit VIs, select Use Active 32-bit Version.
Note: By selecting Use Active 32-bit Version, all LabVIEW VIs in the test sequence will execute in the 32-bit LabVIEW Development System. However, individual VIs can be configured to Always Run VI In LabVIEW Run-Time Engine, which would allow a 64-bit VI to be executed in-process during the execution. This setting can be configured on the Advanced Settings dialog of a step with a LabVIEW code module.

For LabWindows/CVI, select Execute Steps in an External Instance of LabWindows/CVI.
  1. Click OK. You have now configured the Adapter to execute out-of-process.