Contol of GPIB initializing at LV Runtime Startup

[RodAtBoeing]

I am creating 25 to 30 LabView executable files to run a semi automatic test set. I have gotten all the apps to run fine in LabView, without any inoperability problems. Now I am trying to convert each of the separate vi�s into executables. This also works fine. Each of the programs runs individually. My problem is in running multiple apps that use the GPIB bus at the same time. I am running three Sorenson power supplies. I set them up using LabView.
Error Mode 1.
After I setup the voltage and exit the program, the supplies go back to local mode and reset to 0.
Error Mode 2.
Leave the power supply program active, then open a second program the uses the GPIB bus (but not the power supplies). When the second program ini
tializes the GPIB bus it resets the power supplies with the same result as Error Mode 1.

Using the GPIB spy utility I can see the commands that the LV runtime engine makes at startup and shutdown, is their any way to control the initializing and exit process for the GPIB bus.

[AaronK]

Hi Rod,
I was unable to repoduce this behavior using the Labview<->GPIB example provided with labview. I am not sure what you may be specifically doing to cause this behavior. You may just want to reinitialize after each open or better yet, take your sub vi's and create a state machine that will enable running individual parts in any sequence from a nice front panel.

Hope this helps out. If the state machine is not an option, give me more information and I can try to help out out!

Best Regards,
Aaron K.
Application Engineer
National Instruments