RUTX11 IEC 60870-5

Wiki mirrorView source
The information in this page is updated in accordance with firmware version RUTX_R_00.07.22.1.

Summary

IEC 60870-5 is an international standard that defines communication protocols for telecontrol systems used in electrical power systems and other industrial automation environments. It focuses on reliable, real-time exchange of data between control centers and remote terminal units (RTUs), protection devices, and other field equipment.

Supported Information Object Types table (IOT/TI)

TypeDexHexDescription
ASDU_TYPEUNDEF00x00Not used
M_SP_NA_110x01Single-point information
M_SP_TA_120x02Single-point information with time tag
M_DP_NA_130x03Double-point information
M_DP_TA_140x04Double-point information with time tag
M_ST_NA_150x05Step position information
M_ST_TA_160x06Step position information with time tag
M_BO_NA_170x07Bitstring of 32 bit
M_BO_TA_180x08Bitstring of 32 bit with time tag
M_ME_NA_190x09Measured value, normalised value
M_ME_TA_1100x0AMeasured value, normalized value with time tag
M_ME_NB_1110x0BMeasured value, scaled value
M_ME_TB_1120x0CMeasured value, scaled value wit time tag
M_ME_NC_1130x0DMeasured value, short floating point number
M_ME_TC_1140x0EMeasured value, short floating point number with time tag
M_IT_NA_1150x0FIntegrated totals
M_IT_TA_1160x10Integrated totals with time tag
M_EP_TA_1170x11Event of protection equipment with time tag
M_EP_TB_1180x12Packed start events of protection equipment with time tag
M_EP_TC_1190x13Packed output circuit information of protection equipment with time tag
M_PS_NA_1200x14Packed single point information with status change detection
M_ME_ND_1210x15Measured value, normalized value without quality descriptor
M_SP_TB_1300x1ESingle-point information with time tag CP56Time2a
M_DP_TB_1310x1FDouble-point information with time tag CP56Time2a
M_ST_TB_1320x20Step position information with time tag CP56Time2a
M_BO_TB_1330x21Bitstring of 32 bit with time tag CP56Time2a
M_ME_TD_1340x22Measured value, normalised value with time tag CP56Time2a
M_ME_TE_1350x23Measured value, scaled value with time tag CP56Time2a
M_ME_TF_1360x24Measured value, short floating point number with time tag CP56Time2a
M_IT_TB_1370x25Integrated totals with time tag CP56Time2a
M_EP_TD_1380x26Event of protection equipment with time tag CP56Time2a
M_EP_TE_1390x27Packed start events of protection equipment with time tag CP56Time2a
M_EP_TF_1400x28Packed output circuit information of protection equipment with time tag CP56Time2a

IEC 60870-5 Client

An IEC 60870-5 Client is a communication component in a SCADA or automation system that initiates and manages data exchange with remote devices using the IEC 60870-5 telecontrol protocol IEC 60870-5-104 (TCP/IP). Note: IEC 60870-5-101 (serial) is not currently supported.

IEC 60870-5 Client general

This section displays IEC 60870-5 Client status information and allows to enable/disable the service.
FieldValueDescription
Enabledoff | on; default: onEnable/disable IEC 60870-5 client service.
StatusStatus of service, whether it is currently running. If it is active, it will also show how long it has been running.

IEC 60870-5 Clients

By default, the client list is empty. To add a new client, click the 'Add' button.
After clicking 'Add' you will be redirected to the newly added client's configuration page.

General settings

FieldValueDescription
Enabledoff | on; default: onCheck to enable this configuration.
Namestring; default: Client 1Name of the client. Used for easier device management purposes only.
Periodinteger [1..86400]; default: 60Interval in seconds for sending requests to server.
Originator addressinteger [0..100]; default: 1Address used to identify the source of the request within the IEC 60870-5 system.
Timeoutinteger [1..60]; default: 5Time in seconds that the client waits for a response to an interrogation request.
Test*-(interactive button)Reads data from the IEC 60870-5 server.
*Response from the test button:

Connection settings

