Foreword

The Norwegian User Conventions for IEC 870-5-101 has been developed in a
project involving many of the major companies in
the area of power generation and power distribution. Also the major control
equipment suppliers has contributed both financiall
y
and with actual work in the project. The project has been managed by RF-
Rogaland Research and the steering committee has
been headed by Statnet SF. About 40% of the financial support for the project has
been supplied by The Research Council of
Norway, the rest has been financed by support from the following companies:
Communication Protocol
Communication Protocols are the grammars through which computer-based
devices communicate with one another
- the way they organise, and transmit the bits and bytes of electronic on-off
(binary) signals whose patterns encode
data. Simply, a protocol is a set of rules that governs how message
containing data and control information are
assembled at a source for their transmission across the network and then
dissembled when they reach their
destination.

Definitions
For the purpose of this user conventions, the following definitions apply:
Companion standard
A companion standard adds semantics to the definitions of the basic standard or a
functional profile. This may be expressed by
defining particular uses for information objects or by defining additional information
objects, service procedures and paramete
rs
of the basic standard.
Group (of information objects)
A group (of information objects) is a selection of
COMMON ADDRESSES
or
INFORMATION
A
DDRESSES
which is specifically defined for
a particular system.
Control direction
The direction of transmission from the controlling station, typical a SCADA system,
to a controlled station, typical a station
control system or a RTU..
Monitor direction
The direction of transmission from a controlled station to the controlling station.
Unbalanced transmission
Unbalanced transmission procedures are used in supervisory control and data
acquisition (SCADA) systems in which a master
station controls the data traffic by polling outstations sequentially. In this case the
master station (master) is the primary
station
that initiates all message transfers while outstations are secondary stations (slaves)
that may transmit only when they are
polled.
The unbalanced mode procedure can be used generally, but must be used in party
line configuration.
Balanced transmission
If balanced transmission procedures are used, each station may initiate message
transfers.
The balanced mode procedure is restrict to “point to point or multiple point to point”.
In due to unbalanced mode is balanced mode the most effective way of
communication on «point to point or multiple
point».Balanced transmission can be used in full duplex mode.
Controlled Station (Outstation, Remote station, Remote terminal unit (RTU), Slave
station)
A station that is monitored or commanded by a master station.
Controlling Station (Master station)
A station at which telecontrol of outstations is performed.
Network configurations
The following fixed network configurations are supported:
- Point - to - point
- Multiple point - to - point
- Party line
- Redundant line
Transmission rules
1
Line idle is binary 1.
2
Each character has one start bit (binary = 0) 8 information bits, one even
parity bit and one stop bit
(binary = 1).
3
No line idle intervals are admitted between characters of a frame.
4
Upon detecting an error according to rule 6, a minimum interval of 33 bits (3
characters) is required
between frames.
5
The sequence of user data characters is terminated by a 8 bits checksum
(CS). The checksum is
the arithmetic sum over all user data octets.
6
The receiver checks:
per character
the start bit, the stop bit and the even parity bit
per frame
the start character, the length (2 bytes in frames with variable lengths), the
frame check sum and the end character and, upon detecting an error, the
line idle interval specified by rule 4
Control field
The control field contains information that characterises the direction of the
message, the type of the service
provided and supports control functions for suppressing losses or duplications of
messages.
Control field unbalanced mode:
Unbalanced transmission procedures are used in supervisory control and data
acquisition systems in which a
master station controls the data traffic by polling outstations sequentially. In this
case the master station is the
primary station that initiates all message transfers while the outstations are
secondary stations that may transmit
only when they are polled
Control field balanced mode:
Balanced transmission:
If blanched transmission procedures are used, each station may initiate
message transfers. Because such stations
may act simultaneously as primary and secondary stations, they are called
combined stations. In the following, the
combined stations is called either primary or secondary station according to
its described functions.
The balanced transmission procedure is restricted to point to point and
multiple point to point.
Interoperability
This companion standard presents sets of parameters and alternatives from
which subsets have to be selected to
implement particular telecontrol systems. The marked functions and ASDUs
in the interoperability list on the
following pages represent the current requirements for an IEC 60870-5-101
system according to the Norwegian
User Conventions. Certain parameter values, such as the number of octets
in the common address of ASDUs
represent mutually exclusive alternatives. This means that only one value of
the defined parameters is admitted per
system. This clause summarises the parameters of the previous clauses to
facilitate a suitable selection for a
specific application. If a system is composed of equipment stemming from
different manufacturers it is necessary
that all partners agree on the selected parameters.
The selected parameters are crossed in the white boxes. Unmarked white
boxes represent parameters that are
currently not required. However, selections of such parameters can be
agreed upon in specific projects. Black
check boxes indicates that these options cannot be selected.
Note
-
Full specification of a system may require individual selection of additional
parameters Recommended scaling factors for
measured values and setpoint commands are described in section 7.8.
5.1.1 Network configuration
(network-specific parameter)
Point-to-point
Multi-point-party line
Multiple point to point
Multi-point-star
Redundant lines
5.1.2 Physical layer
(network-specific parameter)
Transmission speed (control direction)
Unbalanced interchange Unbalanced interchange
Balanced interchange
circuit V.24/V.28
circuit V.24/V.28
circuit X.24/X.27
Standard
Recommended if > 1200 bit/s
Transmission speed (monitor direction)
Unbalanced interchange Unbalanced interchange
Balanced interchange
circuit V.24/V.28
circuit V.24/V.28
circuit X.24/X.27
Standard
Recommended if > 1200 bit/s

