Professional Documents
Culture Documents
ADVC IEC 60870-5-101104 Protocol Technical Manual
ADVC IEC 60870-5-101104 Protocol Technical Manual
Manual
For
ADVC Controller Range
Document Status
As Implemented
Subject to Change
Scope
This document describes the IEC 60870-5-101 and IEC 60870-5-104 Protocols and Database
Implementation on ADVC controller range
80 Schneider Road
Queensland
Australia.
LIMITATIONS
This document is copyright and is provided solely for the use of the recipient. It is not to be copied in any
way, nor its contents divulged to any third party, nor to be used as the basis of a tender or specification
without the express written permission of Schneider Electric (Australia) Pty Limited.
This document discloses confidential intellectual property that belongs to Schneider Electric (Australia) Pty
Limited. This document does not invest any rights to Schneider Electric (Australia) Pty Limited intellectual
property in the recipient. Moreover the recipient is required not to disclose any of the intellectual property
ADVC IEC 60870-5-101/104 Protocol Technical Manual
contained in this document to any other party unless authorised in writing by Schneider Electric (Australia)
Pty Limited.
Revision Control
R01 GC 10/07/06 Removed Measured Value Points not yet implemented for the ADVC
R05 PJM 01/08/06 Added 104 Interoperability Statement. General rearrangement to handle 104
better.
R06 DPC 02/08/06 Changed IOA base addresses to avoid overlap with Read Command
R07 PJM 22/08/06 Corrected Interoperability statement to have supported baud rates
R08 RDM 15/02/07 Add IEC101 - Max ASDU Size, COT Size and IEC104 APDU Parameters
R09 RDM 22/02/07 Add ‘Auto Reclose’ to Double Command point list.
R11 RDM 28/03/07 Amend IEC104 t3 parameter range and description, IEC104 Max ASDU
R12 RDM 16/04/07 Remove ‘For Comment’ watermark, correct IEC104 ASDU max size Document Tx-
Delay Transmission-2 field.
R14 RDM 11/12/07 Show all IEC Transmission Default IEC104 OCPM pages. Correct point mappings,
for:- (A42-05.16)
R15 SJC 29/06/10 Show that we don’t support 104 test command. Rename t0 timeout parameter.
R17 RDM 09/04/15 Manual amendments and functionality introduced for “SRS OCR-184-69 IEC-104”
released in A45-43.00+
R18 PJM 25/09/18 Removed Watermark and regenerated
Contents
1. Introduction .......................................................................................................................................... 0
2. Overview ............................................................................................................................................... 0
3. Applicability .......................................................................................................................................... 2
4. Protocol Configuration.......................................................................................................................... 3
1. Introduction
This document describes the IEC 60870-5-101 and IEC 60870-5-104 implementations for Automatic
Circuit Reclosers (ACRs) on Advanced Controllers.
This implementation is more complex than most telemetry protocols and thus it is essential to read
the Overview section in order to set up the SCADA system correctly.
2. Overview
The ADVC Controller combines the functions of a protection relay and a switchgear controller into a
single Intelligent Electronic Device (IED).
The controller provides a Human Machine Interface (HMI) LCD ‘local’ operator control panel that
allows configuration and control of the switchgear.
The controller generates time tagged “events” which are displayed on the control panels LCD. The
event-log displays a history of the switchgear operation for the benefit of a ‘local’ operator during
post fault analysis.
Electricity supply utilities frequently link the controller into their SCADA systems as a Remote
Terminal Unit (RTU).
The IEC-60870 protocol allows digital and measured data events to be sent from the ADVC
Controller to the SCADA system with time tags attached. This allows comprehensive coverage of
controller operations and distribution system events and attributes.
For example:
• Open or Close Status
• Lockout Status
• Fault Flags
• Line Currents and Voltages
Time tags are optional for some ASDU (Application Specific Data Unit) object types.
2.2. Controls
SCADA controls supported by the protocol handler are listed in the N00-331 SCADA Protocol
Database document.
All controls have a corresponding binary status point. The master station must use these status
points for control action verification. Sometimes a control will be rejected because of an underlying
ADVC Controller condition preventing the control action being achieved, even if the IEC application
responds with an ‘Acknowledged Activation’.
The IEC870 protocol handler can invoke controls that trigger events that are recorded in the ADVC
event log - “IEC870 Trip Req” and “IEC870 Close Req” are two examples. This event log reporting
indicates only that the protocol handler has requested a trip or a close from the ADVC. It does not
mean that the action has necessarily been undertaken. As detailed above, the request may be
over-ridden by operational conditions.
The IEC870 protocol defaults to being a remote user. Refer to the equipment manual ‘‘Controller-
Mode: LOCAL/Remote’ for more information.
• Ability to change the points monitored and reported by the controller. This allows the
controller be configured to suit the communications and SCADA system constraints.
• ASDU object type selection for binary and measured input data.
2.4. Terminology
Earth Fault or Ground Fault is described as Earth / Ground Fault.
Sensitive Earth Fault (SEF) or Sensitive Ground Fault (SGF) is described as SEF/SGF.
The bushing terminology used in this document is for U and W series switchgear i.e. I and X for the
switchgear terminals. For an N or RL series switchgear I should be interpreted as the 1 side and X
should be interpreted as the 2 side.
The phase terminology is ABC and refers always to the phase set by the Terminal Designation or
“Phasing” option, never to the physical bushing or terminal on the switchgear.
For more information on operator control panel usage refer to the equipment manual.
3. Applicability
4. Protocol Configuration
This section details the various parameters that are available for configuration when using the
IEC101/4 protocol. The configuration can be performed via WSOS5, or the ADVC Controller (using
the flexVUE or setVUE panels). The location, on the panel pages, of the various fields detailed in
this section is given in Appendix A.
The WSOS5 ‘Protocol Configuration Tool’ feature is used to select and configure an optimal set of
data points for one or more ADVC controllers. These points are contained in a map that is loaded
into the ADVC Controller using WSOS5. The same map is generally used in every ADVC Controller
that is connected to the SCADA system but it does not have to be. Until a map is loaded a default
map will be in use. The map is created with a maximum ADVC Controller firmware version. This is
done to ensure that only data points that the ADVC Controller knows about can be selected and is
needed because the data points available are added to as new features are created but the ADVC
Controller firmware in use will not have these points (i.e. WSOS5 may have been updated but the
ADVC Controller firmware has not been). It is possible to upgrade the map to the latest firmware
version at a later time if newer points are needed.
Refer to “Protocol Configuration Tool Help” and N00-331 protocol database “Points List” for details
of the points available for use. Both of these are accessible via the ‘WSOS5’: “Protocol
Configuration Tool” menu which is visible when Protocol Configuration Tool is selected from the
Customise menu.
The particular port used by this protocol. It may be NONE if no port is used.
This field may be selected to allow scrolling though the list of available ports.
Displays the name of the protocol map, or “Invalid Mapping” if no map can
be read. The map in use can only be configured via WSOS. Refer to WSOS5
for details of the contents of the default map.
4.2. Communications
The communications settings available for configuration are given in the following table.
All IEC 60870-5-101 data link messages are transmitted with FT1.2 format frames.
Statistic Description
Note 1 The number of FT1.2 frames transmitted from the ADVC Controller into
the communication link.
Range: [0 to 99999]
Rx Count Rx Count
Range: [0 to 99999]
Range: [0 to 99999]
Range: [0 to 99999]
Note 1 The number of times that the receive time, Frame TO, for a frame is
exceeded before a valid frame is found after the start of frame is
received.
Range: [0 to 99999]
Note 1 The number of messages received that with unrecognised frame type
or second octet that is not correct for FT1.2 format.
Range: [0 to 99999]
Note 3, 2 The IP address of the network node that sent the last IP packet with an
invalid (i.e. not authorised) IP address.
Statistic Description
Note 3, 2 The quantity of invalid IP packets received from the Last Invalid IP
address.
Range: [0 to 99999]
Note:
1. Status fields have the following characteristics;
• Reset when IEC-104 protocol does a warm/cold restart, or the port is reopened, or when explicitly reset by
operator.
• Pressing Select on the ADVC Controller operator control panel page will allow resetting of the stored
values.
• Communication statistic counters are not password protected.
• When the maximum range is reached the counter rolls over to 1 and start counting again.
2. Supported in version A45-43.00 and later firmware.
3. Status fields have the following characteristics;
• Reset when
o IEC-104 protocol does a warm/cold restart
o Protocol turned On
o Port Selection changed to 10BaseT
o Turn monitoring of Invalid IP On
o Operator does a stats reset.
• Pressing Select on the ADVC Controller operator control panel page will allow resetting of the stored
values.
• Communication statistic counters are not password protected.
• When the maximum range is reached the counter rolls over to 1 and start counting again.
• The ADVC Controller has performed a cold start and has not received a clock synchronisation
command.
• The ADVC Controller has not received any communications from the master station for 24
hours
• The ADVC Controller has not received any clock synchronisation commands from the master
station for 72 hours
Refer to the WSOS5 help information for information on configuring the Time Zone feature
correctly.
Notes
1. The IEC-104 protocol operates with a 1 hour Summer Time Offset. This means that the
Daylight Saving Time Zone can only be set to 1 hour ahead of the Base Time Zone and the
Daylight Saving Offset must be equal to the Time Zone Offset.
Parameter Description
point information transmitted to the master station.
Range: ON, OFF
Factory default: ON
Measured Time Measured Time Tag Usage
Determines if time tags are included with all Class1 (spontaneous)
measured value information.
The inclusion of time tags affects the measured data reporting
method. Refer to Sections 4.7.2, 4.7.3 for more information.
This field is not used if Measured Data is OFF.
Range: ON, OFF
Factory default: OFF
Single Pts Single Point Base Information Object Address
The base address for the single point objects
Range: 1 – 255, 1 – 65535 or 1 – 16777215
depending upon configured Object Addr Size
Factory default: 1
Double Pts Double Point Base Information Object Address
The base address for the double point objects
Range: 1 – 255, 1 – 65535 or 1 – 16777215
depending upon configured Object Addr Size
Factory default: 200
Single Cmds Single Command Base Information Object Address
The base address for the single command objects
Range: 1 – 255, 1 – 65535 or 1 – 16777215
depending upon configured Object Addr Size
Factory default: 600
Double Cmds Double Command Base Information Object Address
The base address for the double command objects
Range: 1 – 255, 1 – 65535, or 1 – 16777215
depending upon configured Object Addr Size
Factory default: 700
Data type Reported Measured Data Type
The type of ASDU data values used by the ADVC:-
• scaled values (engineering units)
• normalised values, or
• short float (engineering units) Note 1
The Data Type determines the measurand, parameter and setpoint
data types.
Refer to sections 4.7.2 and 4.7.4 for more information.
Range: SCALED, NORMAL, FLOAT
Factory default: SCALED
Meas Vals Measured Values Base Information Object Address
The base address for the measured value objects
Range: 1 – 255, 1 – 65535, or 1 – 16777215
depending upon configured Object Addr Size
Factory default: 300
SetPt Cmds Setpoint Command Base Information Object Address
Parameter Description
The base address for the set point command objects
Range: 1 – 255, 1 – 65535, or 1 – 16777215
depending upon configured Object Addr Size
Factory default: 800
Param Cmds Parameter Command Base Information Object Address
The base address for the parameter command objects
Range: 1 – 255, 1 – 65535, or 1 – 16777215
depending upon configured Object Addr Size
Factory default: 400
Integ Total Rep Integrated Total Usage
Determines if the integrated total object information is reported in
the data transmitted to the master station.
Range: ON, OFF
Factory default: ON
Integ Total Integrated Total Base Information Object Address
The base address for the integrated total objects
Range: 1 – 255, 1 – 65535, or 1 – 16777215
depending upon configured Object Addr Size
Factory default: 500
Note:
7. For Class = CY, enabling cyclic data reporting with the Measured Time tag ON will result in ‘cyclic’ data
being reported in Class1 and Class 2 command responses. Enabling cyclic data reporting with the
Measured Time tag OFF will result in no ‘cyclic’ data being reported in Class1 command responses.
8. Read request (ASDU 102) is not responded to with time tagged ASDU.
9. Short Floats supported in version A45-43.00, and later firmware.
4.7.3.1. Buffering
The ADVC maintains separate buffers for change of state event reporting for each ASDU data type
supported. Each buffer may be of a different depth.
Notes 4
Notes:
1. If the ADVC is configured to have Measured Time tags ON then an event is stored in the change of
state buffer every time the value exceeds its dead band. All changes of state values are reported,
with their time tags, in response to a master station poll.
2. For Class = CY, disabling cyclic data reporting with the Measured Time tags OFF then no measured
values are stored in the change of state buffer.
3. For Class = CY, enabling cyclic data reporting with the Measured Time tags OFF then a single non-
time tagged event per measured value is stored in the change of state buffer. Only the one event is
stored irrespective of the number of times the value exceeds its dead band. The value for the event
that is reported to the master station is the current value at the time of transmission. Note that if a
measured value is rapidly changing during a multi-message exchange poll then a second report of the
spontaneous value change is possible.
4. The usage of clock change events is explained in section 4.5.
The "IEC Event Buffer Overflow" data-point is only operationally effective (i.e. will only do
anything) when the IEC101/104 protocol application feature is ‘Available’.
Examples:
Raw Value Range Units Transmitted Scaled Value
0 to 16000A 2A 0 to 8000
Normalised
7FFFH (32767)
- (Range Max) 0
+(Range Max)
All measured values are transmitted as a signed 16-bit value (FFFFH to 7FFFH or -32767 to 32767).
0 (0)
The value transmitted is calculated as shown below:
Examples:
The data is formatted as 4 Octets with the definition of each Octet given in the following table.
Octets Bit
8 7 6 5 4 3 2 1
F = Fraction
1
2-16 2-17 2-18 2-19 2-20 2-21 2-22 2-23
F = Fraction
2
2-8 2-9 2-10 2-11 2-12 2-13 2-14 2-15
F = Fraction
3 E
2-1 2-2 2-3 2-4 2-5 2-6 2-7
2-0
E =Exponent
4 Sign
27 26 25 24 23 22 21
S
ASDUs marked in the interoperability guides, for process information in the monitored
direction, with a quality descriptor, support the following quality bits where applicable:-
• IV = INVALID/VALID
• OV = OVERFLOW/NO OVERFLOW
5. Dial Out
5.1. Overview
When the protocol hander determines that it has change of state events to be reported to the
master station it requests the Hayes compatible modem driver to initiate a dial-out sequence.
Refer to the communications section of the ADVC Operations Manual for further
details on the controllers Hayes modem driver.
5.2. Details
If the master station establishes communications with the controller during dial-out
commencement but before a communications link is established, then the dial out sequence is
aborted.
The modem must not return results codes or echo commands. When the protocol determines a
connection to the master is required it will initiate a request to the Hayes modem driver to
establish a connection. If the modem is offline the Hayes modem driver will dial the master station.
If the modem is already online - a dial out sequence is not triggered and an IEC-101 communication
session is commenced. When the modem is online the protocol handler will examine any received
data and decode it as IEC-101 packets.
After a successful communications session (i.e. a link has been established) the Hayes modem
driver will hang up the modem after a configurable delay period during which no valid 101
packet(s) were received or transmitted. The first phone number to be dialled is set to the head of
the list of Dial-Out Numbers. If the Class 1 buffers are not emptied before the communications link
is broken, another dial-out sequence is initiated.
5.3. Configuration
5.3.1. OCPM
The protocol handler page for IEC-101 Dial-Out:
Setting Description
The number of change of state events that must occur in Class 1 before a dial
out sequence is triggered.
Range: 1 to 255
The maximum time a change of state event will wait before a dial out
connection sequence is triggered.
Display only
Display only
Dial-out is only available when the IEC protocol handler is using 60870-5-101 mode
and the protocol handlers selected communications port has the Hayes modem driver
enabled.
A.1 Communications
This appendix details the layout of the pages for configuring the IEC-101 and IEC-104 protocols.
A.1.1 setVUE
Make the protocol Available via the options page
View and edit the protocol setup via the Communications Setup 1 page. The port currently in use is
displayed alongside the protocol.
The port selected will determine whether IEC-104 or IEC-101 protocol is in use. Selecting
10BaseT makes IEC-104 the protocol otherwise it is IEC-101. The titles of the pages change to
display the running protocol.
A.1.2 flexVUE
Panel pages for IEC101 Panel pages for IEC104
The port selected will determine whether IEC-104 or IEC-101 protocol is in use. Selecting 10BaseT makes IEC-
104 the protocol otherwise it is IEC-101. The titles of the pages change to display the running protocol.
IEC104 IP VALIDATION
Check Master IP ON
IP1 0.0.0.0
IP2 0.0.0.0
IP3 0.0.0.0
IP4 0.0.0.0
IP5 0.0.0.0
Turnaround Time
The turnaround time for the protocol, from the end of receiving a message until the start of the
pre-transmission time, is typically < 30 milliseconds with a range of 5 to 100 milliseconds.
Latency of Data
The protocol task examines the real-time database every 500 milliseconds to see if anything has
changed and to construct the underlying protocol database which is sent to the master station. This
introduces a delay between the actual event and updating the protocol database of up to 500
milliseconds. This is the data latency.
For points tagged to 10 millisecond accuracy, the points correspond to those displayed within the
operator panel event records.
Network configuration
Link layer
Frame format FT 1.2, single character 1 and the fixed time out interval are used exclusively in this
companion standard.
Application Layer
Transmission mode for application data
Mode 1 (Least significant octet first), as defined in clause 4.10 of IEC 870-5-4, is used exclusively in
this companion standard.
Three octets
Cause of transmission
<14> := Measured value, short floating point value with time tag M_ME_TC_1
<18> := Packed start events of protection equipment with time tag M_EP_TB_1
<19> := Packed output circuit information of protection equipment with time tag M_EP_TC_1
<30> := Single-point information with time tag CP56Time2a M_SP_TB_1
<34> := Measured value, normalised value with time tag CP56Time2a M_ME_TD_1
<35> := Measured value, scaled value with time tag CP56Time2a M_ME_TE_1
<36> := Measured value, short floating point value with time tag CP56Time2a M_ME_TF_1
<39> := Packed start events of protection equipment with time tag CP56Time2aT M_EP_TE_1
<61> := Set point command, normalized value with time tag CP56Time 2a C_SE_TA_1
<62> := Set point command, scaled value with time tag CP56Time 2a C_SE_TB_1
<63> := Set point command, short floating point value with time tag CP56Time 2a C_SE_TC_1
File transfer
<122> := Call directory, select file, call file, call section F_SC_NA_1
Remote initialisation
General Interrogation
global
group 5 group 11
group 6 group 12
Clock synchronisation
Clock synchronisation
Command transmission
C_SE_ACTTERM used
No additional definition
Persistent output
Threshold value
Smoothing factor
Parameter activation
File transfer
Network configuration
Physical layer
Transmission speed (control direction)
Link layer
Frame format FT 1.2, single character 1 and the fixed time out interval are used exclusively in this
companion standard.
When using an unbalanced link layer, the following ASDU types are returned in class 2 messages
(low priority) with the indicated causes of transmission:
Note: (In response to a class 2 poll, a controlled station may respond with class 1 data when there is no class 2 data
available).
Application Layer
Mode 1 (Least significant octet first), as defined in clause 4.10 of IEC 870-5-4, is used exclusively in
this companion standard.
Three octets
Cause of transmission
Length of APDU
An individual node setting that limits the maximum length of the ASDU for any given APDU octet
group. The default Maximum ASDU size is 249 octets. The length of the ASDU may vary depending
upon message requirements.
<14> := Measured value, short floating point value with time tag M_ME_TC_1
<18> := Packed start events of protection equipment with time tag M_EP_TB_1
<19> := Packed output circuit information of protection equipment with time tag M_EP_TC_1
<30> := Single-point information with time tag CP56Time2a M_SP_TB_1
<34> := Measured value, normalised value with time tag CP56Time2a M_ME_TD_1
<35> := Measured value, scaled value with time tag CP56Time2a M_ME_TE_1
<36> := Measured value, short floating point value with time tag CP56Time2a M_ME_TF_1
<39> := Packed start events of protection equipment with time tag CP56Time2aT M_EP_TE_1
<61> := Set point command, normalized value with time tag CP56Time 2a C_SE_TA_1
<62> := Set point command, scaled value with time tag CP56Time 2a C_SE_TB_1
<63> := Set point command, short floating point value with time tag CP56Time 2a C_SE_TC_1
ASDUs 61, 62, & 63 supported since firmware version A45-43.00
<64> := Bitstring of 32 bit with time tag CP56Time 2a C_BO_TA_1
File transfer
<122> := Call directory, select file, call file, call section F_SC_NA_1
Station initialisation
Remote initialisation
Read procedure
Read procedure
Spontaneous transmission
Spontaneous
The following type identifications may be transmitted in succession caused by a single status
change of an information object. The particular information object addresses for which double
transmission is enabled are defined in a project-specific list.
Bitstring of 32 bit M_BO_NA_1, M_BO_TA_1 and M_BO_TB_1 (if defined for a specific project)
Measured value, short floating point number M_ME_NC_1, M_ME_TC_1 and M_ME_TF_1
Station Interrogation
global
group 5 group 11
group 6 group 12
Clock synchronisation
Clock synchronisation
Command transmission
C_SE_ACTTERM used
No additional definition
Persistent output
Smoothing factor
Parameter activation
Test procedure
Test Procedure
File transfer
Transparent File
Transparent File
Background scan
(station-specific parameter, mark ‘X’ if function is only used in the standard direction, ‘R’ if only used
in the reverse direction, and ‘B’ if used in both directions)
Background scan
(station-specific parameter, mark ‘X’ if function is only used in the standard direction, ‘R’ if only used
in the reverse direction, and ‘B’ if used in both directions)
Acquisition of transmission delay
Maximum number of outstanding I format APDUs k and latest acknowledge APDUs (w) and IP
port number.
Maximum range of values w: 1 to 32767 APDUs, accuracy 1 APDU (Recommendation: w should not
exceed two-thirds of k).
RFC 2200 is an official Internet Standard which describes the state of standardization of protocols
used in the Internet as determined by the Internet Architecture Board (IAB). It offers a broad
spectrum of actual standards used in the Internet. The suitable selection of documents from RFC
2200 defined in this standard for given projects has to be chosen by the user of this standard.
Ethernet 802.3
Serial X.21 interface
1. ……………………………………………..
2. ……………………………………………..
3. ……………………………………………..