Glider aborted for no pitch battery movement. Battery was halted at .5 in foreward. Batt_vel was 0.0000 which only matched 2/10 battery vel on ru23 for pitch motor disconnected. No attempt was made to put pitch back into service or reset the glider. Thrusting was done on climbs (5 deg fixed pitch angle) to swim and appeared to be working.

CTD pump suspected dead as well. Noticed 3/11-12 time frame.

Recovered by David & Nicole out of AC aboard Sea Tow 26 foot. Performed CTD cast corresponding to segment ru30-2019-071-7-0
(0285.0000) on flume toughbook.

Some strange file creations, yo, goto, etc. Result of which went north for a bit and going to miss a segment of TBD FLBBCD data.

Also

70 SCI: oxy4_run(): 0 error(s) in a row. (5 is fatal)
216270 SCI: oxy4_run(): 0 error(s) since oxy4_begin(). (50 is fatal)
216270 SCI:PROGLET sbe41n_ph start() called
216270 SCI: sbe41n_ph_run(): 0 error(s) in a row. (5 is fatal)
216270 SCI: sbe41n_ph_run(): 0 error(s) since sbe41n_ph_begin(). (50 is fatal)
216281 37 DRIVER_ODDITY:science_super:1800:sbe41n_ph_run, 687: Max error limit reached (1)
216281 DRIVER_ODDITY:science_super:1800:ERROR from PROGLET sbe41n_ph : 1003
216281 DRIVER_ODDITY:science_super:1800:PROGLET sbe41n_ph_run() recently generated an error: 1003
216281 DRIVER_ODDITY:science_super:1800: sbe41n_ph_run(): 1 error(s) in a row. (5 is fatal)
216281 DRIVER_ODDITY:science_super:1800: sbe41n_ph_run(): 1 error(s) since sbe41n_ph_begin(). (50 is fatal)
216332 02770035.mlg LOG FILE OPENED

--------------------------------
216333 behavior surface_4: SUBSTATE 7 ->7 : After data transmission, waiting for control-C to exit/resume

Science holding up this order of operations? Test in lab?

!zr

--------------------------------
216383 49 save_and_change_sensors()....
Changed u_use_ctd_depth_for_flying from 0 to 0
Changed c_science_on from 1 to 0
216383 save_and_change_sensors()....
Changed c_science_printout from 0 to 0
Waiting for motors idle

DELAY science crash

Some strange file creations, yo, goto, etc. Result of which went north for a bit and going to miss a segment of TBD FLBBCD data.

Really need to look at science oddities and get the science logging crashes figured out, pH caused? What's causing it. Surfacings from not too long before this note look strange.

Noisy CTD pressure sensor, about .25 m peak to peak.
CTD s/n 9417

TBD to every 3rd, optics on every 3rd as of PM 3/8. Heading back onshore.

Pressure sensor on this CTD looks noisy too, peak to peak about .25 m

Changed TBD to every 4th yo, perhaps until we get offshore and the winds die (1-2 days). Losing to currents currently.

Optics every other yo. May change optics and TBD to every 3rd yo after it hits waypoint.

New plan is to run ELINES as much as we can.

Note regarding lithium lifetime:
2019 pH 1: 120 / 205 AH used
Lithium ions charged prior to deployment: 10.123 AH 8 23 = 232 AH
Lithium ions in lab about 44.2% charge level = 4.470 AH / cell --> (23 * 4.470) = 103 AH remaining
According to packs we used about 129 AH, glider 120 AH
5.65 / 10.123 AH used = 56 % used
120/205 = 58.5% used, pretty close
~ 205 AH for winter mission

CTD off at surface starting late PM 3/5

Abort for stalled for 3 am est 3/4. Glider appeared to dive normally but abandoned dive. Thinking a timer was running during surface interval that shouldn't have been. Must have been stalled for abort timer? m_pressure was stuck for surfacing?

Dave checked pressure sensor on surface; looks good. u_reqd_depth_at_surface to 2m via script, dive-to from 4.5 to 4.25m, climb-to from 4 to 3.25m; all on next surfacing.

Still pH errors turning science on/off during surfacing. Should report to TWR.

CTD s/n 9417
pH s/n C18
FLBBCDSLC s/n 4662
Optode Oxy4 s/n 242

Deployed 2/27 11 EST by Chip, Dave, Liza, Brandon G. out of Morgan Marine aboard RV rutgers.

sb19 1654 was present and water samples taken at 10 m and 25 ft

Glider Config: (same as last mission except with a different optode)

CTD s/n 9417
pH s/n C18
FLBBCDSLC s/n 4662
Optode Oxy4 s/n 242


OS 8.1


project: OTIC pH

POC: Aragon, Haldeman, Waite
Deployment Time: 2/27/19 at 16:25GMT

CTD s/n 9417
pH s/n C18
FLBBCDSLC s/n 4662
Optode Oxy4 s/n 242