-
Notifications
You must be signed in to change notification settings - Fork 0
Open
Labels
firmwareIssues related to glider software/firmwareIssues related to glider software/firmwarehardwareIssues related to glider hardwareIssues related to glider hardware
Description
During Sea019 M49, we experienced several "Ballast" alarms. Because we didn't know what was causing them, and the glider had only just been deployed, we decided to recover it and replace with Sea021.


Apparently this alarm occurs when the ballast position goes farther than the ballast command, but we have no indication what could have caused that to happen (at least twice).
Note that this was with Sea019, which is the glider which on a previous mission (M43) not only hit the bottom several times, but also lost the dropweight and drifted at the surface for several days. The possibility that something may have happened to the glider shouldn't be discounted.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
firmwareIssues related to glider software/firmwareIssues related to glider software/firmwarehardwareIssues related to glider hardwareIssues related to glider hardware