Batch Sequence Shutdown Test Stand Randomly

Question

Hi ,
I have a problem with Test Stand in one of my projects .
I'm using TS 4 & CVI 9.1 . TS is using CVI DLL .
The software is using parallel Device checking for 30 cards , at 25c , 75c and -15c ( temp ).
While checking 9-10 evrey thing works fine and well buy in 11 and so on TS crashes randomlly about 1 of 10 times at the crash the is no TS message only Windows not responding message .
My main idea was a Resource leaking at the CVI code but i checked it very carefully in addition i cant see the resource trekking in dll mode .
Is there any tool , even windows tool or some software i can use to track my memory while working with both programs !? or you have another idea ?
Thank you .
Kobi Kalif
Software Engineer

Answer 1

There are two possibilities for updating a local in one sequence from a subsequence which that sequence calls.
1) Pass the variable as a "By Reference" parameter to the subsequence. Then in the subsequence access it with the lookupstring Parameters.MyParameter. To add a parameter to a sequence, simply insert a variable under the Parameters group. Parameters are passed by reference by default (which is what you want). They can also be passed by value (i.e. a copy to which changes don't affect the original) by changing the setting by right-clicking on the variable and unchecking the by reference setting. Using parameters like this is very flexible and future proof. You can even call the same subsequence from multiple sequences and the subsequence doesn't have to worry about who's calling it. Also it doesn't matter what the name or location of the variable is in the caller, the subsequence just always accesses the variable as its parameter. When you specify the sequence call to call the subsequence you specify what to pass for the parameter.
1a) A variation of this which can help make your code easier to extend is to use a Custom Data Type as the type for your parameter. Make a Custom Data Type that's a container than contains the variables you want to pass. When you need to add a new parameter in the future you can just add it to your Custom Data Type and then you don't have to update any of the places where your subsequences are called to pass the new value. If you go this route I recommend storing the Custom Data Type in a type palette file and keeping it always backwards compatible as much as possible (only add variables, don't remove or change existing variables).
2) Another way which is less flexible is that you can use RunState.Caller.Locals.foo to access a local variable in the sequence which is calling the current sequence. This creates an interdependency between the two sequences though which can lead to code maintenance problems because someone could change the calling sequence's variables, not realizing a subsequence depended on the variables they are changing.
Hope this helps,
-Doug