What is an IED (Intelligent Electronic Device)?

IEC 61850 deals a lot with IEDs. But: What is an IED?

First you can check with two documents of the series IEC 61850:

IEC 61850-1 - Intelligent Electronic Device (IED)
any device incorporating one or more processors with the capability of receiving or sending data/control from or to an external source (for example, electronic multifunktional meters, digital relays, controllers)

IEC 61850-1 - Physical Device (PD)
equivalent to an IED as used in the context of this standard

IEC 61850-5 - Intelligent electronic device (IED)
device incorporating one or more processors with the capability to execute application 
functions, store data locally in a memory and exchange data with other IEDs (sources or sinks) over a digital link

Many years after these definitions have been published, we have different views on the term IED:

Physical IED (in the context of IEC 61850 and IEC 61400-25) - any physical device incorporating one or more processors with the capability of exchanging information (derived from IEC 61850 information models and exchanged with IEC 61850 services for client/server and publisher/subscriber) with other physical device(s). The semantic, the coding and decoding of the exchanged information (messages) follows the standard series.

IED Configuration (in the context of IEC 61850 and IEC 61400-25) - formal description (section in the SCL according to part 6) of the IEC 61850 information models linked to the IEC 61850 information exchange roles client, server, publisher, or subscriber, and the signal flow between physical IEDs.

IED Role (in the context of IEC 61850 and IEC 61400-25) - implementation of the IED Configuration: implementation of the IEC 61850 information model plus implementation of any combination of the following information exchange roles: client, server, publisher, or subscriber.

A Physical IED can host any combination of IED Roles.

