07-11-2008 09:37 AM
07-14-2008 04:28 PM
07-14-2008 04:52 PM
07-15-2008 06:28 PM
07-18-2008 12:44 AM
07-22-2008 12:24 PM
I have not made any changes to BatchModel.seq. The modifications that I've done:
1. modify batchuutdlg.c to accept the serial numbers passed from TestStand and not blank them out each time.
2. Overridde PreBatch to do serial number processing.
3. Override PostBatch to save test data to Excel and put up a message to see if the operator wants print all the reports.
4. Override a function in reportgen_xml.seq to print all the reports if .
I got another weird error today, when running a particular test I put up a LV panel that runs in parallel with the TestStand sequence.
It displays a bunch of error messages, "Sequence Editor: BufferedGraphicsContext cannot be disposed of because a buffer operation is currently in progress".
This is the first time I've seen this error message and I'm wondering if it's related to the other error mentioned above.
Terago
07-24-2008 01:47 PM
I've fixed the BufferedGraphicsContext error. I have a tight polling loop where the steps in the loop have the "Record Result" enabled.
TS allocates memory to record results for these steps and would run out of memory after a while and cause the error.
What I don't understand is why it's still recording results even though I disable it in the calling step. I thought this would override "Record Result" for all the steps in the called sequence but this is not true.
The System Level Exception Error still remains. I look at the BatchModel.seq, it calls Run Batch Info Dialog sequence as a new thread only once at the beginning to Initialize and Run the dialog. This sequence does not get called anywhere else. In my case the error happens when the sequence is called again which should never happen. I'm wondering if any memory/stack corruption would cause the sequence to be called again?
Terago
07-28-2008 01:33 PM
07-28-2008 02:22 PM - edited 07-28-2008 02:23 PM
Hi Jessica,
Does this error occur if you run the sequence for 10 UUTs instead of 40?
If I run with just one UUT and the remaining 39 test sockets disabled the error still occurs frequently. However if I configured the model options to just 1 or 2 test sockets, I haven't seen the error (it's possible that I haven't tried long enough).
How much memory is there on your test system?
1GB.
Can you place a breakpoint in your process model to monitor when the sequence is called a second time?
Where exactly in the process model do you suggest? I've noticed when the error occured, the arrow is pointing to the "Run Dialog" step and the calling stack window displayed only the "Run Batch Info Dialog" sequence on top of the stack so I'm not sure where it's called from. The error typically happens after MainSequence have finished and before the test status box is displayed.
Is it possible for you to post your sequence file so that I can take a look at it?
I'd rather not post it in the forum. I probably can email it to you if you give me your email address.
Thanks,
Terago
07-28-2008 03:29 PM