Echelon IP-852 Channel - Manual (Page 26)

18 Creating an IP-852 Channel
Table 2.2 Troubleshooting the IP-852 Device
Symptom Probable Cause Corrective Action
There is a problem
with network
connectivity, or the
network interface in
the computer may
not be functioning
properly.
Test connectivity between the network
interface driver and the network
interface card in the computer using
L ON W ORKS Interfaces in the Windows
Control Panel . Test to make sure that
the L ON W ORKS Interfaces application
receive a service pin message from some
other device on the same channel as the
IP-852 device.
The IP-852 device
may not be
physically
connected to the
network interface.
Check the network wiring between the
computer and the IP-852 device.
No IP address has
been assigned to the
IP-852 device.
Configure the IP address in the IP-852
device using the setup Web pages and
the IP-852 Configuration Server.
If you are using an
i.LON 600 IP-852
router as the near
router, the router
application has not
yet been created on
the IP-852 device.
Create the LONWORKS router
application using the Console
Application, as described in Chapter 5
of the i.LON 600 LonWorks/IP-852
Router User’s Guide.
If you are using a
SmartServer or an
i.LON 100 Internet
Server as the near
router, it may not
be licensed or
configured to
operate as an
IP-852 router.
License and configure the SmartServer
or i.LON 100 server to operate as an
IP-852 router, as described in Chapter 3
of the SmartServer 2.0 User’s Guide or
i.LON 100 e3 User’s Guide.
No service pin
message is received
from the near
router
(iLONRTR_1 in
Figure 2.10).
The IP channel
properties have not
been properly set.
For a local Intranet, make sure the
channel property/transceiver type in the
LonMaker tool is IP-10L. For a WAN
(Internet), choose IP-10W.