5.1.3 Link layer

IEC 870-5-101
Norwegian User Conventions
2000-03-24
Revision no.2.0
side 45
5.1.5 Basic application functions
Station initialisation
(station-specific parameter)
Remote initialisation
General interrogation
(system- or station-specific parameter)
global
group 1
group 7
group 13
group 2
group 8
group 14
group 3
group 9
group 15
group 4
group 10
group 16
group 5
group 11
group 6
group 12
Addresses per group have to be defined
Clock synchronisation
(station-specific parameter)
Clock synchronisation
Command transmission
(object-specific parameter)
Direct single command transmission
Select and execute single command
Direct double command transmission
Select and execute double command
Direct regulation command transmission
Select and execute regulation command
Direct set point command transmission
Select and execute set point command
C_SE ACTTERM used
No additional definition
Short pulse duration (duration determined by a system parameter in the outstation)
Long pulse duration (duration determined by a system parameter in the outstation)
Persistent output
Transmission of integrated totals
(station- or object-specific parameter)
Counter request
General request counter
Counter freeze without reset
Request counter group 1
Counter freeze with reset
Request counter group 2
Counter reset
Request counter group 3
Request counter group 4
Addresses per group have to be defined
Communication procedures
Table 6.1 shows a list of all basic communication procedures (basic application
functions) that are offered in the IEC 870-5-10
1
companion standard. The subset of these procedures that are applicable to the
Norwegian User Conventions are listed in bold
types.
Table 6.1 Communication procedures specified in IEC 870-5-101
1.
Station initialisation
2.
Data acquisition by polling
3.
Cyclic data transmission
4.
Acquisition of events
5.
General interrogation
6.
Clock synchronisation
7.
Command transmission
8.
Transmission of integrated totals
9.
Parameter loading
10.
Test procedure
11.
File transfer
12.
Acquisition of transmission delay
The relevant basic communication procedures are described in more detail in
section 6.1, illustrated by separate sequence
diagrams for unbalanced and balanced communication systems. Note that only the
telegrams that apply to the described
procedure are shown in the diagrams. Additional telegrams (e.g. event telegrams)
may be transmitted in between the
procedure telegrams.
The basic communication procedures as described are error free procedures. If
communication errors (e.g.disturbed frames)
occur during the execution of a basic procedure, a corresponding exception
procedures is necessary to handle the error
situations. The different exception procedures are described in section 6.2.
The IEC 870-5-101 companion standard specifies a fixed link time-out interval to be
used for repeated frame transmissions.
Link time-outs are indicated with bold vertical lines in the communication procedure
diagrams. The time-out interval and
maximum number of retries are configurable and appropriate values will depend on
the transmission system.
Basic procedures
6.1.1 Station initialisation
6.1.1.1 Local initialisation of the controlling station in
unbalanced transmission systems
The initialisation of the controlling station starts e.g. with power off/on. Any data
requested right before the initialisation
cannot
be received by the controlling station because it is no longer available.
The link of the controlling station then establishes connection with the link of the
controlled station by transmitting a "Req
uest
status of link" that is answered by a "Status of link" response from the controlled
station. The controlling station then tran
smits
a "Reset of remote link" that is answered by an "ACK", which confirms the start
condition of the link layer of the controlled
station.
After the initialisation the controlling station is updated by issuing a general
interrogation command to the controlled statio
n. If
appropriate, the time of the two stations is then synchronised by a clock
synchronisation command.
The sequential procedure for local initialisation of the controlling station is shown in
fig. 6.1. Note that the link telegrams
that
are used are fixed frame telegrams (ref. sec. 4.1) with Primary Message bit (PRM)
and Function Code (FC) as indicated.
Local initialisation of the controlled station in balanced
transmission systems
The initialisation of the controlled station starts e.g. with power off/on. If operations
with the controlling station are goin
g on, this
station detects that its link is disconnected from the controlled station due to
unconfirmed services.
After a number of unsuccessful retries, the controlling station tries to re-establish
the link connection by transmitting "Requ
est
status of link" at specified time-out intervals. When the link layer of the controlled
station is available, it confirms this c
ondition
by a "Status of link" response to the controlling station. The controlling station then
transmits a "Reset of remote link" th
at is
answered by an "ACK", which confirms the reset condition of the link layer of the
controlled station
Then the controlled station synchronises its link with the controlling station by
transmitting "Request status of link" and "Re
set
of remote link". The controlling station responds with "Status of link" and "ACK"
respectively, and when the "ACK" is received
in
the controlled station the link connection is established in both directions.
The initialisation procedure is then completed by an END OF INITIALIZATION
message issued by the controlled station.
After the initialisation the controlling station is updated by issuing a general
interrogation command to the controlled statio
n. If
appropriate, the time of the two stations is then synchronised by a clock
synchronisation command.
The sequential procedure for initialisation of the controlled station is shown in fig.
6.5. Note that the link telegrams that a
re used
are fixed frame telegrams (ref. sec. 4.1) with Primary Message bit and Function
Code as indicated.
6.1.2 Data acquisition by polling
Reference is made to sec. 6.2 in document IEC 870-5-5.
The Norwegian User Convention specifies data to be acquired from the controlled
station solely by means of general
interrogation or event transfer, in order to reduce the traffic on the communication
line. This communication procedure is
therefore not further described in this document.
6.1.3 Cyclic data transmission
Reference is made to sec. 6.3 in document IEC 870-5-5.
Cyclic data transmission would typically be used to transfer measured values from
the controlled station, but the Norwegian
User Convention specifies measured values to be transferred as events as a result
of a deadband crossing (ref. previous
section). Hence this communication procedure is not further specified in this
document.
It should be noted, however, that the link is prepared for this procedure even in
unbalanced mode, as the IEC 870-5-101
companion standard specifies the link to poll for class 2 (cyclic) data.
6.1.4 Acquisition of events
Events occur spontaneously at the application level of the local (controlled) station.
The local process requires an event buff
er
to collect events that may appear faster than their transmission to the remote
(controlling) station can be accomplished.

