Operator Interface Files

[Clint Eastwood]

I have 2 different UUT's Tested on the same Station.  Thru this Discus Grp I was shown a way to hardcode in the path to the file of the seq I wanted to test.  This was so the operator didn't have to navigate to 2 different files(seq's).  I created 2 different Simple OI each with a diff seq hardcoded.  When I create the "exe" the supporting files seem to be just the OI files.  Should I also include the seq I'm testing along w the vi's that TS uses??  Both seq.s seem to run fine.  I didn't know if it was just a coincidnce that I was getting the correct vis when I need them because I was on the Develop Machine and not the target.

[RayFarmer]

Hi,

I would say normally you wouldn't deploy your test sequence files and code modules with your OI.

But in this case, as your OI is linked to a specific sequence file then include all the test components with the deployment of the OI.

Regards

Ray Farmer

[Joe_H]

Build your OI exe in LabVIEW. Then use the TS deployment utility to distribute all and include your EXE in the deployment.