NI TestStand

cancel
Showing results for 
Search instead for 
Did you mean: 

The OI Problem

Hello All,

 

I am seeking a perfect solution to this Problem,

 

 I am adding a VI named  TEST.vi to the fully featured Operator Interface and built an EXE.  The OI  EXE is also running  without any issues. Now, using that OI I am creating a step with LabVIEW as an adapter and on specify module I select a VI with the name TEST.vi, it threw an error (atttached as an Image). This is obvious since no two VI's cannot be in memory with the same name. So I planned to make them unique by adding a lvlib to TEST.vi, and when I loaded it threw the same error dialog. 

 

On next attempt, while creating the EXE for the OI, I checked this option "Add Files to new project libary" to make all the VI's inside the EXE to get the lvlib namespace,

but this also not working.

 

EXE.png

 

 

I

 

We have built a customized sequence editor with thousands of VI's in memory,  they also used these same VI's to create the Step Types, So while loading I get this conflict.

 

I can't understand why Teststand is neglecting the Library, please get me a solution for this (please don't say rename the VI)..

 

Thanks,

Sundar. S

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

 

 

Forget to attach the Error Image

0 Kudos
Message 2 of 2
(2,995 Views)