GOOSE communication is one of the most important features of IEC 61850-based digital substations. It allows protection relays and other Intelligent Electronic Devices (IEDs) to exchange high-speed status, trip, blocking, interlocking and protection signals over an Ethernet network without relying on traditional hardwired binary connections for every signal.
In this practical guide, we explain how to configure IEC 61850 GOOSE communication in SEL protection relays, including GOOSE publishers and subscribers, datasets, control blocks, signal mapping, relay logic, network configuration, communication supervision and commissioning tests.
The article is intended for protection engineers, substation automation engineers, commissioning engineers and technicians working with SEL relays and multi-vendor IEC 61850 systems.
GOOSE Communication in SEL Protection Relays: Complete Configuration, Publisher-Subscriber Mapping and Testing Guide
- 1. What is GOOSE communication?
- 2. GOOSE publisher and subscriber architecture
- 3. Important GOOSE configuration parameters
- 4. GOOSE configuration software for SEL relays
- 5. Step-by-step GOOSE publisher configuration
- 6. Step-by-step GOOSE subscriber configuration
- 7. Practical GOOSE applications in SEL protection relays
- 8. Example: GOOSE-based feeder trip scheme
- 9. GOOSE communication supervision and failure handling
- 10. GOOSE testing and commissioning
- 11. Analysing GOOSE messages with Wireshark
- 12. Ethernet network design for GOOSE
- 13. Common GOOSE configuration mistakes
- 14. GOOSE versus hardwired signals
- 15. Recommended GOOSE commissioning checklist
- 16. SEL relays and IEC 61850 GOOSE support
- 17. Frequently asked questions
- What is GOOSE communication in SEL relays?
- Which software is used to configure GOOSE in SEL relays?
- Can an SEL relay communicate with a Siemens SIPROTEC relay using GOOSE?
- Is GOOSE faster than hardwired communication?
- Does GOOSE require an IP address?
- What happens if the Ethernet network fails?
- Can GOOSE replace all hardwired trip signals?
- How can I test GOOSE communication?
- 18. Practical IEC 61850 and SEL relay training
- Official references and further reading
1. What is GOOSE communication?
GOOSE stands for Generic Object-Oriented Substation Event. It is an IEC 61850 communication service designed for fast transmission of event-based information between IEDs.
Traditional protection systems use copper wiring to exchange signals such as:
- Circuit breaker failure initiation.
- Busbar protection trip.
- Transformer differential protection trip.
- Feeder protection trip.
- Protection blocking and interlocking.
- Circuit breaker position.
- Disconnector and earthing switch status.
- Permissive and intertrip signals.
With GOOSE, these signals can be exchanged through Ethernet communication.
For example, when a feeder relay detects a fault, it can publish a GOOSE message containing its trip status. Another relay subscribing to that message can receive the signal and use it in its protection or control logic.
GOOSE is a Layer 2 Ethernet communication service. It does not depend on an ordinary TCP/IP client-server connection for its real-time event transmission.
Main characteristics of GOOSE
- Fast event-based communication.
- Publisher-subscriber architecture.
- Multicast Ethernet transmission.
- Cyclic retransmission and event-driven updates.
- Communication between IEDs from different manufacturers, subject to compatible IEC 61850 data models and implementation.
- Suitable for protection, control, interlocking and automation applications.
GOOSE is not simply a replacement for every copper wire. Its use must be supported by a suitable protection design, communication architecture, supervision strategy and commissioning procedure.
2. GOOSE publisher and subscriber architecture
GOOSE communication uses two main roles.
GOOSE publisher
The publisher is the IED that sends the GOOSE message.
For example, an SEL-751 feeder protection relay may publish:
- Feeder protection trip.
- Breaker failure initiation.
- Overcurrent element operation.
- Circuit breaker status.
- Protection blocking status.
The publisher creates a dataset containing selected IEC 61850 data attributes. A GOOSE control block is then configured to transmit that dataset.
GOOSE subscriber
The subscriber is the IED that receives and processes the GOOSE message.
For example, an SEL-451 bay control relay may subscribe to the feeder trip signal published by an SEL-751.
The received signal can be mapped into a relay logic variable or another supported application input.
Example architecture
Consider a substation with two SEL relays:
- SEL-751: feeder protection.
- SEL-451: bay protection and control.
When the SEL-751 detects a feeder fault, it publishes a GOOSE trip signal. The SEL-451 subscribes to this signal and can use it to initiate a defined control or protection action.
The actual signal mapping, logic implementation and availability of GOOSE functions depend on the exact relay model, firmware, hardware and ordered IEC 61850 options.
3. Important GOOSE configuration parameters
Before configuring GOOSE communication, engineers should understand the main parameters contained in the GOOSE control block and transmitted message.
| Parameter | Description |
|---|---|
| GoCB | GOOSE control block defining the publication |
| DataSet | Collection of IEC 61850 data attributes transmitted |
| APPID | Application identifier used to identify the GOOSE application |
| Multicast MAC | Destination Ethernet multicast address |
| VLAN ID | Optional virtual LAN identifier |
| VLAN priority | Ethernet priority assigned to the message |
| ConfRev | Dataset configuration revision |
| stNum | State number, incremented when the published state changes |
| sqNum | Sequence number used for successive transmissions |
| MinTime | Configured minimum retransmission interval |
| MaxTime | Configured maximum retransmission interval |
| timeAllowedToLive | Maximum expected interval before the receiver considers the message expired |
| Test | Indicates a test-mode message |
| Simulation | Indicates simulated communication where supported |
| NdsCom | Indicates that the configuration is not yet complete |
The precise implementation and available configuration options vary between IEDs.
Understanding stNum and sqNum
These two parameters are important when analysing GOOSE traffic.
stNum — State Number
The state number changes when the published dataset state changes. For example, when a protection trip signal changes from FALSE to TRUE, the publisher transmits a new state.
sqNum — Sequence Number
The sequence number identifies successive transmissions associated with the current state. It helps receivers and diagnostic tools distinguish repeated transmissions from new state changes.
When analysing GOOSE communication with Wireshark, engineers should examine both values.
MinTime and MaxTime
GOOSE messages are retransmitted even when the dataset has not changed.
Following an event, the publisher generally retransmits more frequently. The retransmission interval then increases towards the configured steady-state interval.
This mechanism allows a subscriber to detect communication problems if expected messages stop arriving.
Do not assume that every relay uses identical default timing values. Confirm the actual settings in the applicable instruction manual and configured GOOSE control block.
4. GOOSE configuration software for SEL relays
The main software tool for IEC 61850 communication engineering in SEL systems is:
acSELerator Architect SEL-5032
Architect is used to configure and document IEC 61850 communication between SEL devices and supported third-party IEDs.
Its functions include:
- Creating IEC 61850 projects.
- Adding IEDs to a project.
- Importing and exporting SCL files.
- Creating GOOSE datasets.
- Configuring GOOSE publications.
- Configuring GOOSE subscriptions.
- Configuring MMS reports.
- Configuring Sampled Values where supported.
- Validating and documenting IEC 61850 configurations.
For SEL devices, Architect is normally used together with acSELerator QuickSet SEL-5030.
QuickSet is primarily used for relay settings and supported programmable logic. Architect handles the IEC 61850 communication configuration. They are complementary tools, not interchangeable applications.
5. Step-by-step GOOSE publisher configuration
In this example, an SEL-751 publishes a feeder protection trip signal.
The exact menu names and available data objects depend on the Architect version, device description package, relay model and firmware.
Step 1: Create an IEC 61850 project
Open acSELerator Architect and create a new project.
Define the project name and add the required IEDs.
For example:
- SEL-751 — feeder protection relay.
- SEL-451 — bay protection and control relay.
Step 2: Add the SEL relay
Select the required SEL IED from the available device library or import its applicable device description.
Check that the selected device definition matches the actual relay model and supported firmware.
Do not select a similar relay model simply because its name looks close. The available logical nodes, data objects and communication capabilities may differ.
Step 3: Identify the signal to publish
Select the protection or control signal that must be transmitted.
For example, a feeder trip indication may be represented by an appropriate IEC 61850 data object in the relay’s supported server model.
Possible signal categories include:
- Protection operation.
- Circuit breaker status.
- Protection blocking.
- Breaker failure initiation.
- General-purpose programmable status.
The actual logical node and data attribute must be confirmed from the device-specific IEC 61850 model.
Step 4: Create a dataset
A dataset defines the information included in the GOOSE message.
For a simple feeder protection application, a dataset might contain:
- Feeder protection trip status.
- Breaker failure initiation status.
- Circuit breaker position.
- Protection blocking status.
Only include signals required by the receiving application. Unnecessary dataset entries increase configuration complexity and may affect message size and processing requirements.
Step 5: Create the GOOSE control block
Create a GOOSE control block and associate it with the required dataset.
Configure the available parameters, including:
- Control block reference.
- APPID.
- Multicast destination address.
- VLAN settings, where required.
- MinTime and MaxTime.
- Dataset association.
Make sure the communication design is consistent with the station Ethernet network configuration.
Step 6: Validate the publication
Use Architect’s validation and diagnostic facilities to check the configuration.
Review the generated SCL configuration and publication information before deploying it to the relay.
6. Step-by-step GOOSE subscriber configuration
Now configure the SEL-451 to receive the feeder trip signal from the SEL-751.
Step 1: Identify the publisher
In the Architect project, locate the SEL-751 GOOSE publication.
Confirm that the required dataset and control block are correctly defined.
Step 2: Add the subscription
Select the required GOOSE publication and configure the SEL-451 as a subscriber.
The subscription must identify the correct source IED, dataset and published data attributes.
Step 3: Map the received signal
Map the required published data attribute to a supported input or internal signal in the subscriber relay.
For example:
- Published signal: Feeder trip.
- Receiving relay: SEL-451.
- Application: Defined protection or control logic.
The exact internal signal name and mapping method depend on the supported device model and firmware.
Step 4: Configure application logic
Receiving a GOOSE message does not automatically mean that a circuit breaker will trip.
The received signal must be used by the appropriate application logic.
For example, an engineer may use a received GOOSE status as an input to a permissive, blocking or trip equation, subject to the relay’s supported logic functions.
Step 5: Check subscription supervision
Verify that the subscriber can detect the status of the GOOSE communication.
Review the available supervision indications and determine what the application should do if the message becomes invalid or expires.
Step 6: Validate and deploy
Check the complete configuration, generate the appropriate IED configuration files and deploy them according to the approved engineering and commissioning procedure.
After deployment, verify that the relay has accepted the configuration and that the subscription is operating correctly.
7. Practical GOOSE applications in SEL protection relays
GOOSE communication can be used in several protection and automation applications.
7.1 Feeder protection trip transfer
An SEL-751 detects a feeder fault and publishes a trip signal.
A receiving relay subscribes to the signal and performs a defined action.
Possible applications include:
- Remote trip initiation.
- Upstream protection coordination.
- Interlocking.
- Backup protection schemes.
The complete scheme must account for communication failure, protection selectivity and the required operating time.
7.2 Circuit breaker failure protection
Breaker failure protection is a common application for GOOSE communication.
For example, when a feeder relay issues a trip command, it can publish a breaker failure initiation signal.
A busbar protection relay or another IED can subscribe to the signal and use it as part of a coordinated breaker failure scheme.
The scheme must consider:
- Breaker failure initiation.
- Current supervision.
- Breaker position.
- Breaker failure timer.
- Retrip logic.
- Upstream or busbar trip initiation.
The required logic and timing must be engineered for the actual protection arrangement.
7.3 Busbar protection interlocking
GOOSE can exchange information between feeder relays and busbar protection equipment.
For example, feeder status or protection information may be used in a defined interlocking or protection application.
The busbar protection design must remain secure and dependable under communication failure, invalid data and incorrect configuration conditions.
7.4 Transformer protection
Transformer protection applications may exchange signals such as:
- Transformer differential protection operation.
- Restricted earth fault operation.
- Transformer lockout status.
- Circuit breaker position.
- Interlocking information.
A transformer protection relay can publish an appropriate status to other IEDs in the transformer bay.
7.5 Electrical and mechanical interlocking
GOOSE is useful for exchanging equipment status and interlocking information.
Examples include:
- Circuit breaker position.
- Disconnector position.
- Earthing switch position.
- Bay interlocking conditions.
- Remote permissive signals.
The logic must be designed so that invalid or unavailable status information does not create an unsafe switching condition.
8. Example: GOOSE-based feeder trip scheme
Consider a substation with two feeder bays.
The objective is to transmit a protection trip signal from one relay to another through GOOSE.
IED 1 — SEL-751
- Detects the feeder fault.
- Operates the protection logic.
- Publishes a GOOSE trip indication.
IED 2 — SEL-451
- Subscribes to the SEL-751 publication.
- Receives the trip indication.
- Uses the mapped signal in the approved application logic.
The engineering sequence is:
- Define the protection function and trip philosophy.
- Identify the publisher data object.
- Create the publisher dataset.
- Configure the GOOSE control block.
- Configure the subscriber.
- Map the received signal.
- Implement the receiving logic.
- Configure communication supervision.
- Test normal operation and communication failure.
- Record the final configuration and test results.
A key engineering point: a successful GOOSE subscription does not by itself prove that the complete protection scheme will operate correctly. The end-to-end logic and physical output path must also be tested.
9. GOOSE communication supervision and failure handling
GOOSE is designed to provide fast and reliable communication, but an Ethernet network can still experience failures.
Possible causes include:
- Ethernet cable disconnection.
- Switch failure.
- Incorrect VLAN configuration.
- Incorrect multicast configuration.
- Publisher relay failure.
- Subscriber relay failure.
- Incorrect APPID or destination address.
- Invalid or incompatible SCL configuration.
- Dataset revision mismatch.
- Incorrect subscription mapping.
What happens if a GOOSE message is lost?
GOOSE subscribers use the message timing information, including timeAllowedToLive, to identify when an expected message has not been received within the allowed period.
The subscriber can then indicate that the communication is no longer valid.
However, the action taken by the protection application depends on the relay implementation and engineering logic.
Possible strategies include:
- Alarm generation.
- Blocking selected functions.
- Transferring to an alternative protection scheme.
- Using an independent hardwired backup signal.
- Applying a predefined safe-state response.
There is no universal fail-safe response suitable for every application.
Important: Do not assume that communication failure should always cause a trip or always block a trip. The correct response depends on the protection philosophy and risk assessment.
10. GOOSE testing and commissioning
GOOSE commissioning should include both publisher and subscriber testing.
A successful communication indication alone is not sufficient evidence that the protection application works correctly.
10.1 Publisher testing
Check that:
- The publisher is enabled.
- The correct dataset is configured.
- The GOOSE control block is active.
- The correct destination multicast address is used.
- APPID and VLAN settings match the network design.
- The published status changes when the associated relay signal changes.
- The message retransmission behaviour is consistent with the configured parameters.
10.2 Subscriber testing
Check that:
- The subscriber is correctly configured.
- The correct publisher is selected.
- The required data attributes are mapped.
- The subscription is valid.
- The received signal changes correctly.
- The signal is connected to the intended application logic.
- The receiving relay responds as designed.
10.3 End-to-end testing
For a feeder trip application, a practical test sequence is:
- Confirm that both relays have the approved configuration.
- Confirm that the GOOSE network is operational.
- Operate the relevant protection or test logic in the publisher relay.
- Confirm that the publisher transmits the expected GOOSE state.
- Confirm that the subscriber receives the message.
- Verify the mapped internal signal.
- Verify the receiving logic.
- Verify the intended output or indication.
- Repeat the test for the reset condition.
- Record the test results.
Where a trip circuit is connected to live equipment, apply the approved isolation and safety procedures before testing.
10.4 Communication failure testing
Communication failure tests are essential.
Depending on the approved test procedure, engineers can simulate or isolate the communication path and verify:
- Detection of missing GOOSE messages.
- Communication alarm generation.
- Supervision signal changes.
- Application response to invalid communication.
- Recovery after communication is restored.
Testing should not unintentionally operate other IEDs or circuit breakers.
10.5 Test mode and simulation
IEC 61850 includes test and simulation-related mechanisms, but their exact implementation and support vary between devices.
Before testing, confirm how the publisher and subscriber handle test-mode messages and whether the receiving application blocks or processes them.
Do not assume that a test flag automatically isolates every protection output.
A carefully designed test philosophy should prevent inadvertent operation while still allowing meaningful end-to-end verification.
11. Analysing GOOSE messages with Wireshark
Wireshark is a useful tool for diagnosing IEC 61850 GOOSE communication.
It allows engineers to inspect the Ethernet frames and verify whether the expected messages are being transmitted and received.
What should you check in Wireshark?
| Item | What to verify |
|---|---|
| EtherType | GOOSE uses Ethernet EtherType 0x88B8 |
| Source MAC | Matches the publishing device/network interface |
| Destination MAC | Matches the configured multicast address |
| APPID | Matches the expected GOOSE application |
| VLAN ID | Matches the network design, if VLAN tagging is used |
| stNum | Changes when the published state changes |
| sqNum | Increases across successive transmissions for a state |
| ConfRev | Matches the intended dataset configuration revision |
| timeAllowedToLive | Is consistent with the retransmission behaviour |
| Dataset values | Contain the expected status information |
Example Wireshark troubleshooting procedure
- Connect the engineering laptop to an appropriate switch mirror port or approved network test point.
- Start a packet capture.
- Apply a filter for GOOSE traffic.
- Identify the publisher’s source MAC address.
- Check the destination multicast address.
- Inspect APPID and VLAN information.
- Expand the GOOSE protocol fields.
- Trigger the required relay signal.
- Confirm that the dataset state changes.
- Check that the subscriber receives the expected traffic.
A useful display filter is:
goose
You can also filter using the Ethernet type:
eth.type == 0x88b8
The exact decoded fields shown depend on the Wireshark version and capture quality.
12. Ethernet network design for GOOSE
GOOSE communication depends on a properly engineered Ethernet network.
The network design should consider:
- Managed industrial Ethernet switches.
- Multicast traffic handling.
- VLAN segmentation.
- VLAN priority and Quality of Service.
- Network bandwidth.
- Switch redundancy.
- Network monitoring.
- Cybersecurity.
- Time synchronisation where required by the wider substation architecture.
VLAN configuration
VLANs can be used to separate different categories of substation traffic.
For example:
- Protection GOOSE traffic.
- MMS station-bus communication.
- Engineering access.
- SCADA communication.
The VLAN configuration must be consistent between the publisher, subscriber and network switches.
Network redundancy
Substation Ethernet networks may use redundancy technologies such as:
- PRP — Parallel Redundancy Protocol.
- HSR — High-availability Seamless Redundancy.
The selected redundancy architecture must be supported by the relevant devices and network equipment.
Do not assume that every SEL relay supports every redundancy method. Confirm the exact hardware, firmware and communication options.
13. Common GOOSE configuration mistakes
The following problems are frequently encountered during IEC 61850 engineering and commissioning.
1. Incorrect dataset
The publisher transmits a dataset that does not contain the required signal.
Solution: Review the dataset entries and compare them with the approved signal list.
2. Incorrect APPID or multicast address
The publisher and subscriber are not configured consistently.
Solution: Compare the GOOSE control block and subscription configuration with the approved SCL files.
3. Incorrect VLAN settings
The GOOSE message is transmitted but cannot reach the subscriber because of an incorrect VLAN configuration.
Solution: Check the VLAN configuration in the IEDs and Ethernet switches.
4. Incorrect signal mapping
The subscriber receives the message, but the required data attribute is not mapped to the intended internal signal.
Solution: Verify the subscription mapping and the receiving relay logic.
5. Dataset revision mismatch
The publisher dataset has been changed, but the receiving configuration has not been updated accordingly.
Solution: Review ConfRev and the final SCL configuration. Regenerate and deploy the necessary IED configurations.
6. No communication-loss strategy
The application works normally but does not respond appropriately when the GOOSE message expires.
Solution: Define and test the communication-failure response before commissioning.
7. Testing only the Ethernet message
The engineer confirms that a GOOSE packet is visible but does not verify the receiving relay logic or output.
Solution: Perform end-to-end testing from the publisher signal through the subscriber application to the intended indication or output.
14. GOOSE versus hardwired signals
GOOSE and traditional hardwired signals both have important roles in protection and control systems.
| Feature | Hardwired signal | GOOSE |
|---|---|---|
| Signal transmission | Copper wiring | Ethernet network |
| Physical connections | Individual wiring circuits | Shared communication infrastructure |
| Signal exchange | Usually point-to-point | Publisher-subscriber |
| Engineering | Wiring diagrams and terminal plans | SCL and communication configuration |
| Troubleshooting | Electrical measurements and wiring checks | Network diagnostics and IED supervision |
| Expansion | Often requires additional wiring | May require configuration and network changes |
| Failure considerations | Cable and contact failures | Network, configuration and device failures |
GOOSE can reduce wiring and provide flexible signal exchange, but it also introduces communication engineering and cybersecurity requirements.
A hybrid architecture using both GOOSE and hardwired signals may be appropriate, particularly for critical protection functions.
15. Recommended GOOSE commissioning checklist
Before handing over an IEC 61850 protection system, verify the following items.
- Confirm the exact relay models and IEC 61850 options.
- Confirm the firmware and device description versions.
- Review the approved SCD file.
- Verify publisher datasets.
- Verify GOOSE control blocks.
- Check APPID and multicast MAC addresses.
- Check VLAN ID and priority.
- Verify subscriber mappings.
- Check ConfRev and configuration consistency.
- Confirm GOOSE supervision.
- Test normal signal transmission.
- Test signal reset.
- Verify receiving relay logic.
- Perform end-to-end functional tests.
- Test communication failure response.
- Confirm test-mode behaviour.
- Capture and review GOOSE traffic.
- Save final SCL files and relay settings.
- Record all test results and configuration revisions.
16. SEL relays and IEC 61850 GOOSE support
Several SEL relay families can be used in IEC 61850 applications. However, support for GOOSE publishing and subscribing must be checked against the exact device and configuration.
Examples of SEL product families used in protection and control applications include:
- SEL-751 — feeder protection.
- SEL-451 — protection, automation and bay control.
- SEL-421 — transmission line protection.
- SEL-411L — line current differential protection.
- SEL-487B — bus differential and breaker failure protection.
- SEL-787 — transformer protection.
- SEL-700G — generator protection.
Do not interpret this list as confirmation that every hardware or firmware version supports the same GOOSE functions. Always check the relevant SEL product documentation, IEC 61850 conformance information and device-specific ICD files.
17. Frequently asked questions
What is GOOSE communication in SEL relays?
GOOSE is an IEC 61850 communication service that allows SEL protection relays and other compatible IEDs to exchange event-based information over Ethernet. Typical applications include trip signals, breaker failure initiation, interlocking and protection blocking.
Which software is used to configure GOOSE in SEL relays?
The primary tool is acSELerator Architect SEL-5032. It is used to configure IEC 61850 communication, including GOOSE publications, subscriptions and datasets. QuickSet SEL-5030 is used for relay settings and supported programmable logic.
Can an SEL relay communicate with a Siemens SIPROTEC relay using GOOSE?
Yes, a multi-vendor GOOSE application is possible when both devices support the required IEC 61850 services and compatible data models. The IED descriptions, SCL configuration, signal mapping and network settings must be engineered and tested.
Is GOOSE faster than hardwired communication?
GOOSE is designed for fast event communication, but actual end-to-end performance depends on the IED processing, network architecture, switch configuration and application logic. Do not assume a universal operating time without testing the actual system.
Does GOOSE require an IP address?
GOOSE uses Ethernet Layer 2 multicast communication and does not rely on an ordinary IP-based client-server connection for its message transmission. Other services in the substation, such as MMS, may use IP networking.
What happens if the Ethernet network fails?
The subscriber can detect missing or expired GOOSE messages through the applicable supervision mechanisms. The resulting protection or control action depends on the engineered application and relay implementation.
Can GOOSE replace all hardwired trip signals?
Not necessarily. The decision depends on the protection philosophy, system requirements, reliability assessment, applicable standards and the supported communication architecture. Critical applications may require independent hardwired paths or other backup arrangements.
How can I test GOOSE communication?
Use a combination of Architect configuration checks, relay indications, functional testing and Ethernet packet analysis with Wireshark. Verify the complete path from publisher to subscriber and the final application response.
18. Practical IEC 61850 and SEL relay training
Understanding GOOSE requires more than knowing the protocol definitions. Engineers should be able to configure datasets, create publications and subscriptions, map signals, analyse communication traffic and perform end-to-end tests.
Elec-Engg provides practical training in power system protection, SEL relays and IEC 61850 substation automation.
Training topics can include:
- SEL relay configuration and commissioning.
- acSELerator QuickSet SEL-5030.
- acSELerator Architect SEL-5032.
- IEC 61850 MMS, GOOSE and Sampled Values.
- SCL, ICD, CID and SCD files.
- GOOSE publisher and subscriber configuration.
- Wireshark-based IEC 61850 troubleshooting.
- Protection logic and end-to-end testing.
Online and customized training can be arranged based on the requirements of engineers and companies.
For further information, visit https://elec-engg.com/ or contact Elec-Engg.
Official references and further reading
- SEL-5032 acSELerator Architect Software: https://selinc.com/products/5032/
- SEL-5032 Software Downloads and ICD Package: https://selinc.com/products/5032/support/
- SEL Digital Secondary Systems: https://selinc.com/solutions/digital-secondary-systems/
- SEL technical paper — If You Cannot Test It, You Cannot Use It: IEC 61850 GOOSE System Designed With Testing in Mind: https://cdn.selinc.com/assets/Literature/Publications/Technical%20Papers/6778_IfYouCannot_AA_20170207_Web2.pdf
- SEL-451 Protection, Automation and Bay Control System: https://selinc.com/products/451/
- SEL-751 Feeder Protection Relay: https://selinc.com/products/751/

