Hemisphere GPS Crescent Vector H220 - Page 40

H220 Integrator Guide Appendix B-Troubleshooting Page B2
Appendix B: Troubleshooting
Use the following checklist to troubleshoot anomalous H220 operation. Table B-1 provides a list of issues
with possible solutions.
Table B-1: Troubleshooting
Issue Possible Solution
What is the first thing I do if I
have a problem with the
operation of the H220?
Try to isolate the source of the problem. Problems are
likely to fall within one of the following categories:
 Power, communication, and configuration
 GNSS reception and performance
 Beacon reception and performance
 SBAS reception and performance
 External corrections
 Installation
 Shielding and isolating interference
Note: It is important to review each category in detail
to eliminate it as a problem.
 No data from the
H220
 No communication
 Check receiver power status (this may be done a
Multimeter
 Confirm communication with H220 via
Hemisphere query command $JI, $JSHOW
 Verify that H220 is locked to GNSS satellites (this
can often be done on the receiving device or by
using SLXMon)
 Check integrity and connectivity of power and data
cable connections
Random binary data from the
H220
 Verify that the RTCM or Bin messages are not being
accidentally output (send a $JSHOW command).
 Verify that the baud rate settings of H220 and
remote device match.
 Potentially, the volume of data requested to be output
by the H220 could be higher than the current baud
rate supports. Try using 19200 or higher for the baud
rate for all devices.