How to Implement Test UUT concept in TestStand 4.0 using C#.NET

[rkk]

Hi,

I do start of implementation of Test UUT concept in TestStand 4.0 using C#.NET. Please can any body explain me the same.

Thank you,

Regards

RKK

[Jonathan_C]

Hi RRK,

I am assuming that you are talking about implementing a custom Operator Interface using C#.NET to run a UUT Test.  Based on this assumption, you should be able to use the C# User Interface examples that are shipped with TestStand 4.0.  There are two sepearte C# examples that are provided.  One is a Full Featured Operator Interface and the other example is a Simplified Operator Interface.  These examples are located at C:\Program Files\National Instruments\TestStand 4.0\UserInterfaces\NI\Full-Featured\CSharp and C:\Program Files\National Instruments\TestStand 4.0\UserInterfaces\NI\Simple\CSharp.

[rkk]

Hi Jonathan C,

Thank you for reply. We are implementing own GUI using TestStand API's to test the UUT. Could you please explain me about API which is used for test UUT?. AS we seen option to test UUT in TestStand 4.0, similarly we would like to implement.

Thank you,

Regards

RKK

[Jonathan_C]

Hi RKK,

You can use the Engine.NewExecution Method in the TestStand API to launch a new sequence file execution.  This method creates and returns a new Execution object.  When you call this method, the execution begins immediately.  The TestStand 4.0 Sequence editor uses this method to run sequences.

The full documentation for the Engine.NewExecution Method can be found in the NI TestStand help.  This method has the following required parameters:

• sequenceFileParam As SequenceFile
• Pass the SequenceFile object that contains the sequence to execute. If the execution uses a process model, pass the client SequenceFile object.
• sequenceNameParam As String
• Pass the name of the sequence or Process Model entry point to execute.
• processModelParam As SequenceFile
• Pass the process model SequenceFile object if you want to execute a Process Model entry point.
• Otherwise, a NULL object reference in LabVIEW, 0 in LabWindows/CVI, the Nothing keyword in Visual Basic, or a NULL dispatch pointer in MFC.
• breakAtFirstStep As Boolean
• Pass True to suspend execution before executing the first step.
• executionTypeMaskParam As long
• Pass 0 for the default behavior or pass one or more ExecutionTypeMask constants. Use the bitwise-OR operator to pass multiple constants.

[James_Grey]

If you look in the source code for the simple C# UI, you'll find the following line:

axSequenceFileViewMgr.ConnectCommand(axEntryPoint1Button,

CommandKinds.CommandKind_ExecutionEntryPoints_Set, 0, CommandConnectionOptions.CommandConnection_NoOptions);

This is what connects the Test UUTs command to the button.

If you want execute the Test UUTs command yourself, you could call:

axSequenceFileViewMgr.GetCommand(

CommandKinds.CommandKind_ExecutionEntryPoints_Set, 0).Execute();

This runs the first process model entry point, which by convention is Test UUTs.

Note that this call does nothing if the first process model entry is not currently available or not applicable (in this case the button connected to this same command will be dimmed).