Tuesday, February 14, 2017
Friday, July 8, 2016
Experience with the OMICRON IEDScout Version 4.10 - The Name Space Concept
This concept has been incorporated into the standard (IEC 61850-6, -7-1, -7-2, -7-3, 7-4, and 8-1) some 15 years ago. At that time I was the editor of parts -7-1 and -7-2.
By the way: These five (5) parts are often called "The Core Parts of IEC 61850".
The name space “IEC 61850-7-4:2003” indicates that ALL instances within this logical device
are derived from the 2003 editions of IEC 61850-7-4, IEC 61850-7-3, and IEC 61850-7-2. The logical device name space could be understood as the prime name space. The attribute ldNs is an attribute contained in the name plate of the logical node zero (LLN0).
A device that implements more than one Logical Device can support multiple prime name spaces - one per Logical Device.
The name space for Edition 2 of the core documents is as follows:
The Omicron IEDScout V4.1 analyzes this Logical Device name space and acts according to the name space configured. Let's see how that works.
If the LD name space is missing then the default value will be used: this means Edition 1 of the core documents).
The following figure shows an SCL file that does not contain a value for the "ldNs". Now we open the SCL file with the IEDScout 4.1.The IEDScout figures out that the prime name space is Edition 1 of the core parts. In Edition 1 of IEC 61850-7-3 (Common Data Classes) there are no CDCs like ENS and ENC defined. This is indicated in the warning area. Edition 1 of IEC 61850-7-3 defines INS and INC instead.
The new enumerated Common Data Classes (ENS, ENC and ENG) have been added in Edition 2 of IEC 61850-7-3. The SCL File with the Edition 2 prime name space is shown next:
The IEDScout does not show any warning!
Smart!
What does that mean for all of us? We have to make sure that our IEC 61850 models configured in an SCL File are according to the prime name space we want to use!
And: The IEDScout has many other powerful (browsing, testing, ...) features build-in that help you to get your IEC 61850 based system running according to the standard series IEC 61850, IEC 61400-25, ...
I am using the IEDScout 4.1 in my training courses. Attendees learn how to model IEDs and how to test them.
Click HERE for downloading a 30 days fully functional evaluation license.
Thursday, June 28, 2012
Updated IEC 61850 analyzer for WireShark (V2.6)
An updated analyzer for WireShark (V2.6) is available. It supports IEC 61850 (8-1, SCL import for GOOSE, 9-2, and 90-5), MMS and ICCP-TASE.2. Older versions show some problems that do not really exist. Some people are using the Wireshark as THE reference implementation of IEC 61850! The reference is the standard – but the tool is very helpful!
Download the exe file to install the new Wireshark version for IEC 61850.
The skunkworks version 2.6 analyzes all of the data. An additional utility that must be run to extract the dataset definitions into ETR files. The directory that the ETR files are located in can be set in the protocol preferences tab.
Thanks to Herb Falk for continuously updating the analyzer!
Thursday, July 7, 2011
Wireshark Analyzer and IEC 61850 Messages (MMS, GOOSE, SAV)
When you use Wireshark (I run Version 1.6.0) you may have had a problem to see GOOSE and MMS messages. There is a simple solution how to visualize the MMS and GOOSE messages:
You have to start the Wireshark first, start analyzing and THEN connect from a IEC 61850 client to a server to open a MMS association. Now you see the messages … strange but it works … as you can see:
Posts
