Vector Sensor Reference Manual 117
9. Troubleshooting
Use the following checklist to troubleshoot anomalous Vector Sensor receiver operation. Table 9-
1 provides a problem symptom, followed by a list of possible solutions.
Table 9-1 Troubleshooting
Symptom Possible Solution
Receiver fails to power • Verify polarity of power leads
• Check 1.0 A in-line power cable fuse
• Check integrity of power cable connections
• Check power input voltage (8 to 40 VDC)
• Check current restrictions imposed by power
source (minimum available should be > 1.0 A)
No data from Vector Sensor • Check receiver power status LED to ensure that
the receiver is powered
• Verify that Vector Sensor is locked to a valid
DGPS signal (this can often be done on the
receiving device or with the use with
PocketMAX running on a PC)
• Verify that Vector Sensor is locked to GPS
satellites (this can often be done on the receiving
device or with the use with PocketMAX running
on a PC)
• Check integrity and connectivity of power and
data cable connections
Random data from Vector
Sensor
• Verify that the RTCM or the Bin95 and Bin96
messages are not being output accidentally (send
a $JSHOW command)
• Verify baud rate settings of Vector Sensor and
remote device match correctly
• Potentially, the volume of data requested to be
output by the Vector Sensor could be higher
than the current baud rate supports. Try using
38,400 as the baud rate for all devices or reduce
the amount of data being output
No GPS lock • Check integrity of antenna cable
• Verify Vector Antenna Array’s unobstructed
view of the sky
• Verify the lock status of GPS satellites (this can
often be done on the receiving device or with
the use with PocketMAX running on a PC)
No SBAS lock • Check antenna connections
• Verify Vector Antenna Array’s unobstructed
view of the sky
• Verify the lock status of SBAS satellites (this can
often be done on the receiving device or with
the use with PocketMAX running on a PC -
monitor BER value)
No beacon lock • Check antenna connections
• Verify that the receiver is tuned to the correct
frequency and bit rate
• Ensure that beacon signal coverage is expected
in your area
• Move the MBL-3 away from sources of
interference and increase the height
No DGPS position in external
RTCM mode
• Verify that the baud rate of the RTCM input
port matches the baud rate of the external