Manual -> Energy Edition -> Command input -> Engineering in the Editor -> Define command input -> Command conditions -> Define command conditions -> Internal interlocking conditions |
Show all Hide all |
With the help of the internal interlocking conditions the basic requirements for the action are checked (plausibility check). The results resp. the activation of an interlocking are displayed during runtime in the command input window as interlocking condition.
Status already exists |
The state which should be set equals the current value of the response variable. This check is only active if the command interlocking of the 'Nominal/actual value comparison' is active. This interlocking is unlockable. |
Internal error occured |
Command cannot execute the check. Example: Action 'Single command On' for
string variables |
no interlocking object |
Command interlocking could not be
determined. |
Action not defined |
Action to be executed could not be
determined. |
Differences between local and global interlocking |
Single command parameter not consistent.
Parameterizing error |
One or more values are not available |
Value of condition variable not available.
Lock code: 14 |
Locking administration not valid |
The administration of the lockings could
not be loaded or is invalid. |
Datapoint locked for changes |
Command locked by response variable
(congestion). |
SBO rejected |
The activation of the Select was rejected
by the PLC. |
Timeout for SBO activation |
No confirmation for the activation
(positive or negative) was received within the timeout. |
Timeout for SBO deactivation |
No confirmation for the deactivation
(positive or negative) was received within the timeout. |
Timeout for execution |
There was no notice for finishing the
action execution within the timeout. |
SBO expired |
The PLC has reported the expiration of the
SBO activation. |