Honeywell Experion PKS, Руководство пользователя

Страница: 258 / 270

Cause 1 No connection
Solution Check cable connections on module IOTA (FTEA and FTEB connectors) and at CF9 IOTAs.
Cause 2 Cables bad
Solution Swap known good cable with suspect cable. Replace bad cable.
Cause 3 Switch port bad
Solution Swap cables with known good port to identify defective port. Replace assembly that contains defective
port.
Cause 4 IOTA bad
Solution Replace IOTA
FTE receive fault diagnostic
The PGM has detected an open receive signal line between either of its two Ethernet interface devices and the
processor handling incoming communication.
Diagnostic
Check • The Status LED on the front panel of the PGM turns RED.
• The 'LAN_A' or 'LAN_B' indicator for the faulted port turns RED. The indicators are found on the FTE
tab of the PGM block configuration form.
• An alarm is generated by the PGM that indicates "FTE Port A Receive Fault" or "FTE Port B Receive
Fault."
Cause The following conditions may result in a spurious (false) indication of an FTE Receive Diagnostic fault.
These conditions are external to the PGM that allow a carrier to be detected by the PGM's Port A or Port B
Ethernet interface but eliminate FTE traffic on that port.
• Disconnecting the uplink cable of a CF9 when only one PGM is connected to any of the downlink ports
on the CF9.
In this case, the only source of external FTE Diagnostic messages are nodes that
communicate through the uplink port of the CF9. When the uplink cable is disconnected, there are no
incoming FTE Diagnostic messages on the PGM. Since the downlink cable from the CF9 to the PGM
remains attached, the PGM has a 'good' Link Status on the port. The combination of a good Link Status
and no incoming FTE Diagnostic messages results in the
spurious indication of an FTE Receive Fault.
• Removal and re-insertion of a CF9 module or power cycling a CF9, when the associated PGM is not
power cycled.
In this case, when the CF9 is powered up, Link Status transitions to the 'good' state before
the CF9 completes its power on self tests (POST) and starts passing FTE Diagnostic messages again.
This interval is long enough that the PGM's FTE Receive Fault Diagnostic will indicate a
spurious
fault.
• Throttling of Ethernet traffic during of an abnormal amount of communication traffic on one or both of
the PGM's Ethernet ports.
During a 'storm' on the FTE network, the PGM initiates limiting of incoming Ethernet traffic on its FTE
ports. As a result of this limiting, a sufficient number of FTE Diagnostic messages may be lost so that
one or both ports see 'good' Link Status signals but no FTE Diagnostic messages over the sample
interval of this diagnostic. In this case, the PGM's FTE Receive Fault Diagnostic will indicate a
spurious fault. The spurious alarm generated by the FTE Receive Fault Diagnostic is a relatively minor
side effect, in the case of a network storm. A network storm is signaled by other alarms in the system.
Solution Unless you suspect that one of the causes described above exists and is resulting in a spurious indication,
you should replace the PGM exhibiting this diagnostic at your earliest convenience. When this fault exists,
network redundancy for this node no longer is working.
13 PROFIBUS GATEWAY MODULE (PGM) TROUBLESHOOTING
258 www.honeywell.com