.. ......................................
.. UHDAS/CODAS restructured text document
.. ......................................


Check: UHDAS is unresponsive?
--------------------------------

.. admonition:: NOTE

        This means the buttons don't respond, or the gui is in some way hung.
        This is not the same as
        `Hopelessly Confused <TS_Hopelessly_Confused.html>`_,
        which is an actual error triggered by a firmware bug.

**If the UHDAS gui is in a strange state:**

(1) kill the ``DAS.py`` process:

   * enter``pkill DAS.py`` at the command line

(2) kill the serial logging processes:

   * look for the processes,

        - ``ps -ef | grep ser_``

   * kill them,

        - ``pkill ser_asc``
        - ``pkill ser_bin``

   * look again to make sure they're gone

        - ``ps -ef | grep ser_``

(3) remove the files in /home/adcp/flags

   * ``rm /home/adcp/flags/*``

(4) If any ``DAS*`` processes cling to life, kill them:

   * ``ps -ef | grep DAS``
   * ``pkill DAS_while_logging.py``
   * ``pkill DAS_while_cruise.py``

(5) Make sure permissions are "all read write" in ``/dev/tty*``

   * find the kind of tty (serial) lines we're using:

       - ``grep tty /home/adcp/config/sensor_cfg.py``

   * look at the permissions for the typs of serial lines used:

       - ``ls -l /dev/ttyS* /dev/ttyUSB*``

   * if any do not have all read and all write permission:

       - ``sudo chmod a+rw /dev/ttyS* /dev/ttyUSB*``

(6) If the serial-USB device lost power, you might need to reboot.
    Do that now

(7) OK to restart the UHDAS.

   * It should find the present cruise and go straight to the Control Tab.