Opening TestStand Ref from LabView sometimes fails

[Bill2@NGC]

I'm having an intermitten problem when opening a TestStand reference from LabView.  The error explaination just says, "LabVIEW:  (Hex 0x80004005) Unspecified error."  Attached is a little vi that can reproduce the problem when set to run continuously. 

Any idea on how to fix this?  Thanks a lot.

Note that because of compatibility requirements I have to use TestStand 2.0 with LabView 7.1.

[Caroline Bright]

Hi,

This is an issue with compatibilty between the oder version of TestStand and the newer version of LabVIEW.  However it can be fixed.  The error occcurs because of a change in the defualt threading configuration of LabVIEW 7.x that is incompatible with the behavior of TestStand 1.x/2.x.  This problem does not occur in newer releases of TestStand.  To correct this problem, add the following line at the end of the labview.ini file found in your LabVIEW installation directory.

ESys.StdNParallel=1

You must restart LabVIEW after making this edit for the change to take effect.

[Bill2@NGC]

Thanks Caroline, the problem has not reoccurred.

I have another problem with LV 7.1 and TS 2.0.  After running any test through TS, when I try to exit from the LV interface, it crashes.  Gives a message about memory error.  I'm sorry I can't include any sample code.  Do you have any idea why this is occuring?  Thanks.

[Caroline Bright]

Hi,

There could be anumber of different reasons that this may be happening so I need more information to begin attacking the problem.  First, is this a custom LV operator interface or one of the defaults that comes with TestStand?  Second, does this happen with every sequence you try to run in the OI?  Are you exiting the OI by clicking an Exit button on the OI or are you trying to exit all of LV?  Finally, and most importantly, what is the exact error message you are seeing?  Even a screenshot would be helpful.

[Bill2@NGC]

Yes it is a custom LV interface.  Yes it happens after every test we have.  I exit by clicking on an Exit button on our OI.  I'm not trying to exit all of LV, but after the error that's what happens. 

I will get you a screen shot, as soon as I can get access to the test set.  Thanks for your help.

[Caroline Bright]

Hi,

A screenshot will help since I need to know what error you are getting.  However, in the mean time, I think that you will need to just do some normal debugging steps to determine what is causing the error.  Place breakpoints and use Highlight Execution in LV to determine what may be throwing the error.  Also, try run sequences in the OIs that ship with TestStand.  That way we can be sure that the problem is not in the sequences or TestStand.

[Bill2@NGC]

Attached is a screen shot of the error message.  This is one of at least 2 error messages.  I will get the other one when I can get time on the equipment.  Right now, I would like to get the error log (mentioned in the screen shot), but I can't find it.  Where should it be?

Unfortunately, the equipment is being shared and I haven't received time to debug it more.  But this is what I have seen. 

Trying to Highlight Execution with breakpoints seemed to point the vi closing the reference to TestStand as the source of the error message.  Using the Simplified TestStand Operator Interface vi that came with TestStand, and some fake tests, we did not have this error.  Only when we use our customized OI with dynamic test sequence generation do we get the error.  This error doesn't occur with LabView 6.1.  So I think it may be another incompatibility between LV 7.1 and TS 2.0.

Thanks for your help.

[Caroline Bright]

Hi,

One quick question.  In your last post you stated that this used to work in 6.1.  Is this OI the exact same as the one you had in 6.1 just upgraded or have you changed any part of the OI?
Also, with behavior like this, you will need to go through normal debugging steps to determine what may be happening.  Since you seem to have found the trouble in the Close TestStand reference, try and determine how your OI differs from the shipping Simple OI with TestStand.  Try removing parts of your custom OI to match the Simple OI.  This may help you determine the difference that is returning the error.  I would also place probes in the OI to try and determine if the correct references are being passed to the Close TestStand reference VI.

[Bill2@NGC]

The problem occured even before we modified the OI.  That's why I thought it was another incompatibility between LV 7.1 and TS 2.0. 

Thanks for your advice.  I will try them when the hardware is available.  I would also appreciate any other ideas about how to correct the incompatibilities.  Thanks again.

[Caroline Bright]

Hi,

I still do not believe that there is any sort of incompatibilty between LabVIEW7.0 and TestStand 2.0.  What may have happened is that the execution order may have changed between the LabVIEW versions and that may be why you are seeing the error now.  I would use normal debugging steps and try and narrow down the problem.  These debugging steps will probably be our best tool in determining what is happening.