Error 1000 in TestStand

[ArtTCG]

I get an Error -1000 when trying to configure a step vi in TestStand.  I am using the test shell method to pass parameters into the step vi.  I set up the custom menu option "Configure Test VI..." as in the documentation, which is supposed to call the vi in the configure mode as opposed to the run mode when called as a step in a sequence.  I have successfully had this work in the past but am having problems this time on this installation.  When I select the "Configure Test VI..." menu option, I get the Error -1000.  The machine is running Windows 2000 and I am using LabVIEW 6.1 and TestStand 2.0.

[Caroline Bright]

Hi,

Since you have had this work on another computer, you may want to just try repairing the installation of TestStand and LabVIEW to make sure that neither of these are messed up in any way on this particular machine.  Also, can you tell me if there is anything different about this machine than the other machines that you were able to get this working on?

Also, can you point me to the documentation that you are following so that I can try and replicate the issue here?  If I can replicate the issue, then I will be better able to help determine what may be causing this error.

[ArtTCG]

Hi Caroline,

The

[ArtTCG]

Hi Caroline,

I have actually had this feature working on the machine with which I am having trouble.  After that, we deployed this machine with only the run-time executable operator interface when we put it on the factory floor.  For unrelated reasons, it was returned to me and I did a full installation again to solve a problem and now have this problem.

One place you can find the instructions is in the Start Menu/National Instruments/TestStand/Online help/LabVIEW TE Compatibility and look for the topic "Open Test VI Callback".

Thanks

[ArtTCG]

Caroline,

I found another clue that might be helpful.  I used the "Assemble Test VI's for Run Time Distribution..." menu option to build the two libraries (Main.llb and support.llb) for my sequences like I usually do.  But this time, I allowed the diagrams to be included and when I perform the "Configure Test VI..." menu option, my vi comes up in the configure mode and everything works fine.  What is it about including the diagrams that would make this feature work?  Again, I have had this work successfuly before when I assemble the test vi's without diagrams.  The error 1000 documentation seems to indicate that there may be a problem with having the vi in memory, or perhaps running when it is called.

Thanks

[Caroline Bright]

Hi,

I am also finding that this error code usually indicates errors when trying to edit a vi that is running or reserved for running.  This being said, do you use any Open Vi References or Call by Reference Nodes in your vis?  Also, is this the exact same vis that you had working in the past or have you changed them at all since the last time you were able to configure them?

I noticed that the documentation you pointed me to was for upgrading your tests from the older TestExecutive software to TestStand.  Are the sequences and vis you are using originally from TestExecutive?  In all honesty, I am not very familiar with the older TestExecutive software so it may take me a little time to try and replicate your issue or dig more into it.  However, as soon as I have any more clues as to what may be happening, I will make sure to post to you immediately.

[ArtTCG]

Hi Caroline,

No, there are no Open VI References of Call by Reference Nodes in my code.  And yes, this is the same code.  I seem to have stumbled upon the following.  If I "Assemble Test VI's for Runtime Distribution" and include the diagrams, this seems to make things a little better.  However, it seems very notional.  Another thing that has helped is unchecking the box in the Configure LabVIEW adapter menu option that reserves the vi's for execution.  Things are even better when I do this, but still a tad notional.  It seems that if I run my sequence once, I can configure my step vi's at will.  It has to have something to do with the way the vi's are loaded and executed when the sequence is loaded and executed.

Thanks

[Caroline Bright]

Hi,

The sequence called in the Configure Test VI Callback is called TestStand - Call Test VI Shell.vi and can be found at <TestStand>\Components\NI\Tools\LVTECompatibility folder.  Try opening this VI and turning on Highlight execution.  Then go through the normal steps that cause you to see the error message.  See if you can tell where in the VI the error is occurring.  Place breakpoints and step through the VI to find which subvi is throwing the error.  If we can narrow down where there is an issue, we can take a more direct approach at detemining the root cause.