LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

operator interface cannot create ActiveX-Controls (TS3.1)

Using Teststand3.1 & Labview7.1
I have altered the built in Full Featured Operator Interface in the following way:
- I installed an Callback for the ExecutionClosedEvent
- This Callback checks if the property Executions.NumIncomplete==0
- If this is true, it triggers an Labview-UserEvent which in turn triggers the Main-Event-Loop in the OI
- In the Main-Event-Loop, I call ApplicationMgr.Shutdown

Is this correct to automate closing the OI if all Executions are terminated?

(I changed some other things as well like autologin, and autoload and -run of sequencefiles. But unlike the solution above, these causes me no trouble.)

I want to load and run the OI by using the VIServer (the OI is an VI, not an Exe) and selfterminate after a number of runs. In most cases the solution works properly, but sometimes there are some errors running the OI after multiple calls with the VI that uses the VIServer to start the OI:
- "error -17500 TS.ApplicationMngr could not be created" or
- unfamiliar Dialogboxes with "Operation Failed" or
- Null-Refnum rises error in TSOPI_Configure Application Manager.vi
- Sometimes it seems that the TS-UI-Controls could not been properly loaded (showing only red text instead the control).
On any of these errors I have to close and restart Labview to get it working again.

Can somebody give me an hint what's wrong? Maybe I cannot use VIServer or I have to do some extra work on deinitilizing?
0 Kudos
Message 1 of 1
(1,956 Views)