Hemisphere GPS S320 User Manual page 32

Appendix A: Troubleshooting
Table A-1 provides troubleshooting tips for the S320.
Table A-1: S320 troubleshooting
Issue
Receiver fails to
power
No data logged
No
communication
No valid data
Random binary data
from Eclipse OEM
board
No GNSS position
No DGPS position in
external RTCM mode
Non-DGPS output
S320 User Guide
Possible Resolution
External power is low
Check charge on external battery and the fuse on the power cable, if
applicable
Internal power: Check charge on internal batteries
Check all power cables and pins
Try other batteries or cables
Make sure to hold the power button down for a minimum of one full
second to turn on
Ensure batteries are installed with contacts pointed in the correct
direction
(1) Check receiver power status
(2) Verify it is locked to a valid DGPS signal
(2) Verify that it is locked to 4 or more GPS satellites
(2) Check integrity and connectivity of power and data cable
connections
Verify that the baud rate settings match
If trying to connect over Bluetooth, ensure Bluetooth module is
powered ON and device is paired prior to opening the port
Verify the RCTM or the Bin messages are not being
accidentally output (send a $JSHOW command)
Verify the baud rate settings match
Potentially, the volume of data requested to be output could be
higher than the current baud rate supports. Try using a higher baud
rate for communications.
Verify the antenna's view of the sky, especially toward SBAS satellites,
south in the northern hemisphere
Verify the bit error rate (BER) and lock status of SBAS satellites (this can
often be done on the receiving device or by using SLXMon - monitor
BER value)
Verify the proper application is running on the Eclipse
(SBASRTKB)
Set the satellite selection to automatic mode $JFREQ,AUTO
Set the differential mode to $JDIFF,WAAS
Ensure there is SBAS coverage in your area
Verify the baud rate of the RTCM input port matches the baud rate of
the external source
Verify the pinout between the RTCM source and the RTCM input port
(the "ground" pin and pinout must be connected, and the "transmit"
from the source must connect to the "receiver" of the RTCM input
port)
If using RTK, ensure receiver is properly authorized for RTK by sending a
$JI command or a $JK command
PN 875-0281-000 Rev C2