Compiling Error

When compiling command interlockings, a comprehensive check for errors and missing links is conducted.

Info

After an Error the object the caused the error is not available during runtime.

If the command interlocking has an Error, no command interlocking is assigned to the data point. Consequently, during the Runtime, all user operations are locked.

A Warning is generated when the project would cause a problem but runs error-free.

In the error messages, the following placeholders are used:

<VERNAME>	Placeholder is replaced in the error message by the name of the command interlocking.
<VERRM>	Placeholder is replaced in the error message by the name of the response variable.
<AUFVAR>	Placeholder is replaced in the error message by the name of the data point, to which the command interlocking is assigned.
<ACTVAR>	Placeholder is replaced in the error message by the name of the data point of the action.
<Actionname>	Placeholder is replaced in the error message by the description of the action.
<VARNAME>	Placeholder is replaced by the data point in the visualization.

The following error messages can be displayed during compiling.

Message text	Description
<VERNAME>: Interlocking PV <VERRM> does not exist!	Condition variable for general interlocking not available.
Variable '<AUFVAR>' uses not existing command input!	Variable uses a non-existing command input.
(<AUFVAR>) command input '<VERNAME>' contains no actions!	Command interlockings without action are not considered by the Runtime. This message can also be a follow-up error.
(<AUFVAR>) response variable '<VARRM>' does not use the command interlocking '<VERNAME>'	A response variable using another command interlocking is used. The response variable always has to be linked with the interlocking, which uses it as response variable.
(<AUFVAR>) response varibale '<VARRM>' for command '<VERNAME>' uses a driver without process linking!	The response variable must lie on a driver with process connection.
(<AUFVAR>Command '<VERNAME>' contains no actions after compiling!	A command interlocking without actions does not make sense.
(<AUFVAR>) response variable '<VARRM>' of command '<VERNAME>' not available!	The used response variable is not present or marked as deleted.
(<AUFVAR>) command '<VERNAME>' uses picture '<Bild GUID>'(<BILDNAME>) which is not of the type Power!	This message is a warning. If a user action becomes necessary during execution, it cannot be performed.
(<AUFVAR>) command '<VERNAME>' uses not available picture '<Bild GUID>'!	The picture assigned to the command interlocking does not exist.
(<AUFVAR>) Substituted action variable '<ACTVAR>' for action '<Actionname>' of command '<VERNAME>' not available!	The action variable, after a substitution, is not present or marked as deleted.
(<AUFVAR>) action '<actionname>' of the command input '<VERNAME>' uses the not existing variable '<ACTVAR>'	The action uses a data point, which is not present in the project or marked as deleted.
(<AUFVAR>) action variable '<ACTVAR>' for action '<Actionname>' of command '<VERNAME>' uses a driver without process connection!	The data point assigned to an action must not lie on an internal driver.
<VERNAME>(<AUFVAR>): Aktion '<Actionname>' already exists!	The following actions may only be configured once per action variable and command interlocking: Double command with the same command status. Correction with the same switching direction. Replacing with the same switching direction. Revision with the same switching direction. Single command Setpoint default Release Block Lock
<VERNAME>(<AUFVAR>): Action '<Actionname>': Single and double command for the same command variable not possible!	Single and double command must not be used in parallel.
(<AUFVAR>) command '<VERNAME>' uses picture '<Bild GUID>'(<BILDNAME>) which is not of the type Power!	This message is a warning. No user actions will be possible.
(<AUFVAR>) action '<actionname>' of the command input '<VERNAME>' uses the not existing picture '<Bild GUID>'!	The action is assigned to a non-exising picture.
<VERNAME>(<AUFVAR>): Interlocking PV '<VARNAME>' does not exist!	Substituted condition variable does not exist.
(<AUFVAR>) variable '<VARRM>' of action interlocking condition of the command input '<VERNAME>' does not exist!	Data point of interlocking condition does not exist.
(<AUFVAR>) action variable '<ACTVAR>' for action '<Actionname>' of command input '<VERNAME>' uses another command interlocking!	The action variables used for a command interlocking may only be connected to no command interlocking or to the command interlocking in which they are used.
(<AUFVAR>) command variable <ACTVAR> does not have a validly compiled interlocking! Action <Actionname> removed.	The action variable used in the action has no compiled command interlocking. This message can also be a follow-up error.
(<AUFVAR>) command variable <ACTVAR> uses response variable <VARNAME>! Action <Actionname> removed.	The compiled command interlocking of the response variable contains actions with action variables which do not use the same response variable as <AUFVAR>. Hint: There must not be any actions of response variables changing other response variables.