Specifications

Page 5–4
FOCUS System Manual
Table 5–1. Reasons for Failure of APM Loop to ARM.
Reason
recorded
in target
T1 Bad
Inactive Node
Wrong XID
Time Out
Address
Mismatch
Explanation
The node at the given address has an T1
error on at least one side of the loop definition
(possibly both sides). This reason is reported
if any of the following T1 states are present at
the time the “APM Arm” command was
received:
Not in sync error
Yellow alarm
Low signal level
The node at the given address has a problem
with the loop definition programmed. One of
the transceivers could have gone BAD or may
have been PULLED.
A loop definition programmed to “Not Defined”
will also cause a node to go Inactive.
The node at the given address has received
an XID message from a node other than the
nodes programmed. (neighbor addresses set
using the “APM Define” command).
The address reported with this reason will
always be the node that is attempting to arm
APM. This indicates that the Enable APM
message did not get around the loop, and the
failed node did not have the capability to
respond. Three possible reasons why a node
could not respond:
A node on the loop is powered down
A node on the loop does not contain the
FPS2 software revision
A node on the loop has an inaccurate
loop definition
This occurs only if two nodes are attempting
to arm a chassis at the same time.
User Action
Repeat the “APM Arm” command. If the same
reason is repeated, go to the node that
matches the address and fix the T1 problem.
Try to arm from that node.
Repeat Step 5 on the node that matches the
address in the logged target. Try to arm from
that node.
Repeat Step 5 on the node that matches the
address in the logged target. Try to arm from
that node.
Check the APM configuration settings and the
chassis on the loop.
Make sure no one is attempting to arm the
loop from another chassis. Try the “APM Arm”
command again.