Slocum Deployment Checklist¶

Print this page

Deployment mission:  ________________________________   Glider S/N:  _____________

Engineer:  _________________________________________   Date:  ________________

1. Startup¶

• Contacts clean and greased; go plug inserted
• ^c  gain control of the glider
• callback 30
• lab_mode on
• report clearall
• where  record m_veh_temp, m_vacuum, m_battery
• Confirm BMS currents are non-zero  m_bms_aft_current, m_bms_ebay_current, m_bms_pitch_current
• boot app → consci → boot app → quit  cycle both processors up
• simul? and dir config — confirm simul.sim is not present in \config

2. Motor Check¶

• use  review device list
• wiggle on, report ++ m_battpos m_fin m_de_oil_vol — leave 5 min
• use again — record any oddities, warnings, or errors, and confirm motors moved their full ranges  m_de_oil_vol −415 : 415 cc · m_battpos −0.9 : 0.9 in · m_fin −0.45 : 0.45 rad
• wiggle off
• ballast
• report clearall
• lab_mode off

3. GPS Check¶

• put c_gps_on 3 — confirm a fix (where, or the V→A flag in the data stream; a fresh almanac can take several minutes)
• put c_gps_on 1
• sync_time

4. Mission Settings & Onboard Status¶

• Test-dive mission file staged (e.g. yo14.ma: num_half_cycles_to_do 2 · d_target_depth 10–20 m · d_bpump_value 500–600 cc · d_target_altitude > 15 m · pitch mode 3, ±0.4538)
• surfac21.ma when_secs set (e.g. 1200 s)
• goto_l10.ma staged — initial waypoint lat/lon recorded and given to the skipper
• run status.mi completes normally  a surface_2 timeout on m_raw_altitude while on the bench is expected and OK
• GPS fix acquired; Iridium connects after the mission
• callback 30 → use → send *.* → data processes successfully
• callback 0 0 — confirm modem connection in SFMC
• callback 1 0 — confirm RUDICS connection in SFMC
• where — m_vacuum > 9 in Hg; get m_de_oil_vol > 415 cc; get m_battpos > 0.9 in
• Air bladder filled and pitch battery all the way forward

MicroRider (if fitted) — mounted securely, MCIL-8-FS cable connected, sensors installed with serial numbers/orientation recorded, bench-calibrated (odas5ir -c all) and 60 s bench-tested with a review of the resulting statistics.

5. Prepare for Launch¶

• Wings attached securely, Phillips screw fastened
• CTD, DO, and other sensor covers removed
• Floats attached and line organized (if used)
• Trolley front ring and securing strap removed
• OK received from the skipper
• Release system prepared

• callback 10, then launch the glider

6. In Water¶

• Glider sitting correctly in the water
• where — record leak-detect voltages  m_leakdetect_voltage_forward > 2.4 · m_digifin_leakdetect_reading > 1018 · m_vacuum > 9
• run status.mi — GPS fix acquired, mission completes normally
• callback 0 0 — confirm modem connection; callback 0 1 — confirm RUDICS connection

7. Science Check¶

• loadmission sci_on.mi — all sensors reporting reasonable values, no oddities
• loadmission sci_off.mi

8. Test Dives¶

• Test dive 1 — depth 10–15 m, ~10 min (when_secs ≈ 1200s) — run <mission>.mi completes normally; record surfacing behaviour, max depth, dive/climb pitch angle, roll, science data
• Floats removed, if fitted
• Test dive 2 — depth 30–50 m, ~20 min (when_secs ≈ 1800s) — edit yo14.ma / surfac21.ma for the deeper dive before running
• Depth increased incrementally on subsequent dives once the glider is flying cleanly

Sign-Off¶

Notes:

___________________________________________________________________________