In the SAT of an IEC 61850 substation, the test confirms that what the SCD file says must travel on the network actually does: every GOOSE subscription arrives and is valid, devices respect test mode, communication-loss alarms appear and the end-to-end time of trips between bays fits the limit. It tests the whole system, not each relay.
Short answer
The SAT of the communications of an IEC 61850 substation answers one question: does what the configuration file says must travel actually travel, arrive and arrive on time? To do that, the SCD is compared with the real network traffic, each GOOSE subscription is checked, the behavior of test mode is verified, communication failures are provoked to see that the alarms appear, and the end-to-end time of trips between bays is measured. Each relay was already tested earlier; here the assembled system is tested.
Why it is a separate test
In a digital substation, much of the testing moves to the factory: devices are validated in the laboratory. On site, what remains is to check what only exists with everything connected: the fiber, the switches, the address of every message and the final configuration of each subscriber. A relay that passed its functional test can stop receiving a message because of a changed multicast address, a wrong priority on a port or a badly connected fiber. Those faults are not seen in the relay; they are seen in the system. That is why a passed FAT does not close the question: the SAT checks what the factory could not see, namely the real installation.
What is tested
- The physical network. Clean, labeled fibers, switch ports configured as the design says, and redundancy, if any, checked by cutting a link. See communications network tests.
- The SCD against the network. The list of GOOSE messages (who publishes, to which address, with which identifier) and of their subscriptions (who receives what) is taken from the SCD. With an analyzer on a mirror port, each message is checked to be on the network and its content to match. See SCL files.
- Each subscription. The subscribing device must show the message as received and valid. The state of each one is recorded.
- Test mode and simulation. A device in test mode marks its messages as test messages; a subscriber only accepts them if it is configured to simulate. Both behaviors are checked to be as intended. See test mode and simulation.
- Loss of communication. A publisher is disconnected (switched off or its fiber removed) and the subscriber is checked to raise its alarm, the control system to receive it and the scheme to go to its safe state.
- End-to-end time. The time of a trip from one bay to another is measured, contact to contact, and compared with the design limit.
What is recorded
For each message: publisher, subscribers, address, state of each subscription and date of the test. For each provoked failure: cause, observed alarm and reaction time. For times: each measurement with its instrument. These records are part of the commissioning dossier.
When a subscription does not arrive
The most frequent causes, from simplest to most complex: the publisher is off or in another state; a fiber or a switch port is not right; the configuration changed in the publisher and the SCD was not updated; the subscriber has an older SCD loaded. The order of checking is from the network toward the device. See GOOSE that does not arrive or arrives late.
Worked example
Example data (assumed): substation with one busbar IED and four line IEDs (L1 to L4). Each line IED publishes a GOOSE message to the busbar IED (breaker failure start), and the busbar IED publishes a trip message that the four line IEDs receive. Example time limit for the trip between bays, contact to contact: 20 ms.
- Subscriptions per the SCD: 4 (from the bays to the busbar) + 4 (from the busbar to the bays) = 8.
- First run: 7 valid subscriptions. 7 / 8 = 0.875, or 87.5 %. The eighth does not arrive: the bay publishes with a multicast address different from the SCD’s.
- Correction: the bay’s configuration is aligned with the SCD and the test is repeated. Result: 8 of 8 valid.
- End-to-end time: the bay detects the input and publishes in 3 ms; the network adds 0.5 ms; the subscriber processes in 2.5 ms; the output contact operates in 4 ms. Total: 3 + 0.5 + 2.5 + 4 = 10 ms.
- Margin: 20 − 10 = 10 ms, half the limit.
If in step 2 the system had been accepted with 7 of 8, the affected bay would not have received the busbar trip: the error would have been found with a real fault.
Time to live and loss alarms
A GOOSE publisher keeps sending its message at intervals even when nothing changes, and each message says how long the subscriber must wait before declaring the publisher lost. When that time passes without a new message, the subscriber flags the subscription as invalid and raises its alarm. In the SAT it is checked that this time is the designed one and that the alarm reaches the control system and the operator screen, not only the device.
Redundancy and common time
If the station network is redundant, one link is cut at a time and no message must be lost. And since events from several bays can only be ordered if all share the same time, time synchronization is checked too: the time source, its backup and the difference between devices.
Who takes part
The integrator, who knows the SCD; the protection engineer, who knows which trip must reach where; and the client’s operator, who verifies what appears on their screen. If one is missing, the test loses one of the three viewpoints and usually leaves a fault unseen.
What is delivered
When the communications SAT closes, the following are delivered: the final SCD with its version; the list of messages and subscriptions with the state of each; the records of the provoked failures, with the alarm and the reaction time; the end-to-end time measurements with the instrument used; and the punch items, if any, with their category. With that, whoever maintains the substation can repeat the test after a modification and compare with what existed on the day of delivery.
What not to do
- Do not accept the system because each relay passed its factory test.
- Do not leave any device in test mode at the end.
- Do not compare only what the device screen says: also compare with what is seen on the network.
- Do not skip the loss-of-communication test: it is the one that shows the system fails safe.
- Do not close the SAT without delivering the final SCD and the records with their dates.
Checklist
- Current SCD loaded in all devices and archived with version and date.
- Fibers, ports and redundancy checked.
- List of messages and subscriptions extracted from the SCD.
- Each message seen on the network with an analyzer.
- State of each subscription recorded at the subscribing device.
- Test mode and simulation verified, and deactivated at the end.
- Loss of communication provoked: alarm and safe state checked.
- End-to-end time measured and compared with the limit.
- Records added to the dossier.
Related guides
- GOOSE: event messages in IEC 61850
- Protection tests with GOOSE
- Substation communications network tests
- IEC 61850 SCL files
- Test mode and simulation in IEC 61850
- GOOSE that does not arrive or arrives late
References
- IEC 61850-4, Communication networks and systems for power utility automation, Part 4: System and project management (system tests; FAT and SAT).
Need these tests?
We design the communications test plan, the message list and the acceptance criteria as part of our engineering design and studies service, for projects in any country. Contact us.
Frequently asked questions
What is the difference between testing GOOSE on a relay and in the SAT?
A relay test checks that it publishes and reacts to a simulated message. The SAT checks the system: that all the SCD's messages travel on the real network, that each subscriber receives them and that the complete chain of a trip between bays works with the installed wiring, switches and fiber.
What is a device's test mode for?
To flag the device's messages as test messages so that in-service devices ignore them. A bay or scheme can then be exercised without the rest of the substation acting by mistake. It must be active during the test and deactivated, and checked, at the end.
How do you know a subscription is alive?
The subscribing device reports it through its subscription supervision logical nodes (LGOS for GOOSE), and it is also checked by seeing the message on the network with an analyzer. In commissioning the two sources are cross-checked: what the device says and what is seen on the wire.