Hemisphere GPS Vector V113 - Common Problem Solutions

V103/113 Vector User Guide Appendix A- Troubleshooting
Page A2
Appendix A: Troubleshooting
Table A-1 provides troubleshooting for common problems.
Table A-1: Troubleshooting
Symptom Possible Solution
Receiver fails to power
 Verify polarity of power lead
 Check integrity of power cable connectors
 Check power input voltage (6 to 36VDC)
 Check current restrictions imposed by power source
(minimum available should be > 1.0 A)
No data from V103/113
 Check receiver power status to ensure the receiver is
powered (an ammeter can be used for this)
 Verify desired messages are activated (using PocketMax3 or
$JSHOW command in any terminal program)
 Ensure the baud rate of the V103/113 matches that of the receiving
device
 Check integrity and connectivity of power and data cable
connections
Random data from V103/113
 Verify the RTCM or binary messages are not being output accidentally
(send a $JSHOW command)
 Ensure the baud rate of the V103/113 matches that of the remote
device
 Potentially, the volume of data requested to be output by the V103/113
could be higher than the current baud rate supports (try using 19200
as the baud rate for all devices or reduce the amount of data being
output)
No GPS lock
 Verify the V103/113 has a clear view of the sky
 Verify the lock status of GPS satellites (this can be done with
PocketMax3)
No SBAS lock
 Verify the V103/113 has a clear view of the sky
 Verify the lock status of SBAS satellites (this can be done with
PocketMax3 - monitor BER value)
 Set SBAS mode to automatic with the
$JWAASPRN,AUTO command
Note: SBAS lock is only possible if you are in an appropriate SBAS region;
currently, there is limited SBAS availability in the southern hemisphere.