Using 64-bit TestStand to Execute 32-bit LabVIEW VIs

Updated Oct 1, 2018

Reported In

Software

  • TestStand
  • LabVIEW

Issue Details

  • I am using 64-bit TestStand to execute my test sequences, but I have LabVIEW VIs created in a 32-bit version of LabVIEW that I would like to use in my sequence. How can I call 32-bit VIs from 64-bit TestStand?
  • I developed my sequence in 64-bit TestStand but I am calling code modules that are written in 32-bit LabVIEW. I cannot move to 64-bit LabVIEW because I am using the database connectivity toolkit. Is it possible to call these code modules that are written in a different bitness?

Solution

There are two primary methods for calling VIs that are written in a different bitness than the TestStand environment:

Configure the LabVIEW adaptor to execute VIs in the LabVIEW Development System
  1. Navigate to Configure»Adapters...
  2. Select the LabVIEW adapter and click the Configure button.
  3. Click the LabVIEW Development System radio button and click the Use Active 32-bit Version radio button.
Use remote sequence execution
This allow you to call a sequence in one bitness of TestStand from a sequence executing the other bitness of TestStand. Refer to Executing Cross-Bitness Sequence Calls for more information about this method.

Additional Information

Due to an operating system-level limitation, 64-bit processes are unable to directly execute 32-bit code. Since 64-bit TestStand is a 64-bit process, it is unable to directly execute 32-bit LabVIEW VIs and instead must execute the VIs out-of-process. Since the LabVIEW Development System is a separate process from TestStand, it is possible to use a 32-bit version of the LabVIEW Development System to execute 32-bit VIs from 64-bit TestStand. 

The caveat to this approach is that all LabVIEW VIs in the test sequence will execute in the 32-bit LabVIEW Development System. Individual VIs can, however, be configured to always execute using the 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. You can learn more about this setting from the LabVIEW Advanced Settings Window page from the TestStand Help.

WAS THIS ARTICLE HELPFUL?

Not Helpful