How do I Make a Custom Process Model?

TestStand allows you to easily and quickly create a process model. You may choose to create a new sequence file with process model attributes, but due to the complexity of a process model, it is much easier to modify the behavior of a pre-existing model. This tutorial will teach you how to copy a pre-existing, default process model and modify its content to change its behavior.

Copying the Default Process Model

Before modifying a default process model, you must first copy a pre-existing process model. From Windows Explorer, copy the contents of <TestStand>\Components\Models\TestStandModels to <TestStand>\TestStand Public\Components\Models\TestStandModels 

Note 1: Prior to TestStand 4.1, components in the <TestStand>\Components\USER\ directory took precedence over components in the <TestStand>\Components\NI\ directory. Hence, any default files you wish to modify in the NI directory should be copied and modified in the USER directory. TestStand 4.1 and later implements a directory installation change to comply with Windows Vista restrictions on writing to the Program Files directory. Because of this directory installation change, you will copy the <TestStand>\Components\Models\TestStandModels directory to <TestStand Public>\Components\Models directory.

After copying the contents, launch the TestStand Sequence Editor. Note on the bottom-left corner of the screen that the path to TestStand Station Model is now referencing the copied process model. This will now be the copy that TestStand will use to execute your routines.

Figure 1. Loaded Process Model

Modifying the Process Model

Open the copied process model by double-clicking on the displayed process model string found on the bottom-left corner of the TestStand Sequence Editor, as shown in Figure 1. You may now modify your copy of the process model by adding steps or variables to perform the specific operations that you need. You may also add new sequences, callbacks, execution or configuration entry points.

When you add steps to the execution entry point sequences, you are strongly encouraged to disable Record Results. Only the results of the MainSequence Callback should be sent to the TestReport Callback for reporting. Enabling Record Results for steps other than the MainSequence callback will cause the results of the step(s) to appear in your test report.

Figure 2: A TestStand Process Model

Related Links:
Developer Zone Tutorial: What is a Configuration Entry Point?
Developer Zone Tutorial: Adding Configuration Entry Points to TestStand Process Models
Developer Zone Tutorial: Adding Execution Entry Points to TestStand Process Models

2 ratings | 3.50 out of 5

Print

Reader Comments | Submit a comment »