CHAPTER 7: COMMANDS AND TARGETS TARGETS MENUM60 MOTOR PROTECTION SYSTEM – INSTRUCTION MANUAL 7-97• What to do: A web page "SFP Transceiver Information" is provided. This page displays the type of the SFP in it. This datais to be used with the CPU type to know the cause of the problem.• Latched target message: No.• Description of problem: A faulty SFP or unplugging the SFP would generate this self test.What to do: The web page "SFP Transceiver Information" described in the previous section applies for this self test as well.The "SFP Module Fail" has higher priority and it suppresses the "Ethernet Fail" target message. The "SFP MODULE FAILFUNCTION" setting enables/disables this self test. The target for this self test is priority-based, with the third one being thehighest priority. For example, if all three SFP modules fail, then the third SFP target is activated. If the third SFP modulefailure resolves, then the second SFP target is activated.7.2.2.4 HardFiber self-test error messagesIn addition to those provided by the standard UR-series devices, the UR devices implement HardFiber self-tests. These arelisted here. Any abnormal diagnostic condition indicated by the LEDs or the critical failure relay also results in a self-testmessage, so troubleshooting is described here. For other relays, such at the B95Plus, see that product’s instruction manual.Equipment mismatch major self-test• Description of problem: The number or type of installed hardware modules does not match the order code stored inthe CPU. The standard UR-series Equipment Mismatch self-test is extended to cover the possible presence of aProcess Card.• Severity: Protection is not available and all contact outputs and shared outputs are de-asserted.• What to do: Check all modules against the order code. Ensure they are inserted properly, and cycle the control power.If a module has intentionally been added or removed use the Update Order Code command to notify the relay that thecurrent module configuration is correct.Module failure major self-test• Description of problem: UR-series device module hardware failure detected.• Severity: Protection is not available and all contact outputs and shared outputs are de-asserted.• What to do: Contact the factory and supply the failure code noted in the display. Text in the message identifies thefailed module (for example, H81). If operated on a Process Card failure, the Module Fail self-test seals-in (latches) till theUR-series device is restarted.Process bus failure major self-test• Description of problem: Mission critical data is not available via the process bus. An AC quantity is considered critical ifboth AC bank origins and the crosschecking settings are other than none. This self-test is also initiated by an AC inputdiscrepancy being detected. See the description of the crosschecking setting in this manual for further information. Inaddition, this self-test can be initiated by user logic responding to loss of critical contact input/output or other datausing the Process Bus Failure Operand user-programmable self-test setting. This setting is located in the Settings >Product Setup > User-Programmable Self Test menu.• Severity: Protection is not available and all contact outputs and shared outputs are de-asserted.• What to do: First rectify any Process Bus Trouble and Brick Trouble self-test errors. Check the actual value of theoperand referenced by the Process Bus Failure Operand setting, and if “On,” determine the cause and rectify.If the problem persists with the foregoing all clear, the cause must be an AC input discrepancy, which is typically theresult of problems in the input signals to the Bricks, or faults in the Brick input conditioning hardware. If the error wasannunciated the first time significant signal was encountered, suspect the former cause and check the copperconnections external to the Brick. Where multiple UR-series devices have self-test errors, look for common causes.SFP MODULE x FAIL