GoMoos Sensor History for Sensor: RMYWM48492
- Manufacturer: RM_Young,
Model: 05106-5
Purchase Date: 2001-04-01
Deployed on Mooring: VI114
- Mooring Details: from 2024-09-09 15:46:00 to 0000-00-00 00:00:00
- Time Event: 2024-09-02 12:54:00, deployed by Lighthouse Marine
- Data_type: wind_gust and Depth: -4 m
Data_type: wind_direction and Depth: -4 m
Data_type: wind_speed and Depth: -4 m
Deployed on Mooring: B0135
- Mooring Details: from 2021-06-16 11:50:00 to 2021-11-03 11:25:00
- Time Event: 2021-06-16 11:50:00, deployed by R/V Connecticut after instrument swap
Time Event: 2021-11-03 11:25:00, recovered by M/V Warren
- Data_type: wind_gust and Depth: -4 m
Data_type: wind_direction and Depth: -4 m
Data_type: wind_speed and Depth: -4 m
Deployed on Mooring: B0134
- Mooring Details: from 2020-09-15 02:21:00 to 2021-06-16 10:45:00
- Time Event: 2020-09-15 02:21:00, deployed by the R/V Connecticut
Time Event: 2020-09-15 18:35:00, recovered by the R/V Connecticut
Time Event: 2021-06-16 11:00:00, recovered by R/V Connecticut prior to instrument swap
- Data_type: wind_speed and Depth: -4 m
Data_type: wind_direction and Depth: -4 m
Data_type: wind_gust and Depth: -4 m
Deployed on Mooring: PR209
- Mooring Details: from 2018-05-08 14:40:00 to 2019-08-12 13:05:00
- Time Event: 2018-05-08 14:40:00, CARICOOS buoy 41053 (PR2 - San Juan) was redeployed at about 1440 GMT.
Time Event: 2019-08-12 13:05:00, recovered by Lighthouse Marine
- Data_type: wind_gust and Depth: -4 m
Data_type: wind_direction and Depth: -4 m
Data_type: wind_speed and Depth: -4 m
Deployed on Mooring: F0129
- Mooring Details: from 2016-10-07 13:10:00 to 2018-01-24 13:09:00
- Time Event: 2016-10-07 13:10:00, Redeployed by R/V PISCES
Time Event: 2016-11-20 00:00:00, Last data received from both cell and goes - datalogger appears locked up?
Time Event: 2016-11-23 05:00:00, Data coms have resumed - both cell and goes reporting valid data once again.
Time Event: 2017-02-09 03:10:00, All communications stopped from this buoy (no cellphone, no Goes).
Time Event: 2017-02-09 09:00:00, Normal communications resumed from this buoy (both cell and Goes). Note: visibility voltage went to a constant 4.9 after reading 0 for past few months.
Time Event: 2017-03-04 01:00:00, Last cellphone transmission from this buoy. Goes transmissions continue to be valid.
Time Event: 2017-06-01 15:15:00, New phone was installed in control box and complete data transfer has resumed once again.
Time Event: 2017-06-23 14:30:00, All communications failed for this buoy (both cell and Goes); probably data logger lockup.
Time Event: 2017-06-24 19:50:00, Buoy is sending valid data once again after probable datalogger lockup.
Time Event: 2018-01-24 13:20:00, Recovered by R/V Connecticut.
- Data_type: wind_speed and Depth: -4 m
Data_type: wind_direction and Depth: -4 m
Data_type: wind_gust and Depth: -4 m
Deployed on Mooring: F0128
- Mooring Details: from 2015-10-28 18:45:00 to 2016-10-06 12:31:00
- Time Event: 2015-10-28 18:45:00, Redeployed (turnaround) by R/V Connecticut
Time Event: 2016-07-12 07:10:00, Last cell phone connection from buoy; backup Goes data stream is still sending good data.
Time Event: 2016-07-14 00:00:00, Cellphone transmissions have resumed once again from this buoy.
Time Event: 2016-10-06 12:31:00, recovered by R/V Pisces
- Data_type: wind_gust and Depth: -4 m
Data_type: wind_direction and Depth: -4 m
Data_type: wind_speed and Depth: -4 m
Deployed on Mooring: F0127
- Mooring Details: from 2014-12-05 17:50:00 to 2015-10-28 11:08:00
- Time Event: 2014-12-05 17:50:00, New control box swapped in by R/V C-Bold
Time Event: 2015-10-28 11:08:00, Recoverd by R/V Connecticut
- Data_type: wind_speed and Depth: -4 m
Data_type: wind_direction and Depth: -4 m
Data_type: wind_gust and Depth: -4 m
Deployed on Mooring: F0126
- Mooring Details: from 2014-06-01 23:05:00 to 2014-12-05 18:02:00
- Time Event: 2014-06-01 23:05:00, Redeployed by R/V Connecticut.
Time Event: 2014-12-05 18:02:00, F0126's data logger/control box being replaced by R/V C-Bold.
- Data_type: wind_gust and Depth: -4 m
Table 'instruments.mooring_events' doesn't exist