How to manage variables in dynamically loaded sequence

Question

Variables in dynamically loaded sequence files are not managed properly.
Steps to reproduce:
1. Unpack attached zip file
2. Launch TestStand Sequence Editor
3. Add directory of unpacked files to Search Directories list (Configure>>Search Directories...)
4. Set Station Model to unpacked "UpdatedSequentialModel.seq" (Configure>>Station Options...; Model tab in TestStand Sequence Editor)
5. Load unpacked "A.seq" sequence file  (File>>Open Sequence File.. in TestStand Sequence Editor)
6. Check "Execute>>Break on First Step"
7. Run "Test UUTs"
8. When execution breaks, note the following:
a) "Locals.SomeVar" contain "The value, which stored in the file" instead of "New value"
b) Although actual running sequence file is "B.seq", the tab title is: "Test UUTs - A.seq"
Try also:
1. To examine "RunState.ProcessModelClient.Data.Seq["MainSequence"].Locals.SomeVar" variable, when breakpoint is set at <End Group> of PreUUT of Station Model "UpdatedSequentialModel.seq".
2. Open unpacked "B.seq" sequence file in TestStand Sequence Editor and repeat all the checks
Additional info:
1. I use TestStand 4.0.0.326
2. Attached Process Model file "UpdatedSequentialModel.seq" is original "SequentialModel.seq" with only one step "UpdateClientSequence" added in PreUUT.
3. The source of mentioned above new added step is attached as well.
thanks.misha
Attachments:
UpdateClientSequence1.zip ‏135 KB

Answer 1

Kristen,
"Why I architect "My application" this way?"
"My application" is intended to serve significant amount of test stations and products. Each product is represented by its own test sequence file.
"My application" and client sequence files are independent products. Client sequence files are responsible for products testing, while "My application" is responsible for common tasks.
Process Model is most pertinent place to perform common tasks (common for all test stations and for all products).
Providing supplemental sequence file just to perform SequenceCall, is completely unnatural.
Moreover, if using SequenceCall, I see no way to update local variables of new launched sequence file, before it starts to execute (step 5 of "Message 3 of 4").
Thus, the solution, which you propose, cannot satisfy our factory requirements.
Back to my questions.
1. Is something wrong with the way, which I implement the task?
2. Is it possible to implement my task using NI TestStand?
3. Is my problem caused by incorrect usage of "edit copy" and "runtime copy" of the variable? TestStandReferenceManual says:
"Built-in properties of steps and sequences are flagged to be shared at run time. For these shared properties, TestStand does not create a unique run-time copy, but instead references the edit-time copy. Any changes to the run-time reference of these built-in properties edits the original Step or Sequence object in the sequence file."
The variable, which we discussing is not Built-in property.
4. If previous correct, how differentiate between "edit copy" and "runtime copy" of the variable?
thanks.misha
Message Edited by mishaw on 06-05-2008 07:17 AM