Home / Products / EmbedCore-v5
IED side · MMS server + client · GOOSE

EmbedCore-v5 — IEC 61850 IED-side SDK

Turn a conventional protection or bay controller into a compliant IEC 61850 IED in one to two weeks.

EmbedCore-v5 is a library you link into your own device firmware. It publishes your measurements, status points, settings and events as a standard IEC 61850 MMS server, and can also act as a client. The kernel is platform independent and has been deployed across embedded RTOS, Linux and VxWorks targets.

EmbedCore-v5
Beijing New Technology & New Product Certificate, issued 2015 for EmbedCore
Delivery
C source code + project files + API manual + sample projects (binary library option available)
Roles
MMS server and MMS client in one library; GOOSE publisher/subscriber
Standards
IEC 61850 Edition 1 and Edition 2 service set
Platforms
Windows, Linux, Unix, VxWorks · x86, ARM9, MIPS · big- and little-endian
Integration effort
Typically 1–2 weeks for a conventional protection or measurement device
Licensing
Per-project source licence; royalty-free binary redistribution for your own product line

What it does

The package is filled into the device you manufacture and talks to your existing application through a data mapping table, so your control logic keeps running unchanged while the outside world sees a standard IEC 61850 server.

Because the library also contains the client side, the same kernel can be used for a bay-level unit that both serves the station bus and polls downstream devices — one protocol implementation to validate instead of two.

  • Telemetry, status, control, set-point, SOE, protection events, setting groups, file transfer and inter-bay interlocking
  • Multiple clients served concurrently, with correct behaviour for both synchronous and asynchronous client operations
  • Per-port service configuration when the device has more than one network interface
  • Service IP taken from the model, not restricted to the host IP address
  • Data mapping from heterogeneous sources into one service surface

Modelling without a 61850 specialist

The library ships the modelling layer as well as the protocol layer: logic nodes for the common protection and measurement functions are pre-built, and the package includes an ICD configuration tool plus a tool that maps model data to the device data (currents, voltages, status).

The practical consequence is staffing. A protection engineer who already knows the device can complete the 61850 integration after a short training session, without hiring a dedicated 61850 engineer.

  • ICD / CID configuration tool included
  • Sample server and client projects showing how each library call is used
  • Model-to-device data mapping tool

IEC 61850 service coverage

Service areaCoverage
Server / logical device / logical node directorySupported
Association (associate, abort, release)Supported
Data — read, write, directory, definitionSupported
Data sets — read, write, create, delete, directorySupported
SubstitutionSupported
Setting groups — select active/edit, write, confirm, read, SGCBSupported
Reporting — buffered and unbuffered, dchg / qchg / dupd triggers, read and write RCBSupported
Logging — LCB read/write, query by time and by entry, log statusSupported
Control — select, select-with-value, cancel, execute, command terminationSupported
Time-activated operateOptional
File transfer — read, write, delete, attributesSupported
Time synchronisation — SNTP server and clientSupported

Service list as published for the product; Edition 1 and Edition 2 services are both covered.

Frequently asked

Do we get source code or only a binary?

Both models exist. Source delivery is C source plus project files, interface documentation and sample projects under a per-project source licence. A binary library with symbols and a debug build is available for production devices where you prefer not to carry the source.

Which editions and roles are covered?

MMS client and server in the same library, GOOSE transmit and receive, SV subscription, and model/data-set definitions for Edition 1 and Edition 2. SCL parsing and a model consistency check are included, so existing CID/ICD files can be imported directly.

Can we test conformance before committing to a licence?

Yes. A trial build of the test system and a remote or on-site conformance test are available, with a per-clause report. Licensing and delivery start after you have seen the result.

Related reading

Decision guide

Commercial IEC 61850 SDK vs open source: what you are actually buying

Both options work in a lab. The difference shows up at type approval, on VxWorks, and the first time a third-party maste…

Migration

Replacing libiec61850 without rewriting your device

When an open-source IEC 61850 stack no longer fits — licensing, non-Linux targets, Edition 2 depth, conformance evidence…

Standards

IEC 61850 Edition 1 vs Edition 2: read the ICD before you argue

Most edition arguments are settled by the device's own SCL file. How to read version, revision and the Services block, w…

Related

StationCore

Bring up to 200 IEDs into your master station or gateway with a few lines per device.

IEC 60870-5-101/103/104 SDK

One code base for serial telecontrol, protection information and TCP/IP SCADA links — plus the tester that ships with it.

Ask about EmbedCore-v5

Tell us the platform, the protocols and the acceptance criteria. We will answer with what the licence covers and what the integration effort looks like — not with a brochure.