NI TestStand

cancel
Showing results for 
Search instead for 
Did you mean: 

TS LV step running with development adapter but not runtime adapter

Solved!
Go to solution

I created a simple proof of concept of the issue I am having. The example tries to write to a station globals string variable named "text".

 

The sequence pops up a message box prompting the user to enter a string. That string is passed to a LabVIEW VI that simply writes the string to the station global. It works when the LabVIEW adapter is set to the LabVIEW development but does not work when it is set to the runtime engine.

 

The issue is that the runtime adapter cannot find the TestStand set property (string) VI, but the VI is in its expected place ("C:\Program Files\National Instruments\LabVIEW 2018\vi.lib\addons\TestStand\_TSUtility.llb").

 

Is anyone aware of any way to configure the runtime engine search path?

 

error info.png

 

VI diagram.png

0 Kudos
Message 1 of 5
(2,404 Views)

Does the runtime engine even work with vi.lib?

0 Kudos
Message 2 of 5
(2,388 Views)
Solution
Accepted by topic author stephenb2

Hey, 

 

Go to LabVIEW development environment, and go to Tools>>Advanced and choose Mass Compile and choose the folder "C:\Program Files\National Instruments\LabVIEW 2018\vi.lib\addons\TestStand." I recreated your issue and the mass compile of that folder fixed it.  

0 Kudos
Message 3 of 5
(2,383 Views)

That worked, thanks.

0 Kudos
Message 4 of 5
(2,378 Views)

I'll file a bug report so that we can have this content added to the TestStand help.

 

Thanks for pointing it out!

 

Roxy

0 Kudos
Message 5 of 5
(2,373 Views)