Note: A gateway may host a server role to an up-link (first SCL file plus a client role and a subscriber role (both configured in a second SCL file) to the underlying Physical IEDs.

Please note that in SCL a Server configuration comprises the models including the DataSets, Report Control Blocks, GOOSE Control Blocks, SV Control Blocks, and Log Control Blocks:

From a communication point of view GOOSE and SV publisher and subscriber are NOT part of the client/server communication ... 

I hope this definition will help to reduce the disconnects in the communication of the experts.

Let me know what you think.

IEC 61850 (MMS) Messages Traced with Wireshark, Local Host, and Loopback

Have you tried to trace some IEC 61850 (MMS) messages with Wireshark? 

Usually you expect to run Client and Server on different machines to have communication going through an Ethernet Network! Yes! No!

You could easily run the two on one PC and trace the traffic using Wireshark and select the TCP loopback adapter as the interface for Wireshark to look at !!! It is simple.

The address for the server is:

The Client and Server using the IEDScout 5.2 from Omicron:

Trace:

New Merging Unit Development Kit

A new Merging Unit Development Kit based on the NovTech IoT Smart Grid Platform with Intel Cyclone V SoC Core is available for your next project.
Utility companies are adapting their infrastructures to support bidirectional energy flow to handle the emergence of DER (Distributed Energy Resources) via microgrids, photovoltaic panels, and local energy storage. As distributed energy generation increases, new intelligence of sensors, measurement and protection equipment will be required to process data at the edge. Also with the increase in variable DER, it is more challenging for substations to deliver sinusoidal and predictable steady-state voltage and current. Utility companies rely on substation metering of secondary voltage (VT) and current transformer (CT) circuits to detect performance issues and to provide vital information in real time to distributed digital protection nodes.

To satisfy this need, SystemCORP and Intel developed an IEC 61850-9-2LE compliant merging unit solution in form of a demonstrator/development platform.

This development kit consists of 6 parts:

1. NovTech IoT Octopus Smart Grid IoT Platform
2. SystemCORP VT/CT Interface board
3. SystemCORP IEC 61850-9-2LE Sample Value software stack (PIS-11) on ARM Cortex A9 core 1
4. SystemCORP IEC standard 61850 server/client software stack (PIS-10) on ARM Cortex A9 core 2 (optional)
5. Flexibilis embedded FPGA analogue front-end IP core
6. Flexibilis Ethernet PRP/HSR FPGA IP core (optional) 

Click HERE for more information.

New Application Example for EvaDeHon Package

We have posted a new example extending the use of the Evaluation, Demonstration and Hands-On (EvaDeHon) Package.

We will publish from time to time additional models and documentation for interesting applications. The objective is to help you to understand the various topologies and possibilities to use the IEC 61850 technology for the process information exchange.

One focus is on the application of the IXXAT (HMS) Smart Grid Gateways.

The example offers polling and reporting (Server on PC, Client on IXXAT WEB-PLC Gateway). The download contains the client CID for the gateway, the server CID and the JSON file for the PC. The gateway polls every 2 seconds and receives reports every 5 seconds - these intervals can be configured. Additionally it includes some specific documentation.



Click HERE for more information.

An All NEW Evaluation, Demo, Hands-On Package for IEC 61850 and IEC 61400-25

NettedAutomation GmbH (Karlsruhe, Germany) has released an All NEW Evaluation, Demo, Hands-On Package for IEC 61850 and IEC 61400-25 (EvaDeHon) for immediate download and use!
The new EvaDeHon Package comprises the roles Client, Server, Publisher, and Subscriber running on a PC, HMS (IXXAT, Beck IPC) Gateways, SystemCorp IEDs, ...
The new solutions allow to run multiple IED models (all roles) in parallel on one PC (simulating IEDs of a complete system!) ... and more. The roles and applications are configured directly by SCL files (.cid). You can build your own models and run them with all roles ... if configured.
This Package is based on our 30+ years of experience. We are really proud of offering these tools to the industry today! Sit down, enjoy and relax ...


Copyright, 2017, Michael Hüter

Click HERE to download the documentation only [pdf, 3.2 MB]
Click HERE for downloading the demo package including the documentation and license conditions.

Example: Server and Client on two PCs:


Many topologies on PCs:


... and topologies with gateways:


Click HERE to download the documentation only [pdf, 3.2 MB]
Click HERE for downloading the demo package including the documentation and license conditions.

NEW IEC 61850 Demo Package for Windows available

The main purpose of the new demonstration and evaluation package is to provide a free of charge simple and easy to use IEC 61850 Client/Subscriber Tool (running on Windows PCs) that can be used to communicate with a Server/Publisher implemented on the platforms:

Beck IPC DK151 Development Kit for SC145 (DK61)
Beck IPC com.tom / IXXAT SG-gateways (WEB-PLC)
SystemCorp Smart Grid Controllers
Windows PC

Several other uses cases are possible:

The demonstration uses a single generic SCL model (and a derived JSON file [JavaScript Object Notation] that can (beyond the main purpose) be used on the above platforms to automatically configure (tree structured graphical applications) for Clients, Server/Publisher, and Client/Subscriber roles as shown on the next slides.

The specification of additional models (.icd and .json) could be provided for a fee. 

Contact NettedAutomation if you are looking for other models, please.

Click HERE for further details and instructions to download the new package including the documentation.

Click HERE for documentation only.

The package is used in our training courses.

Distribution On-Load Tap Changer Control Using IEC 61850 Client /Server Architecture

Mr. Andrius Maneikis has successfully finished his master thesis at KTH (Stockholm, Sweden) in electrical engineering with the title:

Distribution On Load Tap Changer Control Using IEC 61850 Client /Server Architecture

Please click HERE to download his thesis [pdf, 93 pages, 17 MB].

Abstract. Distributed generation is transforming the power system grid to decentralized system where separate units like wind power generators or solar panel shall coexist and operate in tandem in order to supplement each other and make one extensive system as a whole so called smart grid. It is utmost important to have a control ability over such units not only on a field level but on a system level as well. To be able to communicate with numerous devices and maintain interoperability universal standard is a must. Therefore, one of the core standards relevant to smart grids is IEC 61850 – Power Utility Automation which comes into assistance and tackles aforementioned challenges. This project uses IEC 61850 architecture to implement client/server windows applications for on-load tap changer remote control. The proposed solution and designed applications are tested together with a real time simulator [OPAL] where simple power system is modelled to emulate the system response to control signals in a real time. In this way, the implemented applications can be tried and assessed as if performing in real environment. Consequently, a user of the client application is able to remotely control voltage on the power transformer's secondary side and manipulate the switching equipment simulated in the model.

New Work Proposal for Extending the System Configuration Language (SCL) for HMIs

IEC TC 57 has published (57/1767/NP) a proposal for extending the System Configuration Language (SCL) to provide high-level direction in terms of how best to bind the HMI graphical objects with the IEC 61850 data objects/attributes using the configuration description language defined in IEC 61850-6. It builds upon the existing System Configuration Language (SCL) defined in IEC 61850-6, in addition to possibly incorporating other non-IEC namespaces such as the W3C's Scalable Vector Graphics (SVG) namespace.

Communication networks and systems for power utility automation - Part 6xx: Configuration description language for communication in power utility automation systems related to Human Machine Interfaces (proposed IEC 61850-6xx)

This work will definitely helping to simplify the graphical representation of DataTypeTemplates in IEC 61850-6 (SCL).


A SCL DataTypeTemplate for a temperature measurement "STMP_0" could be bound to a graphical representation.

The depicted LNType has five related DataObjects. The temperature curve could be shown at an HMI as implemented in the client (HMI) interface of the VHPready demo. The VHPready demo could be downloaded. Click HERE for the access.
The client application of the demo is programmed in C#. A graphical template could be programmed ... if you need it. We could offer such a template if you are interested.

New IEC 61850 Edition 2 Demo Package Available to run on Windows

After successful usage of our old demo package provided 2010 and 2011 NettedAutomation provides a new package for Edition 2 of the IEC 61850 core parts.

The new package comes with a DLL comprising the IEC 61850 Stack, an simple API, and a powerful SCL configuration tool – all included in the DLL. The package contains executable programs that can be used right away. Additionally you will find also the course code of the applications for you to modify the applications to your own needs.

There are two different applications for the client and server:

1. C++ programmed very basic console applications:

The values can manually be changed … use the listed commands.

2. .Net/C# programmed enhanced applications (SCADA like):

The client starts the CER system by clicking the box on the upper left corner of the Client application. The Server application will run. Add values in ther server application … to be reported to the client. The use-case is quite realistic.

All client and server applications use the same DLL (provided by SystemCorp). The IEC 61850 models and communication services are configured by corresponding SCL Files. The applications provided are intended to show what IEC 61850 offers and how to use the simple API for a short time-to-marked development. The applications show how to exchange information with your applications:

 

The client and server can run on one machine (local host) or on two machines. In case of two machines you can trace the communication with, e.g., Wireshark. The addresses (MAC and IP) have to be configured differently for the two cases. The client connects automatically with the server (based on the SCL files) – no need for manual intervention. The demo shows how an embedded client can communicate with a server – without and browsing service.

The client and server can be configured to publish GOOSE and SV.

Some basic documentation comes with the package that can be downloaded. The main objective is the use of the package in our comprehensive hands-on training courses.

Click HERE to get access to the package.

Enjoy!

IEC 61400-25-4 Mappings: IEC 610870-5-104 AND/OR IEC 61850-8-1 MMS?

As an engineer I have been involved in many discussions on protocols – for the last 30 years. Sometimes it seems to be better to just ignore the arguments pro and contra a specific solution. The mapping in IEC 61850 uses ISO 9506 (MMS) as the “transport layer” of the messages required for IEC 61850 client-server applications.

In IEC 61400-25-4 (WIND TURBINES – Part 25-4: Communications for monitoring and control of wind power plants – Mapping to communication profile) there are the following five options defined:

• Web-services
• OPC XML DA
• IEC 61850-8-1 (MMS)
• IEC 60870-5-101/104
• DNP3

Depending on the company you will find one or the other solution. Most applications use MMS – not all.

Yesterday I attended a presentation of a big (well known wind turbine manufacturer). The presentation showed the use of IEC 60870-5-104 to communicate information defined in IEC 61400-25-2 (Information Models). The fourth option expressively allows to use 104. So, does this mean the market will split in five parts? Why should this happen?

The following application running on the WEB-PLC of the Beck IPC com.tom shows that it is quite easy to support one or the other solution or BOTH – at the same time.

The com.tom 5.1 provides two servers: IEC 60870-5-104 AND IEC 61850. The decision which signal to communicate by which protocol is engineered by drawing a line (on a standard web browser!) from the source information (coming from the Janitza UMG 604 power quality analyzer) to the corresponding output signal: IEC 60870-5-104 and/or IEC 61850:

The two clients on top (left QTester104, right IEDScout) can tap the same information. It is no question anymore: either ONE or the OTHER. The communication of the signals can be decided by drawing a simple line – without programming a single line in C/C++ or IEC 61131-3. Sure, the applications to be run on the com.tom family of products can also be programmed in IEC 61131-3 (CoDeSys) and C/C++ … which means: it is more work.

The WEB-PLC Object at the bottom right in the above figure can be an IEC 61400-25-2 object like: WGEN1.PhV.cVal.mag. For the platform these are all just names. I will provide more examples soon.

This solution shows that there is no need to fight for one or the other solution: just use whatever fits with your needs. DNP3 will be available soon … Modbus RTU is already used (see above).

Is Security really a big Issue in the Power Industry?

It all depends on to whom you listen. I have discussed the security issue quite often. Hope that some people have listened to me. ;-)

These days you can see a lot of intensified discussions related to the use of DNP3 and especially the application at the control center (or master) side of the communication channel. One IED talks usually to one master station – but: One master station may talk to many many IEDs. DNP3 master stations are centralized components in SCADA systems used in many industries: power, gas, oil, water, waste water, … in general automation.

One of the crucial issues is that it seems quite easy to send a specific message from a control center (master) to the substation to put the slave (RTU) into a infinite loop condition (blocking further information sharing) or a spontaneous message from a substation to the control center to put the master into infinite a loop condition (blocking further information sharing). In both cases the devices must be shut down and restarted.

Click HERE to read one of the latest discussions.

I experienced recently the following: an IEC 61850 Server sent a report message with a value derived from a DataSet member of type FCDA to a client (in a gateway for a big control system, DCS). The client (client application) stopped working properly … just did not react anymore. As a result the client did not only “refuse” to work with this server – it also stopped communicating with other servers it was connected to.

Hm, by reporting just a value from a FCDA member (LN XX FC=ST DO=Pos DA=stVal) instead from a FCD member (LN XX FC=ST DO=Pos  with three DA components: stVal, q and t) the client (client application) gives up to work … what a surprise. I was really surprised!

One solution to overcome this situation could be to require more conformance tests of clients (and servers!). That would help a lot.

BUT at the end of the day you may run into similar issues even if the client has been successfully conformance tested and certified: The clients and servers implementing IEC 61850 will support a subset of the features the standard defines. Independent of a certificate it would be more important to get a document that lists all the restrictions and specialties of a client or a server. If you know that a client crashes when you report a value from a FCDA member of a DataSet, then you could (at least) work around that problem by just configuring FCD members!

Figuring out that the use of a FCDA member causes a gateway to crash may take days of analysis and discussions … and is produces a lot of frustration before, during and after such a process.

Lesson learned: Clients, Server, Publisher and Subscriber have to come not only with a certificate but also with comprehensive documentation.

Dear Utility user: ask for sufficient documentation! We could help you to analyze the documentation to figure out …

Register of tested IEC 61850 devices

KEMA has recently published an updated Test Register (version 2011-11-28) for

• IEC 61850 Client Systems [8 clients successfully test]
• IEC 61850 Server Devices [total: 212 – 2011:42 / 2010:21 / 2009:34 /before:115]
• IEC 61850 Ethernet Switches [23]
• IEC 61850 Sampled Value Publishers (Merging Units) [2]

Click HERE for the complete list [pdf]

Click HERE for the IEC 61850 certificates; if you don’t have an UCAIUG login account you can apply for a free guest account.