Actions

Command interlockings always contain a set of predefined actions, which are usually adjusted to a specific data point (a specific device) . For example, different command interlockings can be defined individually and centrally for different topological elements (switch / disconnector etc.) .

A defined command variable is assigned to every action inside a command interlocking. The response variable is defined centrally for the whole command interlocking.

To simplify and to generalize the definition of the data points, these data point references (for command and response variables) can be defined over a name substitution (wildcard use). With this flexible definition, general interlocking conditions can be defined very simply. As a consequence, the number of command interlockings that have to be defined is reduced drastically.

Example

Definition of the command variables '*_BE'
Definition of the response variables '*_RM'

During runtime, the command input automatically adds the name of the response variable, which is shown/selected in the process picture, to the name of the command variable. The names of both data points differ only in their endings.

The action types are the actually available switching commands. According to the command, different activities are performed.

The system provides a variety of actions. The following types can be defined for command interlockings.

Action type: ' Command'

According to the command type, this is used as 'Single command' or 'Double command' in the system.

When a command is executed, the configured Command status (0 or 1) is written to the command variable. The value which is expected from the response variable as a result of the command is defined under the property 'Switching direction (on / off / none)'.

Switching direction	Value of the response variable
None	Will not change
Off	Value will be 0
On	Value will be 1

For single commands, there is an automatic reset of the variable to 0 or 1 (depending on the switching direction), after the engineered 'edge delay'. This does not apply if SBO is activated for the command variable.

Info

If during the action execution the current value of the response variable is different to the one defined in the switching direction or if the switching direction was defined to be On or Off, the status bit 'DESIREDDIRECTION(10)' is set.

Action type: ' Setpoint default'

Offers the possibility to write any numerical value to the selected command variable. The command window offers special control elements for that, which allow the definition of the set value. No other settings are necessary for the action.

Action type: ' Status default'

Depending on the definition in the 'Switching direction', the following is executed:

Off	The states configured in the list "modifiable states" are all reset to 0.
On	The states configured in the list "modifiable states" are all set to 1 (active).
None	The states configured in the list "modifiable states" must be defined in the RT over the control element 'Set status'. Every status is defined individually.

If you change a status in the Runtime, that change is logged in the Chronological Event List (status incl. value). You can make that language-switchable in the Runtime.

Info

For all status defaults, there is always a write to the response variable.

Action type: ' Release'

Sets the status bits 'OFF' and 'ALTERNATIVEVALUE' of the selected response variable to 0.

Action type: ' Correct'

Sets the value of the selected response variable, according to the setting of the 'Switching direction', as follows:

Off	0
On	1
Diff	2
Fault	3
Set value	Value of the control element 'Set value' is written to the response variable.

Info

Action type: ' Replace'

The response variable is set to the status alternative value (EWERT aktiv). Additionally, the value defined by the 'Switching direction' is placed on the response variable.

Off	0
On	1
Diff	2
Fault	3
None	4

Action type: ' Lock'

Enables the lock of a response variable for the actions of the command input.

Prerequisites for this is that there are users present in the system who have a configured 'Lock code'. Locking/unlocking a response variable can only be done with the correct input of a 'Lock code'.

The same variable can be locked by multiple users in parallel. Actions for the response variable are possible only after alls locks have been unlocked by entering the lock code.

There can be no actions executed if

the locked variable is used as an action variable
actions of the command variable use the locked variable as response variable

The lock code can be defined individually for every user. This parameterization is done directly for an already existing user with the property 'lock code'

You can also set the lock code during Runtime/Online for an existing user.

During Runtime, you cannot delete users, who still have an active command lock.

Attention

Users can be deleted in the development environment. This causes the loss of the defined locks after restarting or reloading.

Users locked (deactivated) in the administration cannot activate or deactivate command locks.

Info

Information about active locks are also synchronized in the redundant network and therefore are available after a server switch.

Info

A list of the currently active locks can be shown in the command picture over a special control element ('lock list').

Action type: ' Revision'

Sets the statusbit 'Revision(9)' of the response variable to the value configured in the 'Switching direction'.

Off	Set to 0
On	Set to 1

Action type: 'Block'

By executing this action, the response variable is switched off.

Sets the status bit 'N_AKT' of the response variable.