7-10 L30 LINE CURRENT DIFFERENTIAL SYSTEM – INSTRUCTION MANUALTARGETS MENU CHAPTER 7: COMMANDS AND TARGETS7• Description of problem: The SNTP server is not responding.• How often the test is performed: Every 10 to 60 seconds.• What to do: Check that Ethernet cable(s) are properly connected. Check that configuration for the SNTP servercorresponds to the actual server settings. Check connectivity to the server (ping the server IP address.• Latched target message: No.• Description of problem: A discrepancy has been detected between the actual and desired state of a latching contactoutput of an installed type “4L” module.• How often the test is performed: Upon initiation of a contact output state change.• What to do: Verify the state of the output contact and contact the factory if the problem persists.• Latched target message: No.• Description of problem: A data item in a configurable GOOSE data set is oscillating.• How often the test is performed: Upon scanning of each configurable GOOSE data set.• What to do: The “xxx” text denotes the data item that has been detected as oscillating. Evaluate all logic pertaining tothis item.• Latched target message: No.• Description of problem: Any device settings were changed over any available interface.• How often the test is performed: On any setting changes, when new settings were written to device.• What to do: Verify that the setting change was legitimate and essential for proper functioning of the protection andcontrol system.• Latched target message: No.• Description of problem: A direct device is configured but not connected.• How often the test is performed: Every second.• What to do: Check direct input and output configuration and wiring.• Latched target message: No.• Description of problem: One or more RxGOOSE messages are not being received.• How often the test is performed: The self-test is activated when no message is received within the expected timeinterval, which is the time-to-live time in the previous message. This time can be from milliseconds to minutes.• What to do: Check GOOSE setup.• Latched target message: No.• Description of problem: The second line of this self-test error indicates the problem with the PMU Aggregator.MAINTENANCE ALERT:4L DiscrepancyMAINTENANCE ALERT:GGIO Ind xxx oscillMAINTENANCE ALERT:Setting ChangedDIRECT I/O FAILURE:COMM Path IncompleteRxGOOSE FAIL:Missing messagesAGGREGATOR ERROR:
