Echelon IP-852 Channel - Manual (Page 27)

IP-852 Channel User’s Guide 19
Symptom Probable Cause Corrective Action
The near router
(iLONRTR_1)
commissions
successfully, but no
service pin
message is received
from the far router
(iLONRTR_2).
There is a problem
with the IP-852
channel setup.
Be sure the IP-852 Configuration
Server is running when you commission
the devices on the IP-852 channel.
Verify that the near router is online and
that the IP-852 Configuration Server
reports connectivity among all members
of the IP-852 channel (for example, all
icons are green).
Both IP-852 device
routers commission
successfully, but
the device on the
far side of
iLONRTR_2 (the
DI-10 device) does
not install
correctly.
There is a problem
with the IP-852
channel or the
device being
installed.
Verify that the far router is online. Test
devices on the far side channel (using
the LonMaker Test command). If the
test succeeds for any other device on the
far channel, the IP-852 channel is
working, and the improperly working
device may not be installed correctly.
If no test succeeds, verify connectivity
between the IP-852 devices in the main
dialog status window of the IP-852
Configuration Server.
An IP-852 device
added to an IP-852
channel using the
IP-852
Configuration
Server remains red
in the device tree.
IP connectivity
problem: the IP-852
Configuration
Server is not able to
communicate with
the IP-852 device on
the defined IP-852
channel.
Verify that the computer running the
IP-852 Configuration Server can ping
the IP-852 device. To perform a ping,
open the Windows Command Prompt
(in the Accessories program folder) and
type “ping X.X.X.X” (the device’s IP
address). You should receive a reply
from your device.
Examine the IP-852 Configuration
Server trace window for clues as to
what may be going wrong.
Verify that you can ping the IP-852
Configuration Server computer or
members of the IP-852 channel using
the Windows Command Prompt.