Troubleshoot GOOSE Publishers
The GOOSE Tracker Tool identifies duplicate, missing, extra, simulated, misconfigured, corrupt, and valid GOOSE Streams in the workspace. Each row in the table is a GOOSE Stream, either defined in one of the SCL files loaded, or found on one of the selected network adapter cards.
The GOOSE Tracker contains a Status Column which indicates if any of the columns for a row contain an error or warning message. Grouping by the Status Column brings any GOOSE Streams with an error or warning message to the User's attention.
The main GOOSE Tracker window has a column showing time between the last Retransmission. In order to preserve bandwidth on the network, this number grows over time from minTime immediately following a state change to maxTime at the steady state condition. To see the time difference between the first 15 Retransmissions after a new GOOSE Message is Published, click the "Record ReTrans" button on the Ribbon Bar:
The following display for GOOSE Retransmissions will appear with columns showing the Publication time in the GOOSE Message Header and the time difference between the next 15 Retransmissions.
Determine if all GOOSE Subscribers are receiving Messages
Once any GOOSE Publisher issues discovered in the GOOSE Tracker Tool are resolved, the
LGOS Tool shown below can verify all Subscribers are receiving the GOOSE Streams defined in the SCD file. The LGOS Logical Node provides the status of the subscription to a GOOSE stream.
Each row in the chart below corresponds to one GOOSE Stream in the publishing IED. Each column in the chart represents a subscribing IED. The intersecting cell graphic represents the LGOS status received from the Subscribing IED, hovering over it will show a tooltip with more detail. The Legend displays all the possible subscription statuses.
Troubleshoot GOOSE Subscribers and Protection Schemes
The GOOSE Publisher Tool allows the user to manually set the GOOSE Message Header information and Data Attribute values for any GOOSE Stream defined in the workspace and publish both new states and retransmissions. The main use cases for the GOOSE Publisher Tool are:
- By default, GOOSE Publisher is configured to send simulated GOOSE messages for Virtual Isolation Testing. This is used to test protection functions in a live substation without affecting other functions that are not involved in the test.
- During Functional Testing, GOOSE Publisher can be used to simulate a GOOSE stream for a missing device.
- If a Subscriber is not receiving messages from a GOOSE Publisher that passes all the checks in GOOSE Tracker, the same GOOSE Stream can be generated in GOOSE Publisher to test the Subscriber from a different source.
- During IED validation testing, GOOSE Publisher can test the reaction of a Subscriber to invalid messages such as missing state numbers or missing sequence numbers.