NI TestStand

cancel
Showing results for 
Search instead for 
Did you mean: 

Problem with LabVIEW OI - error code 1100 Create Queue.vi

TestStand 2.0.1f1 and probably TestStand 3.0 Old Style OI.

The Problem occurs if a SequenceCall which has been set to execute in a new execution but has been set initially hidden.
An Error Dialog box appears relating to Error Code 1100 from Create Queue.vi in TestStand - Refresh Windows.vi.
This seems to be caused because a Refresh Windows message is tried to be generated for a window that doesn't exist.
Solution:
In the VI TestStand - Refresh Windows.vi
Encase the vi's Create Queue.vi and Insert Queue Element.vi in the False Case Statement panel.
Expand the named cluster to include the TS.Thread. Test the TS.Thread if it is a valid refnum and wire the boolean result to the new case statement selector ter
minal.

I have attached a modified TestStand - Refresh Windows.vi

Regards
Ray Farmer
Regards
Ray Farmer
0 Kudos
Message 1 of 4
(3,374 Views)
Ray,

I tried to mimic the behavior that you explained on your post here on my system, but everything ran fine. I basically created a new sequence that has only 1 step of type sequence call. This step launches a new execution (Initially Hidden) with a sequence that has a message pop up. Am I missing something to be able to expose the error?

Thank you for all your contributions to this forum, you definitly enrich the discussion for all Teststand users around.

Best Regards,

Alejandro del Castillo
Application Engineer
0 Kudos
Message 2 of 4
(3,374 Views)
Hi,

Sorry, should have said that we are using one of the Callbacks PostStepFailure for a stop on fail.

Hope this helps.
Regards
Ray Farmer
Regards
Ray Farmer
0 Kudos
Message 3 of 4
(3,374 Views)
Ray,

I tried using the poststepfailure callback and still couldn't reproduce the error. I am attaching the sequence that I am using to see if you can point me out what needs to be modified so I can reproduce the behavior. Then, I will have enough information to pass this to R&D and make sure we have your fix available for future users.

Thanks for everyhting,

Alejandro del Castillo
Application Engineer
0 Kudos
Message 4 of 4
(3,374 Views)