Lithium Ion Set : Orsted

^W name in ALLCAPS means CRITICAL device (* => SUPERCRITICAL)
[I Installed] [- Not_Installed]
[u In_use] [- Not_In_use] [X Out_of_Service]
name limits stats (#total/#mission/#segment)
os w/s w/m os errors warnings oddities
0 simdrvr -
1 test_driver -
2 ARGOS* I u -1 20 5 0
3 WATCHDOG I u -1 -1 -1 0
4 DEADMAN I u -1 20 5 0
5 CONSOLE* I u -1 20 5 0
6 GPS I u -1 20 5 0 [ 0 0 0] [ 187 9 1] [ 0 0 0]
7 attitude_rev I u 3 20 5 0
8 ocean_pressure I u 3 20 5 0 [ 0 0 0] [ 0 0 0] [ 35 0 0]
9 vacuum I u 3 20 5 0
10 battery I u 3 20 5 0
11 air_pump I u 3 20 5 0
12 pitch_motor I u 3 20 5 0 [ 0 0 0] [ 0 0 0] [ 103 4 0]
13 science_super I u 3 20 5 0 [ 0 0 0] [ 4 0 0] [ 50 1 0]
14 digifin I u 3 20 5 0 [ 0 0 0] [ 10 0 0] [ 553 13 2]
15 altimeter I u 3 20 5 0
16 IRIDIUM* I u -1 20 5 0 [ 0 0 0] [ 0 0 0] [ 138 2 0]
17 leakdetect I u 3 20 5 0
18 recovery -
19 coulomb I u 3 20 5 0 [ 0 0 0] [ 0 0 0] [ 81 1 1]
20 veh_temp I u 3 20 5 0
21 BUOYANCY_PUMP I u 3 20 3 0
22 DE_PUMP -
23 HD_PUMP -
24 thruster -
devices:(t/m/s) errs: 0/ 0/ 0 warn: 201/ 9/ 1 odd: 960/ 21/ 3

Changed missions to 100_n.mi for station keeping until recovery tomorrow

-150/215

Realized even if I run optode all the time there will be no CTD data (pressure) so time shifting would have to be done on glider pressure?

At the expense of some live profiles, going to try it out, thinking better to have it vs glider pressure than not at all.

Optode on all the time, but only sending back every other yo, ctd at 1,6,11,16
optode will sync up on 6 and 16, hopefully 2 yo's of oxygen

-165/215 cc

-185,230 cc

-200/245 cc

Started science duty cycling (primarily CTD to make less noise). CTD and optode to 5th yo to sample so 1,6,11

Trying optode duty cycling which we have never done. Makes the TBD easier and is sure to include the first cast.

Seems best match up would be TBD every 2 yo's and CTD ever 3rd yo. That would line up optode and CTD every 4, 10 ,16 , etc. If we had to switch optode to all the time.

Or we just don't sample the first yo but then we miss the upper 2 m.

Created ru34.mi

# ru34
# 2020/8/5 dkaragon initial

sensor: u_reqd_depth_at_surface(m) 2.3

sensor: u_hd_fin_ap_gain(1/rad) 1.50
sensor: u_hd_fin_ap_igain(1/rad-sec) 0.02
sensor: u_hd_fin_ap_dgain(sec/rad) 8.00

sensor: u_heading_deadband(rad) -1

sensor: u_hd_fin_ap_hardover_holdoff(sec) 30.0

sensor: f_fin_safety_max(rad) 0.45


Started slowing glider down.

-220 / 265 cc

May have had some science transfer lock ups? Not sure if because of storm or not, seems coincidental.
Starting zModem transfer of 00580046.tbd to/from ru34 size is 16143
Total Bytes sent/received: 1024
Total Bytes sent/received: 2048
Total Bytes sent/received: 3073
Total Bytes sent/received: 3072
Total Bytes sent/received: 4096
Total Bytes sent/received: 5120
Total Bytes sent/received: 5120
Total Bytes sent/received: 6144
Total Bytes sent/received: 6656
Total Bytes sent/received: 6688
Total Bytes sent/received: 6720
Total Bytes sent/received: 6752
Total Bytes sent/received: 6784
Total Bytes sent/received: 6816
Total Bytes sent/received: 6848
Total Bytes sent/received: 6880
Total Bytes sent/received: 6912
Total Bytes sent/received: 6944
Total Bytes sent/received: 6976
Total Bytes sent/received: 7008
Total Bytes sent/received: 7040
Total Bytes sent/received: 7072
Total Bytes sent/received: 7104
Total Bytes sent/received: 7136
Total Bytes sent/received: 7168
Total Bytes sent/received: 7200
Total Bytes sent/received: 7232
Total Bytes sent/received: 7264
Total Bytes sent/received: 7296
Total Bytes sent/received: 7328
Total Bytes sent/received: 7360
Total Bytes sent/received: 7392
Total Bytes sent/received: 7424
Total Bytes sent/received: 7456
Total Bytes sent/received: 7488
Total Bytes sent/received: 7520
Total Bytes sent/received: 7552
Total Bytes sent/received: 7584
Total Bytes sent/received: 7616
Total Bytes sent/received: 7648
Total Bytes sent/received: 7680
Total Bytes sent/received: 7712
Total Bytes sent/received: 7744
Total Bytes sent/received: 7776
Total Bytes sent/received: 7808
Total Bytes sent/received: 7840
Total Bytes sent/received: 7872
Total Bytes sent/received: 7904
Total Bytes sent/received: 7936
Total Bytes sent/received: 7968
Total Bytes sent/received: 8000
Total Bytes sent/received: 8032
Total Bytes sent/received: 8064
Total Bytes sent/received: 8064
Total Bytes sent/received: 809

Glider connection hung at this point, disconnected via SFMC but didn't call back in. No File transfer script turned on.

Initial noise report from Mark B.:
Currently operating 8 KB / hour max limit
Noise bands caused by pumped CTD. 350 and 700 kHz. Solution = less CTD.
Low frequency noise caused by eddies across hydrophone. Solution = go slower.

zero_ocean_pressure, it was reporting 1 m, did it shortly after calling in

U_reqd_depth_at_surface 2.3

See how it does...

7/31 15 GMT : U_heading_deadband turned off , u_hd_fin_ap_dgain set to 6

Appears to have helped, still need some work with instant gain or fin offset to fix strong drifting to one side.

2 x iridium possible lockups after consci ---> quit ---> bad char received ---> send *.tbd. Happened during testing and on deployment. Haven't seen it since.

Deployment went well except m_pressure showed strong drifting during surfacing and during segment. During test missions initially m_pressure drifted deeper over the course of segment from about 1 m at surface to about 3.5 at surface.

Eventually I zero'd the pressure right after a surfacing. This would be the important time to have it zero'ed since that is what is bases surfacing completion as.

Since deployment it appears to be drifting less overall. Based on surfacings it appears to be drifting upward (shallower) over the course of a surfacing by about 0 to 4 m. Average < 1 m. At call in its usually reading < .5 m which is good.

ru34 ECO-PAM deployment 1
ctd 9646 pumped: 2020-01-17
optode 1504: 2019-09-26
dmon 3A231D06: no cal date
RXLive 457001: no cal date
OS: 10.1beta