IEC 870-5-101
Norwegian User Conventions
2000-03-24
Revision no.2.0
side 114
6.1.2 Data acquisition by polling
Reference is made to sec. 6.2 in document IEC 870-5-5.
The Norwegian User Convention specifies data to be acquired from the controlled
station solely by means of general
interrogation or event transfer, in order to reduce the traffic on the communication
line. This communication procedure is
therefore not further described in this document.
6.1.3 Cyclic data transmission
Reference is made to sec. 6.3 in document IEC 870-5-5.
Cyclic data transmission would typically be used to transfer measured values from
the controlled station, but the Norwegian
User Convention specifies measured values to be transferred as events as a result
of a deadband crossing (ref. previous
section). Hence this communication procedure is not further specified in this
document.
It should be noted, however, that the link is prepared for this procedure even in
unbalanced mode, as the IEC 870-5-101
companion standard specifies the link to poll for class 2 (cyclic) data.
6.1.4 Acquisition of events
Events occur spontaneously at the application level of the local (controlled) station.
The local process requires an event buff
er
to collect events that may appear faster than their transmission to the remote
(controlling) station can be accomplished.
6.1.4.1 Acquisition of events in unbalanced transmission
systems
Fig. 6.7 shows the sequential procedure for event acquisition in unbalanced
transmission systems.
The IEC 870-5 family of protocols specifies two classes of data, class1 and class 2
data. The IEC 870-5-101 companion
standard also specifies the link service "Request user data class 2" to be used for
polling local (controlled) stations. Normal
ly
class 1 contains spontaneous data while class 2 contains cyclic data
(recommended in document IEC 870-5-2). Two
consequences are then possible in each local station when the poll telegram is
received:
CASE 1: No spontaneous data are available
In this case the link layer of the controlled station responds by a NACK, i.e. either
the single character E5H or the fixed
frame telegram "Requested data not available", and the controlling station
continues its poll procedure by polling the
next controlled station.
CASE 2: Spontaneous data (events) are available
In this case the controlled station also responds by the fixed frame NACK telegram
"Requested data not available",
but this time with the ACD (Access Demand) bit set, indicating that spontaneous
data are available and waiting for
transfer. The controlling station then sends a "Request user data class 1" telegram,
and the controlled station
responds by transmitting an event ASDU.
The returned ASDU may contain all or some of the events that are available in the
controlled station when it was polled,
depending on the number and type of events present, and the maximum number of
events allowed in one event ASDU
(blocking).
The link transmission procedures used for event acquisition in unbalanced
transmission systems are always request/respond
procedures.
NOTE - If only spontaneous data is used for data transfer from the controlled
station, a more efficient poll procedure is
achieved by defining all data as class 2 data and having the link requesting only
class 2 data. The corresponding
event transfer procedure in this case is shown in fig. 6.8
Clock synchronisation
Clocks of controlled stations are initially synchronised by the controlling station after
initialisation and then re-synchronis
ed
periodically.
Fig. 6.13 and 6.14 show the sequential procedures for clock synchronisation in
unbalanced and balanced transmission
systems respectively. A CLOCK SYNCHRONIZATION command message
containing the full current clock time is sent from the
controlling station. The actual time that is transferred is the time when the first bit of
the clock synchronisation telegram i
s
transmitted.
The time information must be corrected by the controlling station according to the
sum of the transmission delay and
transmission time before the synchronisation command is sent.
After the execution of the clock synchronisation the controlled station generates a
confirmation message which contains the
local time before synchronisation.
It must be noted that when this procedure is used for time synchronisation the
accuracy of the synchronisation will always
depend on the characteristics of the transmission line.
Command transmission
Commands are used in telecontrol systems to cause a change of state of an
operational equipment.
There are two standard procedures for command transmission:
1.
Select and execute command
2.
Direct command
Select/execute and direct commands may be assigned individually and
independently to each commanded object in the
controlled station (by system configuration parameters in the controlling station).
Select and execute command
The select and execute command is used by the controlling station to:
-
Prepare for a specific control operation in the controlled station
-
Check that the control operation has been prepared (may be performed by the
operator).
-
Execute the prepared operation if checks are positive
The sequential procedure for a select and execute command is shown in fig. 6.15
and 6.16 for unbalanced and balanced
systems respectively. The controlling station sends a SELECT command message
to the controlled station, which responds by
a SELECT confirmation message if it is ready to accept the announced command.
This procedure is non interruptible and the
time from the SELECT command to the SELECT confirmation is controlled by a
configurable time-out interval.
A successful select procedure may then be deactivated by a "Break off command".
This command is transmitted by a BREAK
OFF command message and the controlled station responds by a BREAK OFF
confirmation message. The time between these
messages is controlled by a timeout.
If appropriate, an EXECUTE command message is sent to the controlled station,
which responds by an EXECUTE confirmation
message (positive if the specified control action is about to begin, otherwise
negative). This procedure is also non interrupti
ble
and the time from the EXECUTE command to the EXECUTE confirmation is
controlled by a configurable time-out interva
transmission of integrated totals
Integrated totals are values that are integrated over a specified period of time. The
Norwegian User Convention specifies
counter values to be memorised (frozen) in buffers, without the counters being
reset, before transmission to the controlling
station. Incremented values per period are then calculated in the controlling station.
The Norwegian User Convention also specifies integrated totals to be acquired as
ordinary events in the controlling station, as
indicated in fig. 6.17 and 6.18 for unbalanced and balanced systems respectively.

