IEC 61850 – How to use the Standard in Substations?

The German mirror committee of IEC TC 57 (DKE K 952) is quite active in supporting IEC 61850 and helping the utility industry to discuss the application of IEC 61850 and provide feedback to the international standardization. Congratulation to all experts that have contributed to that work for many years! Well done!
The final documents of the modeling and engineering group provide a great inside view into the many use cases of IEC 61850 in protection and substation automation. The crucial results are written in English, too. Four out of seven topics are published in English:

1. Überblick [DE] / Overview [EN]
2. Engineeringprozess [DE] / Engineering Process [EN]
3. Engineeringwerkzeuge [DE]
4. Modellierungsrichtlinie [DE] / Modeling Guide [EN]
5. Mustermodellierung [DE]
6. Applikationsbeschreibungen [DE] / Application Description [EN]
7. Weitere Applikationen [DE]

Click HERE to access the above documents. The pdf documents are free to download.
Enjoy.

C# Server and Client Application Source Code for IEC 61850 DLL

NettedAutomation has updated the C# Client AND SERVER application (GUI) of the IEC 61850 Evaluation Kit (DLL). You can use the SystemCorp DLL (dated back to 2010) from the evaluation package downloaded from the above NettedAutomation link. If you have installed the IEC 61850 DLL before March 2012 it will not run anymore on your PC (it runs for 6 just months). In that case you can install it on a different machine – maybe you have a new PC anyway since you tested the DLL.

The C# application source code and executable code as well as documentation and the appropriate SCL files for the client and the server are provided via the link below.

The new Server GUI supports manipulating values in the server application, e.g., the temperature and setting for temperature alarms at the server:

The client application allows to see results from polling and Reports:

You may just use another browser (e.g., the Omicron IEDScout) to connect to the server and retrieve the model and the values:

Download the complete C# application examples for the IEC 61850 DLL [zipped file, 1 MB].

Details on downloading the DLL evaluation package could be found here.

Work on IEC 61850-90-11 started -- Logics

It was agreed internationally to develop IEC TR 61850-90-11: Communication networks
and systems for power utility automation – Part 90-11: Methodologies for modelling of logics for IEC 61850 based applications.

The scope could be quite narrow, taking into account simple logics for input and output signal … but it could cover also the way how to program complex distributed applications. The standards like IEC 61131-3 or IEC 61499 may be taken into account.

Some discussion on the use of IEC 61499 …

IEC TR 61850-7-510 ed1.0 has been published

The new part IEC 61850-7-510 has been officially published:

Communication networks and systems for power utility automation -
Part 7-510:
Basic communication structure - Hydroelectric power plants - Modelling concepts and guidelines

Download the Preview of IEC 61850-7-510

IEC/TR 61850-7-510:2012 provides explanations on how to use the Logical Nodes defined in IEC 61850-7-410 as well as other documents in the IEC 61850 series to model complex control functions in power plants, including variable speed pumped storage power plants. This publication is to be used in conjunction with IEC 61850-7-410 which introduced the general modelling concepts of IEC 61850 to hydroelectric power plants.

This document lays a ground for control devices like PLCs to implement the information interface. One simple implementation could be to integrate an IEC 61850 gateway into a PLC. The gateway could, for example, be implemented with an powerful embedded controller.

The controller would implement the information model and the services like GOOSE for operational status, Setting limits or Reporting of status or measured values:

A gateway could be easily build with available embedded controllers that provide an easy API for IEC 61850 clients, servers, publishers and subscribers.

IEC 61850 Gateway And Programmable IED

These days many vendors that have to develop devices for the electric power delivery are interested in applying a third-party Gateway that map the commonly used protocols like DNP3, Modbus, IEC 60870-5-10x, or CAN bus to an IEC 61850 Server. There are ready-to-go gateway available.

Usually the gateways map between one other protocol and an IEC 61850 Server – if you want to have two or three protocols to be mapped to IEC 61850 you likely have to pay a license for each protocol. The gateways usually are just gateways and do not allow any other application running on the same platform providing application data through IEC 61850 models and services.

The Gateway provided by SystemCorp is quite different as the following figure depicts:

In addition to the Gateway functionality any other application programmed on the very same platform can provide data exchange with the IEC 61850 server through the simple API of the IEC 61850 stack. Various embedded controllers like the Beck IPC Chip provide these possibilities.

