CODC5
CODC5
CODC5
ANSI
Document ID 1MRS100126
Rev A 1.0
Features
General functions:
- Remote control
- Secured remote control
- Secured local control
- Interlocking
- MMI indication
- Remote indication
- Alarm of the maximum opening and closing time
Special features:
Application
The function block CODC5 can be used for controlling the open and close states of a
disconnector or an earthing switch. The function block also takes care of the user-defined
interlocking logics and has guaranteed opening and closing pulse widths. The open, close and
undefined states of an object can be indicated both remotely and locally by the function block.
1
Input Description
Output Description
Description of Operation
General
The graphical presentation of the component in the MIMIC view is defined in the REMIC tool while the
logical connection to process data can be configured by means of the RECAP tool.
RECAP configuration
The IV signal should be connected by means of the variable "BIxIV" in the RECAP tool. If BI1 and BI2,
for example, are connected to BINOPEN and BINCLOSE, the connections shown in figure 2 below
could be used for IV.
The interlocking allows open and close operations via the signals OPENENA and CLOSEENA. The
control operations are allowed if the interlocking signals for the concerned operations are TRUE. As a
default, the corresponding actions are not permitted provided the inputs are unconnected.
In addition, the system provides a general interlocking bypass mode (parameter F002V004) that
overrides all interlocking signals of the control function blocks, which means that the function blocks will
internally ignore the status of the interlocking signals and permit any control operation.
Open operation
An open command can be issued locally, remotely or by the logic OPEN signal and the corresponding
actions must be enabled by the interlocking signal (OPENENA). The function block can be controlled
both via the basic remote communication and via the local MMI. The open pulse is issued via the
OOPEN output and the pulse width can be defined by adjusting the setting value.
The open operation is possible provided the object is not blocked by the interlocking logic and the
closing pulse OCLOSE is not active. The interlocking enable signal state is checked on the rising edge
of the open signal and thus, if the interlocking signal blocks the open signal after the rising edge, the
blocking will not cancel the open operation. The secured object control is a special case and does not
directly affect the logic control and the direct control of the object.
The normal open operation is enabled if the OPENENA signal is active, whereas the logic open control
is enabled if the OPENENA signal is active and the OPEN signal rises or if both the signals are
activated at the same time. If the interlocking is not used, the OPENENA signal should be active.
Close operation
A close command can be issued locally, remotely or by the logic CLOSE signal and the corresponding
actions must be enabled by the interlocking signal (CLOSEENA). The function block can be controlled
both via the basic remote communication and via the local MMI. The close pulse is issued via the
OCLOSE output and the pulse width can be defined by adjusting the setting value.
The close operation is possible provided the object is not blocked by the interlocking logic and the
opening pulse OOPEN is not active. The interlocking enable signal state is checked on the rising edge
of the close signal. The secured object control is a special case and does not directly affect the logic
control and direct control of the object.
The normal close operation is enabled if the CLOSEENA signal is active, whereas the logic close
control is enabled if the CLOSEENA signal is active and the CLOSE signal rises or if both the signals
are activated at the same time. If the interlocking is not used, the CLOSEENA signal should be active.
Normally, the command priority is not a critical issue provided the interlocking signals are strictly used.
However, the design of internal control signals may cause unexpected situations and therefore, the
function block validates the logic commands on the rising edge and gives them a certain priority.
The logic commands OPEN and CLOSE are validated on the rising edge. If the command is enabled
and no other pulse (OOPEN, OCLOSE) is active, the command is valid and the concerned output pulse
will be started. Otherwise the command will be ignored as shown in figure 3 below.
3
OPEN
CLOSE
OOPEN
OCLOSE
Fig. 3. Close command is not validated because the rising edge occurs during the open pulse
The internal command priority determines that the open command takes priority over the close
command.
Object state
The object state is defined by the two binary inputs BINOPEN and BINCLOSE. The binary input filtering
time can be adjusted in the RECAP configuration separately for each binary input used by the function
block.
Open ON OFF
Close OFF ON
Undefined 11 ON ON
Undefined 00 OFF OFF
The validity of binary inputs that indicate the object state is used as additional information in indications
and event logging. The IV can be combined from the validity of inputs BINOPEN and BINCLOSE. The
non-active signal (FALSE) shows that the input state is valid, while an active signal indicates the invalid
state. The interlocking should be based on the signals OPENENA and CLOSEENA. Thus, if the validity
information is needed for blocking the control operations, additional user-defined logic should be used.
Refer to "Opening and closing pulse width" to see how the state affects the control command pulses.
The type of the pulse width can be defined with the setting parameter ‘‘Fixed pulse’’. The function block
provides two modes for characterizing the opening and closing pulse widths. The default mode (variable
pulse mode) causes a variable pulse width, which means that the output pulse is deactivated when the
object state shows that the disconnector has entered the correct state. The fixed pulse width mode
(fixed pulse mode) always uses the maximum pulse width which is a setting value defined by the user.
The state checking can be defined with the setting parameter ‘‘Forced pulse’’. The default pulse mode is
a forced pulse mode, which means that the function block will issue command pulses regardless of the
present object state, provided the other conditions are met. However, if the single pulse mode is active,
the object will check whether the object state already indicates the correct position and then ignore the
command and the command pulse. If a command is given in the forced mode and the object is already
in the correct position, the maximum pulse width will be used for the operation.
Note that if the IV input indicates an invalid state of the forced pulse, the function block will internally use
the forced pulse mode regardless of the setting.
4
Opening and closing time monitoring
The function block measures the opening and closing time of the object. The time measurement starts
when the function block activates the specific output pulse (OOPEN or OCLOSE) and ends when the
object state indicates that the object has reached the correct state or when 100 s timeout has elapsed.
Thus, the measured time includes the reaction time plus the travel time. The recorded time 100 s
indicates an unsuccessful measurement.
O OPEN
BI NCLOSE
BINOPEN
TIMOPEN
OCLO SE
BINOPEN
BINCLO SE
TI MCLO SE
Fig. 4. Time measurement for open and close commands
The alarm signal AOPEN or ACLOSE is activated if the opening or closing time monitoring detects a
time period greater than or equal to the alarm limit value. Both the opening and closing time
measurements have their own alarm limits. When an alarm condition is detected, the function block
issues detailed indications of the alarms on the MMI and via the remote system. However, if the alarm
setting limits have been set to zero by the user, the alarm signals will not be activated. The time
measurements are still carried out even if the alarm option is disabled.
The time measurement accuracy depends on the execution interval of the function block. The function
block compensates the output relay delay and the system delays internally by deducting them from the
measured time. The internal compensation factor for the delays is 10 ms.
The latest opening time and closing time are recorded. Additionally, the function block measures the
maximum opening and closing times. The recordings can be cleared all at a time by the command
‘‘Regist clear’’.
The cycle count value will be incremented when the binary input state changes indicate a full cycle.
Generally, one cycle is: close command -> closed -> open command -> opened.
5
Alarm signal acknowledgement
The active alarm signals of the function block are deactivated by acknowledgement or by the next
successful operation. The alarm signals can be simultaneously acknowledged by the rising edge of the
ACK signal, or by a local menu command or a remote command. If the ACK signal is continuously
active, new alarms are still recognized and the corresponding alarm signals are activated.
Acknowledged alarm signals will be reactivated once the same error condition is encountered again.
The following table describes supported monitoring alarm outputs and how they are acknowledged:
The system includes a general interlocking bypass mode (parameter F002V004) that overrides all
interlocking signals. Activating the interlocking bypass mode activates the interlocking enable signals of
the objects controlled. Thus, all control operations are possible and the enable signals of the
controllable objects are not checked during the control operations. As long as the bypass mode is
active, the red interlocking LED on the MMI is blinking and additionally, the special condition is indicated
in the assisting window of the MMI.
Recordings clear
The measured values recorded can be reset locally and remotely via object-related clear commands.
Via remote communication, open and close commands can be issued to the object directly without pre-
selection. A direct command is possible if the control position and interlocking signals allow the
operation. The event E24 or E25 is generated by the command success.
The secured object control is an important feature of the communication protocols that support
horizontal communication (because the command reservation and interlocking signals can be
transferred by bus). All secured control operations require two-step commands; a selection step and an
execution step.
- Command authority - Ensures that the command source is authorized to operate the object
- Mutual exclusion - Ensures that only one command source at a time can control the object
- Interlocking - Allows only safe commands
- Execution - Supervises command execution
6
The virtual LON input and output connections can be configured in the RECAP tool while the actual
LON network connections of the corresponding signals are defined in the LNT tool.
During the selection step, the horizontal interlocking signals (virtual LON inputs) are refreshed in
order to guarantee the signal integrity. The refresh operation is executed only provided the LON is
selected as a communication protocol (parameter V18 at channel 1) and the command timeout
(parameter V19 at channel 1) is 1.5s or more. The actual time for updating the virtual LON inputs is
the command timeout minus 200ms. If the command timeout is less than 1.5s, the secured object
control is accomplished as described in paragraph ‘‘Secured object control (SPA)’’ below.
1. Select command
- The command source is identified from the LON message
2. Command reservation (network broadcast)
- The object activates the RESERVE output
- The RESERVE output is automatically deactivated when the BLOCK signal is activated
- External RESERVE logic is configuration-dependent
- Changes in virtual LON outputs are broadcasted to the network
3. Wait 200 ms
- Activating the BLOCK input can inhibit the operation and cause a response (stage 6)
4. Refresh input data (network poll)
- Activating the BLOCK input can inhibit the operation and cause a response (stage 6)
- Virtual LON inputs are updated by polling the network
- Timeout causes a response (stage 6)
5. Calculate interlocking
6. Response
- The event ack (acknowledged, E25) or nack (not acknowledged, E24) as a response to the
select command
- Message of the ack or nack to the remote system
7. The "Command started" event (E11) on successful selection
SYS COM
6 1
2
Feeder Feeder Feeder
terminal terminal terminal
7
Execute step (LON)
8. Execute command
- The command source identified from the LON message
- In case of a wrong command source, the object will respond with nack
9. Calculate interlocking
- If the interlocking state inhibits the operation, the execution will branch to stage 11
- Activating the BLOCK input can inhibit the operation and cause a response (stage 11)
10. Perform command
- Start the output pulse
11. Response
- The event ack (acknowledged, E25) or nack (not acknowledged, E24) as a response to the
execute command
- Message of the ack or nack to the remote system
12. New state indication
13. Release command reservation (nv broadcast)
- The RESERVE output will be deactivated
14. The "Command completed" event (E10)
SYS COM
11 8
14
13
Feeder Feeder Feeder
terminal terminal terminal
If the configuration does not support horizontal communication via LON, the following command
handling scheme is applied instead of the one described above:
1. Select command
- Message of the ack or nack to the remote system according to the present interlocking state
2. Command reservation
- The object will activate the RESERVE output
- The RESERVE output is automatically deactivated when the BLOCK signal is activated
- External RESERVE logic is configuration-dependent
3. Wait 200 ms
-Activating the BLOCK input can inhibit the operation and cause a response (stage 6)
5. Calculate interlocking
6. Response
- The event ack (acknowledged, E25) or nack (not acknowledged, E24) as a response to the
select command
7. The "Command started" event (E11) on successful selection
8
Execute step (SPA)
8. Execute command
- Message of the ack or nack to the remote system according to the present interlocking state
9. Calculate interlocking
- If the interlocking state inhibits the operation, the execution will branch to stage 11
- Activating the BLOCK input can forbid the operation and cause an execution branch to stage11
10. Perform command
- Start the output pulse
11. Response
- The event ack (acknowledged, E25) or nack (not acknowledged, E24) as a response to the
execute command
12. New state indication
13. Release command reservation
- The RESERVE output will be deactivated
14. The "Command completed" event (E10)
The following facts should be considered regarding the logging of command handling events. The
commands nack (E24) and ack (E25) will always follow the given local or remote command. They
should be considered as user interface responses. An "unsuccessful" event (E28) is generated as a
result of commands issued by binary inputs i.e. when a conflict occurs due to an interlocking enable
signal or when the forced mode is not selected and a command is given that requires the option.
Depending on the configuration of horizontal communication, the secured object control can be based
on SPA or LON solutions. Pressing the MMI control buttons "1" and "0" of a locally selected object starts
the required command select step which is immediately followed by the start of the execution step,
provided the selection stage was successful. The local visual selection of an object in the MIMIC view,
i.e. pressing the select push-button, does not immediately cause the select step.
9
Actual Settings
1)
Fixed pulse 126 1 S1 0 or 1 - 0
Forced pulse 126 1 S2 0 or 1 2) - 1
Event delay 126 1 S3 0.000...60.000 s 10.000
Open pulse 126 1 S6 0.04...100.00 s 0.100
Open alarm 126 1 S7 0.00...100.000 s 0.100
Close pulse 126 1 S8 0.04...100.00 s 0.100
Close alarm 126 1 S9 0.00...100.000 s 0.100
1)
Fixed pulse 0 = Variable pulse; 1 = Fixed pulse
2)
Forced pulse 0 = Single pulse; 1 = Forced pulse
Control Settings
1)
Object state 126 1 V1 0...3 - 0
Interlock close 126 1 V30 0 or 1 2) - 1
Interlock open 126 1 V31 0 or 1 2) - 1
Direct open 126 0 V4 1 - 0
Direct close 126 0 V5 1 - 0
Open select 126 0 V6 1 - 0
Close select 126 0 V7 1 - 0
Cancel 126 0 V10 1 - 0
Execute 126 0 V11 1 - 0
Cycle count 126 1 V12 0...10000 - 0
Last open 126 1 V14 0.000...100.000 s 0.000
Max open 126 1 V15 0.000...100.000 s 0.000
Last close 126 1 V17 0.000...100.000 s 0.000
Max close 126 1 V18 0.000...100.000 s 0.000
IV state 126 1 V34 B9 (512) - 0
Block state 126 1 V35 0 or 1 3) - 0
Summarized stat 126 3 V50 B0...B9 4) - 0
Regist clear 126 1 V98 1 - 0
Alarm ack 126 1 V99 1 - 0
Event mask 1 126 1 V101 0...521142271 - 134917887
Event mask 2 126 1 V103 0...521142271 - 134917887
Event mask 3 126 1 V105 0...521142271 - 134917887
Event mask 4 126 1 V107 0...521142271 - 134917887
10
Parameter Data Non/ Protected Explanation
continued direction Volatile
1)
Object state 1 = Close (01); 2 = Open (10); 0 = Undefined (11); 3 = Undefined2 (00)
2)
Interlocking type 1 = Interlocked; 0 = Enabled
3)
Block state 0 = Inactive; 1 = Active
4)
Status type B0 (1) = BINCLOSE; B1 (2) = BINOPEN; B3 (8) = IV; B4 (16) = CLOSEENA; B5 (32) = OPEENA;
B8 (256) = BLOCK; B9 (512) = reserved
Output paramaters
1)
Active type 0 = Inactive; 1 = Active
11
Events
Events 0...31
Channel Code Weighting Default IEC address GI Table Event Reason Event State
coefficient
Technical data
Execution task
20 ms
Operation accuracies
12