Communication recovery.
If a telegram transfer in either control (send/confirm procedure) or monitoring
direction (request/respond procedure) cannot be
accomplished within the configured maximum number of retries, the reason might
be that the either the controlled station or the
communication line is down.
The first case requires a station initialisation procedure as described in section
6.1.1.5, while this section describes the si
milar
procedure to recover from a communication line fault.
The recovery procedure is shown in fig. 6.26. The faulty (e.g. disconnected) line
causes the TEST command send/confirm
procedure to time out due to a missing ACK. This send confirm procedure is retried
the configured number of times, before the
controlling station starts to transmit "Request status of link" telegrams (retries are
not shown in fig. 6.23).
The controlling station continues to send "Request status of link" telegrams (which
time out) until the communication line is
reconnected. The controlled station then responds with "Status of link", whereafter
a "Reset of remote link" procedure follows,
and the communication is re-established.
Communication recovery
If a telegram transfer in either control or monitoring direction (send/confirm
procedures) cannot be accomplished within the
configured maximum number of retries, the reason might be that the either the
opposite station or the communication line is
down. The first case requires a station initialisation procedure as described in
section 6.1.1.4 or 6.1.1.5, while this section
describes the similar procedures to recover from a communication line fault.
1. Communication recovery in control direction
The recovery procedure in this case is shown in fig. 6.31. The disconnected line
causes the TEST command
send/confirm procedure (example) to time out due to missing ACKs. This
send/confirm procedure is retried a
configurable number of times before the controlling station starts to transmit
"Request status of link" telegrams (retries
are not shown in fig. 6.31).
The controlling station continues to send "Request status of link" telegrams (which
time out) until the communication
line is reconnected. The controlled station then responds with "Status of link",
whereafter the controlling station
transmits a "Reset of remote link" command to reset the link of the controlled
station
When the controlled station has transmitted an "Ack" to confirm that its link has
been reset, it initiates a "Reset of
remote link" request to reset the link of the controlling station. This request is
answered by an "Ack" from the
controlling station, whereafter the whole recovery procedure is terminated by a
"Request status of link / Status of link"
sequence initiated by the controlling station.
2. Communication recovery in monitoring direction
The recovery procedure in this case is shown in fig. 6.32. The event transmission
send/confirm procedure (example)
initiated by the controlled station times out due to a missing ACK, and the
configured number of retries (not shown in
fig. 6.32) are executed without any response. The controlled station therefore starts
to poll the link of the controlling
station by repeatedly transmitting "Request status of link".
When the line is reconnected, the controlled station initiates
Functions
This chapter contains information about functionality which is not necessarily
covered by the standard. However, the functions
described in this chapter are functions needed for the Norwegian marked, and thus
they should be implemented as described
in this chapter.
7.1 Event handling
7.1.1 Transfer of data from Controlled Station to Controlling
Station
In the Norwegian user convention Indications and Measured values and Pulse
Counters are transferred from Controlled
Station to Controlling Station on event basis. Indications after a bit-change,
Measured values after passing of dead-band and
Pulse Counters after a local freezing. These are the basic functions, but cyclic
transfer of Scan Groups can be implemented on
project basis. Events will then have higher priority than cyclic transfer and General
Interrogation. Events can interrupt an
ongoing cyclic transfer or General Interrogation. The Controlled Station algorithm
must guarantee that the end-state of all dat
a
points after a general Interrogation is correct.
7.1.2 Event Buffers
All event handling in an Controlled Station will be based on event queues, one
queue per priority level and a separate one for
Pulse Counters. When overflow of a queue occurs one event must be deleted,
either the oldest or the newest. Both methods
should be implemented and selectable be local parameter. The default will probably
be “delete newest” for Measured values
and Indications and “delete oldest” for Pulse Counters.
When a buffer overflow occurs an internal Indication (Single Point Indication) shall
be sent to the Master Station which decid
es
what to do with the situation, typically a General Interrogation. Recommended
Information Object Address (IOA) for this
indication is 1.
The description of the event buffers must be understood logically. The actual data
structure with corresponding software can be
implemented in many ways.
7.1.3 Indications
After a change of state of an Indication the event is transferred
once
with or without time-stamp. The default function will be
without time-stamp as a response to a and General Interrogation request and with
time-stamp after a change of state event.
For this user convention the formats for with full time will be utilised. However
transferring without time-stamp in all situat
ions is
also a valid function. An Indications address can be represented with multiple
entries in a queue.
7.1.4 Measured values
Measurend values can be sent to Controlling Station with or without time-stamp,
most often without time-stamp. As a response
to general interrogation ASDUs without time stamp are used, and ASDUs with
consecutive information object addresses
(Sequence of information elements, SQ=1) should be used if possible.
In projects without time-stamp the following function is to prefer. One measured
value address shall only have one entry in th
e
queue even if more events are generated before it is transferred to the Controlling
Station. Transfer of the latest possible va
lue
is always desirable.
In projects where measured values are transferred with local time-stamp the
measured values can follow the same functions as
Indications with time-stamp with reduced number of entries.
7.1.5 Pulse Counters
Pulse Counters should have a separate queue so that indications and measurand
values can not cause overflow for Pulse
Counters in case of communication break. Since Pulse Counters is often used for
settlement of accounts it should be possible
to guarantee storing of Pulse Counters for a certain time period. The default
function is “delete oldest” when an overflow
occurs. The standard event criterion is freezing of values after elapsing of a local
timer. Other criteria are possible and doe
s not
affect the further event handling and transferring to Controlling Station.
7.1.6 Priorities
An Controlled Station should support a number priorities at least Station with a
certain amount of data points. The highest or
more priorities can be mapped to class 1 (polling telegram for unbalanced mode)
and the rest to class 2. Alternatively all
priorities can be mapped to class 2 since this is most efficient.

