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 ---------- ----- -------- 12/31/2009 09:00 Troy@bay 01:TestTagFailure,0B:TestTagFailure,15:TestTagFailure: These alarms will be addressed on the next site visit. 12/30/2009 07:26 alan@bay 0B:TestTagFailure,15:TestTagFailure: These alarms will be investigated during the next site visit. 12/29/2009 07:21 Alan@bay 0B:TestTagFailure,15:TestTagFailure: These alarms will be investigated during the next site visit. 12/28/2009 07:22 troy@bay 0B:TestTagFailure,15:TestTagFailure: Noted 12/27/2009 08:37 darren@b 0B:TestTagFailure,15:TestTagFailure: These alarms will be addressed during the next site visit. 12/26/2009 08:56 darren@b 0B:TestTagFailure,15:TestTagFailure: The alarm on 0B will be addressed during the next site visit. The alarm on 15 is on a known problematic system. 12/25/2009 08:09 darren@b 0B:TestTagFailure,15:TestTagFailure: These alarms will be addressed during the next site visit. The alarms on 15 are on a known problematic system. 12/24/2009 08:04 troy@bay 0B:TestTagFailure,15:TestTagFailure: 15 in a known problematic system. 0B will be investigate on the next GMC. 12/20/2009 08:41 Troy@bay 15:TestTagFailure: Known problem, clearing TASS. 12/19/2009 08:29 Troy@bay 0B:TestTagFailure,15:TestTagFailure: 15 is a known problematic system. OB will be investigated on the next site visit. 12/18/2009 07:14 troy@bay 0B:TestTagFailure,15:TestTagFailure: Noted 12/17/2009 07:53 troy@bay 15:TestTagFailure: Known problematic system, clearing TASS. 12/15/2009 07:35 darren@b 15:TestTagFailure: Alarm on known problematic system. 12/14/2009 07:25 troy@bay 15:TestTagFailure: Clearing TASS on a known problematic system. 12/13/2009 08:45 darren@b 15:TestTagFailure: Alarm on known problematic system. 12/12/2009 07:34 darren@b 15:TestTagFailure: Alarm on known problematic system. 12/10/2009 07:10 darren@b 15:TestTagFailure: Alarm on problematic system. 12/09/2009 07:32 darren@b 15:Overrun,15:TestTagFailure: Alarm is on known problematic system. 12/08/2009 07:35 darren@b 15:TestTagFailure: Alarm on known problematic system. 12/07/2009 07:27 darren@b 15:TestTagFailure: Alarm on known problematic system. 12/06/2009 07:34 alan@bay 0E:ReaderReset,15:TestTagFailure: Clearing TASS- 0E is a common reader reset, 15 is a known problematic system. 12/05/2009 06:59 alan@bay 0B:TestTagFailure,15:TestTagFailure: These alarms will be investigated during the next site visit. 12/04/2009 07:21 alan@bay 15:TestTagFailure: Clearing TASS on a known problematic system. 12/03/2009 07:22 alan@bay 15:TestTagFailure: Clearing TASS on a known problematic system. 12/02/2009 08:42 alan@bay 15:TestTagFailure: Clearing TASS on a known problematic system. 11/30/2009 07:07 scottl@b 01:ReaderReset,02:LowExcCurrent,02:ReaderReset,03:ReaderReset,04:ReaderRes et,05:ReaderReset,06:ReaderReset,07:ReaderReset,08:ReaderReset,09:LowExcCu rrent,09:ReaderReset,0A:ReaderReset,0B:ReaderReset,0C:ReaderReset,0D:Reade rReset,0E:ReaderReset,0F:ReaderReset,10:ReaderReset,11:ReaderReset,12:Read erReset,13:ReaderReset,14:ReaderReset,15:ReaderReset,15:TestTagFailure,16: LowExcCurrent,16:ReaderReset,17:ReaderReset,18:ReaderReset,22:InputSyncDet ect,22:ReaderReset,24:InputSyncDetect,24:ReaderReset,26:InputSyncDetect,26 :ReaderReset,28:ReaderReset,32:InputSyncDetect,32:ReaderReset,34:InputSync Detect,34:ReaderReset,36:InputSyncDetect,36:ReaderReset,38:ReaderReset: Appears that a power glitch caused alarms, facility is not in use at this time. 11/24/2009 12:51 Alan A GMC was performed 11/24/2009. All transceivers were checked and tuned as necessary. All outstanding files on PC2 were archived. The temp folders on both PCs were emptied. The clocks on both PCs (~00:05:00 slow) were set to within one second of atomic time. File BO309328.207 was uploaded from PC2 to fill the gap during PC1's downtime. No problems found. 11/23/2009 10:58 Don_Warf Per site EE: Next week, I am going to try to take down the SMF facility here at Bonneville briefly. It might be down for less than a 1/2 hour--that's including clearance time and the actual work time. We are starting to replace the Station Service Bus 1 and Bus 2 Switchgears in PH2 and that will have an impact on a lot of the Bonn fish facilities when changing over from one bus to another. The SMF will be about the first facility to be affected. If we wind up replacing both of the buses' switchgear, then we will have 3 more fairly "brief" interruptions at SMF during this IWWP. If we only wind up doing 1 bus's switchgear then we should only have one more interruption after the first one for SMF for this IWWP. Additionally, we will have at least a at least 2--maybe 4--fairly "brief" interruptions of the power for B2CC, Cascade Island, and Bradford Island pit tag antennas during this upcoming IWWP time. I can talk to you about it in more detail--hopefully sometime next week. The B2CC and Cascade Island interruptions should be really brief. It should just involve opening and closing the two buses' circuit bkrs in the North Tower ATS. I should be up to my neck in clearances fairly shortly. There's really no way to get around these interruptions, but we can hope to make them as brief as possible. I have already talked to our Project head biologist, Ben Hausmann about the SMF clearance. I've also talked with Gene Ballinger of SMF. They are both alright with the planned outage. I am hoping to do the SMF outage next Tuesday (11/24), but it willl depend on electrician availability. 11/23/2009 10:18 Don_Warf DLW email test _____________________________________________ From: Don Warf Sent: Monday, November 23, 2009 9:26 AM To: 'pitevent@psmfc.org'; 'pitevent@ptagis.org' Subject: gra,grj,goj,rpj,lmj,ich,mcj,mc1,mc2,jdj,pro,esj,jcj,cfj,bcc,bo1,bo2,bo3,b2 j,rzf Email test 11/23/2009 09:39 Troy_Hum Email Test from Troy 11/22/2009 07:12 alan@bay 15:TestTagFailure,17:TestTagFailure: Noted 11/21/2009 07:15 alan@bay 15:TestTagFailure: Clearing TASS on a known problematic system. 11/19/2009 07:42 alan@bay 15:TestTagFailure: Clearing TASS on a known problematic system. 11/17/2009 07:25 alan@bay 15:TestTagFailure: Clearing TASS on a known problematic system. 11/16/2009 07:57 alan@bay 15:TestTagFailure: Clearing TASS on a known problematic system. 11/15/2009 09:17 troy@bay 15:Overrun,15:TestTagFailure: Known problematic system, clearing TASS. 11/14/2009 07:48 troy@bay 15:TestTagFailure: Known problematic system, clearing TASS. 11/13/2009 07:22 troy@bay 15:TestTagFailure: Known problematic system, clearing TASS. 11/12/2009 08:22 troy@bay 11:Overrun,15:TestTagFailure: This alarm will be addressed on the next site visit. 11/12/2009 07:27 Alan The Adult Fish Facility was dewatered for winter maintenance Monday, 11/9/2009, at approximately 1000. 11/11/2009 09:09 troy@bay 15:TestTagFailure: Noted 11/10/2009 07:32 troy@bay 15:TestTagFailure: Clearing TASS on a known problematic system. 11/09/2009 07:56 troy@bay 02:TestTagFailure,0B:TestTagFailure,15:TestTagFailure: These alarms will be addressed on the next site visit. 11/01/2009 07:44 darren@b 15:TestTagFailure: This alarm is on a known problematic system. 10/31/2009 08:49 darren@b 0B:TestTagFailure,15:TestTagFailure: The problems with antenna 0B are because the system has drifted. The alarms on 15 are on a known problematic system. 10/30/2009 08:29 alan@bay 0B:TestTagFailure,15:TestTagFailure,22:InputSyncDetect,22:InputSyncLost,26 :InputSyncDetect,26:InputSyncLost,28:ReaderReset: 0B will be monitored, 15 is a known issue, the flume alarms were caused by a random reader reset. 10/28/2009 15:46 Darren I was on site because the timer tag on antenna 0B was not firing. Upon arrival I found that the transceiver showed a Bad Checksum error. I tried to reset the parameters but that did not work. I replaced the transceiver and verified communications. 10/27/2009 08:10 alan@bay 15:TestTagFailure: Clearing TASS on a known problematic system. 10/26/2009 09:06 Alan The former DST rules caused the Multimon file creation intervals to be off by one hour. At 0759 10-26-2009, data collection was exited and restarted on both PCs to re-establish proper file creation intervals. File BO309299.102 was the last file created prior to this procedure and was submitted manually. Outstanding files on PC2 were archived. 10/26/2009 07:45 darren@b 15:TestTagFailure: Alarm on problematic system. 10/21/2009 07:44 troy@bay 15:TestTagFailure: Clearing TASS on a known problmatic system 10/20/2009 07:43 troy@bay 09:TestTagFailure,15:TestTagFailure: 15 is a known problematic system. 09 will be addressed on the next site visit. 10/18/2009 08:17 alan@bay 15:TestTagFailure: Noted. 10/17/2009 09:29 alan@bay 15:TestTagFailure: Noted 10/16/2009 08:01 alan@bay 15:TestTagFailure: Clearing TASS on a known problematic system. 10/15/2009 08:06 alan@bay 15:TestTagFailure: Clearing TASS on a known problematic system. 10/14/2009 13:37 alan@bay 11:Overrun,15:TestTagFailure: Noted. 10/11/2009 09:20 darren@b 15:TestTagFailure: Alarm on known problematic system. 10/10/2009 08:36 darren@b 15:TestTagFailure: Alarm on known problematic system. 10/08/2009 07:56 alan@bay 09:TestTagFailure,15:TestTagFailure: No apparent reason for the one time alarm on 09. PTAGIS Field Operations will continue to monitor. Clearing TASS on the known problematic system 15. 10/07/2009 07:17 darren@b 15:TestTagFailure: Alarm on problematic system. 10/06/2009 07:44 darren@b 15:TestTagFailure: Alarm on known problematic system. 10/05/2009 07:39 darren@b 07:ReaderReset,15:TestTagFailure: The alarms on antenna 15 are on a known problematic system. The alarm on 07 was generated by a random reader reset. 10/04/2009 09:31 troy@bay 15:TestTagFailure: Known problematic system, clearing TASS. 10/02/2009 07:16 darren@b 15:TestTagFailure,32:InputSyncDetect,32:ReaderReset: Alarm on antenna 15 is a known problematic system. The alarm on antenna 32 was caused by a random reader reset. 10/01/2009 07:51 darren@b 15:Overrun,15:TestTagFailure: Alarm noted on problematic system. 09/30/2009 07:41 alan@bay 15:TestTagFailure: Clearing TASS on a known problematic system. 09/27/2009 07:49 alan@bay 15:TestTagFailure: Clearing TASS on a known problematic system. 09/26/2009 07:39 alan@bay 15:TestTagFailure: Clearing TASS on a known problematic system. 09/25/2009 23:20 alan@bay 15:TestTagFailure: Clearing TASS on a known problematic system. 09/23/2009 08:58 alan@bay 15:TestTagFailure: Clearing TASS on a known problematic system. 09/22/2009 07:46 alan@bay 15:TestTagFailure: Clearing TASS on a known problematic system. 09/21/2009 07:50 alan@bay 15:TestTagFailure: Clearing TASS on a known problematic system. 09/19/2009 07:48 troy@bay 15:TestTagFailure: Known problematic system. 09/18/2009 07:47 troy@bay 15:TestTagFailure,26:InputSyncDetect,26:ReaderReset: 15 is a known problematic system, possible random reader reset for 26 09/16/2009 12:38 troy@bay 15:TestTagFailure: Known problem on prolematic system. 09/15/2009 07:24 troy@bay 15:TestTagFailure: Clearing TASS on known problematic system. 09/14/2009 07:41 troy@bay 15:TestTagFailure: Known problematic system, clearing TASS 09/09/2009 07:45 darren@b 15:TestTagFailure: Alarm is on a known problematic system. 09/07/2009 08:57 darren@b 15:TestTagFailure: Alarm is on a known problematic system. 09/06/2009 08:16 darren@b 15:TestTagFailure: Alarm is on a known problematic system. 09/05/2009 07:58 darren@b 15:TestTagFailure: Alarm on problematic system. 09/04/2009 07:22 darren@b 11:LowExcCurrent,15:TestTagFailure,16:LowExcCurrent: The alarms on antennas 11 and 16 were generated by PSMFC personnel during a site GMC. The alarms on antenna 15 are on a known problematic system. 09/03/2009 12:07 Darren A site GMC was performed today 9-3-09. All transceivers were checked and adjusted for tuning, noise and detectability. The files on PC2 were archived. No problems were discovered during this visit. 09/03/2009 07:08 darren@b 15:TestTagFailure: Alarm on problematic system. 09/02/2009 07:06 darren@b 15:TestTagFailure,26:InputSyncDetect,26:ReaderReset: Alarm on antenna 15 is on a known problematic system. The alarm on 26 was caused by a random reader reset. 09/01/2009 07:20 darren@b 15:TestTagFailure: Alarm on problematic system. 08/31/2009 07:10 darren@b 15:TestTagFailure: Alarm noted on problematic system. 08/30/2009 10:07 troy@bay 15:TestTagFailure: Clearing TASS on known problematic system. 08/29/2009 09:57 troy@bay 15:TestTagFailure: Problematic system, clearing TASS. 08/28/2009 07:46 troy@bay 15:TestTagFailure: Clearing TASS on known problematic system. 08/26/2009 08:02 troy@bay 15:TestTagFailure: Clearing TASS on a known problematic system. 08/25/2009 07:49 troy@bay 15:TestTagFailure: Clearing TASS on known problematic system. 08/24/2009 08:38 troy@bay 15:TestTagFailure: Clearing TASS on known problematic system. 08/23/2009 08:23 alan@bay 15:TestTagFailure: Noted 08/22/2009 07:47 alan@bay 15:TestTagFailure: Clearing TASS on a known problematic system. 08/21/2009 07:40 alan@bay 15:TestTagFailure: Clearing TASS on a known problematic system. 08/20/2009 07:43 alan@bay 14:ReaderReset,15:TestTagFailure,17:LowExcCurrent: These alarms were generated by PTAGIS Field Operations personnel during a site visit. 08/19/2009 10:40 Darren A site GMC was performed today 8-19-09. All transceivers were checked and adjusted for tuning, noise and detectability. Transceiver 13 was found to non operational when I arrived. The breaker inside the power panel had been tripped, it was reset but the unit would not power on. The transceiver was replaced and and bi-directional comms were verified. The PC clocks are within 20 seconds of each other and atomic time. The files on PC2 were archived. No other problems were discovered during this visit. 08/19/2009 07:50 alan@bay 15:TestTagFailure: Clearing TASS on a known problematic system. 08/18/2009 07:37 alan@bay 15:TestTagFailure: Clearing TASS on a known problematic system. 08/17/2009 11:03 alan@bay 15:TestTagFailure: Clearing TASS on a known problematic system. 08/16/2009 10:47 alan@bay 15:TestTagFailure: Clearing TASS on a known problematic system. 08/15/2009 10:32 Alan Transceiver 13 went AWOL at ~19:30 PST 8-14 2008. The other transceivers in the ladder are functioning normally. This will be investigated during a site visit Wednesday. 08/15/2009 10:11 alan@bay 15:TestTagFailure: Clearing TASS on a known problematic system. 08/13/2009 07:42 alan@bay 15:TestTagFailure: Clearing TASS on a known problematic system. 08/12/2009 07:51 alan@bay 15:TestTagFailure: Clearing TASS on a known problematic system. 08/11/2009 07:39 alan@bay 15:TestTagFailure: Clearing TASS on a known problematic system. 08/10/2009 07:40 alan@bay 15:TestTagFailure: Clearing TASS on a known problematic system. 08/09/2009 09:03 darren@b 15:TestTagFailure: Alarm on problematic system. 08/08/2009 08:42 darren@b 15:TestTagFailure: This alarm is on a known problematic system. 08/04/2009 07:22 darren@b 15:TestTagFailure,18:LowExcCurrent: The alarms on 15 are on a known problematic system. The alarms on antenna 18 were addressed yesterday by PSMFC personnel during a site GMC. 08/03/2009 11:08 Troy A site GMC was performed 08/03/2009. All transceivers were checked for tune and adjustments made where needed. PC1 is 28 seconds behind atomic time and PC2 is 24 seconds behind atomic time. 08/03/2009 07:56 alan@bay 15:TestTagFailure,18:TestTagFailure: 15 is a known issue, 18 will be investigated today during a site visit. 07/30/2009 09:58 troy@bay 15:TestTagFailure,18:TestTagFailure: Clearing TASS on known problematic systems. 07/26/2009 09:07 darren@b 15:TestTagFailure,18:TestTagFailure: The alarm on 15 is on a known problematic system. The alarm on 18 will be investigated during the next site visit. 07/25/2009 09:07 darren@b 11:Overrun,15:TestTagFailure,18:TestTagFailure: Alarms will be investigated during the next site visit. 07/23/2009 08:37 darren@b 15:TestTagFailure,18:TestTagFailure: The alarms on antenna 15 are on a known problematic system. The alarms on antenna 18 were investigated during a site GMC. 07/22/2009 13:29 Alan A GMC was performed 7/22/2009. All transceivers were checked and tuned as necessary. All outstanding files on PC2 were archived. The clocks on both PCs (~00:01:45 slow) were set to within one second of atomic time. File BO309203.207 was uploaded from PC2 to fill the gap during PC1's downtime. No problems found. 07/16/2009 12:57 scottl Performed site GMC, all transceivers were retuned and calibrated as necessary, no problems to report. 07/16/2009 08:53 darren@b 15:TestTagFailure,18:TestTagFailure,22:InputSyncDetect,22:ReaderReset: The alarms on antenna 15 are on a known problematic system. The other alarms will be addressed today during a site GMC. 07/12/2009 09:18 troy@bay 15:TestTagFailure,18:TestTagFailure: These antennas are known to be a bit problematic. They will be looked into on the next site visit. 07/11/2009 09:39 troy@bay 11:Overrun,15:TestTagFailure,18:TestTagFailure: Known problems, clearing TASS. 07/10/2009 08:45 darren@b 15:TestTagFailure,22:InputSyncDetect,22:InputSyncLost,26:InputSyncDetect,2 6:InputSyncLost,28:ReaderReset: Alarms on 28-22 were generated by a random reader reset on 28. The failures on 15 are on a known problematic system. 07/09/2009 14:37 Troy A site GMC was performed 07/09/09. All transceivers were checked for tune and adjustments attemtped. The upper ladder is noisy, as seen in the earlier part of this years season. No amount of tuning reduces the noise. PSMFC is hoping to consult with the COE to find what may be causing this noise. PC1 is 50 seconds behind atomic time and PC2 is 62 seconds behind atomic time. No other problems to report. 07/09/2009 08:33 darren@b 15:TestTagFailure,18:TestTagFailure: Alarms on antenna 15 are on a known problematic system. The alarms on 18 will be investigated today during a iste GMC. 07/08/2009 08:06 darren@b 15:TestTagFailure: Alarm on known problematic system. 07/07/2009 08:05 darren@b 15:TestTagFailure,18:TestTagFailure: The test tag failures on antenna 15 are on a known failing antenna. The failure on antenna 18 will be investigated during the next site visit. 07/06/2009 09:41 alan@bay 15:TestTagFailure,18:TestTagFailure: These alarms will be investigated during the next site visit. 07/05/2009 09:17 troy@bay 15:TestTagFailure,18:TestTagFailure: Noted 07/02/2009 08:35 alan@bay 06:LowExcCurrent,15:TestTagFailure,17:LowExcCurrent,18:TestTagFailure: These alarms will be investigated during the next site visit. 06/30/2009 12:21 Darren A site GMC was performed today 6-30-09. All transceivers were checked fro tuning, noise and detectability, especially systems 06 and 09. There is noise on antenna 06 but there did not appear to be any noise on 09, all others were adjusted as necessary. No problems were discovered during this visit. 06/30/2009 08:27 troy@bay 15:TestTagFailure: Clearing TASS on known probelmatic system. 06/28/2009 08:25 alan@bay 15:TestTagFailure,16:ReaderReset: Clearing TASS on transceiver 15, a known problematic system. The alarm on transceiver 16 is a random reader reset. 06/27/2009 08:03 alan@bay 18:TestTagFailure: This transceiver is experiencing noise into the 20's, but is still reading PIT tags. This alarm will be investigated during the next site visit. 06/27/2009 08:01 alan@bay 15:TestTagFailure: Clearing TASS on a known problematic system. 06/26/2009 08:33 alan@bay 15:TestTagFailure: Clearing TASS on a known problematic system. 06/26/2009 08:32 alan@bay 18:TestTagFailure: This transceiver is experiencing noise into the 20's, but is still reading PIT tags. This alarm will be investigated during the next site visit. 06/25/2009 08:42 alan@bay 11:Overrun,15:TestTagFailure: Clearing TASS on known problematic systems. 06/25/2009 08:41 alan@bay 18:TestTagFailure: No apparent reason for this alarm. PTAGIS Field Operations will continue to monitor. 06/25/2009 08:41 alan@bay 08:ReaderReset: This alarm is the result of a random reader reset 06/22/2009 12:50 Darren A site GMC was performed today 6-22-09. All transceivers were checked for tuning, noise, and detectability. Antennas 11 and 15 are having below water line problems and have been well documented. No problems were discovered during this visit. 06/22/2009 09:06 alan@bay 15:TestTagFailure,18:TestTagFailure: A juvenile chinook, 3D9.1C2CBE0DCC, is probably swimming around antenna 18 (or has shed it's tag) causing the TT alarm on 18. PTAGIS Field Operations will continue to monitor. Transceiver 15 is a known problematic system. 06/21/2009 08:43 darren@b 15:TestTagFailure,18:TestTagFailure: The alarm on antenna 15 is on a known problematic system and the alarm on antenna 18 will be investigated during the next site visit. 06/20/2009 09:00 darren@b 15:TestTagFailure: Alarm on problematic system. 06/19/2009 08:12 darren@b 15:TestTagFailure: Alarm on problematic system. 06/18/2009 08:05 darren@b 05:BadExcFreq,05:BadOscFreq,05:LowExcCurrent,06:ReaderReset,0B:LowExcCurre nt,0E:LowExcCurrent,11:BadExcFreq,11:BadOscFreq,11:LowExcCurrent,11:Reader Reset,11:TestTagFailure,15:TestTagFailure: All of these alarms with the exception of antenna 15 were generated by PSMFC personnel while performing a site GMC. 06/17/2009 13:22 Darren A GMC was performed 6/17/2009. All transceivers were checked and tuned as necessary. The noise on antenna 06 appears to be something out at the antenna, I swapped transceivers and the noise followed the antenna. The problem could below the water line or possible broken conduit.All outstanding files on PC2 were archived. PC1 is 14 seconds behind atomic time, PC2 is 2 seconds behind PC1. No problems found. 06/16/2009 07:59 darren@b 15:TestTagFailure: Alarm occurred on a known problematic system. 06/15/2009 09:59 darren@b 15:TestTagFailure,18:TestTagFailure: Alarm on antenna 15 is a known problematic system. The alarms on 18 will be investigated during the next site visit. 06/11/2009 14:17 Troy A GMC was performed 6/11/2009. All transceivers were checked and tuned as necessary. BO4 transceivers are not showing noise. BO3 transceivers 03, 05, 07, 09 and 0B show noise in the teens which is usual when BO4 is quiet. All outstanding files on PC2 were archived. Both PCs were set to within one second of atomic time. No other problems found. 06/10/2009 08:22 scottl@b 03:TestTagFailure: Noted 06/08/2009 08:03 darren@b 15:TestTagFailure: This alarm is a known failure on a problematic system. 06/07/2009 10:25 troy@bay 15:TestTagFailure: Clearing TASS on a known problematic system. 06/06/2009 09:23 troy@bay 06:ReaderReset,06:TestTagFailure,15:TestTagFailure,17:LowExcCurrent,18:Tes tTagFailure: These alarms will be addressed on the next site visit. 06/02/2009 08:23 troy@bay 15:TestTagFailure: Clearing TASS on a known problematic system. 06/01/2009 08:20 troy@bay 15:TestTagFailure,18:TestTagFailure: Known problematic antenna's, clearing TASS. 05/31/2009 09:38 alan@bay 15:TestTagFailure: Clearing TASS on a known problematic system. 05/30/2009 10:58 alan@bay 15:TestTagFailure: Clearing TASS on a known problematic system. 05/29/2009 08:25 alan@bay 15:TestTagFailure: Clearing TASS on a known problematic system. 05/28/2009 08:31 alan@bay 15:TestTagFailure: Clearing TASS on a known problematic system. 05/27/2009 13:50 Alan A GMC was performed 5/27/2009. All transceivers were checked and tuned as necessary. All outstanding files on PC2 were archived. Both PCs are 49 seconds behind atomic time. No problems found. 05/26/2009 09:28 alan@bay 15:TestTagFailure: Clearing TASS on a known problematic system. 05/22/2009 08:42 darren@b 15:TestTagFailure,18:TestTagFailure: Alarms on antenna system 15 are known problems with the system. The tag failure on 18 does not have any direct cause for the failure and will be investigated during the next site GMC. 05/20/2009 13:12 Alan A GMC was performed 5/20/2009. All transceivers were checked and tuned as necessary. All outstanding files on PC2 were archived. Both PCs are 37 seconds behind atomic time. No problems found. 05/20/2009 08:14 scottl@b 15:TestTagFailure,16:ReaderReset: Noted 05/18/2009 08:57 darren@b 15:TestTagFailure: Alarm on problematic system. 05/17/2009 08:23 darren@b 15:TestTagFailure: alarm on problematic system. 05/16/2009 07:44 darren@b 15:TestTagFailure: Alarm on problematic system. 05/15/2009 08:22 troy@bay 15:TestTagFailure: Clearing TASS on problematic system 05/14/2009 13:43 Alan A GMC was performed 5/14/2009. All transceivers were checked and tuned as necessary. All outstanding files on PC2 were archived. The clocks on both PCs were set to within one second of atomic time. No problems found. 05/12/2009 08:33 alan@bay 15:TestTagFailure: Clearing TASS on a known problematic system. 05/11/2009 08:46 darren@b 15:TestTagFailure: Alarm on problematic system. 05/10/2009 08:53 troy@bay 15:TestTagFailure: Known problem, clearing TASS. 05/09/2009 09:41 troy@bay 15:TestTagFailure: Known issue on problematic system, clearing TASS. 05/08/2009 09:13 troy@bay 15:TestTagFailure: Clearing TASS on a known problematic system. 05/07/2009 11:17 Darren A site GMC was performed today 5-7-09. All transceivers were checked for tuning, noise and detectability.They were adjusted as necessary to optimize the detection systems. No problems were discovered during this visit. 05/07/2009 09:36 alan@bay 15:TestTagFailure: Clearing TASS on a known problematic system. 05/04/2009 10:12 troy@bay 15:TestTagFailure: Known problem, clearing TASS. 05/03/2009 08:24 darren@b 15:TestTagFailure: Alarm on problematic system. 05/02/2009 08:36 darren@b 15:TestTagFailure: Alarm on problematic system. 05/01/2009 12:10 Darren A site GMC was performed today 5-1-09. The RAM was upgraded on PC1 and PC2 and the transceivers were checked for tuning, noise and detectability. The clock on PC2 was 40 seconds fast of PC2 and 32 seconds fast of atomic time so the clock was adjusted to within 1 second of PC1 and 9 seconds of PC2. No problems were discovered during this visit. 04/30/2009 07:43 darren@b 15:TestTagFailure: Alarm on problematic system. 04/29/2009 07:58 darren@b 15:TestTagFailure: Alarm on problematic system. 04/28/2009 08:18 darren@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:BadExcFreq,11:BadOscFreq,11:LowExcCurrent,11:ReaderReset,12:ReaderRe set,13:ReaderReset,14:ReaderReset,15:ReaderReset,15:TestTagFailure,16:Read erReset,17:ReaderReset,18:ReaderReset,22:InputSyncDetect,22:ReaderReset,24 :InputSyncDetect,24:ReaderReset,26:InputSyncDetect,26:ReaderReset,28:Reade rReset,32:InputSyncDetect,32:ReaderReset,34:InputSyncDetect,34:ReaderReset ,36:InputSyncDetect,36:ReaderReset,38:ReaderReset: These alarms were generated during the PH2 power issues. 04/28/2009 08:16 Darren This message was sent yesterday after the message from Tammy Mackey. PH2 units 12-17 have been restored as of 1600 and we are back to our 95K pattern. Fish unit 2 breaker was having issues and was not closing properly so we are still in the process of bringing that unit back in service. Per the e-mail and description below only units 12-17 were tripped of line not all ten as Tammy mentions. Unit 11 remains OOS for rotor pole issues and unit 18 was OOS today for Preferred AC panel installation. Power to the Smolt Monitoring building was restored around 1600 and DSM2 and it's associated orifices and add-in valves have been returned to normal at 1610. The Transformer Trip has been isolated to a signal from the BPA North Bonneville Substation. No work at the project caused this signal to trip the relay so we are in the process of identifying the source. I want to especially thank all project entities involved for their help and support but especially Mr. Brad Sharp and Mr. Dave Smith the L-grades in the Control room and Ray Guajardo, Steve Layn and Tom Cahill I-grades at PH1 and PH2 for their incredible professionalism and quick reactive thinking that allowed us to pull PH2 back online and restart critical hatchery wells in short order. Once I have a full understanding of all of the items and how things evolved I will send out a full e-mail with all of the details. Thanks, Dennis 04/28/2009 08:14 Darren This message was sent yesterday from Tammy Mackey site biologist for Bonneville Dam. Around 1400 on 27 April, it is believed T11/12 tripped, taking the Powerhouse Two offline (all ten turbines). With no turbine capacity at PH2, spill was increased to accommodate flows. At this time spill is roughly 250K. With the power outage, the DSM2 orifices closed, the STSs stopped traveling and the ERG tripped open. The add-in water continues to flow so fish are not stranded in the channel, however, there is no egress from the gatewells. There is no power to the JMF. The upper switchgate moved to the bypass position. The lower switchgate will remain in the high outfall position. The PIT tag detectors are without power, however all fish should have been flushed through by the flushing flow. The B2CC remains open, but the PIT tag detector may have lost power. For the adult fishway, there is no attraction flow from the fish units and the entrance gates, already in manual, are set where they are. The SLADDs are no longer making noise. The Main Dam fishways remain in operation as do all fish facilities at PH1. The Project if working to restore unit capability as quickly as possible. A completed Notification form will be sent once more details are known. Thank you, Tammy 04/27/2009 09:46 alan@bay 15:TestTagFailure: Clearing TASS on a known problematic system. 04/26/2009 10:40 alan@bay 15:TestTagFailure: Clearing TASS on a known problematic system. 04/25/2009 10:56 alan@bay 15:TestTagFailure: Clearing TASS on a known problematic system. 04/24/2009 08:17 alan@bay 15:TestTagFailure: Clearing TASS on a known problematic system. 04/23/2009 10:39 darren@b 15:TestTagFailure: Alarm on problematic system. 04/23/2009 08:50 darren@b 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:Overrun,11:ReaderReset,12:ReaderReset,13:ReaderReset, 14:ReaderReset,15:ReaderReset,15:TestTagFailure,16:ReaderReset,17:ReaderRe set,18:ReaderReset,22:InputSyncDetect,22:ReaderReset,24:InputSyncDetect,24 :ReaderReset,26:InputSyncDetect,26:ReaderReset,28:ReaderReset,32:InputSync Detect,32:ReaderReset,34:InputSyncDetect,34:ReaderReset,36:InputSyncDetect ,36:ReaderReset,38:ReaderReset: Site experienced a brief power outage. 04/22/2009 15:51 Troy A site GMC was performed 04/22/2009. All transceivers were checked for tune and adjustments made where needed. The power was accidentally shut off by a COE employee while I was trying to set the clocks on PC1 and PC2 (PC1 was 2:26 behind atomic time and PC2 was 2:05 behind atomic time) The gap file is BO3112.207. No other problems to report. PC1 and PC2 are now within 2 seconds of each other and atomic time. 04/16/2009 09:02 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,0C:ReaderReset,0D:ReaderReset,0E:ReaderReset,0F:ReaderRes et,10:ReaderReset,11:ReaderReset,12:ReaderReset,12:TestTagFailure,13:Reade rReset,14:ReaderReset,15:ReaderReset,15:TestTagFailure,16:ReaderReset,17:R eaderReset,18:ReaderReset,22:InputSyncDetect,22:ReaderReset,24:InputSyncDe tect,24:ReaderReset,26:InputSyncDetect,26:ReaderReset,28:ReaderReset,32:In putSyncDetect,32:ReaderReset,34:InputSyncDetect,34:ReaderReset,36:InputSyn cDetect,36:ReaderReset,38:ReaderReset: Unscheduled power outage. 04/12/2009 08:01 alan@bay 15:TestTagFailure: Clearing TASS on a known problematic system. 04/12/2009 08:01 alan@bay 0B:ReaderReset: This alarm is the result of a random reader reset. PSMFC and Destron Fearing are aware of the problem. 04/11/2009 09:57 alan@bay 15:TestTagFailure: Clearing TASS on a known problematic system. 04/10/2009 09:04 alan@bay 09:LowExcCurrent,0A:BadExcFreq,0A:BadOscFreq,0A:LowExcCurrent,0A:TestTagFa ilure,15:TestTagFailure: These alarms were generated by PTAGIS Field Operations personnel during a site visit. 04/09/2009 12:30 Troy A site GMC was performed 04/09/2009. All transceivers were checked for tune and adjustments made where needed. PC1 is within 16 seconds of PC2. 0A was found to be noisy and the noise could not be tuned out. Further troubleshooting showed that the trouble followed the antenna. The antenna may be going bad or there may be debris in the antenna, PSMFC will monitor. 04/09/2009 08:32 alan@bay 15:TestTagFailure: Clearing TASS on a known problematic system. 04/08/2009 11:55 alan@bay 15:TestTagFailure: Clearing TASS on a known problematic system. 04/07/2009 08:28 alan@bay 15:TestTagFailure: Clearing TASS on a known problematic system. 04/06/2009 08:29 alan@bay 15:TestTagFailure: Clearing TASS on a known problematic system. 04/05/2009 20:53 Dave File OPEN/CLOSE intervals shifted forward one hour at 2AM because Win98 thinks today is the first day of Daylight Savings Time. I stopped and then restarted data collection in MultiMon on BO3-PC1 and BO3-PC2, as required in these situations. 04/05/2009 10:23 troy@bay 15:TestTagFailure: Known problematic system, clearing TASS. 04/05/2009 10:09 Troy Stopped and started the uploader and pushed the delinquent file. 04/04/2009 10:09 troy@bay 15:TestTagFailure: Noted 04/03/2009 12:31 Troy A site GMC was performed 04/03/2009. All transceivers were checked for tune and adjustments made where needed. No problems to report. 04/03/2009 08:47 darren@b 15:TestTagFailure: Alarm on problematic system. 04/02/2009 13:26 troy@bay 15:TestTagFailure: Noted 03/31/2009 08:20 troy@bay 15:TestTagFailure: Noted 03/30/2009 08:34 troy@bay 15:TestTagFailure: Noted 03/29/2009 09:41 darren@b 15:TestTagFailure: Alarm on problematic system. 03/28/2009 08:01 darren@b 15:TestTagFailure: Alarm on Problematic system. 03/27/2009 23:31 darren@b 15:TestTagFailure: Problem noted on problematic system. 03/26/2009 10:34 alan@bay 15:TestTagFailure: Clearing TASS on a known problematic system. 03/24/2009 09:12 troy@bay 15:TestTagFailure: Known problematic system, clearing TASS. 03/19/2009 08:27 troy@bay 08:ReaderReset,15:TestTagFailure: These alarms will be investigated on the next site visit. 03/15/2009 09:04 troy@bay 15:TestTagFailure: Known problematic system, clearing TASS. 03/14/2009 08:25 troy@bay 15:TestTagFailure: Known problem antenna, clearing TASS. 03/12/2009 08:28 troy@bay 15:TestTagFailure: Known problem antenna, clearing TASS. 03/11/2009 13:41 Troy A site GMC was performed 03/11/2009. All transceivers were checked for tune and adjustments made where needed. PC1 is 3 sec's faster than PC2 and 18 sec's behind atomic time. 03/10/2009 08:11 troy@bay 15:TestTagFailure: Known problem antenna, clearing TASS. 03/09/2009 08:37 troy@bay 15:TestTagFailure: Noted, known problematic antenna. 03/08/2009 08:17 alan@bay 15:TestTagFailure: Clearing TASS on known problem antenna. 03/07/2009 06:45 alan@bay 15:TestTagFailure: Clearing TASS on a known problematic system. 03/06/2009 11:27 alan@bay 15:TestTagFailure: Clearing TASS on a known problematic antenna. 03/05/2009 11:56 alan@bay 0E:LowExcCurrent,15:TestTagFailure: The current and threshold for transceiver 0E were matched at 2900mA. I remotely lowered the threshold to 2600mA. This will be investigated during the next site visit. Clearing TASS on known problematic antenna 15. 03/04/2009 15:25 Dave I was on-site earlier today to reset the B03 MultiMon platform for the beginning of the year. I cleared all the old counter and log files, erased the persistent default.cfg file, and reset MultiMon to use the generic db, map, and b2j-0600 hardware files. Since the site is already up and running, I seamlessly patched the data between PC2 and PC1. Once back in the office, I pcA'd into BO3-PC1 to verify the configuration. I ran into a memory allocation error for MultiMon as I tried to switch from a partial window to a full DOS screen. I worked through the error and restored the full DOS box, at which point the screen displayed in reverse video. I again placed MultiMon in a partial window, stopped data collection, and exited the program. (You MUST exit from a window when connected via pcA!). I then restarted MultiMon (minimized, as expected) and brought it back into a full DOS box without any further errors. 03/04/2009 08:31 alan@bay 15:TestTagFailure: Clearing TASS on a known problematic system. 03/04/2009 08:28 Alan Manually pushed BO309063.102 to PTAGIS via PCA. 03/03/2009 08:23 darren@b 15:TestTagFailure: This is a problematic detection system. 03/01/2009 08:11 darren@b 02:LowExcCurrent,05:LowExcCurrent,05:TestTagFailure,08:LowExcCurrent,0D:Lo wExcCurrent,0E:LowExcCurrent,15:TestTagFailure,18:TestTagFailure,22:InputS yncDetect,22:ReaderReset: It appears that the ladder watered-up yesterday around 10:30-11:00. I will try to confirm the times and I will update the site operational page when I have the information. 02/02/2009 07:51 troy@bay 02:LowExcCurrent,05:LowExcCurrent,05:TestTagFailure,08:LowExcCurrent,0D:Lo wExcCurrent,15:TestTagFailure,16:LowExcCurrent,18:TestTagFailure: Site dewatered,clearing TASS. 01/28/2009 07:03 scottl@b 01:ReaderReset,02:LowExcCurrent,02:ReaderReset,03:ReaderReset,04:ReaderRes et,05:LowExcCurrent,05:ReaderReset,05:TestTagFailure,06:ReaderReset,07:Rea derReset,08:LowExcCurrent,08:ReaderReset,09:ReaderReset,0A:ReaderReset,0B: ReaderReset,0C:ReaderReset,0D:LowExcCurrent,0D:ReaderReset,0E:LowExcCurren t,0E:ReaderReset,0F:ReaderReset,10:ReaderReset,11:ReaderReset,12:ReaderRes et,12:TestTagFailure,13:ReaderReset,14:ReaderReset,15:ReaderReset,15:TestT agFailure,16:ReaderReset,17:ReaderReset,18:ReaderReset,18:TestTagFailure,2 2:InputSyncDetect,22:ReaderReset,24:InputSyncDetect,24:ReaderReset,26:Inpu tSyncDetect,26:ReaderReset,28:ReaderReset,32:InputSyncDetect,32:ReaderRese t,34:InputSyncDetect,34:ReaderReset,36:InputSyncDetect,36:ReaderReset,38:R eaderReset: Alarms were caused by a power outage. The facility and ladder are not operational at this time. 01/24/2009 09:08 darren@b 02:TestTagFailure,05:LowExcCurrent,05:TestTagFailure,0E:LowExcCurrent,15:O verrun,15:TestTagFailure,18:TestTagFailure: Site down. Clearing TASS. 01/19/2009 09:17 troy@bay 02:TestTagFailure,0E:LowExcCurrent,15:TestTagFailure: Site down, clearing TASS. 01/19/2009 09:09 Troy Archived old zip files and pushed the delinquent file. 01/18/2009 08:10 Troy Manually pushed BO309018.B1 to PTAGIS. 01/17/2009 09:34 troy@bay 01:ReaderReset,02:ReaderReset,02:TestTagFailure,03:ReaderReset,04:ReaderRe set,05:LowExcCurrent,05:ReaderReset,06:ReaderReset,07:ReaderReset,08:Reade rReset,09:ReaderReset,0A:ReaderReset,0B:ReaderReset,0C:ReaderReset,0D:Read erReset,0E:LowExcCurrent,0E:ReaderReset,0F:ReaderReset,10:ReaderReset,11:R eaderReset,12:ReaderReset,12:TestTagFailure,13:ReaderReset,14:ReaderReset, 15:ReaderReset,15:TestTagFailure,16:ReaderReset,17:ReaderReset,18:ReaderRe set,22:InputSyncDetect,22:ReaderReset,24:InputSyncDetect,24:ReaderReset,26 :InputSyncDetect,26:ReaderReset,28:ReaderReset,32:InputSyncDetect,32:Reade rReset,34:InputSyncDetect,34:ReaderReset,36:InputSyncDetect,36:ReaderReset ,38:ReaderReset: Alarms caused by a power outage. Site down clearing TASS. 01/13/2009 07:59 troy@bay 02:TestTagFailure,03:LowExcCurrent,05:LowExcCurrent,06:LowExcCurrent,08:Lo wExcCurrent,09:LowExcCurrent,0B:LowExcCurrent,0D:LowExcCurrent,0E:LowExcCu rrent,0F:LowExcCurrent,15:TestTagFailure,18:LowExcCurrent: Site down for season, clearing TASS. 01/12/2009 10:42 Darren The Washington shore ladder was de-watered as of 10:00 on 1-12-09. The site operational status page has been updated. The ladder is scheduled to be out of service until 2-28-09. 01/11/2009 07:09 darren@b 15:TestTagFailure: Alarm on problematic system. 01/10/2009 07:26 darren@b 15:TestTagFailure: Alarm on problematic system. 01/09/2009 07:11 darren@b 15:TestTagFailure: Alarm noted on problematic system. 01/08/2009 07:21 darren@b 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: It appears that there were two separate power issues at the site causing the alarms. 01/07/2009 07:00 darren@b 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:InputSyncLost,22:ReaderReset,24:InputSyncDet ect,24:ReaderReset,26:InputSyncDetect,26:InputSyncLost,26:ReaderReset,28:R eaderReset,32:InputSyncDetect,32:ReaderReset,34:InputSyncDetect,34:ReaderR eset,36:InputSyncDetect,36:ReaderReset,38:ReaderReset: Site Power outage. CLearing TASS. 01/06/2009 07:06 darren@b 01:LowExcCurrent,02:LowExcCurrent,0A:LowExcCurrent,0E:LowExcCurrent,0E:Tes tTagFailure,12:TestTagFailure,15:TestTagFailure: These alarms may have been generated by PSMFC personnel during a site GMC. 01/05/2009 12:21 Alan A GMC was performed 1/5/2008. All transceivers were checked and tuned as necessary. The clocks on both PCs (~5 min slow) were set to within one second of atomic time. Data files from 2008 were moved from the archive folder to the "Previous Years' Data\2008" folder on both PCs. File BO309005.206 was uploaded from PC2 the fill the gap during PC1's downtime. No problems found. 01/05/2009 07:31 darren@b 15:TestTagFailure: Alarm noted on probelmatic system. 01/01/2009 00:00 PTOC_Bot Annual log file initiation for BO3 #### End of Event Log for BO3 ###