TS LV step running with development adapter but not runtime adapter

[stephenb2]

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?

[stephenb2]

Does the runtime engine even work with vi.lib?

[RoxtheFox · Accepted solution]

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.  

[stephenb2]

That worked, thanks.

[RoxtheFox]

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

Thanks for pointing it out!

Roxy