Free ASN.1 Browser for IEC 61850-8-3 ASN.1 Module from RTI2 PoC

If you want to browse easily the ASN.1 message schema for the new project IEC 61850-8-3 (DSM) underway, check out this free browser: 

https://www.nettedautomation.com/editor

A preliminary asn.1 module for IEC 61850-8-3 (from PoC of RTI2) is available for download:

This is how it looks like:

and ...

The schema is very simple compared to MMS for IEC 61850-8-1.

Let us know if you have any question.

Extended Video on IEC 61850-8-3 Available - Example Messages

 An extended version of the video on  

IEC 61850-8-3
Communication networks and systems for power utility automation –
Specific Communication Service Mapping (SCSM) –
Mapping to Direct Message Specification (DMS), JSON Encoding Rules, and WebSockets 

is available. I have added some five minutes ... total time is 23 minutes.

I have added mainly two examples of services for IEC 61850-8-1 (MMS) and IEC 61850-8-3 (DMS):

The figure above shows how a client can get the list of logical nodes from the server with MMS ... and with DMS:

Details can be watched in the video ... enjoy.

IEC 61850 Series for Any Automation Domain using Electric Power (two Examples)

The standard series IEC 61850 is applicable for simple applications and huge systems. The standard is not restricted to a specific domain. Like electric power is everywhere. So could IEC 61850 be everywhere.

I have discussed this briefly in the context of a LinkedIn post.

Now it's time to discuss briefly two simple applications ... just looking at the two models ... without further explanations.

The German FNN Steuerbox

The Steuerbox is mainly providing schedules for the interface between the grid and the power user:

This model is defined for a special use-case: Steuern (remote control). No need for an engineering tool ... it is just a fixed model ...

The Netherlands RTI (Real-Time Interface) for power generation (> 1 MW)

... this is a fixed model with some details:

The RTI models and services are currently using IEC 61850-8-1 (MMS) communication (RTI 1). The RTI 2 will finally use the IEC 61850-8-3 (DMS) once it is specified. A Task Force has started to specify the new standard in May 2026.

The fixed models allow for a high level of interoperability. The central systems (representing the IEC 61850 clients) can communicate with and IED following these specifications. In the case of the FNN Steuerbox it has been proven that the client application could talk to all steuerboxes in the field without paying attention to which vendors device it is talking to.

REAL INTEROPPERABILITY !!

Why is there an Need for an Additional Service Mapping in IEC 61850 (IEC 61850-8-3)?

The two service mappings for IEC 61850 are IEC 61850-8-1 (MMS) and IEC 61850-8-2 (MMS/XML). The mapping IEC 61850-8-1 is in operation from the first days when IEC 61850 was implemented and used ... all over ... in millions of devices and thousands of systems. Ok ... perfect.

Why is there an need for an additional service mapping in IEC 61850 (IEC 61850-8-3)? 

Simply because of the complex and tricky mapping to MMS (Manufacturing Message Specification, ISO 9506). 

IEC 61850-8-3
Communication networks and systems for power utility automation –
Specific Communication Service Mapping (SCSM) –
Mapping to Direct Message Specification (DMS), JSON Encoding Rules, and WebSockets 

In order to explain details of the new approach to be used for the new work item proposal IEC 61850-8-3 I have produced a 17 minute video (updated version 2026-06-04, 23 minutes).

It is likely that this will become a major shift in the use of IEC 61850.

Enjoy!

What is a model in the context of IEC 61850?

A model is a model is a model ... huch.

The question is: What does a model provide? In short: It provides an external visible PATH to an actual value of something, e.g., a voltage or temperature. A model of my home is not something where I can life in! It shows where the rooms, stairs, ... are ... 

The leaves (or end points) of the model in the IEC 61850 TREE (of a model) are NOT where the actual value reside! Basic Data Attribute (BDA) in IEC 61850 are the leaves of the trees. 

Just a minor comment on the BDA: I found this: "This is the lowest level, where the actual value resides." IEC 61850 defines models that hide the storage location of an actual value. The BDA is a PATH to the actual value. The value resides "behind" that model. The BDA holds an externally non-visible or non-accessible reference to the actual measurement value or status.

When reading the current value of the phase A of the MODEL MMXU1 you send a read request with the PATH: "LD/MMXU1.A.phsA.cVal.mag.f". This PATH is translated into the direct or indirect storage location of a specific IED. How that is implemented, depends on the architecture of the interface and application software. It may even be mapped to an underlying fieldbus specific address (e.g., Modbus coil 2828). When the read request is received, the IED uses Modbus to read the actual value from coil 2828. In this case the actual value resides beyond the IED with its MODEL. The IED needs a non-visible specific mapping from the PATH to the Modbus register.

