Problem re-building the Runtime Operator for testStand

[Declan]

I am trying to use the LabVIEW build application tool to create an executable version of the LabVIEW
run-time operator interface for TestStand. I followed the instructions for this task given in the TestStand User Manual. In addition to these instructions I chose to use this VI as my ActiveX sever and created an installer with the LabView run-time engine selected.The file was built without any problems but when the executable runs it hangs on the intruduction screen (National Instruments TestStand Logo). I was hoping you may have an explaination for this hang

[Dennis_Knutson]

What version of LabVIEW are you running and which version of TestStand? Have you made any changes to the run-time operator interface or is it the shipping example? Did you use the .bld file provided when you created the executable? If the problem is happening on a systme different than your TestStand development system, make sure that the TestStand engine is installed.

[Declan]

Thanks Dennis for your quick reply.
I am running LabVIEW V6.0.2 and TestStand V1.0.3. It is the shipping example but I used the .vi not .bld version. I followed the "Building a Standalone Executable" instructions outlined in the TestStand User manual shipped with v1.0.3 which states to use the .vi, is this wrong? I have yet to try the app on my target system, problem was encountered on the development machine. any futher help would be much appreciated.

Kind regards
Declan

[Jason F.]

Hi Declan,

Actually, Dennis was correct about the .bld file, but you were also correct in that the TS User Manual described a manual setup in the LV App Builder tool instead of the .bld file. Nonetheless, you should actually use the "testexec.bld" build script file in your C:\TestStand\OperatorInterfaces\NI\LV directory instead of the process outlined in the user manual. For instructions on using the testexec.bld file to build your run-time operator interface you should read the "readme.doc" file in the same directory as the testexec.bld file as it supercedes the information found in the user manual (the information in the user manual dates back to version 1.0, and since then we have created an easy to use build script file that takes the place of the le
ngthy process described in the manual). Hope this helps!

Jason F.
Applications Engineer
National Instruments
www.ni.com/ask