12-12-2006 05:00 PM
12-13-2006 08:04 AM
Howdy 2and4,
I was also in the same boat as you of not understanding what the sequence context was when I first started out with TestStand.
A sequence context is an object in the TestStand API that represents the execution state of a sequence. TestStand maintains a sequence context that contains references to all objects, global variables, local variables, and step properties that relate to the execution of the active sequence. The contents of the sequence context change depending on the currently executing sequence and step.
There are edit time and run-time copies of sequence contexts. You can view the edit time sequence context by selecting View >> Browse Sequence Context. This shows you all the objects, variables, step properties that exist at edit time. During run-time additional objects are created, and thus the sequnce context will now have more information. You can view the run-time sequence context by placing a breakpoint in the sequence, then switch to the Context tab when your code breaks at that step.
Chapter 5 of the "Using TestStand" manual as well as Chapter 3 of the "TestStand Reference Manual" discuss these topics in more detail as well.
Hope this clarifies.
Best Regards,
12-13-2007 04:07 AM
I'm also new to Labview and I'm currently learning from my colleague's code.
according to the Getting Started manual, page 10-6:
"Add additional controls to the front panel so that the LabView Standard Prototype Adapter can call the VI from TestStand..."
As I understand, I need to specify LabView Standard Prototype Adapter so that a VI can be called from TestStand and that Test Data and error out control is a must.
Is it necessary to add context sequence? Context Sequence will contain all data and property but is it required for the code to run?
maybe i should experiment(remove the context sequence) and see how it goes 🙂
12-13-2007 04:23 AM
Hi,
You only need to add the Sequence Context control if you are going to make call to the TestStand API methods and properties.
Regards
Ray Farmer
12-13-2007 04:43 PM
rfbu,
TestStand can call any VI. It doesn't matter if the connector pane has 2 elements, 15 elements, or no elements. Using Error In and Error Out is certaintly recommended, but not required.
Keep in mind, that when you change the connector pane, you will have to reload the module in TestStand.