Fleet Configurations
Deployments
Gliders
Projects
Payload Bays
Instruments
Users
API
Log In
Deployment ru22-20110823T1112
Pilot Notes
Glider aborted for low charge twice during deployment. 2nd time abort count was reset, downloaded sys.log and showed the software may have crashed: 2011-08-23T12:00:42 mission_surface: (0108.0000): nothing commanded 2011-08-23T11:57:22 mission_start: ru22-2011-234-7-0 (0108.0000) 100_TN.MI 2011-08-23T11:38:16 mission_end: ru22-2011-234-6-0 (0107.0000) 100_TN.MI 2011-08-23T11:33:53 mission_surface: (0107.0000): nothing commanded 2011-08-23T11:30:39 mission_start: ru22-2011-234-6-0 (0107.0000) 100_TN.MI 2011-08-23T11:28:34 APP_start 7.6 2011-08-23T11:26:26 abort_start: MS_ABORT_LOW_REL_CHARGE 2011-08-23T11:26:06 mission_start: ru22-2011-234-5-0 (0106.0000) 100_TN.MI 2011-08-23T11:24:28 mission_end: ru22-2011-234-4-0 (0105.0000) 100_TN.MI 2011-08-23T11:23:58 abort_start: MS_ABORT_BEH_ERROR 2011-08-23T11:23:33 mission_start: ru22-2011-234-4-0 (0105.0000) 100_TN.MI 2011-08-23T11:13:30 mission_end: ru22-2011-234-3-0 (0104.0000) ODCTD.MI Above appears to show (and with some glance at MAfiles) that the mission had half a goto file, yo file was from last deployment and was impossible configuration (climb to 20 m deep in < 20 m water). Many MA files same as last deployment. Fixed MAfiles, put new TBDlist on glider and re-sequenced on 10 min mission. Also c_science_send_all was set to 1, causing ringbuff overload, set it back to 0 and put new 100_tnu.mi mission on there that is updated with fix.
Category
Informational
Alert
Action Needed
Action Taken
Operations
Update
Credentials Required
Username
Password