Navigation

  • index
  • next |
  • previous |
  • UHDAS+CODAS 2019.10.15-python3 documentation »
  • 3. UHDAS Operations Guide »
  • 3.3. Troubleshooting »
CODAS+UHDAS Documentation

Home

  • 1. CODAS ADCP Processing
  • 2. CODAS Installation
  • 3. UHDAS Operations
    • 3.1. UHDAS at sea
    • 3.2. Monitoring the System
    • 3.3. Troubleshooting
      • 3.3.1. Troubleshooting Serial Feeds (beware ZMQ)
      • 3.3.2. Interpreting Accurate Heading NMEA messages
      • 3.3.3. Troubleshooting Speedlog
      • 3.3.4. NTP diagnostics
      • 3.3.5. Hopelessly Confused message
      • 3.3.6. Gui is Hung?
      • 3.3.7. Diagnostic tools
    • 3.4. HOWTOs
    • 3.5. UHDAS Computer
  • 4. ADCP Data: Examples
  • 5. Appendix
  • 6. Glossary

Previous topic

3.3.1. Troubleshooting Serial feeds: check ZMQ first

Next topic

3.3.2.1. Ashtech Diagnostics

This Page

  • Show Source

Quick search

3.3.2. Interpreting NMEA messagesΒΆ

This section shows the NMEA messages used for accurate heading on various ships. It is useful to be able to inspect the NMEA messages directly, to see the failure in the QA messages

  • 3.3.2.1. Ashtech NMEA messages
    • 3.3.2.1.1. $PASHR,ATT messages
    • 3.3.2.1.2. $PASHR,AT2 messages
    • 3.3.2.1.3. $GPPAT messages
    • 3.3.2.1.4. Indications of bad data:
    • 3.3.2.1.5. checking on UHDAS computer
  • 3.3.2.2. Seapath NMEA messages
    • 3.3.2.2.1. $PSXN,20 messages
  • 3.3.2.3. POSMV NMEA messages
    • 3.3.2.3.1. $PASHR message
  • 3.3.2.4. MAHRS messages
    • 3.3.2.4.1. TSS1 message
    • 3.3.2.4.2. Interpreting the Status Flag

Navigation

  • index
  • next |
  • previous |
  • UHDAS+CODAS 2019.10.15-python3 documentation »
  • 3. UHDAS Operations Guide »
  • 3.3. Troubleshooting »
© Copyright 2009, J. Hummon. Created using Sphinx 2.1.1.