APPLICATION BULLETIN

Helpful Information on the Application, Operation and Technical Aspects of Megger Test Equipment
By: Rene Aguilar

Megger Goose Configurator (MGC)

MGC software is used in the testing or commissioning of IEC 61850 devices. The MGC graphical
user interface provides a quick and easy tool used to configure the test sets. This application
guide will provide information on the controls and functionality of the MGC. In this guide a detailed
example will be provided. This example deals with testing a breaker failure scheme using two
relays A and B. The example will show how to configure the test set and the various files required
to test this scheme.
IEC 61850 Operations
All communications in an IEC 61850 substation is via Ethernet or fiber optic cable. Each IED
(Intelligent Electronic Device) has a specific GOOSE (Generic Object Oriented Substation Event)
message or messages that it will publish to the network. In order to receive a published GOOSE
message these IED’s will have to subscribe (receive) to that specific message. These messages
are used for protection and control. When an event occurs in the system, the IED’s will publish
their specific GOOSEs to the network over a span of time. The IED’s logic will determine whether
a breaker is tripped or closed.

The MGC program will assist the user in programming the test set for these specific GOOSE
messages. A GOOSE message can be imported directly from an SCL (Substation Configuration
Language) type file or directly captured by sniffing the network. Once a message is imported or
captured, the user will be able to either subscribe or publish GOOSE messages. The latter
sections will explain more in detail how this is done.

MGC Menu Items

The MGC tool bar contains File, Edit, View, Tools, and Help. All functionality can be accessed
from the tool bar. We will now focus on each option.

File
The File option contains 4 selections which are:

Save: This option allows the user to save a *.mgc file. This file will contain all the SCL files
or sniffed GOOSE messages used to configure the test set. The *.mgc file will also contain
the mappings to either binary inputs/outputs.
 Save As: This is similar to save except it allows the user to create another *.mgc file with a
different name.

Open: Opens up an *.mgc file

Download Settings to Test Set: This option will download all the mappings to the test set.

Exit: Closes the MGC software.

Edit

The Edit option contains 6 selections which are:

Delete Selected GOOSE: Will delete selected GOOSE messages from the MY GOOSE
tab.

Mark Unconfirmed (All GOOSEs this Tab): Will mark captured GOOSEs as unconfirmed.
This is helpful to determine if a particular GOOSE message is found within the network. All
imported GOOSE messages are unconfirmed.

Reset Binary Input Mapping: Will reset all mappings to binary inputs under the MY
GOOSE tab.

Reset Binary Output Mapping: Will reset all mappings to binary outputs under the MY
GOOSE tab.

Reset All Binary Input/Output Mappings (All GOOSEs): Will reset all mappings to binary
inputs and outputs under the MY GOOSE tab.

Delete Current Tab: Will delete GOOSE message tab from either imported or captured
GOOSEs.
View

The View option contains 2 selections which are:

Collapse All: If a GOOSE message is opened, this command will collapse the GOOSE
messages to GOOSE name field.

Expand All: If a GOOSE message is opened in the name field, expand all will show all the
properties of the GOOSE messages.

This can be better explained by the following two figures. Figure 1 shows a collapsed
GOOSE message.

Figure 1: Collapsed GOOSE Message

When the “expand all” option is selected all properties of the GOOSE message will be displayed
as in Figure 2.
Figure 2: Expanded GOOSE Message
Tools
The Tools option contains 7 selections which are:

Capture: Will sniff or capture GOOSE messages from a network device. This will open
the select network device window shown below in Figure 3.

Figure 3: Device Network Selection

Import: Will import GOOSE messages from an SCL type file. These files have an
extension of .SCL, .SCD, .CID, .ICD, and XML. This will open up a browse window to
select an SCL file to open.

Sort: Will sort GOOSE messages in either descending or ascending order based. The
sort categories are shown in Figure 4.

Figure 4: Sort Categories

Reset GOOSE Configuration: Will reset the test set GOOSE configurations.

Select Network Device: Will display window from Figure 3.

Select Test Set IP: Display window used to enter IP address of test set.

Preferences: Shows test preferences such as: full and easy view modes, GOOSE
mapping modes, test mode, bypass test set, and GOOSE filter options.

View Modes: Full mode displays all GOOSE attributes. While easy view only
displays main attributes of the GOOSE message. This attributes include GOOSE
control name, Mac address, App Id, and dataset name. Figure X below shows
the difference in the two views.

Choose GOOSE Mode: Allows user to select GOOSE Mode. This can be the
following: MPRT, PC GOOSER, or Expanded MPRT. The modes of operation
define how a GOOSE message will be mapped.

MPRT Mode: All published GOOSE messages will be assigned to binary

outputs. All subscribed messages will be assigned to binary inputs.

PC GOOSER Mode: All published GOOSE messages will be assigned

to binary inputs. All subscribed messages will be assigned to binary
outputs.

Expanded MPRT Mode: All published and subscribed GOOSE

messages can be mapped to either binary inputs or outputs.

Test Mode: Used for verification of GOOSE messages test set will publish. This
mode will not allow the test set to publish GOOSE messages to the network. All
published GOOSE messages will be forwarded to the PC port only. Unselecting
test mode, will allow the test set to publish GOOSE messages to the network.
This mode will help prevent false tripping due to wrong GOOSE selection.
Bypass Test Set: Will allow the user to capture GOOSE messages without
being connected to a test set. This only applies to test sets with single port
Ethernet. If a test set with duo Ethernet ports is being used, do not use this
selection. This will disable the GOOSE forwarding feature in the test set which
the user will not be able to capture GOOSE messages on the network.

GOOSE Filter Options: This option allows the user to select different type of
GOOSE filters. These options are: VLAN ID, Delete on Add to Filter, and Filter
Allows Update.

VLAN ID: This filter option if unchecked will remove VLAN ID from the
GOOSE verification filter. This means that VLAN ID will not be
considered for the identification of a GOOSE messages. This is
important due to some PC’s Ethernet cards will remove VLAN tag from
the GOOSE messages. This can cause problems during testing. For
example, an IED is publishing a GOOSE message with VLAN ID 1. The
message is captured thru the PC Ethernet card and the PC removes the
VLAN information. This message is selected and the test set will
subscribe to this message. Remember, the VLAN information is no
longer there. When the IED publishes this message and the test set
receives and applies its GOOSE filter and VLAN ID is selected, the test
set will detect the differences and will not consider it. Figure x below
shows the VLAN ID option.

Delete on Add to Filter: This option will remove the specific GOOSE
message from list to be added to a filter tab. If the GOOSE message is
added from a captured, the message will be removed temporarily until
that GOOSE message reappears again.
 Filter Allows Update: This option will allow for a filtered GOOSE
message to be updated during a capture. This means only GOOSE
messages in the filtered tab will be updated or captured. If this option is
not selected, all GOOSE messages in the filtered tab will be ignored
during a capture.

Send License Key to Test Set: Will allow user to activate MPRT IEC 61850 by entering
a 32 digit code provided by factory.
Help
About: The help option will display the version of the software.

MGC Toolbar
The MGC buttons provide a shortcut to either importing or capturing a GOOSE message without
navigating through the tool bar. The various buttons are shown below in Figure 5.

Figure 5: MGC Buttons

SCL button: Accesses the import option from the toolbar. This will open up a browse window to
allow the user to import GOOSE messages from an SCL type file.

C button: Accesses the capture option from the toolbar. This will open up the network device
selection window to allow the user to select network device being used.

DL button: This will download all mappings to the test set.

Merge button: This will merge captured and imported GOOSE messages into one tab.

Copy to MyGOOSE button: This will allow a user to copy a GOOSE message to My GOOSE
tab. The My GOOSE tab is where all GOOSE messages are assigned to either binary inputs or
outputs.

New Search: This will allow the user to search for GOOSE attributes to help identify GOOSE
messages of interest. Figure x below shows the search options available.

Previous and Next: Takes the user to the previous or the next GOOSE message with the
particular search attributes.

These preceding sections were intended to provide information on the general controls of the
MGC.
 Importing of GOOSE Messages via an SCL Type File