This allows with one IEC 61850 license to implement gateway functionalities AND let any other application functionality “speak” IEC 61850.

Access the description of the IEC 61850 Protocol Stack Online API Manual.

Easy, Affordable and Fast Integration of IEC 61850 in Small Devices

High financial and time expenditures for the implementation of IEC 61850 in control systems and other devices prevented so far a broad market penetration of the standard in the lower voltage levels and in distributed power generation. A reasonable and cost effective solution is now available with the Beck IPC@CHIP. The development of IEC 61850 conformant interfaces in power delivery systems – particularly renewable and decentralized power producers and consumers – can now be realized within very short time to market.

The stack and API used on many platforms has been developed by SystemCorp (Bentley, Western Australia), e.g., on the Beck IPC Chip.

A new paper has been written about the benefits of using ready-to-go solutions. The paper discusses embedded controller with IEC 61850 stack and API, DLL and other libraries with IEC 61850 stack and API, … You will find also a brief discussion of the information models for PV inverters (IEC 61850-90-7).

Download the discussion about benefits using ready-to-go solutions with IEC 61850 and PV Inverter models [pdf, 2.3 MB, 18 pages]

MMS (ISO 9506) Introduction – Why to focus on the API?

Jan Tore Sørensen and Martin Gilje Jaatun (SINTEF ICT, Trondheim, Norway) have published a nice introduction to the basic architecture and definitions of MMS in a 46 page document – easy to read and understand.

This documents demonstrates that MMS is not complex. IEC 61850-8-1 (and IEC 61850-9-2) use MMS for specifying the message exchange between IEC 61850 servers (publishers) and clients (subscribers).

Implementing IEC 61850 compliant systems comprising SCL tools, servers, clients, publishers, and subscribers means to implement:

1. Upper layers on top of TCP/IP (or on Ethertype for publisher/subscriber)
2. Protocol machine (MMS, GOOSE and SV)
3. Encoding/Decoding ASN.1 BER messages
4. ACSI services (LD, LN, Control Blocks (reporting, Logging, service tracking, GOOSE, and SV), DataSets, Control, LOG –> mapped to protocols, mainly MMS)
5. Object model (dictionary in IED and behavior according to IEC 61850-7-4)
6. API (application program interface) for server, client, publisher, and subscriber
7. IED configuration using SCL file
8. SCL tool for system engineering and IED configuration

A ballpark estimate of the efforts needed to implement a reasonable subset of IEC 61850 (if one develops the software from scratch) is in the range of some 10 man-years. Only a small part of efforts (likely less than 10 per cent) deals with MMS and the underlying protocols required by MMS.

A different solution for the client-server messaging, e.g., by using a webservice, would have a minor impact on the total efforts. From a application point of view an efficient API should be in the focus when implementing of using IEC 61850!

Click HERE for the complete paper on MMS [pdf, 446 KB]

Note that IEC 61850 is much more than a protocol – and much more than MMS. MMS is just an international standard like Ethernet or TCP/IP.

New Embedded Modules from TQ with IEC 61850 and IEC 61400-25 using ARM Architectures and Linux

Two New Embedded Modules developed by TQ with IEC 61850 und IEC 61400-25 (using ARM Architectures, Linux and the very simple and powerful SystemCorp IEC61850 API) are available:

ARM9 Modul with i.MX28 from Freescale
Click HERE for more details.

ARM11 Modul with i.MX35 from Freescale
Click HERE for more details.

TQ is conducting a one day introduction into the standards IEC 61850 and IEC 61400-25 and demonstrates how to build applications for IEC 61850 based on the above controllers.

Date: 2011-12-14 (Wednesday)

Location:
TQ-Systems GmbH
Mühlstraße 2
82229 Seefeld
Germany (near Munich)

Click HERE for more details on the seminar.

Click HERE for the Program (Presentation Language: German)

If you are interested in a presentation in English, please contact TQ.

What Do You Need to Know to Retrieve Process Values from an IEC 61850 Compliant Device?

The answer is quite simple: Almost nothing! It depends – of course – on the availability of software for IEC 61850. Let’s assume that we have a device that plays the role of an IEC 61850 server (providing a data model and services to access the values referenced by the model).

What you need is a software that plays the IEC 61850 client role. There are several options:

• Purchase source code and build your own client and API (Application Program Interface)
• Purchase source code and build your own client with an API already incorporated
• Purchase a client DLL with a simple and easy to use API
• Purchase a ready to go Browser with a graphical interface

If you want to just retrieve some data values from a IEC 61850 compliant device, you JUST need to know the IP address of the device and a free Browser evaluation software. Download the well known OMICRON IEDScout; the IEDScout runs in Demo mode for free (restricted services!):

Click HERE for more information and download link for the IEDScout.

Install the IEDScout, go to Configure (right), select New Server just by entering the below IP address and assign a server name:

SEL-421: 99.14.76.126

Use default values … click on OK … OK … done. Go to Discover … select the server you just configured … and start communication with the corresponding device. Retrieving the information model may take several minutes! The IEDScout retrieves the model … some thousand messages exchanged … you may trace the messages using the Wireshark analyzer. Start the Wireshark first and then start IEDScout and connect to any IED.

Once you have the model retrieved, open the model tree and read a value in the tree or see DataSets and Control Blocks.

How long did it take to access data values from an IEC conformant device? 30 minutes … may be 45. Maybe it took another 30 minutes to make it run on your Windows system ;-)

How many of the following standards have you read to get access to one of the above IEDs? IEC 61850-7-x, IEC 61850-8-1, ISO 9506-1/-2, ISO 8824, ISO 8825, IEEE 802.1Q, IETF RFC 792, … 1.000, 2.000, or 5.000 pages?

To use a (graphical) interface at a client there was NO NEED to read any of the above standards! What you may need is basic information about IEC 61850.

Of course, this IEDScout is not an API to be used by client applications. You cannot store the retrieved data values … ok, the full version allows to store the model as an SCL document … and store subscribed GOOSE messages.

Another easy to use API is the SystemCorp API used to build a very simple client HMI – a .Net/C# application:

http://blog.iec61850.com/2011/02/updated-c-client-application-for-iec.html

The API (in form of a DLL) can be used to build your own client application in Windows (DLL) or in Linux (library).

Even the use of the DLL for the client and the use of the C# build HMI does not require to understand all details of the protocol.

Lesson 1 learned: To use the comprehensive protocols like IEC 61850, IEC 60870-5-105, IEC 60870-6 TASE.2, or DNP3 … a simple and easy to use API is needed!! Reading thousands of pages of standards is NOT what is required!!

Lesson 2 learned: The efforts to use any of the above protocols is more or less the same! Of course there is a configuration language SCL in IEC 61850 that requires a little bit more information/education …

Implementing the protocols requires a lot of time and efforts … there may be some difference depending on the protocol.

Be happy by just applying simple and easy to use APIs for clients and servers. Get your first data values communicated within hours – not months …

Getting Started with SystemCorp’s IEC 61850 API on Embedded Linux in Hours

Yesterday (July 21, 2011) I conducted a one day seminar and hands-on training for a German vendor that offers embedded controllers with embedded Linux. SystemCorp ported their IEC 61850 software including the easy to use API (Application Program Interface) onto the embedded Linux controller and provided a simple example for digital inputs and outputs. They shipped the controller with an IEC 61850 example to me to run some tests and demonstrate the solution to the vendor of the controller (in Northern Germany).

During the morning I presented IEC 61850 basics in modeling, engineering, configuration, and communication. My intention was: Help the programmers to understand basics of IEC 61850 and support them to enhance the simple application program example with an temperature measurement (STMP logical node) that provides random values. I provided the enhanced CID file with the extended model (STMP).

After lunch we set up the environment and all needed components. Then the C-Programmer started to understand the given simple application program and the API at about 14:00 h. Some three hours later the extended application was up and running and providing values through IEC 61850 messages – just 2 minutes before the general manager of the company joined our meeting!

We were able to use the new information (temperature) with the various IEC 61850 services like polling, reporting, …

This exercise has again proven that Application programmers can learn the basics of IEC 61850 and write their own application software on the SystemCorp API within a few hours – instead of weeks and months.

The customer was very happy to reach such a challenging objective within a day – before summer vacation season starts!

The embedded Linux platform will be available within the next few months.

Please come by and check this blog – or simply subscribe to the blog (see above right corner).

What is a Stack?

The term Stack has many meanings, flavors,  … ask 10 experts and you may get 11 definitions. People talk about an IEC 61850 stack, an OPC UA stack, .... What do these mean? Are they comparable?

Let’s start with the general definition:

According to the Wikipedia: “The protocol stack is an implementation of a computer networking protocol suite. The terms are often used interchangeably. Strictly speaking, the suite is the definition of the protocols, and the stack is the software implementation of them.”

So, the software that processes the protocols is called the (protocol) stack.

With regards to IEC 61850 this can mean many things: Session, Presentation, ACSE, MMS, ACSI, MMS-SCSM, Model management and configuration language, API to the application, … let’s have a look at the server side of the communication:

	“Protocol” aspects	Remarks and Explanations
1	API to application	Control of Server SW, local services for read, write, events, control, … “Protocol” that defines how the application can communicate with the underlying IEC 61850 software.
2	Models, model management and model and ACSI configuration language	Describe the server’s information model and binding to application (LDs, LNs, DO, DA, …) Be aware that LNs have also services and protocols (see below for LN GLOG). The information models has to be organized in the IED’s software (including retrieving the self-description of the model)
3	ACSI (Abstract Communication Service Interface)	The (protocol) software has to implement the services Association control, retrieve self-description (Server, Client, Publisher, Subscriber, LD, LN, DO, DA, ControlBlocks, …), Get, Set, DataSet services, Reporting (events), Logging (events; historian), GOOSE, Sampled Values, Control, File services, time synchronization, … The implementation of the protocols that define the dynamical behavior of the services are one of the crucial parts of IEC 61850.
4	MMS SCSM	The ACSI services use MMS to carry the payload between client and server. MMS provides the serialization of (service) messages. Example: A Buffered Report Control Block is a quite comprehensive “Service” model with a set of service parameters (for control block attributes). The state machine of the Control Block requires a bit of a software!
5	MMS	Simple classes like NamedVariables, NamedDataSets, Journal, … Message schema (encoding using ASN.1)
6	ACSE	Kind of a remote procedure call
7	Presentation	Concrete encoding: ASN.1 BER
8	Session	Session between client and server
9	RFC 1006	Binding OSI upper layers to TCP
10	Security	Security according to IEC 62351 … TLS
11	TCP/IP	you know …!!
12	Lower layers	…

Note: GOOSE and Sampled Value messages are mapped directly to Ethernet!

What is the Logical Node GLOG? An application or a model with services and protocol (messages)? The GLOG is a standardized application that defines a model, services and a protocol! Guess you did not expect this … others may not agree with me …

IEC 61850-7-4 Edition 2 defines:

“5.7.4 LN: Generic log Name: GLOG
The LN GLOG refers to a function which allows to log not only changed data itself but also any related data being defined in the settings of LN GLOG. The logging is started by the changed data object (TrgRef1) or by the operator (LogTrg). The logged data are identified by the references to the related source data objects in the data model.” This in short the state machine of the GLOG service model and protocol (in abstract terms). The GLOG communicates with a client via services and a protocol …

The logged Data Values will be stored in an IEC 61850 Log … it can be queried by services from a client.

Let’s come back to our question, what is implemented in a stack?

Stacks from different vendors may be for free, may be reasonable priced, or may be expensive! What does this mean? Almost nothing! Because the CRUCIAL question is: WHAT would you get for your Euros or Dollars?

A stack of vendor X may cover the implementation described under bullets 1, 2, 3, 4, 5, 6, 7, 8, 9, and 10.

A stack of vendor Y may cover only 5, 6, 7, 8, 9, and 10.

The difference is tremendous: The efforts to implement the requirements listed in bullets 1, 2, 3, and 4 are (to my experience) likely more than 90 … 95 per cent of what needs to be implemented with regard to IEC 61850!

If you hear something like “the stack so-and-so is cheaper …” listen twice and then think about what you have heart three times and ask what that stack really provides four times AND ASK PEOPLE WITH EXPERIENCES WHAT IS LEFT FOR YOU TO DO to get a compliant IED !!! I have talked to many experts that were surprised that it took sooo long … and cost sooooo … much to get a compliant IED.

When it comes to the comparison of OPC UA and IEC 61850: Listen very carefully, and ask questions … and then … and then you may understand the difference from a standard and from an implementation point of view.

Click HERE if you want to experience what could be provided by a specific stack providing integrated software for issues 1 to 10 … with little left for you [German].
A workshop in English may be set up when you are interested … let Beck IPC know that you would attend a workshop in English.

ICD Documents for programmable and modular IEDs

If you have a modular 61850 product that can be shipped with a variable number of I/O cards, this may have a number of consequences:

1. The number of LNs this product can support depends on the hardware configuration.
2. LNs use shared resources, so if the user adds an LN of one type, he may not be able to add an LN of another type.

