.. troubleshooting documentation master file, created by sphinx-quickstart on Wed Jan  7 13:24:57 2009.
   You can adapt this file completely to your liking, but it should at least
   contain the root `toctree` directive.

Troubleshooting
===============

If for some reason the figures quit updating, check the panels and
make sure everything is green and active. If they are, DON'T ADJUST
ANYTHING: the raw data are being logged, but the processing software
hit a glitch for some reason. The ADCP Operator may start data
acquisition again under a new cruise name (eg. adding a letter to the
cruise name) in an attempt to re-initialize the processing, but if
this still does not revive the figures after several hours, email us
and we will try to help.

You might find the UHDAS serial communication tool
:ref:`tk_terminal.py <tk_terminal>` to be helpful.

There is also a different section about :ref:`ADCP failure modes <adcp_failure_modes>`
which may help.

.. toctree::
   :maxdepth: 2

   Troubleshooting Serial Feeds (beware ZMQ) <zmq_troubleshooting>
   Interpreting Accurate Heading NMEA messages <serial_nmea/index>
   Troubleshooting Speedlog <speedlog/index>
   NTP diagnostics <ntp/index>
   Hopelessly Confused message <TS_Hopelessly_Confused>
   Gui is Hung?  <TS_StrangeState>
   Diagnostic tools <diagnostic_tools/index>