EVENT LOG FOR SITE BO3 The first line of each entry contains a date/time stamp & who is reporting. The most recent entry is listed first. Date Time Who ---------- ----- -------- 01/02/2013 07:41 Troy@bay 01:LowLithium,15:TestTagFailure: These alarms will be addressed tomorrow during a site visit. 01/01/2013 10:23 troy@bay 01:LowLithium,15:TestTagFailure: Well documented alarms, clearing TASS. 12/31/2012 08:24 troy@bay 01:LowLithium,15:TestTagFailure: Low Lithium will be addressed on the next site visit. 12/30/2012 09:03 troy@bay 01:LowLithium,15:TestTagFailure: 01 will be addressed on the next site visit. 15 is a known problematic antenna, clearing TASS. 12/29/2012 09:07 troy@bay 01:LowLithium,15:TestTagFailure: Ladder is dewatered, clearing TASS 12/27/2012 08:54 Troy@bay 01:LowLithium,15:TestTagFailure: This ladder is de-watered, clearing TASS. 12/26/2012 12:35 Troy@bay 01:LowLithium,11:Overrun,15:TestTagFailure: Water is de-watered, clearing TASS. 12/19/2012 09:05 Alan The Network cabinet UPS in the BO3/BO4 network cabinet failed at ~1330PST 12-18-2012. Dean Ballinger bypassed the failed unit at ~0845PST 12-19- 2012. The UPS will be replaced at the next opportunity. 12/18/2012 14:43 Scott_Li Zymon shows both DSL lines down at Bonneville. Called Centrylink and placed trouble ticket. They indicated that the line at B2J is passing traffic one way but not the other. The BO3 line shows completely dead. Ticket numbers: 427.5359 is 5032423 427.2279 is 4438115 Tech to call if access is needed on site. Called left message with Dean and crew to see if they could power cycle modem. More info as becomes available. 12/10/2012 07:37 Troy@bay 01:LowLithium,02:TestTagFailure,15:TestTagFailure: The ladder is de- watered, clearing TASS. 12/07/2012 10:09 Troy@bay 01:LowLithium,02:TestTagFailure,15:TestTagFailure: This ladder is de- watered, clearing TASS. 12/06/2012 11:19 Roger Installed PCAnywhere on PC2. Tested remote connection. No problems to report. 12/05/2012 07:57 Alan A power outage occurred 12-4-2012. Any file gaps are inconsequential as the site is de-watered. 12/02/2012 09:35 troy@bay 01:ReaderReset,02:ReaderReset,02:TestTagFailure,03:ReaderReset,03:RocketPo rtNoEOT,04:ReaderReset,05:ReaderReset,06:ReaderReset,07:ReaderReset,08:Rea derReset,09:ReaderReset,0A:ReaderReset,0B:ReaderReset,0C:ReaderReset,0D:Re aderReset,0E:ReaderReset,0F:ReaderReset,10:ReaderReset,11:RocketPortNoEOT, 12:ReaderReset,13:ReaderReset,14:ReaderReset,15:ReaderReset,15:TestTagFail ure,16:ReaderReset,17:ReaderReset,18:LowExcCurrent,18:ReaderReset,22:Input SyncDetect,22:ReaderReset,24:InputSyncDetect,24:ReaderReset,26:InputSyncDe tect,26:ReaderReset,28:ReaderReset,32:InputSyncDetect,32:ReaderReset,34:In putSyncDetect,34:ReaderReset,36:InputSyncDetect,38:ReaderReset: These alarms are most likely due to a power outage. 11/30/2012 10:19 Rclark@b 02:ReaderReset,03:ReaderReset,04:ReaderReset,05:ReaderReset,06:ReaderReset ,07:ReaderReset,08:ReaderReset,09:ReaderReset,0A:ReaderReset,0B:ReaderRese t,0C:ReaderReset,0D:ReaderReset,0E:ReaderReset,0F:ReaderReset,10:ReaderRes et,11:ReaderReset,12:ReaderReset,12:TestTagFailure,13:ReaderReset,14:Reade rReset,15:ReaderReset,15:TestTagFailure,16:ReaderReset,17:ReaderReset,18:R eaderReset,22:InputSyncDetect,22:ReaderReset,24:InputSyncDetect,24:ReaderR eset,26:InputSyncDetect,26:ReaderReset,28:ReaderReset,32:InputSyncDetect,3 2:ReaderReset,34:InputSyncDetect,34:ReaderReset,36:InputSyncDetect,36:Read erReset,38:ReaderReset: Caused by momentary power outage. 11/26/2012 07:52 Troy@bay 02:TestTagFailure,15:TestTagFailure: Ladder is de-watered. 11/25/2012 08:12 rclark@b 02:TestTagFailure,15:TestTagFailure: The ladder is dewatered. 11/24/2012 08:36 rclark@b 15:TestTagFailure: Noted. 11/23/2012 08:57 rclark@b 02:TestTagFailure,15:TestTagFailure: The ladder is dewatered. 11/22/2012 07:54 rclark@b 02:TestTagFailure,0C:ReaderReset,15:TestTagFailure: The ladder is dewatered. 11/21/2012 07:11 Rclark@b 02:TestTagFailure,15:TestTagFailure: The ladder is dewatered. 11/20/2012 07:06 Rclark@b 02:TestTagFailure,15:TestTagFailure: The ladder is dewatered. 11/19/2012 13:06 Scott_Li Site has been upgraded to M4 ver. 1.4.7 Scott Livingston Sr. Engineering Technician PSMFC-PTAGIS 7103 W. Clearwater Ave. Suite H. Kennewick, Wa. 99336 Office: 509.735.2773 x.2 Mobile: 509.539.0894 Scottl@psmfc.org 11/19/2012 08:40 Rclark@b 02:TestTagFailure,08:LowExcCurrent,11:Overrun,15:TestTagFailure: The ladder is dewatered. 11/15/2012 13:48 scottl Replaced PC2 with Dell 755 configured with M4 Ver. 1.4.6. Tested comms to all transceivers, purged most un-necessay files and applications and general clean up of the PC. As of now , there are is no remote access to this PC. PCA was not on the computer when taken from Kennewick and PCA do not have the PCA installation disk. Going to make an attempt to get a RDP session into this PC in order to avoid another trip just to install app. 11/13/2012 08:03 alan@bay 15:TestTagFailure: Noted 11/13/2012 07:54 Darren PSMFC confirmed today with site Biologist Andrew Taylor that the Washington shore ladder will be de-watered today. The process started at 08:00. 11/12/2012 08:13 darren@b 15:TestTagFailure: Alarm noted. 11/10/2012 07:22 darren@b 08:LowExcCurrent,15:TestTagFailure: The ladder was placed at orifice flows on Thursday and will be de-watered on Tuesday of next week. 11/07/2012 07:34 darren@b 15:TestTagFailure: Alarm noted. 11/06/2012 07:35 darren@b 15:TestTagFailure: known problematic system. 11/05/2012 07:48 darren@b 15:TestTagFailure: Alarm on known problematic system. 11/02/2012 06:26 darren@b 01:Overrun,15:TestTagFailure: The alarms on antenna 15 are on a known problematic system. The other alarm was a one time alarm and will be monitored for future alarms. 11/01/2012 10:56 Roger Performed site GMC on 11/1/2012. All transceivers were checked for tune and adjusted as needed. PC1 was 2 minutes 48 seconds ahead of atomic time. PC2 was 2 minute 52 seconds behind atomic time. Adjusted clocks to within 1 second of atomic time and each other. BO312306.206 was submitted as a gap file. Files on PC2 were archived. There are no problems to report. 10/30/2012 10:45 Alan With the help of site personnel, PC1 was rebooted which restored PCA access. This also set the Multimon file creation times to PST. The last file created on the PDT creation schedule was BO312304.102. Files BO312304.903 and 904 were tailored to fit the gap in data and uploaded as patch files. No problems to report. 10/30/2012 06:38 darren@b 11:Overrun,15:TestTagFailure: Known problematic systems. 10/28/2012 09:28 Troy Could not access PC1 via PCA. PC2 was accessed and Multimon was stopped and restarted for DST. All files were archived. The .205 is the first file at the correct time. 10/28/2012 09:24 troy@bay 15:TestTagFailure: Known problematic antenna, clearing TASS. 10/27/2012 07:11 troy@bay 15:TestTagFailure: Known problematic antenna, clearing TASS. 10/25/2012 06:40 darren@b 15:TestTagFailure: Alarm on known problematic system. 10/24/2012 10:30 Troy@bay 15:TestTagFailure: Known problematic antenna, clearing TASS. 10/23/2012 06:56 Troy@bay 15:TestTagFailure: Known problematic antenna, clearing TASS. 10/22/2012 06:30 scottl@b 01:ReaderReset,02:ReaderReset,03:ReaderReset,04:ReaderReset,05:ReaderReset ,06:ReaderReset,07:ReaderReset,08:ReaderReset,09:ReaderReset,0A:ReaderRese t,0B:ReaderReset,0B:RocketPortNoEOT,0C:ReaderReset,0D:ReaderReset,0E:Reade rReset,0F:ReaderReset,10:ReaderReset,11:Overrun,11:ReaderReset,12:ReaderRe set,12:TestTagFailure,13:ReaderReset,14:ReaderReset,15:ReaderReset,15:Test TagFailure,16:ReaderReset,17:ReaderReset,18:ReaderReset,22:InputSyncDetect ,22:ReaderReset,24:InputSyncDetect,24:ReaderReset,26:InputSyncDetect,26:Re aderReset,28:ReaderReset,32:InputSyncDetect,32:ReaderReset,34:InputSyncDet ect,34:ReaderReset,36:InputSyncDetect,36:ReaderReset,38:ReaderReset: Appears that there was a power outage, will investigate 10/21/2012 12:42 rclark@b 01:ReaderReset,02:ReaderReset,03:ReaderReset,04:ReaderReset,05:ReaderReset ,06:ReaderReset,07:ReaderReset,08:ReaderReset,09:ReaderReset,0A:ReaderRese t,0B:ReaderReset,0B:RocketPortNoEOT,0C:ReaderReset,0D:ReaderReset,0E:Reade rReset,0F:ReaderReset,10:ReaderReset,11:ReaderReset,12:ReaderReset,13:Read erReset,14:ReaderReset,15:RocketPortNoEOT,15:TestTagFailure,16:ReaderReset ,17:ReaderReset,18:ReaderReset,22:InputSyncDetect,22:ReaderReset,24:InputS yncDetect,24:ReaderReset,26:InputSyncDetect,26:ReaderReset,28:ReaderReset, 32:InputSyncDetect,32:ReaderReset,34:InputSyncDetect,34:ReaderReset,36:Inp utSyncDetect,36:ReaderReset,38:ReaderReset: Caused by momentary power outage. 10/21/2012 07:21 rclark@b 11:Overrun: This will be checked during the next site visit. 10/21/2012 07:19 rclark@b 15:TestTagFailure: Noted. 10/21/2012 07:18 rclark@b 02:ReaderReset,03:ReaderReset,04:ReaderReset,05:ReaderReset,06:ReaderReset ,07:ReaderReset,08:ReaderReset,09:ReaderReset,0A:ReaderReset,0B:ReaderRese t,0B:RocketPortNoEOT,0C:ReaderReset,0D:ReaderReset,0E:ReaderReset,0F:Reade rReset,10:ReaderReset,11:ReaderReset,12:ReaderReset,12:TestTagFailure,13:R eaderReset,14:ReaderReset,15:ReaderReset,16:ReaderReset,17:ReaderReset,18: ReaderReset,22:InputSyncDetect,22:ReaderReset,24:InputSyncDetect,24:Reader Reset,26:InputSyncDetect,26:ReaderReset,28:ReaderReset,32:InputSyncDetect, 32:ReaderReset,34:InputSyncDetect,34:ReaderReset,36:InputSyncDetect,36:Rea derReset,38:ReaderReset: Caused by momentary power outage. 10/20/2012 06:51 rclark@b 15:TestTagFailure: Noted. 10/19/2012 06:33 Rclark@b 15:TestTagFailure: Noted. 10/18/2012 06:29 Rclark@b 15:TestTagFailure: Noted. 10/17/2012 06:27 Rclark@b 15:TestTagFailure: Noted. 10/17/2012 06:26 Rclark@b 11:Overrun: This will be checked during the next site visit. 10/16/2012 06:24 Rclark@b 15:TestTagFailure: Noted. 10/15/2012 06:34 darren@b 11:TestTagFailure,15:TestTagFailure: Alarms have been noted and will be investigated during the next site visit. 10/14/2012 06:50 darren@b 15:TestTagFailure: Alarm on known problematic system. 10/13/2012 06:31 darren@b 15:TestTagFailure: Alarm noted. 10/11/2012 10:51 Roger Performed site GMC on 10/11/2012. All transceivers were checked for tune and adjusted as needed. PC1 and PC2 are 2 minutes 10 seconds behind atomic time. Clocks were not adjusted due to ongoing fish sampling. Files on PC2 were archived. There are no problems to report. 10/11/2012 06:27 darren@b 01:Overrun,06:TestTagFailure,11:Overrun,15:TestTagFailure: Alarms will be investigated during the site visit today (10-11-12). Some of these systems have known and documented problems. 10/09/2012 06:23 darren@b 15:TestTagFailure: Known problematic system. 10/08/2012 06:20 darren@b 15:TestTagFailure: alarm noted. problematic system. 10/05/2012 06:20 Rclark@b 15:TestTagFailure: Noted. 10/04/2012 06:54 Rclark@b 15:TestTagFailure: Noted. 09/30/2012 08:20 alan@bay 15:TestTagFailure: Noted 09/29/2012 09:35 alan@bay 15:TestTagFailure: Noted 09/28/2012 07:05 troy@bay 15:TestTagFailure: Known problematic antenna, clearing TASS. 09/27/2012 06:41 Rclark@b 15:TestTagFailure: Noted. 09/26/2012 10:35 Roger Performed site GMC on 9/26/2012. All transceivers were checked for tune and adjusted as needed. PC1 is 1 minute 41 seconds behind atomic time. PC2 was 2 minutes 6 seconds behind atomic time and was adjusted to within 1 second of PC1. The time on PC1 was not corrected due to ongoing fish studies. There are no problems to report. 09/26/2012 07:13 alan@bay 15:TestTagFailure: Noted 09/24/2012 07:19 alan@bay 15:TestTagFailure: Noted 09/23/2012 06:51 rclark@b 15:TestTagFailure: Noted. 09/23/2012 06:51 rclark@b 02:ReaderReset: Random reader reset. Clearing TASS. 09/22/2012 06:48 rclark@b 15:TestTagFailure: Noted. 09/21/2012 07:14 PTOC_Bot CenturyLink reports they are currently experiencing an outage, the estimated return to service is no later than 16:00 PDT 9-21-2012. 09/21/2012 07:07 Rclark@b 15:TestTagFailure: Noted. 09/20/2012 06:26 Rclark@b 15:TestTagFailure: Noted. 09/19/2012 06:31 Rclark@b 15:TestTagFailure: Noted. 09/19/2012 05:56 Rclark@b 06:ReaderReset: Random reader reset. Clearing TASS. 09/18/2012 06:23 Rclark@b 15:TestTagFailure: Noted 09/17/2012 06:22 Rclark@b 15:TestTagFailure: Noted. 09/16/2012 06:40 troy@bay 15:TestTagFailure: Known problematic antenna, clearing TASS. 09/15/2012 06:54 troy@bay 15:TestTagFailure: Known problematic antenna, clearing TASS. 09/12/2012 07:07 Troy@bay 15:TestTagFailure: Known problematic antenna, clearing TASS. 09/11/2012 06:30 Troy@bay 15:TestTagFailure: Known problematic antenna, clearing TASS. 09/10/2012 07:54 Troy@bay 15:TestTagFailure: Known problematic antenna, clearing TASS. 09/09/2012 06:29 darren@b 15:TestTagFailure: Alarm on known problematic system. 09/08/2012 06:28 darren@b 15:TestTagFailure: Alarm on known problematic system. 09/07/2012 06:30 darren@b 15:TestTagFailure: Alarm on known problematic system. 09/06/2012 06:31 darren@b 15:TestTagFailure: Alarm noted on problematic system. 09/05/2012 06:29 darren@b 15:TestTagFailure: Alarm on known problematic system. 09/04/2012 07:45 alan@bay 15:TestTagFailure: Noted 09/03/2012 06:47 alan@bay 15:TestTagFailure: Noted 09/02/2012 07:11 alan@bay 15:TestTagFailure: Noted 09/01/2012 07:26 alan@bay 15:TestTagFailure: Noted 08/30/2012 06:50 alan@bay 15:TestTagFailure: Noted 08/29/2012 07:33 alan@bay 15:TestTagFailure: Noted 08/28/2012 06:55 alan@bay 15:TestTagFailure: Noted 08/27/2012 07:13 alan@bay 15:TestTagFailure: Noted 08/26/2012 06:58 darren@b 06:ReaderReset,15:TestTagFailure: Alarm on 06 was generated by a reader reset. The alarms on 15 have been well documented. 08/25/2012 07:20 darren@b 15:TestTagFailure: Alarm on known problematic system. 08/24/2012 06:40 alan@bay 15:TestTagFailure: Noted 08/22/2012 06:40 darren@b 15:TestTagFailure: Alarm noted. problematic system. 08/21/2012 06:44 darren@b 15:TestTagFailure: Alarm noted. 08/20/2012 06:56 darren@b 15:TestTagFailure: Alarm noted. System has been well documented and is in a diminished capacity. 08/19/2012 07:06 troy@bay 15:TestTagFailure: Known problematic antenna, clearing TASS. 08/18/2012 08:25 Troy@bay 01:ReaderReset,02:ReaderReset,03:ReaderReset,04:ReaderReset,05:ReaderReset ,06:ReaderReset,07:ReaderReset,08:ReaderReset,09:ReaderReset,0A:ReaderRese t,0B:ReaderReset,0C:ReaderReset,0D:ReaderReset,0E:ReaderReset,0F:ReaderRes et,10:ReaderReset,11:ReaderReset,12:ReaderReset,13:ReaderReset,14:ReaderRe set,15:ReaderReset,15:TestTagFailure,16:ReaderReset,17:ReaderReset,18:Read erReset,22:InputSyncDetect,22:ReaderReset,24:InputSyncDetect,24:ReaderRese t,26:InputSyncDetect,26:ReaderReset,28:ReaderReset,32:InputSyncDetect,32:R eaderReset,34:InputSyncDetect,34:ReaderReset,36:InputSyncDetect,36:ReaderR eset,38:ReaderReset: Most likely a power outage. PSMFC will monitor. 08/17/2012 07:19 Troy@bay 15:TestTagFailure: Known problematic antenna, clearing TASS. 08/10/2012 06:18 darren@b 15:TestTagFailure: Alarm on known problematic system. 08/09/2012 06:48 Rclark@b 15:TestTagFailure: Noted. 08/08/2012 11:35 Roger Performed site GMC on 8/8/2012. All transceivers were checked for tune and adjusted as needed. PC1 is 27 seconds behind atomic time. PC2 was 45 seconds behind atomic time and was adjusted to within 1 second of PC1. Files on PC2 were archived. There are no problems to report. 08/07/2012 06:05 Rclark@b 15:TestTagFailure: Noted. 08/06/2012 07:44 Troy@bay 15:TestTagFailure: Known problematic antenna, clearing TASS. 08/05/2012 06:54 rclark@b 15:TestTagFailure: Noted. 08/05/2012 06:53 rclark@b 06:ReaderReset: Random reader reset. 08/04/2012 06:50 rclark@b 15:TestTagFailure: Noted. 08/04/2012 06:50 rclark@b 06:ReaderReset: Random reader reset. 08/03/2012 06:40 Troy@bay 15:TestTagFailure: Known problematic antenna, clearing TASS. 08/02/2012 15:50 rclark@b 0E:LowExcCurrent: Caused by PSMFC personnel during site visit. 08/02/2012 11:06 Roger Performed site GMC on 8/2/2012. All transceivers were checked for tune and adjusted as needed. PC1 is 20 seconds and PC2 is 34 seconds behind atomic time. Files on PC2 were archived. Note: This is the first time in months that the upper ladder noise level has dropped. Transceiver 01 is now at approx. 20% instead of 100%. There are no problems to report. 08/02/2012 06:15 Rclark@b 15:TestTagFailure: Noted. 08/01/2012 06:38 Rclark@b 01:ReaderReset,02:ReaderReset,03:ReaderReset,04:ReaderReset,05:ReaderReset ,06:ReaderReset,07:ReaderReset,08:ReaderReset,09:ReaderReset,0A:ReaderRese t,0B:ReaderReset,0B:RocketPortNoEOT,0C:ReaderReset,0D:ReaderReset,0E:Reade rReset,0F:ReaderReset,10:ReaderReset,11:ReaderReset,12:ReaderReset,13:Read erReset,14:ReaderReset,15:ReaderReset,15:TestTagFailure,16:ReaderReset,17: ReaderReset,18:ReaderReset,22:InputSyncDetect,22:ReaderReset,24:InputSyncD etect,24:ReaderReset,26:InputSyncDetect,26:ReaderReset,28:ReaderReset,32:I nputSyncDetect,32:ReaderReset,34:InputSyncDetect,34:ReaderReset,36:InputSy ncDetect,36:ReaderReset,38:ReaderReset: Caused by momentary power loss. 07/31/2012 06:06 Rclark@b 15:TestTagFailure: Noted 07/30/2012 06:16 Rclark@b 15:TestTagFailure: Noted. 07/30/2012 06:07 Rclark@b 01:ReaderReset,02:ReaderReset,03:ReaderReset,04:ReaderReset,05:ReaderReset ,06:ReaderReset,07:ReaderReset,08:ReaderReset,09:ReaderReset,0A:ReaderRese t,0B:ReaderReset,0B:RocketPortNoEOT,0C:ReaderReset,0D:ReaderReset,0E:Reade rReset,0F:ReaderReset,10:ReaderReset,11:ReaderReset,12:ReaderReset,13:Read erReset,14:ReaderReset,15:ReaderReset,15:TestTagFailure,16:ReaderReset,17: ReaderReset,18:ReaderReset,22:InputSyncDetect,22:ReaderReset,24:InputSyncD etect,24:ReaderReset,26:InputSyncDetect,26:ReaderReset,28:ReaderReset,32:I nputSyncDetect,32:ReaderReset,34:InputSyncDetect,34:ReaderReset,36:InputSy ncDetect,36:ReaderReset,38:ReaderReset: Most likely due to momentary power outage. 07/29/2012 06:38 darren@b 15:TestTagFailure: Alarm on known problematic system. 07/28/2012 06:29 darren@b 15:TestTagFailure,22:InputSyncDetect,22:InputSyncLost,26:InputSyncDetect,2 6:InputSyncLost,28:ReaderReset: The alarms on antenna 15 are on a known problematic system. The alarms on all others was generated by a reader reset. 07/27/2012 06:30 darren@b 15:TestTagFailure: Alarm on problematic system. 07/26/2012 06:10 darren@b 07:TestTagFailure,15:TestTagFailure: The alarms on system 15 are well documented. The failure of the timer tag on system 07 was caused by a PITtag being in the field at the time of the timer tag firing. 07/25/2012 11:28 Roger Performed site GMC on 7/25/2012. All transceivers were checked for tune and adjusted as needed. PC1 is 7 seconds and PC2 18 seconds behind atomic time. Files on PC2 were archived. There are no problems to report. 07/25/2012 06:48 darren@b 15:TestTagFailure: Alarm on known problematic system. 07/25/2012 06:11 darren@b 15:TestTagFailure: Alarm on known problematic system. 07/24/2012 06:20 darren@b 15:TestTagFailure: Alarm on known problematic system. 07/23/2012 06:57 alan@bay 15:TestTagFailure: Noted 07/22/2012 08:00 alan@bay 15:TestTagFailure: Noted 07/21/2012 07:05 alan@bay 11:Overrun,15:TestTagFailure: Noted 07/19/2012 07:10 alan@bay 15:TestTagFailure: Noted 07/18/2012 10:04 alan@bay 11:Overrun,15:TestTagFailure: Noted 07/17/2012 07:58 alan@bay 15:TestTagFailure: Noted 07/16/2012 08:21 alan@bay 15:TestTagFailure: Noted 07/13/2012 09:22 Rclark@b 15:TestTagFailure: Noted. 07/11/2012 06:46 Troy@bay 15:TestTagFailure: Known problematic antenna, clearing TASS. 07/10/2012 11:43 Roger Performed site GMC on 7/10/2012. All transceivers were checked for tune and adjusted as needed. PC1 is 14 seconds ahead of atomic time. PC2 was 37 seconds ahead of atomic time and was adjusted to within 1 second of PC1. Files on PC2 were archived. There are no problems to report. 07/10/2012 07:12 Troy@bay 09:TestTagFailure,11:Overrun,15:TestTagFailure: These alarms will be addressed on the next site visit. 07/06/2012 10:20 scottl Changed DNS entries on all data collection computers including the utility pc's in prep for the network change over and as requested by Todd and Chris. 07/01/2012 07:10 Troy@bay 15:TestTagFailure: Known problematic antenna, clearing TASS. 06/30/2012 06:39 Troy@bay 15:TestTagFailure: Known problematic antenna, clearing TASS. 06/29/2012 06:20 Rclark@b 15:TestTagFailure: Noted. 06/28/2012 06:57 Troy@bay 0D:ReaderReset,11:Overrun,15:TestTagFailure: ReaderReset noted. The other alarms are from know problematic antennas. Clearing TASS. 06/27/2012 10:35 Roger Performed site GMC on 6/27/2012. All transceivers were checked for tune and adjusted as needed. PC1 is 12 seconds behind and PC2 is 18 seconds behind atomic time. Files on PC2 were archived. There are no problems to report. 06/24/2012 09:16 Troy@bay 11:Overrun,15:TestTagFailure: Known problematic antennas, clearing TASS 06/23/2012 07:46 Troy@bay 15:TestTagFailure: Known problematic antenna, clearing TASS. 06/22/2012 08:02 Troy@bay 15:TestTagFailure: 15:TestTagFailure: Known problematic antenna, clearing TASS. 06/22/2012 08:02 Troy@bay 15:TestTagFailure: Known problematic antenna, clearing TASS. 06/21/2012 07:08 Troy@bay 15:TestTagFailure: Known problematic antenna, clearing TASS. 06/20/2012 07:03 Troy@bay 15:TestTagFailure: Known problematic antenna, clearing TASS. 06/19/2012 11:24 Roger Performed site GMC on 6/19/2012. All transceivers were checked for tune and adjusted as needed. PC1 and PC2 were approx 39 seconds behind atomic time. The clocks were adjusted to within 1 second of atomic time and each other. The UPS units were replaced on both PCs. File BO312171.206 was submitted as a gap file. Files on PC2 were archived. There are no problems to report. 06/19/2012 06:46 alan@bay 15:TestTagFailure: Noted 06/18/2012 06:44 Troy@bay 15:TestTagFailure: Known problematic antenna, clearing TASS. 06/17/2012 05:31 darren@b 15:TestTagFailure: Alarm noted. 06/16/2012 05:18 darren@b 15:TestTagFailure: Alarm on a known problematic system. 06/14/2012 13:04 Roger Plugged PC1 and PC2 direct into AC power due to potential UPS failure on 6/14/2012. The UPS units will be replaced during the next site visit. File BO312166.208 was submitted as a patch file. 06/14/2012 11:24 Roger Performed site GMC on 6/14/2012. All transceivers were checked for tune and adjusted as needed. PC1 is 42 seconds behind atomic time. PC2 was 57 seconds behind atomic time and was adjusted to within 1 second of PC1. The clock on PC1 was not adjusted because tagging operations were in process at the AFF. Files on PC2 were archived. The UPS on PC1 was alarming for about a half a minute while I was in the PIT tag room. The alarm went away but the battery fault indicator is flashing. This UPS may need to be replaced during the next site visit. There are no other problems to report. 06/14/2012 06:23 darren@b 15:TestTagFailure: Alarm on known problematic system. 06/11/2012 06:13 darren@b 15:TestTagFailure: Alarm on known problematic system. 06/10/2012 06:25 rclark@b 15:TestTagFailure: Noted. 06/09/2012 07:22 rclark@b 15:TestTagFailure: Noted. 06/07/2012 12:05 Roger Performed site GMC on 6/7/2012. All transceivers were checked for tune and adjusted as needed. PC1 is 32 seconds behind atomic time. PC2 is 43 seconds behind atomic time. Files on PC2 were archived. There are no problems to report. 06/07/2012 06:25 Rclark@b 15:TestTagFailure: Noted. 06/06/2012 06:28 Rclark@b 15:TestTagFailure: Noted. 06/05/2012 06:22 Rclark@b 15:TestTagFailure: Noted. 06/04/2012 06:23 Rclark@b 15:TestTagFailure: Noted. 06/03/2012 07:16 alan@bay 15:TestTagFailure: Noted 06/02/2012 07:47 alan@bay 15:TestTagFailure: Noted 06/01/2012 10:39 Roger Performed GMC on 6/1/2012. All transceivers were checked for tune and adjusted as needed. PC1 is 23 seconds behind atomic time. PC2 is 32 seconds behind atomic time. Files on PC2 were archived. There are no problems to report. 05/30/2012 08:31 alan@bay 15:TestTagFailure: Noted 05/30/2012 08:31 alan@bay 09:TestTagFailure: A PIT tag was in the field when the timer tag was fired. 05/29/2012 07:01 Troy@bay 15:TestTagFailure: Known problematic antenna, clearing TASS. 05/28/2012 06:22 rclark@b 15:TestTagFailure: Noted. 05/27/2012 06:22 rclark@b 15:TestTagFailure: Noted. 05/27/2012 06:22 rclark@b 11:LowExcCurrent: Current alarm level was lowered on 5/26/2012. 05/27/2012 06:20 rclark@b 0A:ReaderReset: Random reader reset. 05/26/2012 06:48 rclark@b 11:LowExcCurrent: Remotely lowered current alarm threshold to 1500 mA. 05/26/2012 06:39 rclark@b 15:TestTagFailure: Noted. 05/24/2012 10:51 Roger Performed site GMC on 5/24/2012. All transceivers were checked for tune and adjusted as needed. PC1 is 12 seconds behind atomic time. PC2 is 16 seconds behind atomic time. Files on PC2 were archived. There are no problems to report. 05/23/2012 06:37 Rclark@b 15:TestTagFailure: Noted. 05/23/2012 06:37 Rclark@b 11:LowExcCurrent: This will be addressed during the next site visit. 05/23/2012 06:03 Rclark@b 05:ReaderReset: Random reader reset. 05/22/2012 06:10 Rclark@b 15:TestTagFailure: Noted. 05/21/2012 05:58 Rclark@b 17:ReaderReset: Random reader reset. 05/21/2012 05:57 Rclark@b 15:TestTagFailure: Noted 05/18/2012 07:15 alan@bay 15:TestTagFailure: Noted 05/17/2012 12:34 Roger Performed site GMC on 5/17/2012. All transceivers were checked for tune and adjusted as needed. PC1 was 75 seconds behind atomic time. PC2 was 70 seconds behind atomic time. Both clocks were set to within 1 second of atomic time and each other. File BO312138.207 was submitted as a gap file. Files on PC2 were archived. The locker was inventoried. There are no problems to report. 05/17/2012 06:36 Troy@bay 15:TestTagFailure: Known problematic antenna, clearing TASS. 05/13/2012 06:28 rclark@b 15:TestTagFailure: Noted. 05/12/2012 07:09 rclark@b 15:TestTagFailure: Noted. 05/11/2012 06:53 rclark@b 15:TestTagFailure: Noted. 05/10/2012 09:54 Roger Performed site GMC on 5/10/2012. All transceivers were checked for tune and adjusted as needed. PC1 is 52 second behind atomic time. PC2 is 57 seconds behind atomic time. Files on PC2 were archived. There are no problems to report. 05/10/2012 07:26 Troy@bay 15:TestTagFailure: Known problematic antenna, clearing TASS. 05/09/2012 05:59 Rclark@b 15:TestTagFailure: Noted 05/08/2012 06:06 Rclark@b 15:TestTagFailure: Noted 05/07/2012 06:23 Rclark@b 15:TestTagFailure: Noted. 05/06/2012 06:48 Troy@bay 08:LowExcCurrent,15:TestTagFailure: 08 will be addressed on the next site visit. 15 is a known problematic antenna, clearing TASS. 05/05/2012 07:48 Troy@bay 15:TestTagFailure: Known problematic antenna, clearing TASS. 05/04/2012 07:58 alan@bay 08:LowExcCurrent,15:TestTagFailure: Noted 05/03/2012 10:26 Roger Performed site GMC on 5/3/2012. All transceivers were checked for tune and adjusted as needed. Transceiver 11 is currently at 100% signal level. Suspect a defective antenna, cable, or antenna capacitors. PC1 is 45 seconds behind atomic time. PC2 was 1 minute behind atomic time and was adjusted to within 1 second of PC1. There are no other problems to report. 05/03/2012 07:09 alan@bay 15:TestTagFailure: Noted 05/02/2012 07:19 Troy@bay 15:TestTagFailure: Known problematic antenna, clearing TASS. 04/30/2012 06:37 darren@b 11:Overrun,15:TestTagFailure: The alarm on antenna 11 will be investigated during the next site visit. The alarm on antenna 15 is on a known problematic system. 04/29/2012 09:44 alan@bay 14:ReaderReset,15:TestTagFailure: Noted 04/28/2012 08:27 alan@bay 15:TestTagFailure: Noted 04/26/2012 07:04 Troy@bay 15:TestTagFailure,36:InputSyncDetect,36:ReaderReset: 15 is a know problematic antenna. 36 was most likely caused by PSMFC personnel during a site GMC. 04/25/2012 12:12 Roger Correction to previous PIT event. 01 is the transceiver at 100% signal level. 03 and 05 are elevated in signal level. 04/25/2012 11:58 Roger Performed site GMC on 4/25/2012. All transceivers were checked for tun and adjusted as needed. Transceiver 04 is currently at 100% signal level. Transceivers 06 and 08 are at slightly elevated levels. PC1 is 31 second behind atomic time. PC2 is 44 seconds behind atomic time. Files on PC2 were archived. There are no other problems to report. 04/24/2012 08:41 alan@bay 15:TestTagFailure: Noted 04/22/2012 07:16 darren@b 15:TestTagFailure: 15:TestTagFailure: Alarm on known problematic system. 04/22/2012 07:16 darren@b 15:TestTagFailure: Alarm on known problematic system. 04/21/2012 07:30 darren@b 15:TestTagFailure: Alarm on known problematic system. 04/20/2012 07:06 darren@b 15:TestTagFailure: Alarms on known problematic system. 04/19/2012 06:28 darren@b 01:Overrun,15:TestTagFailure: Alarms will be investigated during the next visit. 04/16/2012 07:37 alan@bay 11:Overrun,15:TestTagFailure: Noted 04/16/2012 07:36 alan@bay 0C:LowExcCurrent: Both the current and threshold were set to 3500mA. Remotely lowered threshold to 3200mA. 04/11/2012 11:23 Alan A GMC was performed 4-11-2012. All transceivers were checked and tuned as necessary. Both PCs are 15 seconds behind atomic time. Outstanding files on PC2 were archived. No problems found. 04/11/2012 06:05 Rclark@b 15:TestTagFailure: Noted. 04/11/2012 06:05 Rclark@b 11:Overrun: This will be checked during toidays site visit. 04/09/2012 07:04 darren@b 15:TestTagFailure: Alarm on known problematic system. 04/08/2012 06:38 rclark@b 15:TestTagFailure: Noted. 04/07/2012 06:30 rclark@b 15:TestTagFailure: Noted. 04/06/2012 06:40 alan@bay 15:TestTagFailure: Noted 04/05/2012 06:07 Rclark@b 15:TestTagFailure: Noted. 04/04/2012 10:16 Roger Performed site GMC on 4/4/2012. All transceivers were checked for tune and adjusted as needed. PC1 was 1 minute behind atomic time. PC2 was 1 minute 15 seconds behind atomic time. Set clocks to within 1 second of atomic time and each other. File BO312095.206 was submitted as a gap file. All other files on PC2 were archived. No problems to report. 04/03/2012 06:11 Rclark@b 15:TestTagFailure: Noted. 04/02/2012 06:19 Rclark@b 15:TestTagFailure: Noted. 04/01/2012 08:32 Troy@bay 11:Overrun,15:TestTagFailure: Noted 04/01/2012 08:29 Troy Stopped and started Multimon due to Day Light Savings time. The last file prior to the stop/start was the .103 file. 03/31/2012 07:27 Troy@bay 05:Overrun,15:TestTagFailure: These alarms will be addressed on the next sit visit. 03/29/2012 07:57 Troy@bay 15:TestTagFailure: Known problematic antenna, clearing TASS. 03/28/2012 07:11 alan@bay 15:TestTagFailure: Noted 03/27/2012 07:26 Troy@bay 15:TestTagFailure: Known problematic antenna, clearing TASS. 03/26/2012 07:00 Troy@bay 15:TestTagFailure: Known problematic antenna, clearing TASS. 03/25/2012 06:44 alan@bay 11:Overrun,15:TestTagFailure: Noted 03/24/2012 06:37 alan@bay 15:TestTagFailure: Noted 03/23/2012 06:44 alan@bay 15:TestTagFailure: Noted 03/22/2012 06:46 alan@bay 15:TestTagFailure: Noted 03/21/2012 06:30 alan@bay 15:TestTagFailure: Noted 03/20/2012 06:37 alan@bay 01:Overrun,15:TestTagFailure: Noted 03/19/2012 10:12 alan@bay 15:TestTagFailure: Clearing TASS on a known problematic system. 03/19/2012 07:35 alan@bay 15:TestTagFailure: Clearing TASS on a known problematic system. 03/18/2012 06:48 darren@b 15:TestTagFailure: Alarm on known problematic system. 03/17/2012 07:15 darren@b 15:TestTagFailure: Alarm on known problematic system. 03/15/2012 06:51 Troy@bay 15:TestTagFailure: Known problematic antenna, clearing TASS. 03/13/2012 06:19 darren@b 11:Overrun,15:TestTagFailure,17:ReaderReset: The alarms on antennas 11 and 17 will be investigated during the next site visit. The failures on 15 are on a known problematic system. 03/12/2012 06:37 darren@b 0F:ReaderReset,15:TestTagFailure: The alarm on antenna 0F was due to a random reader reset. The alarms on antenna 15 are on a known problematic system. 03/09/2012 07:22 alan@bay 15:TestTagFailure: Noted 03/09/2012 07:21 alan@bay 0F:ReaderReset: This alarm is the result of a random reader reset. 03/05/2012 10:57 Nicole Performed annual MultiMon reset. Reset clocks to be within one second of each other and atomic time. 03/05/2012 07:37 Rclark@b 15:TestTagFailure: Noted. 03/04/2012 08:02 rclark@b 15:TestTagFailure: Noted. 03/03/2012 07:41 rclark@b 15:TestTagFailure: Noted. 03/02/2012 07:46 rclark@b 01:Overrun,15:TestTagFailure: Noted 03/01/2012 08:38 Rclark@b 15:TestTagFailure: Noted 03/01/2012 08:37 Rclark@b 11:Overrun: This will be checked on the next site visit 03/01/2012 08:37 Rclark@b 01:Overrun: Noted 02/28/2012 07:39 Rclark@b 15:TestTagFailure: Noted 02/27/2012 07:04 Rclark@b 15:TestTagFailure: Noted 02/27/2012 07:03 Rclark@b 11:Overrun: Noted 02/25/2012 09:03 Troy@bay 15:TestTagFailure: Known problematic antenna, clearing TASS. 02/24/2012 12:35 Roger Performed site GMC on 2/24/2012. All transceivers were checked for tune and adjusted as needed. PC1 was 1 minute 14 seconds behind atomic time. PC2 was 1 minute 39 seconds behind atomic time. Clocks were adjusted to within 1 second of atomic time and patch file B0312055.207 was submitted. All other files on PC2 were archived. No problems to report. 02/24/2012 07:31 alan@bay 0D:ReaderReset,15:TestTagFailure: 0D is a random reader reset, 15 is a known problematic system. 02/23/2012 07:35 Troy@bay 11:Overrun,15:TestTagFailure: Known problematic antennas, clearing TASS. 02/21/2012 07:15 Troy@bay 15:TestTagFailure: Known problematica antenna, clearing TASS. 02/20/2012 08:20 darren@b 15:TestTagFailure: Alarm on known problematic system. 02/15/2012 07:31 darren@b 15:TestTagFailure: Alarm on problematic system. 02/13/2012 07:19 darren@b 15:TestTagFailure: alarm on known problematic system. 02/12/2012 06:53 alan@bay 15:TestTagFailure: Noted 02/11/2012 10:51 alan@bay 15:TestTagFailure: Noted 02/10/2012 07:52 alan@bay 01:Overrun: Noted 02/10/2012 07:52 alan@bay 15:TestTagFailure: Noted 02/09/2012 08:10 alan@bay 01:Overrun,15:TestTagFailure: Noted 02/08/2012 07:49 alan@bay 15:TestTagFailure: Noted 02/07/2012 08:19 alan@bay 15:TestTagFailure: Noted 02/06/2012 07:26 alan@bay 15:TestTagFailure: Noted 02/03/2012 07:41 Troy@bay 01:Overrun,14:LowExcCurrent,15:TestTagFailure: These alarms will be addressed on the next site visit. 02/01/2012 07:27 alan@bay 14:LowExcCurrent: Current is 3500mA, the alarm threshold was 3500mA. The threshold was lowered to 3200mA so as not to overload TASS processing. This will be investigated during the next site visit. 02/01/2012 07:26 darren@b 14:LowExcCurrent,15:TestTagFailure: The alarm on antenna 14 is due to the fact that the threshold and the actual current are equal. PSMFC will lower the threshold by 300mA to avoid the large files. 01/31/2012 12:56 Roger Replaced PC1 on 1/31/2011. Files on PC2 were manually pushed. Communications and the gate were tested. The UPS for the Rocketport panel was replaced. No problems to report. 01/29/2012 08:44 rclark@b 15:TestTagFailure: Noted 01/28/2012 08:40 rclark@b 15:TestTagFailure: Noted 01/27/2012 14:36 Roger Manually submitted files B0312027.203 and .204 due to PC1 currently being down. PC1 will be replaced on 1/31/2012. Files will contunue to be submitted manually from PC2 untill that time. 01/27/2012 07:35 Rclark@b 15:TestTagFailure: Noted 01/26/2012 12:20 Roger Performed site GMC on 1/26/2012. All transceivers were checked for tune and adjusted as needed. PC2 was one minute behind and PC1 was 2 minutes ahead of atomic time. Adjusted clocks to within 1 second of atomic time and each other. Submitted BO312026.207 as a patch file. No problems to report. 01/26/2012 06:31 rclark@b 15:TestTagFailure: Noted. 01/25/2012 07:23 Rclark@b 0B:LowExcCurrent: The exciter current alarm threshold has been lowered. This transceiver will be checked mon the next site visit. 01/25/2012 07:21 Rclark@b 15:TestTagFailure: Noted. 01/24/2012 09:45 cloughd@ TASS processing for BO3, which was erroneously suspended earlier today, has been reinstated. Per conversation with Alan, voluminous diagnostic content in recent files from BO3 is due to a known transceiver problem. Sorry for any confusion. - Doug- 01/24/2012 09:18 Alan Tranceiver 0B is operating at 3.6A with an alarm threshold of 3.7A. Remotely lowered the alarm threshold to 3.3A to reduce loading on TASS. This transceiver will be investigated during the next site visit. 01/24/2012 08:45 cloughd@ TASS processing for BO3 was suspended on 24 Jan 12, because the site had been dewatered and consequently was generating lots of alarms and noise data. Processing will be reinstated when the site is watered up again. -Doug- 01/24/2012 07:06 Rclark@b 01:Overrun,0B:LowExcCurrent,15:TestTagFailure: Noted. Will be checked on next site visit. 01/23/2012 07:10 Rclark@b 0B:LowExcCurrent,15:TestTagFailure: Will be addressed during the next site visit. 01/22/2012 20:41 Alan BO312018.205 was tailored to fit a file gap and manually submitted to PTAGIS via email. 01/22/2012 08:13 PTOC_Bot Another call was put into centurylink and they stated that the ETR would be 9pm tomorrow. BO1, BCC, and B2J are de-watered. Fish traffic has been pretty low at BO2, BO3, and BO4 such that IF the PCs are down any fish data should still be in the buffers. PSMFC will monitor and if the system isn't repaired by 9am tomorrow someone will contact site personnel to verify that the PC's are up and collecting data at BO2, BO3, and BO4. 01/22/2012 07:59 Troy@bay 0B:LowExcCurrent,15:TestTagFailure: Well documented alarms, clearing TASS. 01/21/2012 09:41 Troy The ISP was contacted and is aware that there is an outage in the area. The event ID is 108420. 01/20/2012 07:42 Troy@bay 0B:LowExcCurrent,15:TestTagFailure: Well documented alarms, clearing TASS. 01/19/2012 07:08 Troy@bay 0B:LowExcCurrent,15:TestTagFailure: Alarms well documented, clearing TASS. 01/18/2012 08:00 Troy@bay 0B:LowExcCurrent,15:TestTagFailure: If time and weather permit 0B will be investigated today. 15 is a known problematic antenna. 01/17/2012 07:15 Troy@bay 0B:LowExcCurrent,15:TestTagFailure: 0B will be investigate this week as time allows. 15 is a known problematic antenna. 01/16/2012 07:29 alan@bay 0B:LowExcCurrent,15:TestTagFailure: Noted 01/15/2012 08:23 alan@bay 0B:LowExcCurrent,15:TestTagFailure: These will be addressed during the next site visit. 01/14/2012 06:46 alan@bay 0B:LowExcCurrent,15:TestTagFailure: These will be investigated during the next site visit. 01/13/2012 07:19 alan@bay 0B:LowExcCurrent,15:TestTagFailure: These will be addressed during the next site visit. 01/12/2012 07:07 alan@bay 0B:LowExcCurrent,15:TestTagFailure: These will be addressed during the next site visit. 01/11/2012 08:18 alan@bay 0B:LowExcCurrent,15:TestTagFailure: These will be addressed during the next site visit. 01/10/2012 07:57 alan@bay 0B:LowExcCurrent,15:TestTagFailure: These will be addressed during the next site visit. 01/09/2012 08:49 alan@bay 15:TestTagFailure: Noted 01/09/2012 08:49 alan@bay 0B:LowExcCurrent: This will be addressed during the next site visit. 01/08/2012 10:22 darren@b 15:TestTagFailure: Alarm on known problematic system. 01/08/2012 10:21 darren@b 0B:LowExcCurrent: The current threshold and the current are equal. The system will be addressed during the next site visit. 01/07/2012 09:19 darren@b 01:Overrun,15:TestTagFailure: Alarms will be addressed during the next site visit. 01/05/2012 07:38 darren@b 15:TestTagFailure: Alarm on known problematic system. 01/04/2012 07:48 darren@b 01:Overrun,15:TestTagFailure: The problem on antenna 01 will be addressed during the next site visit. the problem on antenna 15 is on a known problematic system. 01/03/2012 07:47 darren@b 15:TestTagFailure: Known problematic system. 01/01/2012 00:00 PTOC_Bot Annual log file initiation for BO3 #### End of Event Log for BO3 ###