Error -17300 is generated when running selected step

Question

Error -17300 is generated when running selected step (with ot without process model).
Using TestStand 2.0.1f1
See BMP file for error dialog.
I was trying out the example in the Resource Library - TestStand | Process Models | Running Selected Steps via Execution Entry Point -Test UUTs or Single Pass
(link http://sine.ni.com/apps/we/niepd_web_display.display_epd4?p_guid=B45EACE3E2B756A4E034080020E74861&p_node=DZ52222&p_source=external ). This example is a 1.0.1 example but the web page does say that it should work in 2.0.x
I followed the readme file to use from "Execute" menu:
I have attached the resulant SequentialModel.seq file.
The modifications to the SequentialModel.seq file appears to wo
rk, but when I tried to run 'Run Selected Steps Using' menu item. I got the error message -17300 displayed. (see ErrorScr.bmp attached). The only way to close the execution was to launch Task manager and 'End Task'.
I have attached a small demo sequencefile.
To try example:
Move the SequentialModel.seq to 'C:\TestStand\Components\User\Models\TestStandModels'.
Launch TestStand Sequence Editor and open 'Debug Example1.seq'.
This is how to generate error condition-
1. Run the sequence file from menu Item Execute | Single Pass. You should get a full run with test result, it fails but that doesn't matter.
2. Select Steps 1 and 3 in Main of MainSequence. Run Selected Steps using Single Pass. Again sequence executes correctly.
3. Now run the same selected steps using the new menu item Execute | Selected Test(s). Again the sequence executes again.
4. With Steps 1 and 3 still selected. Run Selected Steps using Single Pass (as in 2 above). This time the error -17300 will be gener
ated.
I also tried running the sequence first doing step 1 (as above), then step 3, then repeating step 1 and this was ok. So the problem appears to be in interactive only.
Any clues as to whats going on and how to resolve it.
Regards
Ray Farmer
Regards
Ray Farmer
Attachments:
SequentialModel.seq ‏174 KB
Debug_Example1.seq ‏19 KB
ErrorScr.bmp ‏915 KB

Answer 1

Hi,
TestStand 2.0.1f1
Attached is a SequentialModel.seq that will run selected steps in a new execution using the process model. (It started life based on the inital
demo example)
When either Test UUT's or Single Pass is selected a check is made to determine if there is an initial selection.
If there isn't then the normal Test UUT's or Single Pass sequence is run.
If there is then a new sequence file is created with a new MainSequence. The selected steps are cloned and inserted to the new MainSequence. Also
the Setup and Cleanup groups are also cloned. Likewise the FileGlobal Defaults are copied to the FileGlobals of the new Sequencefile and also the
Locals.
Any Sequences contained in the SequenceFile are cloned to the new sequencefile (except the MainSequence, SequenceFileLoad and SequenceFileUnLoad).
In addition, as the Steps are cloned any break point are also set in the new sequence file.
The new sequence file is executed in a new execution using the process model entry point with the break on first step controlled from the menu
option.
One thing I am assuming is that there is only one element in the RunState.InitialSelection.SelectedSequences array.
Question: Under what circumstances will there be more than one selected sequence?
I had one problem, I tried my SequentialModel.seq with the demo auto.seq. This contains the SequenceFileLoad and SequenceFileUnload.
When I run this demo with a few steps selected, it run ok but when I closed the results window the UnloadFile callback was executed.
I found an option that can be set with the Engine.ReleaseSequenceFileEx which should have stopped the UnloadFile callback from running. But it
made no difference.
I then came across SequenceFile.UnloadCallbackEnabled() and using this function it did disable the Unload callback and this worked.
Question: So, Why didn't setting the Option in the Engine.ReleaseSequenceFileEx work?
Limitation using this SequentialModel.seq,
1) Any precondition to a step's execution based on the result of an early steps are not check when cloning the selected steps. Therefore this has
to be done manually when making the selection.
2) All Sequences in the SequenceFile are cloned to the new sequencfile. (May not be a problem when SequenceFile contains only a few sequences.)
3) The selections are limited to the MainSequence. If steps are selected in a Subsequence then these would be copied to a new MainSequence and
this would be run. Providing this doesn't require any parameters passed from the original caller then this should still run. The problem will
arise if parameters are required.
4) This is not really a limitation - If a full run of the SequenceFile using Test UUT's or Single Pass is required then the user must ensure no
steps are selected.
What I whould like to happen is the ability to make a selection in SubSequence calls either one or two levels down from the MainSequence. The new
execution setup would contain those steps in the MainSequence that are required to call those selected steps in the lower levels.
Would welcome any comments on my SequentialModel.seq attached and answers to my questions.
Regards
Ray Farmer
Regards
Ray Farmer
Attachments:
SequentialModel.seq ‏233 KB