Geokon 8800 User manual

Product Tutorial

Troubleshooting GeoNet Wireless
Data Hosting Systems

Many hardware and software issues can be prevented or
resolved with a better understanding of the product
Please read the Installing GeoNet Wireless Data Hosting
Systems and Using Agent Software with GeoNet Wireless Data
Hosting Systems tutorials and review the product manuals prior
to attempting to troubleshoot a Network
Before Continuing

Network Tips

Always mount GeoNet
devices vertically, with the
antenna pointing up
The space around the
antenna should be free of
obstructions
A minimum mounting height
of two meters (six-feet) is
recommended
Device Mounting

Obstructions between,
around, or near GeoNet
devices can cause reflections
of the radio signal
Reflected radio signals can
cause GeoNet devices to
malfunction
For optimum performance,
create as much space as
possible between the straight-
line radio path and any
obstructions (especially
metallic objects)
Device Mounting (Continued)

Common mounting
mistakes include:
►Not enough clear space
around the antenna
►Mounting devices
horizontally
►Metallic objects nearby
The photos to the right
show examples of improper
device mounting
Device Mounting (Continued)

All GeoNet devices are set to operate on the same channel at
the factory
Channels only need to be set if multiple networks will be
operating within radio range of one another
Networks within radio range of one another must not be set to
the same channel
Up to 12 Networks can operate in the same area by utilizing a
different channel for each Network
Setting Channels

To set the channels on a
device:
1. Activate Deployment mode
2. Move the channel switches
to one of the 12 valid settings
3. Press the reset button
GeoNet Devices can only
communicate when set to the
same channel, therefore,
ALL DEVICES in a network
must be set to the same
channel
Setting Channels (Continued)

Must be used when making changes to a network
(adding Nodes, changing batteries, resetting a device, etc.)
Indicated by the LEDs on the Supervisor flashing every 10-15
seconds
Automatically activated when Supervisor is powered
Active for 60 minutes by default
(Can be changed using Agent software)
Can be reactivated/reset by pressing the status button on
the Supervisor
(May take up to 6 minutes to take effect)
Deployment Mode

Avoid powering down or
removing the Supervisor
from a working Network
If the Supervisor must be
powered down or removed,
activate deployment mode
prior to doing so
When downloading data via
a direct PC connection, bring
the PC to the Supervisor
rather than removing the
Supervisor from the Network
Supervisors Control the Network

The Network must be put into deployment mode prior to
replacing the batteries in the Supervisor
(Also best practice when replacing batteries in Nodes)
Replace D cell batteries when voltage drops below 2.0 VDC
Replace 12-volt external batteries when voltage is below 11
volts
All data is stored in nonvolatile flash memory, and will be
retained even if the batteries are absent for an extended period
After replacing the batteries in a Node, make sure it rejoins the
Network, then set the Network time using Agent Software
(Setting time not required when using a Cellular Gateway
Supervisor)
Battery Replacement

Changes to “deploy period”
will take effect the next time
Deployment mode is
activated on the Supervisor
Turn off automatic download
before changing the “scan
rate”
Software Tips

Troubleshooting

Make sure the Network is
in deployment mode (one
or both of the LEDs on
the Supervisor flashing
every 10-15 seconds)
Verify that all four channel
dipswitches inside the Node are
set to the same position as the
switches inside the Supervisor
Devices will only communicate
when set to the same channel
Power the Node while it is in close
proximity to the Supervisor
Node will not Join the Network:
Flashing Red LED
Node
Supervisor

If a Node still will not join the Network after the previous
suggestions have been tried, it may be out of synch with the
Supervisor
The Node will join the Network if given enough time,
however, the connection can be expedited by resetting the
Node
To reset a Node, press the reset button inside the enclosure,
or, hold down the status button until the red and green LEDs
turn on, then release the button
Resetting a Node

Complete the following:
1. Make sure the Network is in deployment mode
2. Power down the Node
3. Position the Node so that it is in close proximity to the
Supervisor (or a Node that has successfully joined the Network)
4. Power up the Node and wait for it to join the Network
5. Move the Node to its intended location
If the Network connection is lost when the Node is in its
original location, try to improve the radio signal by completing
the steps in the next slide
No Signal at Installation Site

Improve the radio signal by:
►Mounting the Node as high as
possible
►Making sure there is plenty of
clear space around the antenna
►Removing obstructions from
the radio path
►Activating more Nodes to
provide alternate data paths
►Moving the Node to a better
location
►High gain directional antenna
may be required (Contact Geokon)
Node has a Weak Radio Signal:
Red & Green LEDs Flashing Together

Green LED flashing slowly (once per second):
Channel switches inside the Node incorrectly set; move to a
valid setting then press the reset button
Green LED flashing quickly (twice per second):
Update the Network firmware to version 160816 or later
(Refer to GeoNet manual for firmware update instructions)
Five green flashes then one long red flash (repeating):
Update the Network firmware
(Refer to GeoNet manual for firmware update instructions)
Alternating green & red LEDs:
Device malfunction, please contact GEOKON
Additional LED Light Codes

Agent Can’t Connect to Supervisor:
Cellular Gateway
Ensure that the external power source is connected and
functioning properly
Verify the Supervisor is connected to the cellular network by
pressing the status button and observing a green, or green and
red flash on the LED indicators
Make sure the token has been copied into the Network address
correctly, and that “token:” has been entered as a prefix