Table 18 Peer Connection Status - Honeywell 900 User Manual

Control station
Table of Contents

Advertisement

Main Menu
Communications
Status
Possible Cause
GOOD
N/A
APPLICATION
The peer connection
ERROR
could not be
established due to an
internal program
problem.
SETUP ERROR
The peer device
indicated that the one
or more data item is
not valid.
PEER FAIL
The assigned peer
could not be located on
the network.
PORT FAIL
The peer data
exchange IO
subsystem could not
be started due to
internal resource
problem.
NOT STARTED
The assigned peer IO
connection has not yet
been attempted.
Normal state during
startup and during
configuration mode.
This status should
automatically change
to GOOD after both
peer controllers are in
the RUN mode.
34

Table 18 Peer Connection Status

Controller Action
Peer is connected and
updating normally
N/A
The error will occur when
an incompatibility exists
between peer devices with
regard to variable or signal
assignments.
This error should not
occur when exchanging
data between HC900
controllers.
N/A
N/A
900 Control Station User Guide
Peer Connections
What to do
N/A
1. Reset the controller to restart
the UDP/IP protocol stack and
reset buffer allocations.
2. Contact Honeywell Technical
Assistance if the problem
exists.
Contact Honeywell Technical
Assistance if the status occurs.
1. Check the controller name and
network name of the peer
device to assure that they
match that specific PDE block.
2. Check that the IP addresses of
the peer devices are all within
the range of the IP mask.
3. Check that the peer devices
have the same IP subnet mask.
See Network parameters for IP
mask setting.
1. Reset the controller to restart
the Ethernet IO hardware and
reassign processor IO
mapping.
2. Contact Honeywell Technical
Assistance if the problem
exists.
1. If this status persists during run
time, check that the peer
device is properly connected
and that the control name and
network name is correct.
2. Check that the IP masks of all
peer devices to assure that all
IP addresses are within the
same subnet.
3. Check that all external network
components such as switches
and routers allow passing of
UDP packets on port 502.
4. Check that the peer device is
powered on and is in RUN
mode.
Revision 9
May 2014

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents