Action: AddDevice

Function: The action adds a new device to the device tree.

Call: Devices test driver

Tab: Configuration

Device name	Name of the new device
Parent object	Object path of the node below which the new device is inserted : Copies the settings of an object which are selected in the POUs tree or device tree to the input field : Opens a list box with suitable objects which are configured in the open project
Add	The device is added below the parent object at the last position.
Insert before	The device is added before the object specified here. : Copies the settings of an object which are selected in the POUs tree or device tree to the input field : Opens a list box with suitable objects which are configured in the open project
Slot ID	Slot where the device is added
Device ID	Identification of the new device description The Module ID is optional here because it is required only for some devices. The […] button opens a device selection dialog (device repository). You can apply the data from a selected device to the configuration.
Device type
Module ID
Device version
Newest	: The newest available device description with matching Device type, Device ID, and Module ID is selected at runtime.
	Opens the Select Device dialog which lists all installed devices

Tab: Parameters

The parameters defined on the Parameters tab are used to exchange values between test script variables and parameters of test actions. Parameters can be used as placeholders on the Configuration tab. For this, the name of the parameter is set in braces in the configuration dialog. Example: {name}.

Tip

Variables defined globally in the script (with the prefix $GLOBALS.) can be used directly in the test action. It is not necessary to use input parameters for passing. Using output parameters is necessary for writing global variables.

Input parameters: When executing the test action, the values of the test script variables are passed to the input parameters of the test action and can be used in the configuration of the test action.
Output parameters: When executing the test action, the values of the output parameters of the test action are passed to the test script variables and can be used (for example, in other test actions).
Name	Name of the input/output parameter This name is defined in addition to the variable name to identify the origin of the parameter when it is passed to another script. During the test run, this name is displayed as the Outer name on the Variables (scope #<n>) tab in the Test progress window. Background: When a script `A` calls another script `B`, and its variable `x` passes `y` as a parameter to the script `B`, then the parameter `y` is the variable `y` from the point of view of script `B`. To see that this variable is recognized as variable `x` "outside" of script `B`, there is the Name column ("Outer name"). The variable `y` has the name `x` in the scope pf script `B` because it has been passed as variable `x` to the parameter `y` in the scope of the calling script `A`.
Variable	Name of the test script variable Example: `TS_CaseA_Result`
Move Up	Moves the selected variable one line up
Move Down	Moves the selected variable one line down
Remove	Removes the selected variable from the list