Remote-i Net
Basic Programming
The
Remote-i Net
comes configured by the factory ready to operate on most local networks without the
need for reprogramming. However, there are some situations which require different programming to
allow its connection to the user's local network.
Local Addressing of Remote-i Net
The factory setting for
Remote-i Net
assumes the following conditions for the local network:
y
TCP/IP network protocol
y
twisted pair
network cable with RJ-45 connector
y
access point which accepts a standard 10base-T (10 Mbits/s in twisted pair)
y
DHCP server
The DHCP (
Dynamic Host Control Protocol
) server is a component of the local network which is
responsible for distributing IP addresses to the other machines. Each machine connected to the local
network when turned on, searches for the DHCP server and requests an IP address to initiate the work.
The DHCP server then verifies its list of available addresses, selects one of them and informs of the
address which each machine must utilize in order to be identified by the other machines on the network.
This centralized control facilitates and disciplines the distribution of addresses when the quantity of
machines connected to the same local network is very high (more than 10 machines).
Often, for small installations, a DHCP server is not required, and if that is the case for your installation,
the
Remote-i Net
will need to be reconfigured.
Searching for a DHCP server on the local network
The test to find out whether or not your local network has a DHCP server is very simple: it is just a matter
of turning on the
Remote-i Net
with the factory configuration. The 3 LEDs of the
Remote-i Net
will light
up while it searches for the DHCP server. If there is a DHCP server on the network, after 3 seconds two
LEDs will go off (COMMUNICATION and LINE), and only the POWER LED will remain on.
Alternatively, should the 3 LEDs remain on after 5 seconds, this means that the
Remote-i Net
did not
managed to find the DHCP server. The possible reasons are:
•
faulty cable contact
•
inappropriate network cable (it must be the same type used for computers)
•
hub turned off
•
DHCP server disconnected
After verifying the first three items and finding that the same signaling remains, one can assume with a
high degree of certainty that your local network does not have a DHCP server available. In this case your
Remote-i Net
will need to be reconfigured.
Contronics
5
