GoMoos Sensor History for Sensor: UMECB332
- Manufacturer: University_of_Maine,
Model: GOM04
Purchase Date: 2010-02-01
Deployed on Mooring: PR213
- Mooring Details: from 2024-08-12 16:35:00 to 0000-00-00 00:00:00
- Time Event: 2024-08-12 16:35:00, deployed by Luis Ramirez
- Data_type: int_temp and Depth: 0 m
Deployed on Mooring: PR212
- Mooring Details: from 2022-05-28 13:30:00 to 2024-08-06 12:15:00
- Time Event: 2022-05-28 13:30:00, Deployed by Lighthouse Marine
Time Event: 2024-08-06 12:15:00, Recovered by Luis Ramirez
- Data_type: int_temp and Depth: 0 m
Deployed on Mooring: PR211
- Mooring Details: from 2021-05-28 15:15:00 to 2022-05-23 16:00:00
- Time Event: 2021-05-28 15:15:00, redeployed by Lighthouse Marine & F/V TanTan
Time Event: 2022-05-23 16:00:00, SMRM Recovered by CARICOOS
- Data_type: int_temp and Depth: 0 m
Deployed on Mooring: PR210
- Mooring Details: from 2019-08-19 15:45:00 to 2021-05-14 17:30:00
- Time Event: 2019-08-19 15:45:00, deployed by Lighthouse Marine
Time Event: 2021-05-14 17:30:00, Recovered for yearly maintenance.
- Data_type: int_temp and Depth: 0 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: int_temp and Depth: 0 m
Deployed on Mooring: PR208
- Mooring Details: from 2017-05-09 11:30:00 to 2018-04-30 10:00:00
- Time Event: 2017-05-09 11:30:00, Deployed by contractor as part of Spring 2017 turnaround
Time Event: 0000-00-00 00:00:00, CARICOOS Buoy 41053 (PR2 - San Juan) was recovered today at about 1000 GMT for maintenance.
Time Event: 2018-04-30 10:00:00, Recovered by Commercial Divers.
Time Event: 2018-04-21 20:00:00, Last cell phone call received from buoy; backup goes transmissions failed earlier.
- Data_type: int_temp and Depth: 0 m
- Time:2017-07-01 16:00:00, Status: 1
- Comments: Last Goes transmission received from the buoy (Goes GPS failure)
- Time:2018-04-21 20:00:00, Status: 1
- Comments: Last cell phone call received from buoy; backup goes transmissions failed earlier.
Deployed on Mooring: PR207
- Mooring Details: from 2016-04-26 12:50:00 to 2017-04-26 12:30:00
- Time Event: 2016-04-26 12:50:00, Deployed by Commercial Divers, Inc
Time Event: 2016-10-22 10:00:00, Buoy recovered by Commercial Divers and towed back to San Juan for work on charging system.
Time Event: 2016-08-04 12:00:00, Battery voltage has started to drop due to apparent problem in charging circuitry.
Time Event: 2016-09-21 21:00:00, Last data received from buoy (low battery issues)
Time Event: 2016-10-29 13:00:00, Redeployed by Commercial Divers. All data valid at this time.
Time Event: 2017-04-26 12:30:00, Recovered for annual maintenance
Time Event: 2017-04-26 12:30:00, Recovered for annual maintenance
- Data_type: int_temp and Depth: 0 m
Deployed on Mooring: PR206
- Mooring Details: from 2015-04-25 14:45:00 to 2016-04-05 09:10:00
- Time Event: 2015-04-25 14:45:00, Redeployed by Commercial Divers.
Time Event: 2016-04-05 09:10:00, Recovered by Commercial Divers.
- Data_type: int_temp and Depth: 0 m
Deployed on Mooring: PR205
- Mooring Details: from 2014-05-22 13:30:00 to 2015-04-06 11:45:00
- Time Event: 2014-05-22 13:30:00, Redeployed by Commercial Divers.
Time Event: 2015-04-06 11:45:00, Recovered by Commercial Divers.
- Data_type: int_temp and Depth: 0 m
Deployed on Mooring: PR204
- Mooring Details: from 2013-05-22 11:35:00 to 2014-05-01 10:30:00
- Time Event: 2013-05-22 11:35:00, Redeployed.
Time Event: 2014-05-01 10:30:00, Recovered by Commercial Divers.
- Data_type: int_temp and Depth: 0 m
Deployed on Mooring: PR203
- Mooring Details: from 2012-06-04 13:20:00 to 2013-05-04 11:45:00
- Time Event: 2012-06-04 13:20:00, Redeployed by CARICOOS.
Time Event: 2013-05-04 11:45:00, Recovered.
- Data_type: int_temp and Depth: 0 m
Deployed on Mooring: PR202
- Mooring Details: from 2011-04-26 13:30:00 to 2012-05-07 11:25:00
- Time Event: 2011-04-25 14:40:00, deployed by contractor barge, San Juan, PR
Time Event: 2012-05-07 11:25:00, Recovered by UPR contractor.
- Data_type: int_temp and Depth: 0 m
Deployed on Mooring: PR102
- Mooring Details: from 2010-05-03 14:20:00 to 2010-07-12 09:55:00
- Time Event: 2010-05-03 14:20:00, Redeployed.
Time Event: 2010-07-12 09:55:00, Recovered by UPRM contractors.
- Data_type: int_temp and Depth: 0 m
Non-Deployment Sensor Events:
- Time Event: 2024-07-03 00:00:00, Event: Prepared
- Comments: Ready for deployment
- Time Event: 2022-05-27 00:00:00, Event: Prepared
- Comments: Ready for deployment
- Time Event: 2022-05-27 00:00:00, Event: Prepared
- Comments: Ready for deployment
- Time Event: 2021-05-21 00:00:00, Event: Prepared
- Comments: Ready for deployment
- Time Event: 2019-08-14 00:00:00, Event: Prepared
- Comments: Ready for deployment
- Time Event: 2018-04-20 00:00:00, Event: Prepared
- Comments: Ready for deployment
- Time Event: 2018-04-20 00:00:00, Event: Prepared
- Comments: Ready for deployment
- Time Event: 2017-04-29 00:00:00, Event: Prepared
- Comments: Ready for deployment
- Time Event: 2017-04-29 00:00:00, Event: Prepared
- Comments: Ready for deployment
- Time Event: 2016-04-16 00:00:00, Event: Prepared
- Comments: Ready for deployment
- Time Event: 2016-04-16 00:00:00, Event: Prepared
- Comments: Ready for deployment
- Time Event: 2015-04-10 00:00:00, Event: Prepared
- Comments: Ready for deployment
- Time Event: 2015-04-10 00:00:00, Event: Prepared
- Comments: Ready for deployment
- Time Event: 2014-05-06 00:00:00, Event: Prepared
- Comments: Ready for deployment
- Time Event: 2014-05-06 00:00:00, Event: Prepared
- Comments: Ready for deployment
- Time Event: 2014-05-06 00:00:00, Event: Prepared
- Comments: Ready for deployment
- Time Event: 2014-05-06 00:00:00, Event: Prepared
- Comments: Ready for deployment
- Time Event: 2013-05-16 00:00:00, Event: Prepared
- Comments: Ready for deployment
- Time Event: 2013-05-16 00:00:00, Event: Prepared
- Comments: Ready for deployment
- Time Event: 2012-06-12 00:00:00, Event: Post-Recovery
- Comments: Data file downloaded
- Time Event: 2012-05-18 00:00:00, Event: Prepared
- Comments: Ready for deployment
- Time Event: 2012-05-18 00:00:00, Event: Prepared
- Comments: Ready for deployment
- Time Event: 2011-04-18 00:00:00, Event: Prepared
- Comments: Ready for deployment
- Time Event: 2011-04-18 00:00:00, Event: Prepared
- Comments: Ready for deployment
- Time Event: 2011-04-18 00:00:00, Event: Prepared
- Comments: Ready for deployment
- Time Event: 2011-04-12 00:00:00, Event: Prepared
- Comments: Ready for deployment
- Time Event: 2011-04-12 00:00:00, Event: Prepared
- Comments: Ready for deployment
- Time Event: 2010-04-07 00:00:00, Event: Prepared
- Comments: Ready for deployment
- Time Event: 2010-04-07 00:00:00, Event: Prepared
- Comments: Ready for deployment
- Time Event: 2010-03-24 00:00:00, Event: Prepared
- Comments: Ready for deployment
- Time Event: 2010-03-12 00:00:00, Event: Prepared
- Comments: Ready for deployment
- Time Event: 2010-03-12 00:00:00, Event: Prepared
- Comments: Ready for deployment
- Time Event: 2010-03-10 00:00:00, Event: Prepared
- Comments: Ready for deployment
- Time Event: 2010-03-10 00:00:00, Event: Prepared
- Comments: Ready for deployment
- Time Event: 2010-03-05 00:00:00, Event: Prepared
- Comments: Ready for deployment
- Time Event: 2010-03-01 00:00:00, Event: Prepared
- Comments: Ready for deployment
- Time Event: 2010-02-23 00:00:00, Event: Prepared
- Comments: Ready for deployment
- Time Event: 2010-02-22 00:00:00, Event: Prepared
- Comments: Ready for deployment