As mentioned earlier, specific GOOSE messages can be imported via an SCL type file. This file is
generated from a substation configurator or by individual IED’s software. An SCL file contains
information about all the devices that are within that particular substation. Each IED can generate
either an ICD (IED Capability Description) or CID (Configuration IED Description) file. Keep in
mind that these files will be different between stations. It is important to use proper naming in
order to keep track of files.

To import an SCL file a user can click on the SCL tab or go to Tools/Import. This will open up a
browse window to search for the specific file. Figure 6 below shows the browse window and the
various extensions that can be imported by the MGC.

Figure 6: Importing an SCL File

Select a specific file and open. Opening a file will generate a tab in the MGC labeled with the file
name. Figure 7 shows an imported GOOSE in the MGC.
 Figure 7: Imported GOOSE message in MGC (Black Colored)

All imported GOOSE messages are black colored and considered unconfirmed messages. Only
captured messages are green colored and considered confirmed messages due to the sniffing
feature of the MGC which obtains the actual messages from the network. We will describe later
how imported and captured GOOSE messages can be combined to determine the differences
between the messages.

Capturing (Sniffing) GOOSE Messages

Capturing GOOSE messages from the network is another method of importing into the MGC
software. Sniffing is used to either verify an SCL file or to determine what GOOSE messages are
needed to test the network. To capture messages a network device must be selected. This is
done by either selecting the C button or Tools/Capture which will open the network select device
window shown in figure 3. After a device is selected, the C button will turn green and messages
will start to appear as they are captured. A capture session will last until the C button is pressed
once again. All captured messages are displayed in green. Green signifies a confirmed GOOSE
message. Every time a captured session is initiated, a separate tab is created that will contain the
captured messages. Figure 8 below shows the MGC with captured GOOSE messages.

Figure 8: Captured GOOSE Messages (Green)

A captured GOOSE can be marked as an unconfirmed GOOSE message. This is done by

selecting the GOOSE message, right click, and select Mark Unconfirmed (Whole GOOSE). This
will change the color from green to black. This is shown in figure 9 and 10 below.
 Figure 9: Marking Unconfirmed

Figure 10: Unconfirmed GOOSE Message

Merging Messages
Merging is useful for comparing imported and captured GOOSE messages. When the MERGE
button is pressed, a new MERGED tab is created. All GOOSE messages that are similar will
contain an “M” icon. Figure 11 shows merged GOOSE messages.
 Figure 11: Merged Messages

GOOSE Identification Tagging

GOOSE identification tagging allows the user to be able to identify a particular GOOSE by
detecting its change of state during a test. For example, I want to identify which GOOSE
message is being published when I apply a fault to a relay. First, capture messages on the
network as shown in figure 12 below.

Figure 12: Initial Captured State of GOOSE Messages

Next, apply a fault and see which of these messages have changed color or have become
highlighted and bolded as shown below in figure 13.

Figure 13: GOOSE Identification by Color Change

The color purple indicates a false state and red indicates a true state for the Boolean value.
Notice from figure 13 above, two messages have changed while the other remains in its initial
state. An important note, a GOOSE message will only change colors when a change has been
detected in the message during a capture.

MY GOOSE
The MY GOOSE tab should contain all GOOSE messages and input/output mappings needed to
perform a test. Any GOOSE message can be copied to MY GOOSE tab. A specific GOOSE can
be copied over to MY GOOSE by selecting that message. Right click and select Copy GOOSE to
“My GOOSE Tab” or press Ctrl + G. Only messages in My GOOSE tab can be assigned to either
binary inputs or outputs. Each GOOSE message will contain a dataset with different indication.
The indications correspond to the different bits that will cause a GOOSE message to be
published. Figure 14 shows the assigned inputs and outputs associated with each GOOSE
copied.
 Figure 14: Assigning inputs or outputs in My GOOSE

If the user accidentally assigns an input or output to two different indications the MGC will display
a message warning the user this mapping already exists. This message is shown below in Figure
15.

Figure 15: BIN Mapping Conflict Message

MGC Operational Modes

