03-30-2022 05:02 PM
OVERVIEW
Our production system uses a Teststand runtime license on a W10 Lenovo i5 PC,
Teststand and LabVIEW runtime engines are used to run a 3rd party Teststand model that calls an inhouse Teststand sequence that calls inhouse and hardware vendor VIs in a LabVIEW packed library
The 2016 setup has been working for years, but does not work since upgrading NI code from 2016 to 2020.
BEHAVIOUR
I have looked at the VIs that are called when Teststand hangs, and there is nothing that I can detect that will cause a hang.
And I have to ask....why does it run in the other modes?
After much head scratching, and nailing down the behaviour I come seeking advice......
Solved! Go to Solution.
03-31-2022 10:22 AM
Hi,
Since it is working in development mode then there are VIs which are not upgraded to higher versions.
From TestStand Tools menu there is an update VI tool which also can be used to upgrade your VI .Since you have mass compiled the VIs i assume all VIs are upgraded.You can still try this tool.
Did you upgrade the packed libraries i.e. rebuild the source code to the new version.YOu need to open the project and rebuild packed libraries to newer version i.e. LV 2020 in your case. Mass compile cannot upgrade the packed libraries.
Ravi
04-03-2022 06:49 PM
Hi
All the packed libraries had been upgraded to 2020, with a mass compile
A packed library was built using 2020 LabVIEW VIs
After a few issues I was able to use the TestStand ran the 'Update VI/LV NXG VI Calls' tool. Though I used the update on change option.
I have now gone through with the force update option on the the 'Update VI/LV NXG VI Calls' tool, and this has fixed the problem.
Thanks Ravi.