The models in IEC 61850 describe a virtual world in the following sense:

If it's there and you can see it         It's REAL
If it's there and you can't see it         It's TRANSPARENT
If it's not there and you can see it It's VIRTUAL
If it's not there and you can't see it It's GONE
Roy Wills

I hope that helps to understand the Models in IEC 61850.

This virtualization has an impact on how an IEC 61850 Stack (is not defined in IEC 61850 what a stack is) you purchase maps the leaves of the model to the location of your actual values.

Mapping of IEC 61850 Models and Information Exchange Services to JSON, HTTP, and MQTT

After I published two sketch videos on IEC 61850 information exchange services and the mapping to MMS, I discuss simple interface options for the last meters between a device that implements the role of IEC 61850 server, GOOSE publisher, and GOOSE subscriber, and the underlying huge world of a myriad of other controllers.

The standard series IEC 61850 and IEC 61400-25 (Wind Power Plants) provide a comprehensive set of standardized information or device models (Logical Nodes, Data Objects, Data Attributes, ...) for a wide range of use cases in the electric power domain (protection, automation, supervision, monitoring, control, ...) and for general applications beyond the electrical world. By the way, tell me where electricity is not a crucial resource in factories, buildings, petrochemical plants, homes, ... it is all over ... required 24/7. These series also comprise information exchange mechanisms like Reporting, Logging, Control, GOOSE, Sampled Values, ... mapped mainly to MMS in IEC 61850-8-1 ... other mappings like mappings to XML and XMPP in IEC 61850-8-2 or MMS, Web Services, IEC 60870-5-104, DNP3, OPC XML DA, ... in IEC 61400-25-4. The most crucial part of IEC 61850 and IEC 61400-25 is the System Configuration Language (SCL, IEC 61850-6).

Many applications use only a very small set of models (a few measurements, control signals, and status signals), a small set of information exchange services, and a simple subset of SCL. Critic comes from experts of various domains: Why do I need to have a complex and comprehensive IEC 61850 stack to implement a simple subset of these standard series? Is there another solution? The wind power plant people developing and maintaining IEC 61400-25 believing that five (5) mappings would help in this regard - really? So, the discussion is still going on. 

A very simple solution has been implemented in various projects: Notation of a subset of the information models and the payload of the messages in JSON. The exchange services could be mapped to various transport mechanisms like MQTT or HTTP ...

This approach would KEEP the models as they are - NO mapping required, just another notation (JSON instead of MMS named Variables etc.). Even SCL could be used.

Whenever there is a need to communicate from a device that plays the role of an IEC 61850 server, GOOSE publisher, GOOSE subscriber, to an underlying (likely simple) device (for the last meters) the decision usually is to use some other communication stacks from a set of 100+ solutions like CAN, Modbus, many fieldbusses, EEBUS, Sunspec, ... and private digital solutions, or even wires only ...

Any of these need to MAP from one standard to another standard, e.g., map MyIED/myMMXU1.Hz.mag.f (measurement of frequency) to register 2246 in one application and to 9817 in another ... hm, that is feasible BUT means a lot of configuration and documentation ... outside the definitions and tools provided by IEC 61850. 

A more reasonable approach would be to use JSON, e.g., to define a DataSet (semantically equivalent to IEC 61850 and MMS) and the report message payload as shown in the figure below:

Please check a couple of blog posts published a few years ago for more details and discussions:

https://blog.nettedautomation.com/2019/07/iec-61850-8-2-versus-iec-61850-8-1.html

https://blog.nettedautomation.com/search?q=mqtt

https://blog.nettedautomation.com/2019/10/iec-61850-for-monitoring-data-private.html

Unfortunately the Beck IPC com.tom Web PLCs with support of IEC 61850, ... disappeared ...

Please let me know your opinion ...

IEC Just Published IEC 61850-80-5 Guideline for Mapping Information Between IEC 61850 and IEC 61158-6 (Modbus)

IEC TC 57 Just Published IEC 61850-80 -5 Guideline for Mapping Information Between IEC 61850 and IEC 61158-6 (Modbus)

(57/2250/CD, 166 pages) - closing date for comments: 2020-09-11

Excerpt from the introduction:

