TestStand/LabVIEW VI Issue

[shreyapatel]

I am using Teststand 2019 (32-bit) and LabVIEW 2019 (32-bit). I am trying to call VIs from the LabVIEW project into Teststand. Even through I am using the same version of LabVIEW and Teststand, along with the same bitness I am running into an issue where the VI is unable to be loaded saying that "LabVIEW 8.0 runtime engine isn't loaded and the bitness isn't 32-bit". 

Can someone help me understand what is causing the issue and how to resolve it?

Thanks,

Shreya

[Kyle97330 · Accepted solution]

It's been a while since I used TestStand but I think I remember this and the issue is probably 1 of 2 things.

TestStand doesn't have the ability to run LabVIEW code directly, it needs to run it through an "adapter".  This adapter can be the LabVIEW "Run-time engine", which doesn't allow editing of code and requires that all VIs be pre-compiled in a version that you have a matching version of the "Run-time engine" on your PC for.  The "Run-time engine" is lighter and does not need a paid license.  Or, the adapter can be an installed version of the development environment of LabVIEW, which is slower but allows for editing/debugging and doesn't need everything pre-compiled.

So one thing you could do would be to switch your adapter.  There should be a menu somewhere that lets you do this, I can't remember where specifically.

The other thing you can do is to get everything to be compiled in a version with a matching run-time engine.  LabView 8.0 is from like 2005, so don't bother looking for an installer for that.  Instead, use LabVIEW 2019 to convert everything to 2019.  Open LabVIEW, go to the Tools menu, then the Advanced submenu, and choose "Mass compile".  Then select the directory in question (for now, looks like a single driver in your instr.lib folder?) and run mass compile on that. It might take a while depending on how many files are in there.

[jcarmody · Accepted solution]

It looks like an instr.lib VI is saved in an old version of LabVIEW.  Can you recompile everything with LabVIEW 2019?  Or, install the older RTE.

Here's from the TestStand help: "This discrepancy occurs most often when a top-level VI uses a subVI or controls located in the <LabVIEW>\vi.lib\addons\TestStand directory and that subVI was saved in a different version of LabVIEW than the LabVIEW RTE. Mass compiling the <LabVIEW>\vi.lib\addons\TestStand directory usually resolves the discrepancy. You can also mass compile top-level VIs, which in turn compiles any subVIs." (Caveats for Configuring the LabVIEW Adapter to Use a LabVIEW Run-Time Engine or Other Executable Server)

[shreyapatel]

This worked, thank you!