48 |
Troubleshooting | HS80/HS80A/MX575C/MX575D User Manual
Troubleshooting
Table A-1 provides troubleshooting for common problems.
Table A-1: Troubleshooting
Symptom Possible Solution
Receiver fails to power • Verify polarity of power leads
• Check integrity of power cable connectors
• Check power input voltage (6 to 36 VDC)
• Check current restrictions imposed by power source
(minimum available should be > 1.0 A)
No data from HS80/HS80A
(N2K Network connection)
• Check N2K connectivity using the Device List from the
CDU.
• Check integrity and connectivity of power and data
cable connections
No data from MX575C/
MX575D (NMEA -0183
connection)
• Check receiver power status to ensure the receiver is
powered (an ammeter can be used for this)
• Verify desired messages are activated (using the CDU or
$JSHOW command in any terminal program)
• Ensure the baud rate of the smart GPS compass matches
that of the receiving device
• Check integrity and connectivity of power and data
cable connections
Random data from
smart GPS compass
• Verify the RTCM or binary messages are not being output
accidentally (send a $JSHOW command)
• Ensure the baud rate of the smart GPS compass matches
that of the remote device
• Potentially, the volume of data requested to be output
by the smart GPS compass 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 smart GPS compass has a clear view of the sky
• Verify the lock status of GPS satellites (this can be done
with using the MFD or CDU)
No SBAS lock • Verify the smart GPS compass has a clear view of the sky
• Verify the lock status of SBAS satellites (this can be done
using the CDU)
• 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.
5
To Next Page
Loading...
Need help?
General