"This technical specification provides a guideline to exchanging information between IEC 61850 and IEC 61185-6 (Modbus TCP). Nowadays, industrial field such as distributed energy resource (wind and solar energy, etc.) and condition monitoring, has been exchanging the information from Modbus to IEC 61850 for an effective operation. Although many manufacturers already implemented the Modbus to IEC 61850 conversion device or system, these devices do not guarantee interoperability. Therefore, it requires the consistent and unified information exchange scheme between IEC 61850 and IEC 61158-6 (Modbus).
Modbus over serial line (Modbus RTU) is not part of IEC 61185-6, but is also considered in this technical specification."

IXXAT Smart Grid Gateway With NEW Possibilities

IXXAT (HMS) has offered their Smart Grid Gateways for some time. Click HERE for some blog posts that give you a good overview of the possibilities so far (HERE for HMS or HERE for Beck).
The other day IXXAT has published an extended range of possibilities to share information between many different communication solutions in almost ALL automation applications:

SG-gateway IO
SG-gateway M-Bus Master
SG-gateway EtherNet/IP
SG-gateway PROFIBUS
SG-gateway PROFINET

New:

SG-gateway Media Converter
SG-gateway Switch

All types support as well:

Modbus-RTU master/slave via RS232/485
Modbus-TCP master/slave
DHCP server, SNTP, Network trace (pcap), SNMPv2c
OPC-UA server
MQTT
Codesys network variables

Optional:

IEC 60870-5-104 client/server with redundancy (Norwegian User Convention)
IEC 60871-5-101 master/slave
IEC 61850 client/server (both roles and GOOSE pub/sub are supported simultaneous)
IEC 61850 GOOSE publisher/subscriber
Outstation DNP3
Hardware versions with 3G or 4G modem

Click HERE to visit the IXXAT website for an overview (German).
Click HERE to download a new 12 page pdf bochure (German).

IEC 61850 For Monitoring Data - Private or Standard?

One of the most crucial issues in the management of energy systems is: HOW TO share or exchange useful information generated by a myriad of sensors and applications needed by hundreds of applications?

Lets assume that lakes of information are generated every second. Usually this information is stored in silos of vendors specific solutions and communicated using one or more vendor specific communication solutions ... as shown in the following sketch drawn by our grandson Jan Oliver:



The expectations to apply IEC 61850 are high! BUT quite often vendors argue, that it is easier to use their private solutions - faster and saves time and costs! This may be true for the first phase of a project - but in the long run and in the view of the life time cost it may be completely opposite.

Three experts from Vattenfall DSO (Sweden; Vincent GLINIEWICZ, David EROL Anders JOHNSSON) have reported at the CIRED conference 2019-06 in Madrid (Spain) from an implementation of a pilot project using IEC 61850 and CIM  with the title:

LEVERAGING INDUSTRY STANDARDS TO BUILD AN ARCHITECTURE FOR ASSET MANAGEMENT AND PREDICTIVE MAINTENANCE

Excerpt from the paper:

"... However the data unfortunately currently often remain unused and unshared outside of the substation or specific silos for various reasons, some technical (e.g. cyber security, system incompatibility), some and organizational (e.g. vendor lock-in, siloed applications and organizations).
Additionally, with an increasing number of use cases requiring access to information, there is a growing number of information flows needed not only between data sources and central level applications but also between these central level applications. Without an IT architecture that allows reuse of information flows, there are legitimate concerns that the opportunities that digitalization promises might be delayed and costly or even worse, not be achievable.
As a result, Vattenfall Eldistribution sees a standard based integration approach as a cost-effective approach that seems to offer in the long run low integration costs and more importantly a greater flexibility, going from supplier specific integrations to a more generic approach. ...

We would also like to highlight some of the deviations from the standards that were observed during this pilot:

The pilot made use of a REST API towards the real time data historian (RTDH in fig. 2), although there was no mention of REST in the 61968-100 standard. One could however expect, given the increasing popularity and use of RESTful services in most industries, that the standard will soon follow and that the mention will be added in a further edition on the standard.
The gateway used in the pilot was a prototype base on a technical report (IEC TR 61850-90-2) [Using IEC 61850 for communication between substations and control centres] which is not yet a standard. This might explain why there doesn’t seem yet to be a complete and robust 61850-90-2 compliant product on offer in the market. Another alternative considered for the pilot gateway was the use of IEC 61850/MMS towards the substation and the use of web services (either RESTful+ JSON or SOAP) to communicate northbound instead of the IEC 61850/MMS used in the pilot. SOA has indeed a robust and well developed architecture for distributed computing, and this should be leveraged. There however did not seem to be any products available on the market. This alternative will be explored in a coming pilot. ..."

