NI TestStand

cancel
Showing results for 
Search instead for 
Did you mean: 

Building LabVIEW TestStand Operator Interface from TestStand 2017 causes issues with CVI test code modules.

Solved!
Go to solution

I am trying to customize the LabVIEW Full Featured 2017 TestStand User Interface, using LabVIEW 2018 sp1.   When I run my sequences which use CVI code modules from the Full Featured LabVIEW OI that comes with TestStand 2017, tests that normally pass, now fail.  If I use the already built TestExec.exe that comes with TestStand 2017 this problem doesn't occur. 

 

To troubleshoot, I tried building the NI version, using LabVIEW 2018 sp1, without making any changes.  The resulting TestExec.exe file is different from the one included with TestStand, and the tests fail.  Since it's NI code and supposedly the same build spec that was used to create the TestExec.exe, this must be an issue with compatibility of CVI RTE, as the original build was probably done several revisions before my LabVIEW version, 2018.  I know this because the code changes and somewhere it is documented that the UI Libraries where from an earlier version of LabVIEW. Also, When I build the CVI version of the 2017 TestStand UI, using CVI 2015 IDE, this problem does not occur. The tests do some serial communication with the UUT where timing is critical and this comm timing seems to be affected. 

0 Kudos
Message 1 of 3
(2,236 Views)

Check out the LabVIEW 2018 release notes. You might need to disable the Backward Compatibility of the LabVIEW Run-Time Engine.

 

 

Regards
Ray Farmer
0 Kudos
Message 2 of 3
(2,218 Views)
Solution
Accepted by topic author JJSMFC

We built the operator Interface with LabVIEW 2015 and our problem went away. We have not yet gotten a chance to upgrade the CVI code modules to 2018 to try the combination of LV 2018 and CVI 2018.

0 Kudos
Message 3 of 3
(2,173 Views)