GoMoos Sensor History for Sensor: SUMAC0902A01107

Manufacturer: Summit,
Model: 34203A
Purchase Date: 2001-12-01

Deployed on Mooring: B0139

Mooring Details: from 2024-12-15 22:02:00 to 0000-00-00 00:00:00
Time Event: 2024-12-15 22:02:00, deployed by R/V Connecticut

Sensor Performance: From 2024-12-15 22:02:00 to 0000-00-00 00:00:00
Data_type: dominant_wave_period and Depth: 0 m
Data_type: significant_wave_height and Depth: 0 m

Deployed on Mooring: B0138

Mooring Details: from 2024-01-03 19:02:00 to 2024-12-15 13:39:00
Time Event: 2024-01-03 19:02:00, instrument swap 10mIM, by UNH diver
Time Event: 2024-12-15 13:39:00, recovered by R/V Connecticut

Sensor Performance: From 2024-01-03 19:02:00 to 2024-12-15 13:39:00
Data_type: dominant_wave_period and Depth: 0 m
Data_type: significant_wave_height and Depth: 0 m

Deployed on Mooring: B0136

Mooring Details: from 2021-11-03 15:46:00 to 2022-09-08 19:35:00
Time Event: 2021-11-03 15:46:00, deployed by M/V Warren
Time Event: 2022-09-08 19:35:00,

Sensor Performance: From 2021-11-03 15:46:00 to 2022-09-08 19:35:00
Data_type: significant_wave_height and Depth: 0 m
Data_type: dominant_wave_period and Depth: 0 m

Deployed on Mooring: B0133

Mooring Details: from 2019-06-01 17:05:00 to 2020-09-14 19:19:00
Time Event: 2019-06-01 17:05:00, deployed by the R/V Connecticut
Time Event: 2020-09-14 19:19:00, recovered by the R/V Connecticut
Time Event: 2020-01-23 15:04:00, cellphone failed, last cellphone data received, cause unknown

Sensor Performance: From 2019-06-01 17:05:00 to 2020-09-14 19:19:00
Data_type: dominant_wave_period and Depth: 0 m

Time:2019-07-15 12:00:00, Status: 1

Comments: Microstrain wave data locked up several times during deployment (talk-through to the port restores the data flow).

Data_type: significant_wave_height and Depth: 0 m

Time:2019-07-15 12:00:00, Status: 1

Comments: Microstrain wave data locked up several times during deployment (talk-through to the port restores the data flow).

Deployed on Mooring: B0131

Mooring Details: from 2018-03-24 00:25:00 to 2018-10-01 06:50:00
Time Event: 2018-03-24 00:25:00, Redeployed by R/V Connecticut.
Time Event: 2018-09-08 02:00:00, Last data received from buoy - phone is not registering and backup satellite transmitter is sending same 'no data available for transmission' message (data logger failure?)
Time Event: 2018-10-01 06:50:00, recovered by R/V Connecticut

Sensor Performance: From 2018-03-24 00:25:00 to 2018-10-01 06:50:00
Data_type: dominant_wave_period and Depth: 0 m

Time:2018-09-08 02:00:00, Status: 1

Comments: Last data received from buoy - phone is not registering and backup satellite transmitter is sending same 'no data available for transmission' message (data logger failure?)

Data_type: significant_wave_height and Depth: 0 m

Time:2018-09-08 02:00:00, Status: 1

Comments: Last data received from buoy - phone is not registering and backup satellite transmitter is sending same 'no data available for transmission' message (data logger failure?)

Deployed on Mooring: B0129

Mooring Details: from 2017-12-08 20:10:00 to 2018-01-25 15:30:00
Time Event: 2017-12-08 20:10:00, Redeployed by R/V Connecticut.
Time Event: 2017-12-13 23:08:00, Last data received from buoy (both cell and goes failed). Note phone was on when logger locked up (23:08)
Time Event: 2017-12-15 13:00:00, Buoy resumed normal operations, calling on both cell and Goes after a complete data logger reset was done remotely.
Time Event: 2018-01-11 17:10:00, last data received from buoy (both cell and GOES failed) note phone was off.
Time Event: 2017-11-28 16:10:00, last data from buoy (during testing in warehouse) - datalogger froze with phone on
Time Event: 2017-11-30 16:10:00, data resumed (logger was manually reset) note this is testing in buoy barn
Time Event: 2018-01-25 17:30:00, Recovered by R/V Connecticut (control box had failed).

Sensor Performance: From 2017-12-08 20:10:00 to 0000-00-00 00:00:00
Data_type: significant_wave_height and Depth: 0 m
Data_type: dominant_wave_period and Depth: 0 m

Deployed on Mooring: B0127

Mooring Details: from 2015-06-04 20:53:00 to 2016-07-08 01:32:00
Time Event: 2015-06-04 20:53:00, Redeployed by R/V Connecticut.
Time Event: 2016-07-08 01:32:00, recovered by R/V Connecticut

Sensor Performance: From 2015-06-04 20:53:00 to 0000-00-00 00:00:00
Data_type: dominant_wave_period and Depth: 0 m
Data_type: significant_wave_height and Depth: 0 m

Deployed on Mooring: B0125

Mooring Details: from 2013-06-20 15:45:00 to 2014-06-01 23:30:00
Time Event: 2013-06-20 15:45:00, Redeployed by R/V Connecticut.
Time Event: 2014-06-01 23:30:00, recovered by R/V Connecticut

Sensor Performance: From 2013-06-20 15:45:00 to 0000-00-00 00:00:00
Data_type: significant_wave_height and Depth: 0 m
Data_type: dominant_wave_period and Depth: 0 m

Deployed on Mooring: B0122

Mooring Details: from 2011-10-07 22:45:00 to 2012-04-15 10:10:00
Time Event: 2011-10-07 22:45:00, Redeployed by R/V Connecticut
Time Event: 2012-02-22 17:05:00, Data logger program apparently became corrupted during a manual connection at 2012-02-22 17:05 and went into low-power mode (phone powered on only at 1800z, 1900z, 2000z).
Time Event: 2012-02-23 18:15:00, A connection was made to the data logger and program was reinitialized. Normal data collection has resumed.
Time Event: 2012-04-15 10:10:00, Recvoered by R/V Delaware II

Sensor Performance: From 2011-10-07 22:45:00 to 0000-00-00 00:00:00
Data_type: dominant_wave_period and Depth: 0 m
Data_type: significant_wave_height and Depth: 0 m

Deployed on Mooring: B0120

Mooring Details: from 2010-06-04 04:41:00 to 2010-10-14 03:45:00
Table 'instruments.mooring_events' doesn't exist