|recovered_cspp||flort_dj_cspp_instrument_recovered||Data Products||Report M2M Stats||Science|
|telemetered||flort_dj_cspp_instrument||Data Products||Report M2M Stats||Science|
|Deployment||Cruise||Start Date||Stop Date||Mooring Asset||Node Asset||Sensor Asset||Latitude||Longitude||Deployment Depth||Water Depth|
No notes yet.
|Metadata||Start Date||End Date||Comment|
||3/8/17, 7:00 PM||4/17/17, 8:00 PM||
The main batteries on CE02SHSP-00005 drained unexpectedly. CSPPs are deployed at 33.4 V. Voltage drops roughly linearly with each profile. Batteries were at 31 V at the beginning of this week. Yesterday (2017-03-09), it reported via acoustic modem that it was in a LOW POWER state, which it does automatically at 28 V to protect the main batteries. In the past, similar drains have been due to faulty connections between the main batteries and the profilers at the battery adapter plates. This has been the CSPP's main failure behavior.
||4/24/17, 8:00 PM||10/4/17, 8:00 PM||
CE02SHSP-00006 reported that it had surfaced unexpectedly April 25 at 5:10 pm local time. Within a few hours it was determined that it was still tethered to its anchor. It's beacon wasn't reporting either. The profiler and its anchor were recovered the following day. Data were sent to the profiler vendor. By April 28 we confirmed there was a firmware bug that had never been seen before. While moving between two positions, the control canister thought the profiler was 20 cm below its destination, but the profiler's winch thought the profiler was 20 cm above its destination, so the profiler was winched up to the surface, instead of retreating 20 cm to its parking depth. The bug will be corrected in the next firmware release. It also turns out that the beacon was programmed improperly, so it had run out of batteries. We switched to a new beacon model this year and confirmed with the vendor which settings to use.
Id: 883 By: michaesm
||5/29/18, 8:00 PM||8/1/18, 4:30 PM||
Profiler was profiling twice per day, but it has not surfaced as planned since May 30 ~1am PDT. It is deployed too far from CE02SHSM for us to have good acoustic communications (1150m vs. the planned 150-400m), so we cannot debug it remotely. It will need to be recovered, but it is not at the surface or adrift, so it does not need immediate recovery.
Id: 1458 By: michaesm