Installation guide

Diagnostics
73
b. There is more than one BlipServer on the net and another BlipServer has
“stolen” the BlipNode.
Solution: Use the white list in all BlipServers on the LAN to specify which
BlipServer the BlipNode belongs to.
c. The BlipNode has outdated software which is not compliant with the current
BlipServer.
The software package distributed with BlipNet 1.0 is able to upgrade BlipNet
0.5 BlipNodes. If the BlipNode is older than this, it must be upgraded to 0.5
first.
Solution: Upgrade the BlipNode to the 0.5 software and start the auto update
BlipNode software, see the BlipServer Properties - Advanced section.
d. Software upgrade of a BlipNode has failed and the BlipNode is in FTP server
mode. Looking at the yellow LEDs on the BlipNode can verify this. If the blink
sequence is SOS in Morse * * */ - - -/ * * * (3 short, 3 long, 3 short flashes)
the BlipNode is in FTP server mode.
Solution: Please make sure that automatic software upgrade is switched on
(see the BlipServer Properties - Advanced section) and try to restart the
BlipNode.
5.
The BlipNode did not retrieve an IP address. Several possible reasons exist. Please
check the following:
a. Make sure that a DHCP server is present on the network. If there is no DHCP
server, please refer to the “Configuration” section in the BlipNet installation
guide to start a DHCP server.
b. Make sure that the DHCP server has not run out of IP addresses. There is a
fixed limit on the number of available addresses. Both terminals (LAN access
clients only) and BlipNodes receive an IP address from the DHCP server, so if
many LAN access clients are connected, this might cause a BlipNode not to be
able to connect to the BlipServer, because the IP address limit has been
reached. To check if this is the case try to disconnect all other terminals /
BlipNodes and see if this solves the problem. If so, re-configure the DHCP
server to have more IP addresses.
c. The BlipNode did not start up properly, e.g. after a software upgrade. Please
refer to the BlipServer Properties - Advanced section.
d. The BlipNode might have received an IP address, but it is not in the arp table.
It may not have received the ping because it is on another subnet. Please
make sure that the BlipNode is placed on the same subnet as the BlipServer.
The BlipNode and the BlipServer find each other via UDP broadcast.