A process model invokes plug-in instances at defined points during execution. A plug-in instance specifies the plug-in sequence file to invoke and the set of options with which to invoke the sequence file. At run time, the process model reads the set of plug-in instances to invoke from the plug-in configuration (.cfg) files located in the <TestStand Application Data>\Cfg\ModelPlugins directory. By default, TestStand creates the ResultProcessing.cfg and Addons.cfg configuration files in the <TestStand Application Data>\Cfg\ModelPlugins directory if the files do not already exist.

ResultProcessing.cfg

The ResultProcessing.cfg file stores the information for plug-in instances you configure in the Result Processing dialog box.

Model Plug-in Add-ons and Addons.cfg

A model plug-in add-on is a model plug-in the process model invokes without requiring end users to create and configure a plug-in instance. For example, you can use an add-on to override the dialog boxes the Test UUTs and Single Pass Execution entry points launch and create a custom serial number entry solution instead.

Place a model plug-in sequence file in the <TestStand Public>\Components\Models\ModelPlugins\Addons directory to create a model plug-in add-on. The process model updates the Addons.cfg file when the model detects a new, removed, or updated plug-in in the Addons directory. The process model automatically uses the default set of options the add-on sequence file defines to create one plug-in instance for each add-on in the Addons.cfg file.

Creating Additional Model Plug-in Configuration Files

You can create additional model plug-in configuration files in the following ways:

  • Call the DisplayModelPluginDialogEx function in ModelSupport2.dll as defined in ResultProcessing.h, located in the <Teststand>\Components\Models\TestStandModels directory, to launch a dialog box that creates and edits a configuration file.
  • Copy an existing configuration file to a new filename, open the new file in a text editor, and replace any occurrence of the previous filename with the new filename.
  • Create a configuration file programmatically using an instance of the PropertyObjectFile class with a file type of FileType_PropertyObjectFile. The type of the PropertyObjectFile.Data property of the file must be NI_ModelPluginConfigurationSet.