Agilent VEE Step Types

Purpose

This example uses ActiveX to call Agilent VEE code from TestStand using custom step types, which you can use to execute the user functions of VEE user libraries.

Example File Location

<TestStand Public>\Examples\Custom Step Types\Agilent VEE Step Types\Agilent VEE Computer Motherboard Test.seq

Highlighted Features

Custom step types

Major API

N/A

Prerequisites

VEE Evaluation, Development, or Run-Time Environment version 6.0 or later.

How to Use This Example

The example sequence file, Agilent VEE Computer Motherboard Test.seq, contains a SequenceFileLoad callback that TestStand automatically executes when you open the sequence file and that performs the following necessary actions:

• Copies the TestStand example file VEE_StepType.dll, which implements the step type functionality, from the <TestStand Public>\Examples\Custom Step Types\Agilent VEE Step Types directory to the <TestStand Public>\Components\StepTypes\Agilent VEE directory and registers the DLL.
  Note VEE_StepType.dll was created using Microsoft Visual Basic. The example directory includes the VEE_StepType.vbp Visual Basic project file, which you can use to recompile VEE_StepType.dll.
• Copies the <TestStand Public>\Examples\Custom Step Types\Agilent VEE Step Types\compMotherBoard.bmp file to the default Bitmaps subdirectory of the VEE installation directory. The SimulationDialog VEE user function displays the bitmap on its view panel. When using a bitmap on a VEE view panel, you can reference the bitmap using an absolute path or you can place the bitmap in the Bitmaps subdirectory of the VEE installation directory.

When you open <TestStand Public>\Examples\Custom Step Types\Agilent VEE Step Types\Agilent VEE Computer Motherboard Test.seq in the TestStand Sequence Editor, the VEE step types appear in the VEE group on the Insertion Palette. You can make the VEE step types available for any sequence file by copying the VEE step types from Computer.seq in the Types window to a type palette, such as MyTypes.ini.

When you insert a VEE step type into a sequence, you must configure the step by clicking the Specify VEE Module button on the Step Settings pane to launch the Edit VEE Module dialog box. For the VEE Library to Load control, specify a valid VEE library. The step automatically populates the VEE Function ring control with user functions the VEE user library exports. When you select an exported function, the step automatically populates the input and output arguments of the function. The VEE step types currently support the following data types and data shapes for arguments of VEE user functions:

• Scalar:
  • Signed 32-bit integer
  • 64-bit real number (double)
  • String
• 1D-Array:
  • Signed 32-bit integer
  • 64-bit real number (double)
  • String

You can select each input and output argument from the Argument control of the Input section and the Output section, respectively, and set a corresponding TestStand property path. The step uses the value of the property as input for input arguments or receives the output value for output arguments.

The VEE step types also support debugging. You can step into a VEE user function and use the VEE debug functionality to debug the user function.

This example includes VB_VEE_Action, VB_VEE_NumericLimitTest, VB_VEE_PassFailTest, and VB_VEE_StringValueTest step types. The VB_VEE_NumericLimitTest, VB_VEE_PassFailTest, and VB_VEE_StringValueTest step types combine the functionality of the VB_VEE_Action step with the built-in Numeric Limit Test, Pass Fail Test, and String Value Test step types, respectively, to call VEE functions in addition to the functionality of the built-in steps. For example, the VB_VEE_NumericLimitTest step returns a number from a VEE user function and compares the number to numeric limits.