Be aware: everything is limited!

These tradeoffs are complex. If you produced an ICD file with the maximum number of LNs of every type your IED supports, for the maximum hardware configuration, the resulting file would be ridiculously large and unwieldy.

How to solve this issue?

All IEDs with a fixed functionality have definitely an easy to build icd file.

IEDs that are programmable or that are modular with one or more I/O cards are different. When the IED comes from the factory, you do not know what the application will be – so you do not know the information model and therefore you cannot provide an icd file for an application running on an IED.

What you could do is to provide an icd file that specifies the communication capabilities (services) and the DataTypeTemplates with all LNTypes that can be instantiated in that IED.

Once it is decided which functions (and LNs) will be running on a particular IED (with one, two, … or five I/O cards), then the IED Configurator (as a manufacturer-specific tool) can create the “final” ICD file for a particular function.

The icd must have exactly one IED section. I would put the LN instances of LLN0 and LPHD in the IED section. The other (functional LNs) would be added be the IED Configurator later … when the number of I/O cards etc are known and selected.

Developers Workshop for IEC 61850 at Myong Ji University, Yongin (RP of Korea) was successful

A successful Developers Workshop for IEC 61850 Client/Server and Publisher/Subscriber Applications was conducted at the Myong Ji University, Yongin/Korea, on 11 March 2011.

The interest was beyond expectations: 45 experts from all over of the RP of Korea attended the Workshop:
 

The attendees followed the instructions of Karlheinz Schwarz, who used the black board to explain the approach of IEC 61850 and the use of the simple API (Application Program Interface):

He explained the use of the API for different architectures (HW and SW) ... questions were discussed in English and Korean:

Professor Hyuk Soo Jang from the Myong Ji University (left) helped to explain the API in Korean.

The attendees used the PCs of the lab and partly their own notebooks to run the API evaluation software. They exercised to configure the IEC 61850 server and to check the effect of SCL file modifications ... a great tool to work with.

After the workshop attendees told me that they have learned a lot about the standard, the stack software, the API, how easy it is to develop applications, and how to use the Beck Chip (with IEC 61850 @ Chip) in many different architectures. One crucial result was, that they figured out that the Beck Chip is a complete PC or PLC that can be used to implement applications (in C, C++ or IEC 61131-3) using IEC 61850 API. The Chip is much more than just a communication chip!!

The objective of the training was:

Students will learn how to use an API for IEC 61850 (IEC 61400-25) for Client, Server (C/S), Publisher, and Subscriber (P/S) Applications. The API provides an IEC 61850 Stack (included in a Windows DLL) that is used by application software written in C, C++ and C#. Prior to the event, students will receive the DLL and sample executable and source code for the applications. Students that bring their own Notebooks will be trained to modify and extend the application examples. After the training sessions students can continue to write their own application software.

Click HERE for the complete program of the workshop [pdf].

It is planned to repeat this workshop and provide more help for developers of IEC 61850 applications - the open and easy to use IEC 61850 platform is a crucial basis for the fast-to-market innovations of sustainable interoperable applications in the energy market.

It's never been easier or faster to get your applications speak IEC 61850.

Let YOUR Application speak IEC 61850 in hours

IEC 61850 has been implemented in hundreds of devices. The UCA Users Group lists some 181 certified devices with server functionality, 3 certified clients, and 2 Merging units (as per 2011-03-02; UCAIug Testing Quality Assurance Program).

Almost all of these devices provide a certain functionality like protection or control. Usually the devices do not provide a simple API (application program interface) that can easily be used by an application program written by a programmer. There is usually nor access to "IEC 6150 Stack". Some test tools may provide restricted access by manually entering values for a data attribute, or using a configurable simulation or providing a CSV (comma separated values) file for a profile. The evaluation licenses are usually quite restricted.

In contrast to this quite limited access to an API there is a free available server and client DLL (from SystemCorp) that runs for six (6) months. The DLL evaluation package comes with various client and server applications. The applications are provided in exe code and source code (C/C++ and C#). You have FULL control over the functionality YOU want to have for your client and server application.

Click HERE for details.

Any application YOU write could easily speak IEC 61850:

The following example shows the .Net / C# client application provided by NettedAutomation GmbH. The received sequence of values can easily be copied and pasted:

 

e.g., pasted into an Excel table and converted to a diagram:

Whatever you need - JUST program it ... or link the client and server applications to your real applications ... which may also be masters to any communication slaves like DNP.3, IEC 60870-5-101/103/104, Modbus, Profibus, CAN, ... This way you can easily and fast build your own GATEWAY. Just link the DNP.3 or 104 points to the DLL by YOUR IEC 61850 server application that is bound to corresponding Model. See next figure:

It is that easy. Just give it a try.

By the way, the API (and the underlying IEC 61850 stack) is also available on the embedded controller from Beck IPC for simple and FAST TO MARKET applications. All you program in C/C++ on a PC could be done on the Chip platform ... the Chip also supports IEC 61131-3 (CoDeSys) and soon ISaGRAF.

NettedAutomation offers public and in-house training courses using a comprehensive set of crucial evaluation tools - including the one shown here.

Extended C# Client Application for IEC 61850 Evaluation Kit based on DLL

NettedAutomation has updated the C# Client application (GUI) of the IEC 61850 Evaluation Kit (DLL); the server is still the same. The new GUI supports polling values, e.g., the temperature, status or alarms, from the server provided earlier:

The API allows manual copy and paste (just select the range of values and copy them) as well as storing the values in a database, Excel sheet, or ...

Values copied and pasted:

07:12:07.562 AM: Temperature value is 32
07:12:17.718 AM: Temperature value is 32
07:12:27.812 AM: Temperature value is 31
07:12:37.921 AM: Temperature value is 30
07:12:48.015 AM: Temperature value is 30
07:12:58.109 AM: Temperature value is 30
07:13:08.218 AM: Temperature value is 30
...

Different polling rates can be selected.

Note that this GUI comes as executable program and in source code (.Net project)! You can use the example and modify as you want ... it is just so easy to use the IEC 61850 Client API ...configured by an SCL file.

The server console (very easy to run and use!) from the existing Kit looks like this: Changes entered, e.g., t29 changes the temp value to 29 in the server ... this is sent to the client and polled by the client ...

Click HERE to download the new C# client application (exe and source code). You will be asked to enter your Email and Password -> "Sign in ..." OR if you don't have an account or forgot your password: Just enter your Email (required) in the middle of the form and click at "I agree with ...". You will immediately receive a new or your current password:

 

Please find the three (3) updated files as shown here:

The exe code can be used as soon as you have the corresponding server from the server running (see figure above: EXE/SOURCE CODE: Simple Server and Client -- IEC 61850/61400-25 FREE Evaluation/Starter Kit using a DLL: Server and Client).

Click HERE for a list of supported Server services that is almost completely implemented in the DLL ; the Client (same DLL) provides complementary services.

Enjoy the extended C# application.

Note that the same API is provided by the IEC61850@CHIP from Beck (see next post).

IEC 61850 Test Tools for SCADA Applications

The other day I was asked for some guidance in the availability of IEC 61850 test tools for SCADA applications. Here is what I have responded (extended in this blog).

First of all, there are dedicated test tools for protection and control testing of the real-time application behavior (from Omicron, Megger, ...)

I guess you are looking non-real-time application issues. To my knowledge, there are no test tools available for SCADA functions that could run test sequences automatically. What I have so far recommend to experts is to develop their own application test tool that exactly provides what they need.

What you may need for your application test (for non-real-time functions) is to test the information exchange between a SCADA IEC 61850 client and an IEC 61850 IED server (protection, control, ...). This would comprise mainly the following tests:

1. Connect client to the server

2. Browse the model of IED

3. Read status and measurements and store the values in a client test application

4. Control outputs from/to a client/server test application

5. Reporting control and receive reports and store the values in a client test application

6. GOOSE control and sending/receiving GOOSE messages and store the values in a subscriber test application

The most known browser software is the IEDScout from Omicron. This can run tests 1 and 2. It would allow you to do a lot of manually tests for tests 3-6.

I guess what you need is a client that has an IEC 61850 API that allows your client and server Test Application to generate and receive messages automatically - in the order you want.

I would recommend to evaluate the IEC 61850 DLL from SystemCorp (Perth, Western Australia). The evaluation kit comes with two simple client applications (including application source code). You could easily extend the client application to implement a test application that could run your test cases automatically.

The evaluation kit is briefly introduced in the following presentation (from my seminars):

Click HERE to download the presentation [pdf, 2 MB]

The complete evaluation kit be downloaded form the following page:

http://nettedautomation.com/iec61850li/dll/index.html

I guess this is the most efficient way!

This kit also allows to build a server ... in order to test your SCADA application.

The kit runs for six months for free. The DLL could be purchased from SystemCorp later for a reasonable price.

NettedAutomation is developing more client and server applications using the DLL - additional applications will be announced on this block.

What does "IEC 61850 Lite" mean?

IEC 61850 is a suite of standards. Implementations usually provide a subset of the various aspects of the many parts (IEC 61850-7-2, 7-3, 7-4, 8-1, 6, ...). There is a document in IEC 61850-7-2 that is used to list the service models and services supported by an implementation (PICS - Protocol Implementation Conformance Statement). The PICS give a good overview about the communication services.

There have been several discussions on specifying a minimum list of these PICS and name it "IEC 61850 Lite". Currently I do not see if there will ever be such a specification, because we have a variety of markets that would need different "Lite" specs. Most programmers (I have talked to the recent years) that want to integrate IEC 61850 software into their application are looking for a "lite" API (Application Program Interface) - for an easy and fast integration into their applications.

This was one of the crucial ideas SystemCorp (Perth, Western Australia, www.systemcorp.com.au) had when they started to implement a "lite" implementation. "Lite" means a - more or less - FULL set of services BUT an easy to use API accompanied by a SCL Design tool that supports designing ICD/CID documents that can directly be used to configure the information model and bind the model to the application program. The resulted easy to use package has gained a huge interest in the marked all over.

The crucial issue is to help people to get started within hours and days - not weeks and months. There is a evaluation package available that can be used on Windows. This package comes with a DLL (IEC 61850 software) and a server application (including C source code of application) and two client applications (including C and C# source code of application). You can run the evaluation right away - it is useable for 6 months.

Here is the link to find more details and how to get the kit:
http://nettedautomation.com/iec61850li/dll/index.html

The feedback from several of the more than 1,000 users of the evaluation kits shows that this seems to be a "lite" solution many had been looking for. The software runs on other platforms as well.

One interesting platform is the Beck IEC61850@CHIP - to get a very "lite" implementation:
http://nettedautomation.com/iec61850li/index.html#beck

I will be at the DistribuTech 2011 (San Diego, Febr 01-03) at booth 2822. Here you can see what a specific "Lite implementation" looks like. Come by for a visit.

CISCO to deliver IP Communication Infrastructure including Substations

EnergyAustralia selected Cisco's Connected Grid solution to build the core of its smart grid infrastructure with greater security, reliability, and operational efficiency, while complying with regulatory mandates and industry standards such as IEC 61850 and supporting new energy supply sources.

Click HERE for the news.

One day "Getting Started Event" on IEC 61850 in Orlando and San Diego end of January 2011

NettedAutomation GmbH /Karlsruhe, Germany) is offering a one day "Getting Started Event" on IEC 61850 and related standards. The program comprises the basics of Edition 1 and 2, an overview on global acceptance and use of the standard, and presentation one of the most efficient and easy to use stack software developed by SystemCorp in Perth (Western Australia).

Dates and Locations:

• Friday, 28. January 2011 in Orlando (Florida)
• Monday, 31. January 2011 in San Diego (California) - just prior to the DistribuTECH 2011

Attendance Fee:

• US$ 295 (including course material, evaluation software, food and beverages).

Students will learn what the standard is all about and how to use the free of charge fully functional evaluation stack software (DLL) for implementing IEC 61850 client/server and publisher/subscriber under Windows. Various application examples written in C, C++ and C# (executable and source code) will be provided to the attendees. This is the FASTEST, EASIEST, and CHEAPEST way to get your devices' data modeled and right away communicated with IEC 61850.

This event is recommended for every person that is interested in IEC 61850 and IEC 61400-25 ... one way or the other. There is no pre-knowledge needed.

IEC 61850 is THE International Standard series for information modeling, information exchange and system configuration to support Smart(er) Automation. Smart(er) Automation comprises application domain like Power Generation, Power Transmission, Power Distribution, Factory Automation, Building Automation, and many other domains.

The new title of IEC 61850 (Communication networks and systems for power utility automation) is definitely wider than the old (Communication networks and systems in substations). IEC does not allow to use the right title that would really describe its application domain: Communication networks and systems for automation.

All basic concepts of IEC 61850 (and IEC 61400-25) are applicable in any automation system:

• native Ethernet for real-time information exchange (GOOSE) and client/server communication,
• TCP/IP including transport layer security for client/server,
• application messaging according to MMS (Manufacturing Message Specification, ISO 9506),
• XML for describing information objects and system configuration,
• many common information objects and functions like "Temperature Supervision", "PID loop control", "device nameplate", etc

Tentative program:

09:30 – 09:45	Welcome, roll call of attendees, expectations
09:45 – 10:45	Introduction into information modeling, models, information exchange and protocols, configuration language SCL ... IEC 61850 and IEC 61400-25
10:45 – 11:00	Coffee break
11:00 - 11:15	The role of the standards in the U.S. NIST SGIP (Smart Grid Interoperability Panel)
11:15 – 12:00	Implementations and global market penetration of IEC 61850 and IEC 61400-25
12:00 - 13:00	Lunch break
13:00 – 14:30	Presentation of SystemCorp’s IEC 61850 Stack PIS-10, IEC 61850 DLL running under Windows, integration of the stack on an embedded controller, SCL tools, network analyzers, etc
14:30 – 14:45	Coffee break
14:45 - 16:00	How to model and interface your application data with the PIS-10 stack API? Sample source code in C, C++ and C# (.Net) will be presented and discussed. Application Source code will be provided on a CD ROM.
16:00 – 17:00	Question & Answer Session
17:00	End of the event

The event will be conducted by Mr. Karlheinz Schwarz. He has trained more than 2.200 people, from more than 50 countries and more than 400 companies since 2004 - all over. Recent training sessions: Frankfurt (DE), Sydney (AU), Montreal (CAN), Dallas (US), Gothenburg (SE), Manila (Phil), Stockholm (SE).

Tap the reach experience of Mr. Schwarz. After the event you or your programmer can continue to use the evaluation software for your real applications!

If you are interested to attend, please let us know. I look forward to seeing you in Orlando or San Diego. Visit SystemCorp and NettedAutomation at the DistribuTECH 2011 (San Diego).

Click HERE to contact us for more information on the "Getting Started Events" in Orlando and San Diego.

FREE IEC 61850/61400-25 Evaluation/Starter Kit

A FREE IEC 61850/61400-25 Evaluation/Starter Kit is now available for immediate download and use. The wait for a FREE IEC 61850/61400-25 Evaluation/Starter Kit is over - here it is for immediate use.

SystemCorp (Perth, Australia) and NettedAutomation offer an IEC 61850/61400-25 DLL (Dynamic Link Library) and three Application examples using the DLL (PIS10.dll; providing a simple stack API):

• C Server Application (simple Console) 
• C Client Application (simple Console) 
• C#/.Net Client Application (runs under XP, Vista, Windows 7)

The Kit contains executable software and the source code of the C and .Net Applications (projects) as well as "Getting started manuals". The PIS10.dll is based on the IEC 61850 stack developed by SystemCorp. The client and server (publisher/subscriber - GOOSE) run on one machine or on different machines as depicted below:

You can use these source code of the application examples and modify them according to your needs. The configuration of the Server AND the Client done by ICD files (according to IEC 61850-6, SCL) - no need for self-description; the model is build at start time. This client/Server package is applicable for M2M (machine to machine) communication. The IEDScout could be used as a Browser-Client as well. Modified applications would require a modified ICD file as well. The "ICD Designer" - a tool to design ICD files - will be available within a week or so.

The services supported are: Association, GetDataObjectValues, SetDataObjectValues, Control, Reporting, GOOSE, ...

NettedAutomation GmbH offers a new services for the integration of the PIS10 stack (DLL, ...) into your application:

Support will be provided by our experienced application programmer: Andreas Pfefferle. Andreas is familiar with Substation Automation, RTUs, IEC 60870-5-10x, protocol integration, ... SystemCorp PIS10-Stack API and many other power utility applications.

Click HERE to Download the IEC 61850/61400-25 Evaluation/Starter Kit
(The Kit comprises first a readme.txt file and four (4) zip files - each file can be downloaded individually; You need at least the <<Console-Server-Client_2010-08-31>> to get the server; to run the client with another server you need to change the ICD file accordingly).
IF you have an Account for downloading content from www.nettedautomation.com then you can use your email address and password. If you have forgotten the password, just enter your email address in the field "Email (required)" and click on the button "I agree ... continue" at the end - you will receive your password. Or just enter your email and further information and you will receive a password immediately.

Enjoy.