Skip to content
IEC 60870-5-103

IEC 60870-5-103

The informative interface of protection equipment: how a substation controller polls protection relays for their state, events, settings and fault records.

Transport
FT 1.2 on a serial line or fibre optic ring; or a terminal server that passes the line through
Link
Unbalanced: the controlling system polls each relay
Addressing
Function type (FUN) and information number (INF)
Library
go-iec60870-5 (iec103)
CLI
iec103ctl
Interop
iec60870-5-interop v0.5.0

IEC 60870-5-103 (IEC 103) is the companion standard for the informative interface of protection equipment. A controlling system (a substation controller, bay controller or gateway) polls protection relays (distance, overcurrent, transformer and line differential protection) over a serial line or a fibre optic ring. It uses the FT 1.2 frames and link procedures of IEC 101, but not its data model: IEC 103 addresses everything by a function type (FUN: the kind of protection) and an information number (INF: what the value means for that function type), so a trip of a distance relay looks the same from every vendor.

Beyond events and measurands, IEC 103 has what protection engineers need: general commands to switch protection functions or reset LEDs, generic services to read and write settings by group and entry, and the transmission of disturbance data, the fault records a relay keeps after it trips, channel by channel.

Where you meet it

  • Substations with protection relays from several vendors, read by a substation automation system or gateway
  • Retrofits, where IEC 103 relays stay in service under a newer IEC 61850 or IEC 104 station level
  • Gateways that translate relay events and fault records into IEC 104 or IEC 61850 for the control centre
  • Fault analysis, where the disturbance records of a relay are collected for engineers

Quickstart

From the command line

Install iec103ctl with curl -fsSL https://get.otfabric.io/iec103ctl | sh, or on Windows irm https://get.otfabric.io/iec103ctl.ps1 | iex (all install options). No relay at hand? Start a simulated one:

Terminal window
iec103ctl server start

and poll it from another terminal:

Terminal window
# Who is it, and what is the state of every indication?
iec103ctl client identify --url tcp://127.0.0.1:2401
iec103ctl client interrogate --url tcp://127.0.0.1:2401
# Settings of group 1, through the generic services
iec103ctl client generic group --url tcp://127.0.0.1:2401 --group 1 --format table
# Recorded faults, and one fault's disturbance data as CSV
iec103ctl client disturbance list --url tcp://127.0.0.1:2401
iec103ctl client disturbance get --url tcp://127.0.0.1:2401 --fan 1 --csv fault1.csv

From Go

Terminal window
go get github.com/otfabric/go-iec60870-5

Bring up the link, synchronize the clock, interrogate the relay and read its settings headings:

main.go
package main
import (
"context"
"fmt"
"log"
"net"
"time"
"github.com/otfabric/go-iec60870-5/iec103"
"github.com/otfabric/go-iec60870-5/iec103/client"
)
func main() {
// A terminal server in front of the relay's serial port.
conn, err := net.DialTimeout("tcp", "10.0.0.30:2401", 5*time.Second)
if err != nil {
log.Fatal(err)
}
c, err := client.New(conn, client.Config{
LinkAddr: 1,
NoInitGI: true, // interrogate explicitly below
Handler: func(a *iec103.ASDU) { fmt.Println(a) }, // events, measurands, answers
})
if err != nil {
log.Fatal(err)
}
defer c.Close()
ctx, cancel := context.WithTimeout(context.Background(), 30*time.Second)
defer cancel()
if err := c.WaitUp(ctx); err != nil { // request status, reset CU, identification
log.Fatal(err)
}
if _, err := c.ClockSync(ctx, time.Now()); err != nil {
log.Fatal(err)
}
data, err := c.Interrogate(ctx)
if err != nil {
log.Fatal(err)
}
fmt.Printf("general interrogation returned %d ASDUs\n", len(data))
headings, err := c.ReadHeadings(ctx) // generic services: the groups of settings
if err != nil {
log.Fatal(err)
}
for _, set := range headings.Sets {
fmt.Printf("group %d: %s\n", set.GIN.Group, set.Value.Text())
}
}

What go-iec60870-5 and iec103ctl support

Roles Controlling system (client) and protection equipment (server)
ASDUs Every compatible type identification (1 to 11, 20, 21, 23 to 31), with private types and causes kept octet for octet
Client Link start-up with identification, time synchronization (addressed and broadcast), general interrogation, general commands checked against the standard’s table, generic read and write (also staged with execute or abort), the full disturbance data transfer
Server Answers the link itself, keeps the clock, queues identification after a reset, runs the disturbance data transfer from a record source
CLI interrogate, command, clock, identify, generic services, disturbance list and get (JSON and CSV), monitor, scan a line, and a simulated relay from YAML
Not yet One controlling system polling several relays on a shared line, test mode and monitor-direction blocking as server features
Dependencies Go standard library only

Interoperability

iec60870-5-interop runs four independent IEC 103 stacks: vitusdong/iec103-dotnet (client and server), masarray ARIEC103, Open103 and the cs103 package of go-iecp5 (clients). go-iec60870-5’s protection equipment passes against all four controlling systems, and its disturbance data transfer runs end to end against Open103. The other direction is weaker: the only open relay that serves test data, vitusdong’s, deviates from the standard in every reply checked, so the go-iec60870-5 client has one independent peer and it does not behave like a real relay. No open stack offers a standard-conforming IEC 103 protection device; finding that out is part of what the interop suite is for.

OT Fabric projects for IEC 60870-5-103

go-iec60870-5

The IEC 60870-5 telecontrol family in one module: IEC 101 on serial lines, IEC 102 for meter readings, IEC 103 for protection relays and IEC 104 over TCP/IP, each as controlling and controlled station, on shared FT 1.2, link-layer and time-tag packages. IEC 104 keeps TLS, IEC 62351-5, file transfer and redundancy groups. Pure Go, standard library only.

go get github.com/otfabric/go-iec60870-5
  • IEC 101
  • IEC 102
  • IEC 103
  • IEC 104
GitHub

iec103ctl

Poll IEC 103 protection relays: general interrogation, general commands, clock, identification, settings through the generic services, recorded faults with their disturbance data as JSON or CSV, monitoring and line scans, or simulate a relay. Part of iec60870ctl.

iec60870-5-interop

Independent IEC 60870-5 implementations in containers behind one contract, per companion standard: IEC 101 (lib60870-C, cB-Sigma, digitalpetri), IEC 102 (gisce/iec870ree, REE profile), IEC 103 (vitusdong, ARIEC103, Open103, go-iecp5 cs103) and IEC 104 (lib60870-C, OpenMUC j60870, wendy512, cB-Sigma, part5). OT Fabric's own go-iec60870-5 stack is published behind the same contract, one image per standard, for testing your stack against.

  • IEC 101
  • IEC 102
  • IEC 103
  • IEC 104
GitHub

Who is behind IEC 60870-5-103

The organizations that publish, test, certify or host open-source work for IEC 60870-5-103. Listed for reference, not as partners. Compare membership and fees.