FieldValueDescription
Connection typeIEC 104 (TCP) | EC 101 (Serial)*; default: IEC 104 (TCP)Client connection type.
IP Addressipv4; default: noneIPv4 address of server.
Portinteger [1..65535]; default: 2404Specify port number the server is listening on..
Link layer addressinteger [1..65534]; default: 1Unique address identifying a station on the communication link.
Device configurationlist; default: noneWhich serial port configuration will be used for serial communication.
Server addressinteger [1..65535]; default: 1Server address of remote station.

Serial Device*

To add a new serial device, press the 'Add' button.
FieldValueDescription
Namestring; default: noneName of the serial configuration. Used for easier configurations management purpose only.
Link layer modeUnbalanced | Balanced; default: UnbalancedWhether communication is balanced (both can initiate) or unbalanced (only one initiates).
Device; default: Selects which serial port to use for communication.
Baud rate (USB)integer [300..4000000]; default:9600Data rate for serial data transmission (in bits per second (bps)).
Data bits5 | 6 | 7 |8; default: 8Number of data bits for each character.
Stop bits1| 2; default: 1Stop bits sent at the end of every character allow the receiving signal hardware to detect the end of a character and to resynchronise with the character stream. Electronic devices usually use one stop bit. Two stop bits are required if slow electromechanical devices are used.
ParityEven | Odd| Mark | Space | None; default: NoneIn serial transmission, parity is a method of detecting errors. An extra data bit is sent with each data character, arranged so that the number of 1 bits in each character, including the parity bit, is always odd or always even. If a byte is received with the wrong number of 1s, then it must have been corrupted. However, an even number of errors can pass the parity check.
  • None (N) - no parity method is used.
  • Odd (O) - the parity bit is set so that the number of "logical ones (1s)" has to be odd.
  • Even (E) - the parity bit is set so that the number of "logical ones (1s)" has to be even.
  • Space (s) - the parity bit will always be a binary 0.
  • Mark (M) - the parity bit will always be a binary 1.
Flow controlNone | RTS/CTS | Xon/Xoff; default: NoneIn many circumstances a transmitter might be able to send data faster than the receiver is able to process it. To cope with this, serial lines often incorporate a "handshaking" method, usually distinguished between hardware and software handshaking.
  • RTS/CTS - hardware handshaking. RTS and CTS are turned OFF and ON from alternate ends to control data flow, for instance when a buffer is almost full.
  • Xon/Xoff - software handshaking. The Xon and Xoff characters are sent by the receiver to the sender to control when the sender will send data, i.e., these characters go in the opposite direction to the data being sent. The circuit starts in the "sending allowed" state. When the receiver's buffers approach capacity, the receiver sends the Xoff character to tell the sender to stop sending data. Later, after the receiver has emptied its buffers, it sends an Xon character to tell the sender to resume transmission.

Information objects

FieldValueDescription
Information object selectionAll | Custom; default: AllShould all information objects that are visible be saved.
Common addressinteger [1..65534]; default: noneList of common addresses from which information objects will be read.
Scanning common addressinteger [1..65534]; default: 1Address from which information objects will be scanned.
Scan-(interactive button)Starts scanning with selected common address.
After selecting the "Custom" information object option and scanning the selected server, a new section appears "Selected information objects" with filled-in data from the server. Here you can manually add or rename object addresses from the scanned list or manually.
FieldValueDescription
Enabledcheck boxData will be pulled only from selected objects.
Namestring; default: noneAdd name for object.
Object addressinteger [0..16777215]Address of object.
Common addressinteger [1..65534]Information object common address.

IEC 60870-5 Server

An IEC 60870-5 Server is a communication component implemented in field devices—such as RTUs, substations, protection relays, and data concentrators—that responds to requests from an IEC 60870-5 Client and provides real-time data, events, and control interfaces. It implements the server-side (outstation) role defined by the IEC 60870-5 telecontrol standards, including IEC 60870-5-101 for serial communication and IEC 60870-5-104 for TCP/IP networks.

IEC 60870-5 Server information objects

If the device doesn't have the needed capabilities for a specic information object, then that object won't exist.
If an error occurs while reading an information object:
  • For a M_IT_NA_1, then the value will be 0 and the invalid ag will be set
  • All other types, then the value will be 0 and the invalid and substituted quality bit will be set
Information object nameAddressTypeWritableNeeded capabilitiesDescription
Uptime (high 32bits)1M_IT_NA_1NoNoneHigh uint32 from uint64 uptime
Uptime (low 32bits)2M_IT_NA_1NoNoneLow uint32 from uint64 uptime
Unix timestamp (high 32bits)3M_IT_NA_1NoNoneHigh uint32 from uint64 unix timestamp
Unix timestamp (low 32bits)4M_IT_NA_1NoNoneLow uint32 from uint64 unix timestamp
Serial number (high 32bits)5M_IT_NA_1NoNoneHigh uint32 from uint64 serial number
Serial number (low 32bits)6M_IT_NA_1NoNoneLow uint32 from uint64 serial number
Selected modem index7M_ME_NB_1YesMobile supportSelect modem when multiple modems are available
Selected SIM number8M_ME_NB_1YesMobile supportSelect SIM slot when multiple SIMs are available
Signal strength9M_ME_NC_1NoMobile supportRSSI from modem
Temperature10M_ME_NC_1NoMobile supportTemperature in °C from modem
SIM statistics, this day, RX (high 32bits)11M_IT_NA_1NoMobile supportHigh uint32 from uint64 SIM data usage
SIM statistics, this day, RX (low 32bits)12M_IT_NA_1NoMobile supportLow uint32 from uint64 SIM data usage
SIM statistics, this day, TX (high 32bits)13M_IT_NA_1NoMobile supportHigh uint32 from uint64 SIM data usage
SIM statistics, this day, TX (low 32bits)14M_IT_NA_1NoMobile supportLow uint32 from uint64 SIM data usage
SIM statistics, last 24h, RX (high 32bits)15M_IT_NA_1NoMobile supportHigh uint32 from uint64 SIM data usage
SIM statistics, last 24h, RX (low 32bits)16M_IT_NA_1NoMobile supportLow uint32 from uint64 SIM data usage
SIM statistics, last 24h, TX (high 32bits)17M_IT_NA_1NoMobile supportHigh uint32 from uint64 SIM data usage
SIM statistics, last 24h, TX (low 32bits)18M_IT_NA_1NoMobile supportLow uint32 from uint64 SIM data usage
SIM statistics, this week, RX (high 32bits)19M_IT_NA_1NoMobile supportHigh uint32 from uint64 SIM data usage
SIM statistics, this week, RX (low 32bits)20M_IT_NA_1NoMobile supportLow uint32 from uint64 SIM data usage
SIM statistics, this week, TX (high 32bits)21M_IT_NA_1NoMobile supportHigh uint32 from uint64 SIM data usage
SIM statistics, this week, TX (low 32bits)22M_IT_NA_1NoMobile supportLow uint32 from uint64 SIM data usage
SIM statistics, last 7 days, RX (high 32bits)23M_IT_NA_1NoMobile supportHigh uint32 from uint64 SIM data usage
SIM statistics, last 7 days, RX (low 32bits)24M_IT_NA_1NoMobile supportLow uint32 from uint64 SIM data usage
SIM statistics, last 7 days, TX (high 32bits)25M_IT_NA_1NoMobile supportHigh uint32 from uint64 SIM data usage
SIM statistics, last 7 days, TX (low 32bits)26M_IT_NA_1NoMobile supportLow uint32 from uint64 SIM data usage
SIM statistics, this month, RX (high 32bits)27M_IT_NA_1NoMobile supportHigh uint32 from uint64 SIM data usage
SIM statistics, this month, RX (low 32bits)28M_IT_NA_1NoMobile supportLow uint32 from uint64 SIM data usage
SIM statistics, this month, TX (high 32bits)29M_IT_NA_1NoMobile supportHigh uint32 from uint64 SIM data usage
SIM statistics, this month, TX (low 32bits)30M_IT_NA_1NoMobile supportLow uint32 from uint64 SIM data usage
SIM statistics, last 30 days, RX (high 32bits)31M_IT_NA_1NoMobile supportHigh uint32 from uint64 SIM data usage
SIM statistics, last 30 days, RX (low 32bits)32M_IT_NA_1NoMobile supportLow uint32 from uint64 SIM data usage
SIM statistics, last 30 days, TX (high 32bits)33M_IT_NA_1NoMobile supportHigh uint32 from uint64 SIM data usage
SIM statistics, last 30 days, TX (low 32bits)34M_IT_NA_1NoMobile supportLow uint32 from uint64 SIM data usage
IMSI (high 32bits)35M_IT_NA_1NoMobile supportHigh uint32 from uint64 IMSI
IMSI (low 32bits)36M_IT_NA_1NoMobile supportLow uint32 from uint64 IMSI
GPS UTC timestamp (high 32bits)37M_IT_NA_1NoGPS supportHigh uint32 from uint64 UTC timestamp
GPS UTC timestamp (low 32bits)38M_IT_NA_1NoGPS supportLow uint32 from uint64 UTC timestamp
GPS position, longitude39M_ME_NC_1NoGPS supportLongitude (~5–6 decimal precision)
GPS position, latitude40M_ME_NC_1NoGPS supportLatitude (~5–6 decimal precision)
GPS position, altitude41M_ME_NC_1NoGPS supportAltitude
GPS position, angle42M_ME_NC_1NoGPS supportAngle
GPS position, speed43M_ME_NC_1NoGPS supportSpeed
GPS position, accuracy (HDOP)44M_ME_NC_1NoGPS supportGPS accuracy
GPS position, satellites45M_ME_NB_1NoGPS supportGPS satellites
I/O pin 146M_SP_NA_1 / M_ME_NC_1Depends on pin typeI/O supportConfigurable I/O pin
I/O pin 247M_SP_NA_1 / M_ME_NC_1Depends on pin typeI/O supportConfigurable I/O pin
I/O pin 348M_SP_NA_1 / M_ME_NC_1Depends on pin typeI/O supportConfigurable I/O pin
I/O pin 449M_SP_NA_1 / M_ME_NC_1Depends on pin typeI/O supportConfigurable I/O pin
I/O pin 550M_SP_NA_1 / M_ME_NC_1Depends on pin typeI/O supportConfigurable I/O pin
I/O pin 651M_SP_NA_1 / M_ME_NC_1Depends on pin typeI/O supportConfigurable I/O pin
I/O pin 752M_SP_NA_1 / M_ME_NC_1Depends on pin typeI/O supportConfigurable I/O pin
I/O pin 853M_SP_NA_1 / M_ME_NC_1Depends on pin typeI/O supportConfigurable I/O pin

IEC 60870-5 Server general

This section displays IEC 60870-5 Server status information and allows to enable/disable the service.
FieldValueDescription
Enabledoff | on; default: onEnable/disable IEC 60870-5 server service.
StatusStatus of service, whether it is currently running. If it is active, it will also show how long it has been running.

IEC 60870-5 Servers

By default, the server list is empty. To add a new server, click the 'Add' button.
After clicking 'Add' you will be redirected to the newly added server's configuration page.

General settings

FieldValueDescription
Enabledoff | on; default: onCheck to enable this configuration.
Namestring; default: Server 1Name of the server. Used for easier device management purposes only.
Common addressinteger [1..65534]; default: 1Common address of the ASDU. It is also sometimes referred to as the application layer address.
Enable spontaneous transmissionoff | on; default: offEnable the transmission of spontaneous events. Will notify clients when an object changes.
Spontaneous information objectsList: Uptime | Unix timestamp | Serial number | Selected modem index | Selected SIM number | Signal strength | Temperature | SIM statistics for this day | SIM statistics for last 24 hours | SIM statistics for this week | SIM statistics for last 7 days | SIM statistics for this month | SIM statistics for last 30 days | IMSI | GPS UTC timestamp | GPS longitude | GPS latitude | GPS altitude | GPS angle | GPS speed | GPS accuracy | GPS satellites | I/O pins (supported pins by device, can be found here default: AllList of information object for which spontaneous messages will be sent.
Enable cyclic transmissionoff | on; default: offEnable the transmission of cyclic messages. Will send the current values of changes on configured period.
Cyclic transmission periodinterger; default: 20000Duration in milliseconds for how often cyclic messages should be sent.
Cyclic information objectsList: Uptime | Unix timestamp | Serial number | Selected modem index | Selected SIM number | Signal strength | Temperature | SIM statistics for this day | SIM statistics for last 24 hours | SIM statistics for this week | SIM statistics for last 7 days | SIM statistics for this month | SIM statistics for last 30 days | IMSI | GPS UTC timestamp | GPS longitude | GPS latitude | GPS altitude | GPS angle | GPS speed | GPS accuracy | GPS satellites | I/O pins (supported pins by device, can be found here); default: AllList of information object for which cyclic messages will be sent.
Configure I/O pinsoff | on; default: offManually specify which I/O will be available as information objects.
I/O pinsList: I/O pins (supported pins by device, can be found here); default: first pinInput/Output pins

Connection settings

FieldValueDescription
Connection typeIEC 104 (TCP) | IEC 101 (Serial); default: IEC 104 (TCP)Server connection type.
Portinteger [1..65535]; default: 2404Specify port number the server is listening on..
Allow remote accessoff | on; default: offAllow access through WAN.
Link layer modeUnbalanced | Balanced; default: UnbalancedWhether communication is balanced (both can initiate) or unbalanced (only one initiates).
Link layer addressinteger [1..65534]; default: 1Unique address identifying a station on the communication link.
Size of link layer addressinteger; default: noneSize of link layer address field in bytes..
Serial device; default: Selects which serial port to use for communication.
Baud rate (USB)integer [300..4000000]; default:9600Data rate for serial data transmission (in bits per second (bps)).
Data bits5 | 6 | 7 |8; default: 8Number of data bits for each character.
Stop bits1| 2; default: 1Stop bits sent at the end of every character allow the receiving signal hardware to detect the end of a character and to resynchronise with the character stream. Electronic devices usually use one stop bit. Two stop bits are required if slow electromechanical devices are used.
ParityEven | Odd| Mark | Space | None; default: NoneIn serial transmission, parity is a method of detecting errors. An extra data bit is sent with each data character, arranged so that the number of 1 bits in each character, including the parity bit, is always odd or always even. If a byte is received with the wrong number of 1s, then it must have been corrupted. However, an even number of errors can pass the parity check.
  • None (N) - no parity method is used.
  • Odd (O) - the parity bit is set so that the number of "logical ones (1s)" has to be odd.
  • Even (E) - the parity bit is set so that the number of "logical ones (1s)" has to be even.
  • Space (s) - the parity bit will always be a binary 0.
  • Mark (M) - the parity bit will always be a binary 1.
Flow controlNone | RTS/CTS | Xon/Xoff; default: NoneIn many circumstances a transmitter might be able to send data faster than the receiver is able to process it. To cope with this, serial lines often incorporate a "handshaking" method, usually distinguished between hardware and software handshaking.
  • RTS/CTS - hardware handshaking. RTS and CTS are turned OFF and ON from alternate ends to control data flow, for instance when a buffer is almost full.
  • Xon/Xoff - software handshaking. The Xon and Xoff characters are sent by the receiver to the sender to control when the sender will send data, i.e., these characters go in the opposite direction to the data being sent. The circuit starts in the "sending allowed" state. When the receiver's buffers approach capacity, the receiver sends the Xoff character to tell the sender to stop sending data. Later, after the receiver has emptied its buffers, it sends an Xon character to tell the sender to resume transmission.

Information objects

Information objects transmit data from one or more data sources (can be a Modbus client, DNP3 client, M-BUS...) and write it to IEC 60870-5 Information objects.
To add new data source, press `Add` button:
Information object configuration:
FieldValueDescription
Enableoff | on; default: offTurns Object configuration on or off.
Information object namestring; default: noneName of configuration.
Information object sourcelist; default: noneClient service which will be sending requests.
Information object valuelist and permissions type; default: noneRequest value and its permissions (Read-Only, Write-Only or Read-Write).
Information object rangeinteger [1..65535]; default: noneSpecify the start index and count for the range.
Information object typeBinary | String | Bool | INT8 | UINT8 | INT16 | UINT16 | INT32 | UINT32 | INT64 | UINT64 | FLOAT32 | FLOAT64; default: BinaryValue data type.
Information object sizeinteger [1..255]; default: noneSize of the value in bytes.
Information object address rangeinteger [1000..16777215]; default: BinaryIEC 60870-5 Information Object Address range.
Type ID1 - Single-point information | 7 - Bitstring of 32 bit | 11 - Measured value, scaled value | 13 - Measured value, short floating point number | 15 - Integrated totals (32-bit counter); default: 1 - Single-point informationIEC 60870-5 Type Identification.