Line failure

This section describes the steps leading up to the system declaring a line as failed when No Reply Alarm Suppression is enabled.

Step 1: A Remote Fails to Respond to a Poll on a Normal Line

When a remote fails to respond to a poll request, the following output appears on the relevant summary windows:

1. Connection Summary window:

   • Line State changes to "Suspect".

   • Failed Remotes increments by one.

   • Last No Reply Communication updates with the time at which the remote failed to reply.

2. Operational Activities Summary window:

   • An event appears with the following Message: Communications on NameOfLine status - no reply.

   • The Annunciated field for the above event outputs "NO".

   • An accompanying event appears with the following Message: Line suspect on connection NameOfLine because remote NameOfRemote did not respond. Temporarily suppressing Remote no reply alarms.

Step 2: Remotes Consecutively Fail to Respond to Polls on a Normal Line

When another remote consecutively fails to respond to a poll request, the system repeats the activities outlined in Step 1.

So long as remotes continue to consecutively fail to respond to a poll request, the process keeps repeating until one of the following occurs:

• The number of consecutively failed remotes reaches the failed remote threshold.

• All remotes on the line are offscan.

  For example, if there are six remotes on the line and the threshold is "10", the system nevertheless marks the line as failed if all six remotes are offscan.

Step 3: The System Determines that the Line State is "Failed"

When a remote fails to respond to a poll request, the following output appears on the relevant summary windows:

3. Connection Summary window:

   • Line State changes to "Suspect".

   • Failed Remotes increments by one.

   • Last No Reply Communication updates with the time at which the remote failed to reply.

4. Operational Activities Summary window:

   • An event appears with the following Message: Communications on NameOfLine status - no reply.

   • The Annunciated field for the above event outputs "NO".

   • An accompanying event appears with the following Message: Line suspect on connection NameOfLine because remote NameOfRemote did not respond. Temporarily suppressing Remote no reply alarms.