Honeywell HPM, Service

Page: 155 / 498

2 Equipment Description
2.27 EUCN Cable System
R688 HPM High-Performance Process Manager Service 155
December 2020 Honeywell
Table 22 Crossover Cable Faults
Error scenario UCN COMM STATUS UCN CABLE
STATUS/FTE
CABLE STATUS
$FTESTS2
displays
(ENB)
$FTESTS2
displays
(all other EUCN
nodes)
If the top level
cross cable
connecting the
Yellow and
Green switches
are correctly
functioning.
A
SIL
B
SIL
A
NSY
B
NSY
OK/OK
UCN: OK/BACKUP
LCN: OK/BACKUP
FTE composite status
A->A A->B B->A B->B
OK OK OK OK
If the top level
cross cable
connecting the
Yellow and
Green Switches
is removed or
has a problem.
A
SIL
B
SIL
A
NSY
B
NSY
FAIL/FAIL
UCN: OK/BACKUP
LCN: OK/BACKUP
FTE composite status
A->A A->B B->A B->B
OK SIL SIL OK
Diagnosing Complex EUCN FTE Network Faults
Complex EUCN FTE Network Faults occur when multiple network faults are injected at different levels
of the network topology. These faults cause complex communication path fault indications as well as
system behaviors.
Communication Path
When analyzing FTE faults, it is important to remember that the faults are reported from the viewpoint of
the reporting node. UCN cable faults are reported by each individual node and will only be faulted if the
fault prevents hearing from any other FTE node on a given interface. $FTESTS1 or $FTESTS2 is
strictly the view of the specified Primary ENIM/ENB generated by listening to FTE diagnostic frames
from every FTE community member. When invoking $FTESTS1 or $FTESTS2 a EUCN network
number and primary ENIM/ENB is specified.
The FTE status reported is from the view of this node. When utilizing the Experion System Management
FTE/Heartbeat Status Display, the display will be from the viewpoint of the node on which the status
display is invoked. When utilizing the Experion Station FTE status display, the display is from the
viewpoint of the Experion Server to which station is connected. Because each of these views is from a
different point in the network, the difference in the view can be helpful in determining the actual location
of the network fault(s).
To diagnose faults, a network topology diagram is imperative. Utilizing the $FTESTS2 schematic, mark
the faults indicated on the network topology diagram. Once faults have been mapped, view the diagram
keeping in mind that the faults are as viewed by the specified Primary ENIM/ENB. This will usually
identify the location of the faults. In the case of multiple faults, it can be difficult to identify all faults at
once. Fix the most obvious issue first and then proceed with other faults. Performing the same analysis
using alternative views and marking a seperate copy of the network topology can also be helpful. Once
multiple views are available compare the views and identify the common faults in the views.