The next sections will discuss the MGC software modes of operation in more detail. This should
help the user understand and select the appropriate mode of operation for their particular
application. The three modes of operation are: MPRT, PC GOOSER, and Expanded MPRT.

MPRT Mode
This mode of operation is intended to be used with the MPRT (Megger Protective Relay Test
System). This mode will only allow binary inputs to be mapped to subscribed GOOSE messages
and binary outputs to published GOOSE messages. In Figure 16 below, all indications of the first
GOOSE message have been assigned to binary inputs (Subscribed). This means that the first
GOOSE message is going to be subscribed by the MPRT. The second GOOSE message is
going to be mapped to the binary outputs (Published). This particular GOOSE message is going
to be published by the MPRT.

Figure 16: MGC in MPRT Mode

PC GOOSER Mode
This mode of operation is intended to be used with the Megger GOOSER. In this mode, all
subscribed GOOSE messages will be assigned to binary outputs and all published will be
assigned to binary inputs. When assigning GOOSE messages, all indication of a particular
GOOSE will either be subscribed or published, not both. Notice in Figure 17 that all indications of
the first GOOSE message are all mapped to binary outputs (Subscribed). In the second GOOSE
message, all indications are mapped to binary inputs (Published).
 Figure 17: MGC in PC GOOSER Mode

Expanded MPRT Mode

In this mode, all subscribed or published GOOSE messages can be assigned to either binary
inputs or outputs. If a GOOSE message contains various indications, then those particular
indications can be mapped to either input or output. Figure 18 shows a GOOSE with indication
one being mapped to input 6 and indication two being mapped to output 6. Notice in this mode it
is difficult to determine whether a GOOSE is a published or subscribed. This type of application is
not very common.

Figure 18: MGC in Expanded MPRT Mode

 Example: Testing a Communications Based Breaker
Failure Scheme with IEC 61850
This example will demonstrate what is required in order to setup the MGC and the test set to test
a communications based distributed breaker failure scheme. The one line diagram is shown
below in Figure 19. The system has two IED’s which are shown as Relay A and Relay B. Relay B
is the main protection and Relay A is the backup. In this example, a fault has been placed at
location A, marked in the one line diagram. The instantaneous overcurrent element in Relay B
will transmit a trip GOOSE to breaker B.

A Relay A
GOOSE A

GOOSE (B,C or D)

ETHERNET SWITCH

GOOSE C GOOSE D
Bu
s
GOOSE B

Relay B Relay C Relay D

B C D

Fault
A

Distributed Breaker Failure

Figure 19: One line Diagram

Simultaneously, Relay B will also transmit a breaker failure initiate GOOSE to Relay A.
Relay A will receive this GOOSE and it will initiate the breaker failure timer which will
expire in 10 cycles. If for any reason the breaker failure initiate message is not received
and breaker B does not open, Relay A will trip for instantaneous over-current in 20
cycles.

The MPRT is going to be used to simulate breaker position to the relays. In the MGC
folder under C:/Program Files/Megger, is a file called MPRT.ICD. This is the file that will
be used to simulate the breaker.
 The aforementioned logic would need to be programmed into the relays. Once the relays
have been programmed, obtain the ICD files from each relay. This can be done by the
exporting functions found in each relay’s software. For this example, a total of three
GOOSE messages are going to be needed to test this scheme. Table 1 below shows the
GOOSE messages needed from each device.

Relay A GOOSE Relay B GOOSE MPRT(XCBR)

GOOSE
Ind 1 Trip Trip Breaker B Pos.
Ind 2 Breaker Fail. Init. Breaker A Pos.
Table 1: GOOSE Messages for Breaker Failure Scheme

For this example, 3 ICD files were created. These files are Main.icd, Backup.icd, and
MPRT.icd. The main file corresponds to Relay B, Backup corresponds to Relay A, and
MPRT corresponds to the Breakers.

Next, open up the MGC and select to start a new session. Also set the MGC mode to
MPRT by going to Tools/ Choose GOOSE Mode/ MPRT. Press the SCL button and
import these three files. Copy these GOOSE messages to My GOOSE. Figure 20 shows
the imported GOOSE messages from each device.

