WSDA
®
-Base-104
®
USB Base Station
User Manual
Troubleshooting
43
Problem
Possible cause and recommended solution
l
For Ethernet gateways, use Live Connect
™
to verify
communications on a DHCP network. Check that the
extended timeouts are enabled in the Node Commander
®
Edit > Preferences menu, under Devices. Once
communication has been established, the network
configuration can be changed.
2.3 node cannot be configured
Observe the node status indicator LED to determine the
device's state: boot, idle, sample, or sleep. If the node is
sampling or sleeping, it cannot be configured. In Node
Commander
®
, execute the Stop Node command to put the
node in idle state, allowing configuration to occur.
If the user inactivity timeout is set very low, the configuration
menu will have to be entered quickly, before the timeout occurs,
putting the node back in a sample or sleep state.
2.4 node is out of range
Perform a bench test with the node in close proximity to the
gateway to verify they are operational. For range test and
installation recommendations
see Range Test on page 40
. The
system has been tested to operate with the node and gateway
up to 2 km apart with clear line of sight.
2.5 node is not in normal boot mode
If the node status indicator shows the node booting in a mode
other than the normal boot mode, it can be bypassed by toggling
the node ON/OFF switch rapidly three times, then leaving it in
the ON position for normal power up. In normal boot mode the
communication can be established with automatic node
discovery (or manually) once the boot process is complete and
the node is in idle state. Start-up mode can then be changed in
the software.
2.6 node is sampling
Observe the node status indicator LED to determine the
device's state: boot, idle, sample, or sleep. If the node is
sampling, it cannot be configured. In Node Commander
®
,