CHAPTER 7: COMMANDS AND TARGETS TARGETS MENUF60 FEEDER PROTECTION SYSTEM – INSTRUCTION MANUAL 7-117• 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: The front panel is not communicating with the CPU module.• How often the test is performed: Every five seconds.What to do: Open the front panel and check the connection between the CPU module and the front panel, then restart therelay in EnerVista under Commands > Relay Maintenance > Reboot Relay or by powering the relay off and on. If troublepersists, contact the factory.• Latched target message: No.• Description of problem: The graphical front panel firmware revision is not synchronized with that of the CPU module inthe relay.• How often the test is performed: Whenever connection is established between the graphical front panel and the CPUmodule in the relay.• What to do: Perform UR firmware upgrade with the graphical front panel connected to the CPU module in the relay. Itcan be done using any communication interface (Ethernet or USB). This synchronizes the graphical firmware revisionwith that of the relay. If trouble persists, contact the factory.• 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.MAINTENANCE ALERT:Setting ChangedMAINTENANCE ALERT:Front Panel TroubleMAINTENANCE ALERT:GFP Version MismatchDIRECT I/O FAILURE:COMM Path IncompleteRxGOOSE FAIL:Missing messagesAGGREGATOR ERROR:
