ATLAS Step Type

Purpose

This example demonstrates a custom step type for calling an Abbreviated Test Language for All Systems (ATLAS) test program set (TPS), which is created in the PAWS Developer Studio. The ATLAS custom step type integrates with the PAWS Run-Time System (RTS) to execute TPS files (.PAWS). These examples require the TYX PAWS RTS Server to run the provided test program sets.

The ATLAS custom step type example includes the following example sequence files:

• A parameter passing example that demonstrates passing parameters between TestStand and a TPS.
• A manual intervention example that demonstrates support for handling a request for manual intervention by the PAWS RTS Server.

Example File Location

<TestStand Public>\Examples\Custom Step Types\ATLAS Step Types\Parameter Passing Example.seq

<TestStand Public>\Examples\Custom Step Types\ATLAS Step Types\Manual Intervention Example.seq

Highlighted Features

Custom step types

Major API

N/A

Prerequisites

TYX PAWS RTS 1.22 or later

How to Use This Example

The example sequence files contain a SequenceFileLoad callback that TestStand automatically executes when you open either sequence file. The SequenceFileLoad callback copies the ATLAS_StepType.dll file from the <TestStand Public>\Examples\Custom Step Types\ATLAS Step Types directory to the <TestStand Public>\Components\StepTypes\ATLAS directory and registers the DLL. The ATLAS custom step type calls functions within ATLAS_StepType.dll to configure and handle interactions between TestStand and PAWS.

You must install the PAWS RTS with the TPS Server before you can build the accompanying project. You must contact TYX Corporation for more information about obtaining the PAWS RTS.

The project assumes you have installed the PAWS RTS in the default location of C:\usr. If you installed the PAWS RTS in a different location, modify the path in the following lines of code, located in <TestStand Public>\Examples\Custom Step Types\ATLAS Step Types\ATLAS\StdAfx.h, to reflect the new location:

• Change the line#import "C:\usr\tyx\com\rtsax.dll" raw_interfaces_only to#import "<New Location>\tyx\com\rtsax.dll" raw_interfaces_only
• Change the line#import "C:\usr\tyx\com\ComUtil.dll" raw_interfaces_only to#import "<New Location>\tyx\com\ComUtil.dll" raw_interfaces_only

When you set the paths correctly, you can build the ATLAS custom step type project with Microsoft Visual C++ 6.0.

The ATLAS custom step type creates the PAWS RTS and executes a TPS through the PAWS TPS COM Server, and communicates with the TPS server by calling methods within the NI ATLAS Step Type ActiveX server located in ATLAS_StepType.dll. The server contains the IExecuteTPS class, which includes the following methods:

• Edit Step—Sets up a TPS to call and the parameter to pass to the TPS.
• Execute TPS—Creates the PAWS RTS and executes a TPS.

The ATLAS custom step type supports the use of the TestStand numeric, Boolean, and string types. You can use parameters of these types to pass data between TestStand and the TPS server. Data is exchanged through COM boundaries between the ATLAS custom step type in TestStand, the NI ATLAS Step Type server, and the TPS server, which monitors the PAWS RTS server, as shown in the following figure.

Parameter Passing Example

When you open the ParameterPassingExample.seq example sequence file, the SequenceFileLoad callback copies the required files to the appropriate directories. When TestStand executes the Main step group of the MainSequence, TestStand launches a dialog box that requests a numeric value to pass to the sample TPS. TestStand passes the numeric value, along with various other parameters, the TPS server. The sample TPS modifies the numeric value and parameters and shows the modified values when execution returns to TestStand.

Manual Intervention Example

When you open the ManualInterventionExample.seq example sequence file, the SequenceFileLoad callback copies the required files to the appropriate directories. When TestStand executes the Main step group of the MainSequence, the ATLAS step calls a TPS that simulates and tests several devices. When the TPS simulates the DMM, TestStand launches a dialog box that prompts for the simulated voltage. If you enter a voltage that is within the acceptable range of 21 to 23 V, the test passes. Otherwise, the test fails.

During execution, the TPS server also simulates a manual intervention request, in which you can pause the execution while the TPS server resolves the condition that caused the request. The simulated manual intervention launches a dialog box on the same computer on which TestStand is running to inform you that manual intervention has been requested. Click Continue in the dialog box to resume TPS execution from TestStand.

Using the ATLAS Step in New Sequence Files

You can call an ATLAS TPS using step instances of the ATLAS custom step type. The example sequence files contain ATLAS steps preconfigured to call a sample TPS. You can execute these sequences without making changes. You can also use the ATLAS custom step type in your own sequence files to call an ATLAS TPS. You can insert an ATLAS step into a sequence in one of the following ways:

• Copy an ATLAS step from one of the example sequence files to the new sequence.
• Copy the ATLAS custom step type from one of the example sequence files to the new sequence.
• Add the ATLAS custom step type to a type palette file and use the Insert Step submenu in the Steps Pane context menu to create an instance of an ATLAS step.

Before you can execute a sequence that contains an ATLAS step, you must configure the step to call the appropriate TPS and pass any desired parameters. Click the Edit ATLAS Step button on the Step Settings pane to launch the Edit ATLAS Call dialog box, in which you can specify the TPS the step executes and the parameters passed between TestStand and the TPS.

You can then execute the sequence that contains the steps. The ATLAS custom step type fails on an ATLAS step if any faults are reported when the TPS executes. The ATLAS custom step type also propagates and reports any errors the TPS server encounters to TestStand. If the TPS server encounters no errors or faults, the step passes.

When TestStand first executes an ATLAS step, the ATLAS custom step type loads an instance of the RTS, or attaches to an existing RTS if one already exists. TestStand stores a reference to this instance as a temporary global variable in the TestStand Engine. Future executions of the ATLAS custom step type use the same reference for TPS executions. The engine releases the reference when it shuts down.

Limitations

The following are known limitations of the ATLAS custom step type:

• The step type does not support passing TestStand arrays, containers, or object references as parameters.
• You can execute only one ATLAS step at a time for each local or remote computer. The ATLAS steps are locked globally with respect to the name of the local or remote computer. A sequence might contain multiple ATLAS steps that pertain to the same local or remote computer, but the step executions are sequential. You can execute ATLAS steps that pertain to different computers simultaneously.
• The TestStand Deployment Utility does not automatically copy and register ActiveX servers. You must add ATLAS_StepType.dll to the list of deployment files to deploy the ATLAS custom step type. When you deploy the step type, you must register the NI ATLAS Step Type ActiveX server. Refer to the SequenceFileLoad callback sequence in either ATLAS example sequence file for an example of registering an ActiveX server.

Error Codes and Descriptions

You might receive some error codes when using this example.