IEC 61850 Driver

dc3-driver-iec61850 acts as an IEC 61850 MMS client. It maintains one MMS association per IED device and reads/writes data attributes addressed by an object reference and functional constraint (e.g. S1MMXU1.TotW.actVal / MX).

Protocol background

IEC 61850 is the standard for substation automation. Data objects are organized in a server model by logical device, logical node, and data object; the MMS protocol retrieves their values. This driver resolves an object reference and functional constraint, fetches the data values, and returns the first basic data attribute value.

• Driver name / code: IEC 61850 Driver / Iec61850Driver
• Type: DRIVER_CLIENT (MMS client to an IED server)
• Underlying library: OpenMUC openiec61850

Attribute configuration

Driver attributes (device-level driver-attribute)

Attribute	code	Type	Default	Description
Host	host	STRING	(empty)	IEC 61850 server (IED) address
Port	port	INT	102	MMS service port

Point attributes (point-attribute)

Attribute	code	Type	Default	Description
Object Reference	objectReference	STRING	(empty)	Data object reference, e.g. S1MMXU1.TotW.actVal
Functional Constraint	functionalConstraint	STRING	MX	MX, ST, CO, SP, SE

Command attributes (command-attribute)

Attribute	code	Type	Default	Description
Object Reference	objectReference	STRING	(empty)	Data object reference for commands

Collection and health

• Collection cycle: default cron 0/30 * * * * ?.
• Health/online: device health defaults to cron 0/15 * * * * ?, lease timeout 45 seconds.

Capability matrix

Capability	Supported	Notes
Read	✓
Write	✓ (boolean/int/float/visible-string by data type)
Subscribe	—

Implementation status: available ::

The server model is retrieved once per association and cached; reads call getDataValues and take the first BasicDataAttribute value via getValueString().

Minimal onboarding example

1. Create a Device using IEC 61850 Driver, set host=<ied-address> and port=102.
2. Add a Point (READ_ONLY) with objectReference=S1MMXU1.TotW.actVal and functionalConstraint=MX.
3. Start the driver; the measurement is polled on the collection cycle.

Further reading

• Driver overview — entry point to all protocol drivers and selection
• Driver capability matrix — quick reference of read/write/subscribe capabilities
• Device onboarding — a complete onboarding walkthrough