All Notes (15)
Bottom sample from previous mission analysis: unsure of why it hit bottom, potentially due to the last accepted altimeter hit providing a positive altitude_rate. If the code is the same as copy on hand that means it ignores turning around by altimeter or water_depth.
emailed TWR about solutions and updates.
Bad hit occurred at about 3.5 m from bottom. Perhaps increasing min altitude to near 4 m could help prevent.
Unsure if this is a G3S issue, an ru34 altimeter issue, or what but its a little unusual.
Lithiums were MARA/HURRI set. Some of the cells didn't show discharge.
Cell Serial Volts Charge_AH Capacity_AH Percent_Charge
1 111 13.822 6.808 9.583 71
2 119 13.817 6.258 9.509 66
3 136 13.82 6.513 9.48 69
4 147 13.824 6.615 9.515 70
5 150 13.827 1.695 9.644 18
6 167 13.827 6.422 9.579 67
7 182 13.832 1.678 9.558 18
8 272 13.833 6.986 9.737 72
9 754 13.854 1.698 10.113 17
10 760 13.855 1.714 10.094 17
11 864 13.851 1.707 10.104 17
12 868 13.84 1.752 10.243 17
13 888 13.849 1.718 10.082 17
14 890 13.847 1.712 10.083 17
15 901 13.842 1.776 10.112 18
16 902 13.841 1.729 9.903 17
17 935 13.846 1.756 10.129 17
18 936 13.842 1.744 10.038 17
19 939 13.844 1.759 10.161 17
20 950 13.842 1.737 9.963 17
21 955 13.843 1.752 10.045 17
22 956 13.844 1.722 9.977 17
23 961 13.833 1.703 9.987 17
According to batteries 69/227 AH. 172 AH used by the glider. If we go by that: 227 - 172 = 55 AH. That is pretty close to 69. But my speculation is if all the batteries drained equally then we probably have about 1.7 AH each * 23 = 39 AH left. 227-39 = 188. So we are within 16 Ah one way and 14 Ah the other way.
Recovered by Dave Aragon, Nicole Waite, and Chip Haldeman on R/V Rutgers out of Tuckerton. Double recovery with RU33.
Comparison CTD cast at recovery done with SB19 a/n 1645 and ballast tank laptop.
12/15 21:30 single bottom sample
u_reqd_depth_at_surface 2
Steering parameters are OK. Steering is great this mission, updated in ru34.mi. Keep alignments same for future mission.
Undo parameters script set by accident, steering. Reminder.
Changed surfac40 no_comms surface time to 390 seconds since TWR analog seems a bit unreliable with missed calls. Lowered it so glider doesn't sit on surface forever.
Investigate digifin warnings and OOD spam, usually see it in wind, see it all the time now on this glider.
Confirmed iridium jarble issue on 2 RU and 1 DAL glider.
ru34 less transfer beh aborts on analog line it seems like, only 1 since Saturday.
Should check last deployment and see if any during the other iridium RUDICS outage.
Iridium issue not time dependent certainly bad initially but problem persists for many minutes (repeatedly typing where command and looking for dropped chars).
Switched to TWR backup, don't like the jarble thing going on.
Document this to TWR, science consci quit then issues....
SciDos>quit
Returning from SciDos
8037 96 Freewave console restored
REVERTING FROM SCIENCE COMMAND MODE
SCIENCE COMMAND MODE TERMINATED because:
Science Program QUIT (cts lowered)
GliderDos N -1 > 8039 97 BAD LINE from science:C" 8764 bad type character 115
8039 DRIVER_ODDITY:science_super:1805:BAD LINE from science:
8039 DRIVER_ODDITY:science_super:1800:gc_handle_clothesline_input: Unknown line received from glider:
8039 DRIVER_ODDITY:science_super:1800: ) 1997
8039 SCI_WARNING:1801:FATAL ERROR from glider_comms_run_clothesline(): 107
8039 DRIVER_WARNING:science_super:1801:Deferred warning from clothesline, See prior oddity
Strange bottom sample 11/26 10GMT. If nothing else an altimeter ground truth but should look into what happened.
Possible surfacing with iridium jarbled message problem again!
Flying well default fin settings.... but u_hd_fin_ap_dgain to 5, ap fin time to 8 sec, and hardover holdoff to 30 sec.
u_reqd_depth_at_surface 2.5
Boat was R/V Rutgers out of Tuckerton - Chip and Nicole on the boat, Dave piloting.
ru34 ECO-PAM deployment 4
ctd 9646 pumped: 2020-01-17
optode 1504: 2019-09-26 factory cal; 11/13/2020 in-house check
dmon 3A231D06: no cal date
RXLive 457001: no cal date
OS: 10.01