.2 Redundant lines
A general requirement in Norway is that the redundant lines may operate at very
different baud rates. The requirements for this
function are influenced by this fact.
7.2.1 Unbalanced mode
7.2.1.1 General requirements
•
After start-up of the Controlling Station, the Controlling Station starts the links with
the link-telegram “Request Status of
Link” on both links. Controlling Station decides which line to use as primary line
fulfil the start-up procedure on this
line.
•
After restart of the Controlled Station it waits for initiative from the Controlling
Station. When the Controlling Station is
ready it will follow the procedure in the previous point. The Controlled Station
understands the line on which it receives
a “Reset of remote link” as the primary line.
•
For supervising the backup line the Controlling Station sends “Request Status of
Link” link-telegram cyclically on the
backup line.
•
When the Controlling Station looses contact on the primary line or if the Controlling
Station wants to change line for
other reasons, it sends a "Reset of Remote Link" and then starts polling on the
other line and this line will now by
definition become primary line.
•
The Controlled Station must guarantee that events are not lost during a switching of
line. This means that an event
must be explicitly acknowledged by the Controlling Station before it is deleted in the
Controlled Station. In unbalanced
mode an event is acknowledged by the Controlling station when the Controlled
station receives a new message
(request) with an altered FCB bit. It is not necessary to perform a full General
Interrogation after switching lines or after
a communication break, but the Controlling Station can decide to do so
Balanced mode
7.2.2.1 General requirements
Redundant communication implies the use of two separate communication lines.
One line is defined to be the main
communication line while the other line is a backup line.
The backup line will typically operate at a different (slower) communication speed
than the main line. A possible solution is
therefore to have two separate protocol links in each station (with identical link
addresses) to handle the communication. The
line (link) which is used for communication at any time is defined to be the active
line (link).
Selection and switch of active line is the responsibility of the controlling station, and
may be performed either automatically
or
manually, by e.g. the application layer or the user process. The controlled station
always understands the line on which it
received the last ASDU (application telegram) as the active line.
The link telegram "Test Function of Link" is transmitted periodically in control
direction on both lines to supervise the statu
s of
the lines. An ACK will be received on the line which is defined to be the active line
in the controlled station, and a NACK wil
l be
received on the passive line. If no response is received on a line, either the line or
the controlled station is down. This lin
k test
procedure may also be performed periodically by the controlled station.
IEC 870-5-101
Norwegian User Conventions
2000-03-24
Revision no.2.0
side 166
7.3 Addressing
There are 3 levels of addresses in the IEC870-5-101 protocol. Valid ranges are
defined in chapter 4.
7.3.1 Link Address
The link address is a number for a communication link which is used for the
communication lines out from a Controlling
Station. It is only used as an address in the communication network itself, an shall
not
be a part of total address of a data point.
According to the standard this parameter can consist of 0,1 or 2 octets. 0 is valid
only for balanced mode. According to the
Norwegian user convention
1 octet
shall be used.
7.3.2 Common Address of ASDU
The Common Address of ASDU is common number used for all objects in one
Controlled Station. One Controlled Station can
be either an entire Station Control System or only a part of it. According to the
standard this parameter can consist of 1 or 2
octets. According to the Norwegian user convention
1 octet
shall be used.
7.3.3 Information Object Address
The Information Object Address is a number given to each data point or object
within one Controlled Station and is common for
all data types. According to the standard this parameter can consist of 1,2 or 3
octets. According to the Norwegian user
convention
2 octets
shall be used.
7.3.4 Addressing rules
All the addresses can be set to any valid number, but these rules must be noted:
•
Link address is only used by the communication equipment.
•
Under one link or line from a Controlling Station the total address built together by
the Common Address of ASDU and
Information Object Address shall be a unique identifier for all data points (objects).
7.3.5 Possible addressing conventions
A modern Station Control System often consists of a common communication
equipment, several bay controllers and a number
of Protection units. Each of them can consist of a number of objects. The IEC870-
5-101 standard gives no rules for how
addresses are given to all these objects as long as the above limitations are
followed. Any structure using Common Address of
ASDU and Information Object Address fields are allowed, but there are advantages
to follow some conventions within a project
to reduce engineering costs. These conventions must be agreed upon for each
project because this user convention does not
give any further rules. Here some possible structures are described.
•
For traditional RTUs with I/O boards etc. one Common Address of ASDU number is
used and all the objects within the RTU
is given a unique Information Object Address. Each data type is given a range
within the two octets.
•
For a Station Control System the entire system is given one Common Address of
ASDU. One of the two octets in the
Information Object Address is used to identify each Bay Controller or Protection
Unit. The other octet is used to identify
each object within one unit.
•
For a Station Control System each Bay Controller or Protection Unit is given a
separate Common Address of ASDU. The
objects within one unit is identified by the Information Object Address field
Frame length
The frame length have to be a parameter in the controlled station.
The maximum frame length is 255 octets.
Each project have to implement the frame length witch is necessary for the correct
functionality, and in due to the line quali
ty
between controlled and controlling station
7.7 Database handling
The database in the controlled station may contain addresses which is not defined
in the project. If the implementation in the
controlled station block information in such a way that information related to
undefined addresses is sent, this should be
regarded as an error. However, the controlling station should be able to handle the
situation so that other messages are
processed normally.
7.8 Scaling
7.8.1
Scaling of normalised measured values
Recommended scaling of normalised measured values (ASDU 9)
Range:
Normalised value to be transferred from controlled
station:
Maximum value in engineering units (V
Max
)+1
Minimum value in engineering units (V
Min
)
0 (unipolar values), -1 (bipolar values)
V
Max
and V
Min
for each measured value shall be exchanged to give correct scaling between
controlled and controlling station
regardless of the internal representation of the signal in controlled station.