Figure 20: Imported GOOSE Messages under My GOOSE

At this point it is the user’s choice to verify the imported GOOSE messages are available
in the network. This is not required if one is certain that the correct files were opened and
imported. However, if there is doubt after importing the files, press the C button to initiate
a capture session. Once all messages have been captured, press the C button once
more to stop capture. Press the Merge button to merge the imported and captured
messages. The similar GOOSE messages will have an “M” indication. This will allow the
user to see if all messages imported are present. Any messages without an “M” indicate
that they are different. Figure 21 shows the merged GOOSE messages for this example.

Figure 21: Merged GOOSE Messages

Notice that all messages for this example are indeed the same. The correct files have been
imported. Now copy these messages to the My GOOSE tab. Once the messages have been
copied, the indications of each message have to be assigned. A test plan was created using the
AVTS software. This plan requires the following assignments shown below in Figure 22.

Figure 22 a: Assignments of GOOSE Messages (Expanded)

Figure 22 b: Assignments of GOOSE Messages (Collapsed)

Once the assignments have been made, these must be downloaded to the test set. Press the DL
button to download this configuration. Upon successful completion the user will receive a
confirmation message as shown in Figure 25.
 Figure 23: Confirmation of Configuration Download

We are now ready to test the breaker failure scheme. The AVTS test plan was created using the
dynamic control. Figure 24 shows the virtual connections required to run the test.

Hardware Test Connections

Ethernet
Switch

Ph A Ph A
Device A Device B

Figure 24 a: Hardware Test Connections

 RELAY A TEST DEVICE
Published GOOSE
Published GOOSE
Trip A
Bkr A Pos.
Subscribed GOOSE

Trip B
Subscribed GOOSE Subscribed GOOSE

Bkr A Pos. Trip A

RELAY B
Published GOOSE Published GOOSE

Trip B Bkr B Pos.

Subscribed GOOSE Subscribed GOOSE

Bkr B Pos. Trip B

Virtual Test Connections

Figure 24 b: Virtual Test Connections

A brief description of the programmed test sequence in the dynamic control is as follows:

The MPRT sends breaker close to Relay A and B and waits until relays have reset from lockout.
After 10 seconds, a pre-fault condition is applied for 30 cycles and then a single phase to ground
fault is applied. After 3 cycles Relay B will issue a trip GOOSE and after 2 cycles of detecting this
message, the MPRT will simulate that Breaker B failed to open. 10 cycles after fault inception,
Relay A publishes its BF Trip GOOSE, which the MPRT receives and after 2 cycles opens
Breaker A. Figure 23 below shows the captured digital traces of the GOOSE messages during
the test. Table 2 below shows the GOOSEs being sent and the status values of each indication
during the event.

Relay B Ind 1= Phase IOC Trip Relay A Ind 1= BF Trip or Phase IOC Trip

MPRT Ind 1= Breaker B Position MPRT Ind 2= Breaker A Position

Pre-Fault Fault BF Trip

Relay B Ind 1=False Ind 1=True Ind 1=True
GOOSE
Relay A Ind 1=False Ind 1=False Ind 1=True
GOOSE
MPRT Ind 1=True Ind 1=False Ind 1=True
GOOSE Ind 2=True Ind 1=True Ind 2=False
Table 2: GOOSE Messages Sent During Event
 IED B Trip GO
IED A Trip GO

Bkr A Pos
Bkr B Pos

FEEDER B TRIP (IED B) BF/IOC TRIP (IED A)

8.50 ms 178.80 ms

Figure 25: Digital Capture of GOOSE Messages

The labels of each trace are as follows:

IED B Trip GO: Relay B Indication 1 (Phase Inst. OC and Breaker Failure Initiate)
IED A Trip GO: Relay A Indication 1 (Breaker Failure Trip)
Bkr B Pos: MPRT Indication 1 (Breaker B Position)
Bkr A Pos: MPRT Indication 2 (Breaker A Position)

This same procedure can be repeated by capturing the GOOSE messages from a network
device. We will leave this as an example for the user to try. This guide has provided operational
information about the MGC as well as a detailed example on how it is used in testing a 61850
scheme.