Advertisement
Table 12: Internal response codes
Code
1
SUCCESS
2
NOT_CONFIGURED
3
COMMS_LOST
4
ALREADY_ACTIVE
5
REMOTE_CONTROL_OFF
6
IN_SESSION
7
LEVER_DOWN
18
Fault current recording
Analog points 12-17 act as a record of the
measured value of fault currents. For
example, a fault might have been measured
as 480 A peak on phase A. In this case A_PID
12 will be set to that value. These values are
overwritten each time there is a new fault
on that phase and will generate a new
event. They are volatile and are cleared on
RCU restart.
String point description
The RCU can return string data to a SCADA
system if supported by the protocol. String
data is usually data about the site, such as
site name.
String points are identified by String_Point
IDentity or S_PID. The following data is
given for each point:
S_PID: the identifier for this point
including nominating the relevant phase
if valid.
Source: the source of the data, namely
the RCU or the switchgear and how it is
set up.
A description of the data.
What happens on restart of the RCU.
Data qualifiers which are supported for
that point.
Internal control response codes
Command request has been accepted and command has been initiated.
Request not accepted because the control target has not been configured (e.g., C phase not configured).
Request not accepted because either the RCU is starting up and has not yet fully verified the Fusesaver, or at
some later date has lost communications to the Fusesaver.
Request not accepted because the control queue is full or the control is already active.
Request not accepted because remote switch is off.
Request not accepted because a Siemens Connect session is in progress and has control of the Fusesaver.
Request not accepted because the a Fusesaver external lever is in the down position.
Controls description
Controls are commands that can be sent by
a protocol to operate Fusesavers or to affect
the RCU (for example, to reset fault flags).
The full list of available controls are listed in
Table 12: Internal response codes.
Control points are identified by Control_
Point IDentity or C_PID. The following data
is given for each point:
C_PID: The control point identifier.
Target: This specifies what is controlled.
Control type: This specifies what type of
control is sent to the target.
When a control is received, it is accepted or
rejected by the RCU. Table 12 describes the
internal control response codes that may be
associated with each control. One of these
codes will be returned by the RCU as a
response to a control request from the
SCADA system, refer to Table 5: DNP3
control response codes on page 10.
Where multiple responses apply, the lowest
numbered one will be reported.
Trip/close controls for Fusesaver are passed
to the Fusesaver and take time to have an
effect, at least 60 seconds and up to 120
seconds.
Some protocols may only be able to support
limited types of control.
Controls to RCU, such as clear flags or
counters, are always accepted. Controls to
Fusesaver may be rejected depending on
other conditions, such as communications
to Fusesaver lost or remote control disabled.
Description
Advertisement
