Diff: new_changelog.txt

Revision:

84:eccd8e837134

Parent:

76:c802e1da4179

Child:

85:dd8176285b6e

--- a/new_changelog.txt	Fri Feb 15 16:14:22 2019 +0000
+++ b/new_changelog.txt	Tue Feb 19 20:11:43 2019 +0000
@@ -72,4 +72,16 @@
         - Did not check roll
         - KNOWN ISSUE of log file not having consistent line length (will throw off python data receiver)
     Modified code at Carderock (2018-08-16)
-        - Observations at LASR lead to fixes on the save PID files, zero offsets were saving incorrectly, fixed
\ No newline at end of file
+        - Observations at LASR lead to fixes on the save PID files, zero offsets were saving incorrectly, fixed
+    2019 feb 15 Modified code jcw
+        - LogOO?.csv name and version number is set with logvers.txt
+        - DIAG00?.txt likewise set with logvers.txt
+        - diagnostic logging to diagnostics file
+        - legfile.txt sets parameters ( max-depth, min_depth, heading, timeout, yo_time)  for a dive leg, after which mbed program ends
+             to allow monitor computer to access via usb filesystem
+        - added states:  Leg_position_dive, leg_position_rise,  fb_exit to handle above yo-yo leg and exit
+             have not yet added these states in menu operations.
+        STILL TO DO:
+        -  test size of log file and set new log file name and update logvers.txt
+        -  allow for something other than 0=leg  in legfile.txt so that state will NOT drop into legfile.txt operations mode
+        -  add access to leg_position_dive ( with exit??)  to menu operations  -maybe
\ No newline at end of file