Action: CheckIncrement

Function: The action checks whether or not a specific variable value changes linearly within a specified time period.

Call: Monitoring test driver

Tab: Configuration

Variable	Fully qualified name of the variable instance to be checked When a project is loaded, the Input Assistant is available to help with this (auto-completion or intelligent coding).
Count loops	Number of test cycles
Interval (ms)	Waiting time for a cycle before changing the variable value
Increment by	Expected value change of variables per cycle Negative values are permitted.

Table 56. Overflow settings

Values wrap at overflow

standard icon : For a value overflow, the value is wrapped for the selected data type. The upper and lower limits for all IEC data types of CODESYS are displayed here. You can define your own intervals for user-defined types (Custom).

Lower limit

Lower limit for the overflow of the data type set above

When the value is changed, the selection jumps upwards to Custom.

Upper limit

Upper limit for the overflow of the data type set above

When the value is changed, the selection jumps upwards to Custom.

Table 57. Tolerance settings

Exact match	: No tolerance The values have to be identical.
Relative	: A percentage of deviation is permitted. The permitted percentage is defined in the field below.
Absolute	: An absolute deviation is permitted. The permitted deviation is defined in the field below.
Time (Jitter)	The values have to match, but the time may vary. The permitted time deviation is defined in the field below.

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