Teststand locks out Labview editing

[Cabman]

When editing a LabView VI called by a TestStand step you have to click on the "Edit code.." or "Edit VI.." in order to gain access. If you have just run the step and open the file, the run arrow is disabled and editing is not possible. I assume this is because TestStand has loaded the file and will not allow another client to gain control of it in memory.

The problem is sometimes subVIs that the called VI use get into this locked mode. When this happens there seems to be know way to gain access unless you shutdown TestStand completely.

My question, what is going on here, and is there a way to gain access for editing without shutting down TestStand?

[Anand_Jain]

Hi
You can do the following
inside the sequence editor you can click on

File-> Unload all Modules

and that should fix your problem

Thanks
Anand

[Cabman]

Thanks that works, however now all the VIs are unloaded and when I go to restart the test I have to wait for all of them to load again. (We set our sequences to pre-load all modules).

Is there anyway to unload only the VI specified?

[Elaine_R.]

Hello Cabbage -

Your only other option to 'unload all' would be to set the per-step load and unload options via right-clicking on the step and selecting Properties.

On the step properties window, examine the tab for Run Options. Here you could tell just one step to unload its module after execution so that you can run a test, edit the VI, and run another test, etc (after you're done debugging you can set it back to its original unload setting). Maybe this will help.


Regards,
Elaine R.
National Instruments
http://www.ni.com/support