01-29-2011 03:39 PM
Labwindows/CVI establishes communication over TCP ports but only closes them when teststand is closed. However, I am suspicious that Labwindows is what allows the sockets to remain established, therefore: Is there a way to quit labwindows/CVI using teststand? While running teststand, labwindows always seems to be open.
01-31-2011 04:52 PM
Hi autorun,
I do not believe that there is any way to programmatically quit LabWindows/CVI through TestStand. However, you can choose to prevent CVI from opening up at all when you run your TestStand program. To do so, select Configure >> Adapters at the top menu bar. This will open up the Adapter Configuration window. Here, you can select LabWindows/CVI and then click "Configure" near the bottom of the window. This will open up the LabWindows/CVI Adapter Configuration window. If you click the radio button next to "Execute Steps In-Process (CVI is NOT Required for this Mode)", then your TestStand will not open up an external instance of CVI when you run your program.
Regards,
Stephanie R.
National Instruments