The paper concludes:

"Although the pilot was made for a primary substation, the widespread use of the IEC 61850 standards series make the results of this pilot not only applicable for primary substations, but potentially also secondary substations and microgrid.
Following the successful pilot, the next step is to look at how to fully implement and verify the concepts in a real substation and to secure production grade components where prototypes have been used as well as test the architecture through other smart grid use cases."

Click HERE for the full paper.

I have run an UCA/IEC 61850 pilot project with Anders Johnsson some 20 years (!) ago:

Two reports out of this pilot project and other discussions have been published in 2002:

Wind Power Communication
Verification report and recommendation

Click HERE for the Report.

Wind Power Communication - Design & Implementation 
of Test Environment for IEC61850/UCA2

Click HERE for the Report.

Enjoy the reports.

By the way: It took some 20 years to understand that the mapping of IEC 61850 models and communication protocols to MMS (ISO 9506) should be extended by a much easier and simpler mapping to JSON and, e.g., MQTT or http ...

It is not too late for such an additional standardized mapping ... e.g., as IEC 61850-8-3.

It may take another 10 years before this becomes true! Hope it will happen a bit earlier!

Further reading on the subject see discussion of IEC 61850-8-1 versus 8-2 (by 2024-02-25: 4074 visits of the post since July 2019).

Other people have similar ideas and published the following paper:

International Electronical Committee (IEC) 61850
Mapping with Constrained Application Protocol
(CoAP) in Smart Grids Based European
Telecommunications Standard Institute
Machine-to-Machine (M2M) Environment

Beck IPC offers MQTT@CHIP in addition to IEC 61850 and other protocols

Beck IPC (Wetzlar, Germany, a subsidary of HMS) is known for their solutions on a single CHIP offering support for IEC 60870-5-104, IEC 61850, Modbus, CANBus, Profibus, Profinet, OPC UA, ... now offers MQTT@CHIP as an additional solution.



The MQTT can be configured on the WEB PLC like it is implemented for other protocols:



In the above example I have mapped a signal from an IEC 61850 Server the signal MMXU1.TotW.instMag.f to a MQTT message. This way you can tag the signal as a JSON Object!!

JSON Objekte:
{ „MMXU01.TotW.instMag.f“:  2325, „MMXU01.Hz.instMag.f“:  49.98 }

Message specification:



This way you can send MQTT messages with values from any other protocol or from the IEC 61850 client or server model. This way you can even map to/from GOOSE messages.

I have used the solution running on the IXXAT Smart Grid Gateway. The WEB PLC version 19.2 is required to run MQTT on the gateway.

Very well done!

Many IEC 61850 Projects Under Progress

37 new parts and parts under revision are under progress as listed in the following table:

As you can see here: IEC 61850 is a bit more than another protocol.

Other parts are published already (some of them are under revision - see above):
https://webstore.iec.ch/publication/6028



Unfortunately many "grey-hair experts" with a lot of experience regarding IEC 61850 have been retired and a lot of experience has been wasted ... politics cares more about wasting food than wasting "experience" good for human survival! It's really a pity when we take into account that the comprehensiveness and complexity of IEC 61850 is growing so fast ...

IEC 61850 Products at CIRED June 3-6, 2019 - Madrid (Spain)

3-6 June 2019, Madrid, Spain

SystemCORP will participate together with Advantech in the CIRED Exhibition in Madrid, Spain. It promotes the SystemCORP ADH Software, a flexible and complete data communication and process automation package, fully integrated in Advantech data gateways.

Based on a distributed real-time database and application management system almost any SCADA communication protocol can now be used as client or server on Advantech modules. SystemCORP offers most commonly used communication protocols such as IEC 61850, IEC 60870-5, DNP3, Modbus and JSON/MQTT as part of a standard communication library for SCADA and Cloud integration. An integrated IEC 61131 compliant programmable logic controller (PLC) extends the capability of the ADH as a true virtual SMART Grid device ready to be installed in distribution automation and smart gird projects.

For application configuration, the eNode Designer, IEC 61850 ICD Designer and IED Configurator tools simplify system engineering and result in reduction of project costs and implementation time. No special tools are required for establishing secure communication with cloud applications.

To know more visit our booth no H1/G2 at the IFEMA North Convention Centre. Address: IFEMA, Av. Partenón, Nº 5, 28042 Madrid, Spain. Entrance is free.

