All Notes (25)
Lithium Ion Set: Challenger
compass check after recovery log file 0345.0001
recovered by Scott and USVI team 10/1/19 2:15pm local
new Goto to head back to STT for recovery
!! u_alt_min_depth 800 !!
u_reqd_depth_at_surface 5
Got stuck in surface beh spam mode again.
This time it abandoned dive at like 8 m because m_speed was 0 --> not moving horiz caused by low pitch angle because c_pitch was +30 deg which is the setting for climb to surface
So surface behavior didn't relinquish control properly.
possible compass problems.... potential for next trip compass, calibration rig, and hand compass for verification
!!! u_alt_min_depth 80 !!!
Glider missed call in's. Same nature as ru26's
Grabbed MLG
the8x3_filename: 03390037
full_filename: ru29-2019-255-2-37
93 sensor: m_gps_lat = 1816.6736 lat
209889 sensor: m_gps_lon = -6354.4195 lon
209889 sensor: m_gps_status = 0 enum
209892 93 end_gps_input()
209892 behavior surface_2: SUBSTATE 5 ->7 : waiting for control-C to exit/resume
209903 95 Iridium has been powered on for 4.7 secs
209903 Waking up Iridium... sending:ATE1
209903 Iridium, modem making attempt #1 at primary number (881600005368)
209908 97 Iridium driver received:[ATE1[0D][0D]]
209908 Iridium modem matched: OK
209908 Waking up Iridium... sending:AT+cbst=6,0,1
209912 98 Iridium driver received:[AT+cbst=6,0,1[0D][0D]]
209913 Iridium modem matched: OK
209913 Waking up Iridium... sending:AT+CSQ
209917 99 Iridium driver received:[AT+CSQ[0D][0D][0A]+CSQ:5[0D][0A][0D]]
209917 Iridium modem matched: OK
209922 0 Iridium waiting for registration...
209931 1 Obtaining Iridium RSSI...
209931 Iridium dialing [ATD00881600005368]...........
209931 Iridium waiting for connection...
209936 2 Iridium driver received:[ATD00881600005368[0D]]
209950 6 Iridium waiting for connection...
209967 8 Iridium waiting for connection...
209986 12 Iridium waiting for connection...
210004 17 Iridium waiting for connection...
210024 20 Iridium waiting for connection...
210033 23 Iridium driver received:[[0D]]
210033 Iridium modem matched: NO ANSWER
About 6 m down off surface MLG reported stuck not moving horizontally. Not really sure why. It was diving OK seemingly and steering. Part of MLG and MBD downloaded.
When it surfaced after this it was in beh_arg spam mode just like a few days ago.
Exited mission and re-sequenced. Not sure if this is related to the surfacing 'altimeter hit caused dive/climb to complete same cycle' or not.
the8x3_filename: 03390046
full_filename: ru29-2019-255-2-46
u_alt_min_depth 5
!!!!!!!! U ALT MIN DEPTH 650 !!!!!!!!!!!!!!!
!!!!!!!! U ALT MIN DEPTH 650 !!!!!!!!!!!!!!!
back to 1sec DVL interval, still just downcasts.
Segment ru29-2019-254-0-2 (0336.0002) was the 90 sec DVL interval segment. DVL file si121512.pd0
Running inshore to start line.
Running DVL at 90 second interval, same dvl.ini settings to see if we can get a file back from deep water to see how returns are down deep.
just dives
Glider came up in behavior spam mode. Caused some short surfacings.
Thought is maybe climb to depth on yo, 4 m, was way too shallow and caused a software loop. Backed that off to 12. Should have been 12 but 4 was leftover from 30 m test mission.
57085 behavior yo_6: argument: d_speed_min = -100.000000 m/s
57085 behavior yo_6: argument: d_speed_max = 100.000000 m/s
57085 behavior yo_6: argument: d_use_thruster = 0.000000 enum
57085 behavior yo_6: argument: d_thruster_value = 0.000000 X
57085 behavior yo_6: argument: d_depth_rate_method = 3.000000 enum
57085 behavior yo_6: argument: d_wait_for_pitch = 1.000000 bool
57085 behavior yo_6: argument: d_wait_for_ballast = 100.000000 sec
57085 behavior yo_6: argument: d_delta_bpump_speed = 50.000000 X
57085 behavior yo_6: argument: d_delta_bpump_ballast = 25.000000 X
57085 behavior yo_6: argument: d_time_ratio = 1.100000 X
57085 behavior yo_6: argument: d_use_sc_model = 0.000000 bool
57085 behavior yo_6: argument: d_max_thermal_charge_time = 1200.000000 sec
57085 behavior yo_6: argument: d_max_pumping_charge_time = 300.000000 sec
57085 behavior yo_6: argument: d_thr_reqd_pres_mul = 1.500000 nodim
57086 behavior yo_6: argument: c_target_depth = 4.000000 m
57086 behavior yo_6: argument: c_target_altitude = -1.000000 m
57086 behavior yo_6: argument: c_use_bpump = 2.000000 enum
57086 behavior yo_6: argument: c_bpump_value = 260.000000 X
57086 behavior yo_6: argument: c_use_pitch = 3.000000 enum
57086 behavior yo_6: argument: c_pitch_value = 0.453786 X
57086 behavior yo_6: argument:
***
57110 behavior yo_6: d_use_pitch(enum)=3.000000
57111 behavior yo_6: d_pitch_value(X)=-0.453786
57111 behavior yo_6: d_stop_when_stalled_for(sec)=180.000000
57111 behavior yo_6: d_stop_when_hover_for(sec)=180.000000
57111 behavior yo_6: c_target_depth(m)=4.000000
57111 behavior yo_6: c_target_altitude(m)=-1.000000
57111 behavior yo_6: c_use_bpump(enum)=2.000000
57111 behavior yo_6: c_bpump_value(X)=260.000000
57111 behavior yo_6: c_use_pitch(enum)=3.000000
57111 behavior yo_6: c_pitch_value(X)=0.453786
DVL settings/power tests, all segments between 30 m and now, new segment:
Ran with same settings as 30 m test mission today @ 2 sec MA rate
WD111100000
WB0
WN15
WP00005
WF0088
WS200
BP000
BX00800
TP00:00.00
EX00000
EZ10000010
#EJ-1100
#EY 0 0 0 0 0 0 8 0
950m DVL test. Segment ru29-2019-253-1-0 (0334.0000)
sample43.ma: state_to_sample = 7 (dives and climbs); intersample_time = 2sec
DVL Settings:
WD111100000
WB0
WN15
WP00005
WF0088
WS200
BP000
BX00800
TP00:00.00
EX00000
EZ10000010
#EJ-1100
#EY 0 0 0 0 0 0 8 0
30m DVL test. Segment 0333.0000 (ru29_2019_253_0_0). DVL file = si111547.pd0
sample43.ma: state_to_sample = 3 (dives); intersample_time = 4sec
DVL Settings:
WD111100000
WB0
WN15
WP00005
WF0088
WS200
BP000
BX00800
TP00:00.00
EX00000
EZ10000010
#EJ-1100
#EY 0 0 0 0 0 0 8 0
u_reqd_depth_at_surface 3.5
SHOULD loadmission ru29.mi or at least set it manually at surface
Some issues with dvl.ini. Possibly came down to can't have comments.
Currently running:
WD111100000
WB0
WN15
WP00001
WF0088
WS200
BP000
BX00800
TP00:00.00
EX00000
EZ10000010
#EJ-1100
#EY 0 0 0 0 0 0 8 0
Did a short cast and downloaded a pd0 file: ru29-2019-252-3-0 : si101533.pd0
Back to 950 m dives, still need to figure out TBDLIST settings for run, Doug wants high resolution
DVL off since deployment
shallow angle yo's to clear reef on accidental shallowing run
deeper and heading towards AN2
CTD S/N 0098 pumped - 2018-03-08
Ocean Innovations Doppler Velocity Log (DVL) S/N 669711 - 2016-05-24
Deployed by Doug Wilson,Chip Haldeman,Matthew Mullins and Elisha Brumant out of Red Hook, St. Thomas aboard the Doubleheader