Why Does My TestStand Sequence Crash/Lock When Using the Auto Schedule Step Type to Lock Resources?Primary Software: TestStandPrimary Software Version: 3.1f1 Primary Software Fixed Version: N/A Secondary Software: N/A
Problem: I am using an Auto Schedule step type to lock resources in my sequence. When I attempt to run this sequence, TestStand freezes, or the steps inside the Auto Schedule step type do not behave as expected. How do I fix this? Solution: If a step within the Auto Schedule block forces the block to exit abnormally, the resources locked by the Use Auto Schedule Resource steps are not released. If you attempt to reenter the Auto Schedule block without first exiting the sequence context (for example with a loop), the resources will still be locked. This could lead to the system waiting for the locked resources indefinitely. To avoid this issue, do not use Goto steps or Post Actions in the Auto Schedule portion of your sequence. If you must use a Goto step, have the step destination be at the end of the Auto Schedule block. Also, this problem does not occur if you exit out of the sequence context. Thus, having the Auto Schedule block in a subsequence would also solve this issue. Related Links: Attachments:
Report Date: 10/17/2005 Last Updated: 06/23/2006 Document ID: 3QGG2U8M |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