For any more information please check the event website: http://www.cired2019.org/

IXXAT (HMS) Offers New POWERFUL Smart Grid Gateways for IEC 61850, IEC 60870-5, Profibus and more

Under the IXXAT brand, HMS delivers connectivity solutions for embedded control, energy, safety and automotive testing.
The new and very powerful IIoT gateways from HMS allow industrial equipment to communicate with power grids based on IEC 60870-5-104 and IEC 61850. In addition they also include Modbus TCP Client/Server and Modbus RTU Master/Slave


IXXAT SG-gateways...

• enable easy remote control and management of electrical systems
• allow to log and display application data and energy consumption
• provide IEC 61850 client/server and IEC 60870-5-104 server support
• have in-built Modbus TCP Client/Server and Modbus RTU Master/Slave interfaces
• provide connectivity for CAN Bus, I/O, M-Bus, PROFIBUS, PROFINET and EtherNet/IP based devices

Click HERE for more details in English
Hier klicken für Details in Deutsch

IEC-61850-Hands-On-Training in Deutsch in Karlsruhe (Dezember 2017 und Mai 2018)

NettedAutomation GmbH bietet zwei IEC-61850 Hands-On-Trainingskurse zu unschlagbar günstigen Preisen in Deutsch in Karlsruhe an:

05.-08. Dezember 2017 
14.-17. Mai 2018
04.-07. Dezember 2018

NEU: Zusätzlicher Schwerpunkt wird das Thema "Sicherheitsanforderungen" (BDEW White Paper, ...) für die Energieversorgung sein.
Die drei (3) Blöcke (1 Tag + 2 Tage + 1 Tag) können einzeln oder in Kombination gebucht werden. Sie entscheiden selbst, ob Sie nur einen Tag von Ihrem Arbeitsplatz fern bleiben möchten oder zwei, drei oder vier. Je nachdem, wieviel Zeit Sie investieren wollen oder können und welchen Bedarf Sie haben.

Lernen Sie, wie über 4.300 Teilnehmer vor Ihnen, was IEC 61850 und andere Normen wie IEC 60870-5-10x oder IEC 62351 (Security) bedeuten. Gewinnen Sie einen Einblick in relevante Realisierungen wie die FNN-Steuerbox oder VHPready, die auf IEC 61850 aufbauen. Verstehen Sie, wie Feldbusse (Profibus, Profinet, Modbus, ...) über lostengünstige Gateways in die Anlagen eingebunden werden können.

Im Hands-On-Training lernen Sie die wesentlichen Konzepte der Normenreihe praktisch kennen. Die umfangreiche Trainings-Software dürfen Sie behalten und weiterhin nutzen!


Copyright, 2017-07, Michael Hüter

Der Kurs ist für alle geeignet, die mehr über IEC 61850 erfahren wollen.

HIER klicken, um zur Beschreibung und den Anmeldeunterlagen zu gelangen [pdf, 430 KB].

Beachten Sie auch, dass die meisten Seminare als Inhouse-Kurse stattfinden! Falls Sie Interesse an einem Inhouse-Kurs (in deutsch, englisch, italienisch oder schwedisch) haben sollten kontaktieren Sie uns bitte!

IEC TC 57 Published Several New IEC 61850 Documents

IEC TC 57 has published several new documents of the standard series IEC 61850 (Communication networks and systems for power utility automation):

57/1832/CD
IEC 61850-2: Glossary [57 pages]
Comments are required by 2017-04-07

57/1829/CD
IEC 61850-80-5: Guideline for mapping information between IEC 61850 and IEC 61158-6 (Modbus) [45 pages]
Comments are required by 2017-04-07

57/1828/RVC
IEC 61850-7-2 A1 Ed.2: Abstract communication service interface (ACSI)
The CDV has been accepted.

IEC 61850 in North America

These days we hear some noise from a few US people telling you that the interest in IEC 61850 in North America is still low. Ok. What does this mean? Almost nothing.
IEC 61850 is used in many applications in North America - many are not publicly reported. Why should a customer that is happy with the solution talk about it in the public?
When you check the list of open positions in the US, you can see that there is new interest in this technology - in addition to traditional communication solutions like Modbus and DNP3:
Check for example a open position at GOOGLE (Data Center Control Systems Engineer, Mountain View, CA):

"Minimum qualifications:

• BS degree or equivalent practical experience.
• 10 years of experience in the design and operation of mission critical facilities, including programming and design experience.
• Experience with facility power and cooling related infrastructure systems for data centers or equivalent critical infrastructure, including PLCs, SCADA systems, historians, industrial automation and controls systems design. Experience with bussed I/O including IEC 61850 and Modbus.
• Experience in the compliance requirements of pertinent codes, regulations, and standards."

Click HERE for the complete GOOGLE Job description.

Another 20+ open positions in the US can be found on www.simplyhired.com. Click HERE.

In Germany you find 10+ open job descriptions. Click HERE.

The number of visitors of this blog from the US is also growing and already high: 300+ per day (average during the last months).

More to come.

Pt 100 Temperature Relay with IEC 61850 GOOSE

Ziehl (Schwäbisch Hall, Germany) has integrated IEC 61850 GOOSE into their Pt 100 temperature relay for up to 12 sensors with electric 10 MBit/s Ethernet interface.

The TR1200IP can be used wherever multiple Pt 100 sensors (up to 12) need to be evaluated simultaneously:
- Motors or generators,
- also with simultaneous monitoring of bearings or, e.g., exhaust temperatures
- Transformers, also with additional core-temperature monitoring
- Machines and plants
Type TR1200IP temperature relays register the temperature of up to 12 sensors simultaneously and provide the values to the electric 10 MBit/s Ethernet interface.
2 IP protocols are supported, so the registered temperatures can be subsequently evaluated by connected devices that are linked with the TR1200IP via an Ethernet network. In motors, that could be a motor contactor, in transformers a transformer contactor with integrated overload function and thermal monitoring.
An alarm relay reports devices and sensor errors. Sensor breaks or sensor short-circuits are also transmitted via the protocol to the connected evaluation unit.

Click HERE for a general overview.
Click HERE for GOOSE configuration.
Click HERE for the manual.

The GOOSE messages could be received by an HMS SG Gateway either as a client or a server. The SG Gateway could convert the received GOOSE messages into an IEC 61850 server to provide Reporting and Logging and convert to IEC 60870-5-104 or DNP3.

New Gateway for EtherNet/IP from and to IEC 61850, DNP3, IEC 60870-5-104, ...

The Anybus® SG-gateway is designed to specifically target Demand Response (networking of industrial electric loads) and Virtual Power Plants (networking of energy resources like biogas plants or combined heat and power units) applications.
REMOTE TERMINAL UNIT FOR SMART GRID APPLICATIONS
The SG-gateway with EtherNet/IP implements a real-time EtherNet/IP adapter interface with an integrated 2-port switch, allowing seamless network integration regardless of network topology (line, star, bus).



















Click HERE for details.

Amendment to Power Quality Meter Goes IEC 61850 and IEC 60870-5-104

The recent post "Power Quality Meter Goes IEC 61850 and IEC 60870-5-104" needs some explanation to understand what the Gateway could do.
In the case described in the post, we use one gateway for one power quality meter. Of course this is only one example. A single gateway can acquire signals from many power quality meters from different brands and via different protocols: Modbus I/O, Modbus/TCP, Profibus, ProfiNet, Ethernet/IP, and IEC 61850.
The gateway acts as well as a data concentrator, data manager, or proxy gateway. You may use it for any other signals - outside the power quality application. It may be connected to a substation LAN and tap GOOSE messages flying around.
The nice thing is: It can transform between (almost) ANY protocol without the need that IEC 61850 or IEC 60870-5-10x is integrated directly into the end device like a power quality meter.
In the future we will see more devices that have IEC 61850 integrated into their devices (by using a special piece of hardware or integrated onto the main controller of the device).

IEC 61850: Gateway for Cloud Computing and Fog Computing

Cloud computing and Fog Computing is in principle supported by a single gateway offered by HMS:

• Bridges any signal from the process level directly to your own or third party cloud.
• Maps any signal from Modbus, Profibus, ProfiNet, Ethernet/IP, IEC 61850, IEC 61400-25, IEC 60870-5-104 ... to Modbus, Profibus, ProfiNet, Ethernet/IP, IEC 61850, IEC 61400-25, IEC 60870-5-104 ...
• Provides many logic functions AND, OR, Timer, Counter, ... to build applications.
• Has digital Input and Output pins.
• Reads M-Bus.
• Supports Client, Server, Client/Server, Client/GOOSE-Subscription (with or more Server/GOOSE-Publishers), and Sever/GOOSE-Subscription
• What else do you need for simple applications?

Click HERE for more information.