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/2007 11:27 Troy Hello, We dewatered the fish ladder AFF fish ladder this morning, 12/31/07, at about 0930. It will remain dewatered until this coming year's research begins. The WA shore ladder is still in service. Jon Rerecich Fisheries Biologist USACE Bonneville Lock and Dam 541-374-7984 jonathan.g.rerecich@usace.army.mil 12/30/2007 08:12 troy@ruf 15:Overrun: Known issue,clearing TASS. 12/28/2007 07:16 troy@ruf 07:ReaderReset,0F:ReaderReset: Possible Random Reader Reset. PSMFC will monitor for future occurances. 12/25/2007 09:40 troy@ruf 15:Overrun: This antenna is suspected to have issues below the water line. 12/22/2007 08:31 troy@ruf 11:Overrun: PSMFC will monitor for future occurances. 12/20/2007 07:14 troy@ruf 15:Overrun: This antenna is known to have issues below the water line. 12/19/2007 07:24 troy@ruf 04:LowExcCurrent: This alarm was generated during a site GMC. 12/18/2007 12:45 Alan A GMC was performed 12/18/2007. All transceivers were tuned. PC1 was interrogating properly upon arrival, but PCA was out of service according to a cryptic windows error. PC1 was rebooted to restore operation. No activity was observed on PC2 during PC1's downtime. The clocks on both PCs were set to within one second of atomic time. No other problems found. 12/17/2007 07:43 troy@ruf 15:Overrun: Noted 12/09/2007 07:54 darren@r 15:Overrun: This alarm has been noted. 12/08/2007 08:59 darren@r 15:Overrun: This system has been well documented and PSMFC will address any alarms and will adjust the system for it's peak performance on the next site visit. 12/06/2007 07:53 darren@r 15:Overrun: The system has been well documented. 12/04/2007 07:09 darren@r 15:Overrun: Alarm noted. This system is well documented. 12/03/2007 07:23 darren@r 15:Overrun: Alarms noted. Detection system has been well documented. 12/02/2007 08:38 Alan Manually pushed BO307336.102 02-Dec to PTAGIS via PCA. 12/01/2007 09:00 alan@ree 15:LowExcCurrent: Noted 12/01/2007 08:59 alan@ree 0C:ReaderReset: This alarm was caused by a random reader reset. PSMFC and DA are aware of the problem. 11/30/2007 07:31 alan@ree 11:Overrun,15:LowExcCurrent,15:Overrun: Noted 11/29/2007 07:40 alan@ree 15:Overrun: Noted 11/26/2007 07:32 alan@ree 15:LowExcCurrent,15:Overrun: Noted 11/25/2007 11:00 alan@ree 15:Overrun: Moted 11/24/2007 08:20 alan@ree 15:Overrun: Noted 11/23/2007 08:49 alan@ree 15:Overrun: Noted 11/22/2007 09:16 alan@ree 15:Overrun: Noted 11/21/2007 07:54 alan@ree 15:Overrun: Noted 11/20/2007 07:49 alan@ree 15:LowExcCurrent,15:Overrun,15:TestTagFailure: Noted 11/19/2007 13:35 Alan A GMC was performed 11/19/2007. All transceivers were checked and tuned as necessary. Both PCs clocks were set to within one second of atomic time. No activity was observed on PC2 during PC1's downtime. No problems found. 11/15/2007 07:24 darren@r 15:LowExcCurrent,15:TestTagFailure: 15:LowExcCurrent,15:TestTagFailure: This system will be investigated during the next site visit. Every effort will be made to try and stabilize the system. 11/15/2007 07:24 darren@r 15:LowExcCurrent,15:TestTagFailure: This system will be investigated during the next site visit. Every effort will be made to try and stabilize the system. 11/12/2007 08:13 darren@r 15:TestTagFailure: Alarm noted. This system has been well documented. 11/11/2007 08:02 darren@r 15:TestTagFailure: Alarm on this system has been well documented. 11/10/2007 09:08 darren@r 15:TestTagFailure: Alarm will be addressed during the next site visit. 11/07/2007 07:54 darren@r 11:BadOscFreq,11:LowExcCurrent: Alarms were addressed yesterday during a site GMC. 11/06/2007 11:59 Troy A GMC was performed on 11/06/2007. All transceivers were checked for tune and adjustments made where needed. 11/06/2007 07:14 darren@r 15:TestTagFailure: System will be investigated during todays site GMC. 11/05/2007 07:30 darren@r 15:TestTagFailure: 15:TestTagFailure: This system has been well documented and will be investigated during the next site visit. 11/05/2007 07:29 darren@r 15:TestTagFailure: This system has been well documented and will be investigated during the next site visit. 11/04/2007 08:12 troy@ree 15:TestTagFailure: ongoing problem. 11/03/2007 08:54 troy@ree 15:TestTagFailure: Noted 11/02/2007 09:56 troy@ree 15:TestTagFailure: Noted 11/01/2007 08:21 troy@ree 15:TestTagFailure: Noted 10/31/2007 07:57 troy@ree 15:TestTagFailure: Well documented issue. 10/30/2007 07:42 troy@ree 15:TestTagFailure: Alarm well documented. 10/29/2007 08:01 troy@ree 15:TestTagFailure: Noted 10/28/2007 10:00 Dave Win98 thinks we dropped out of Daylight Savings Time at 2AM this morning, and set its internal timer back one hour. This does NOT affect the timestamps in the MultiMon data files, but it does shift automatic file create back one hour. I pcA'd in and stopped/restarted MultiMon data collection to re-initialize the file creation timer. 10/28/2007 09:25 alan@ree 15:TestTagFailure: Noted 10/27/2007 07:45 alan@ree 15:TestTagFailure: Noted 10/25/2007 07:43 alan@ree 15:TestTagFailure: Noted 10/24/2007 07:58 alan@ree 15:TestTagFailure: Noted 10/23/2007 12:17 scottl All transcievers were checked and TT hits rates and adjusted to 100 percent as necessary. Some units are not capable of achieving the 100 percent due to various and well documented reasons. BO3 pc clocks were within 6 seconds of each other and within 20 of atomic time. No other problems to report. 10/23/2007 07:38 alan@ree 15:TestTagFailure: Noted 10/22/2007 08:03 troy@ree 15:TestTagFailure: Known issue. 10/20/2007 10:34 scottl@r 15:Overrun,15:TestTagFailure: Problem noted. 10/18/2007 07:31 alan@ree 15:TestTagFailure: Noted 10/17/2007 07:39 troy@ree 15:TestTagFailure: Noted 10/16/2007 07:43 alan@ree 15:TestTagFailure: Noted 10/15/2007 07:51 scottl@r 15:TestTagFailure: This is a chronic problem relating the health of this antenna. Tass will not subsequently be cleared for this reason. 10/14/2007 08:09 darren@r 15:Overrun,15:TestTagFailure: Alarm noted. 10/13/2007 08:50 darren@r 15:TestTagFailure: This system has been well documented. The problem appears to be below the water line. 10/11/2007 08:26 alan@ree 15:TestTagFailure: Noted 10/10/2007 07:29 darren@r 0F:ReaderReset,15:TestTagFailure,18:ReaderReset: The alarms on antennas 0F, and 18 were addressed by PSMFC personnel during a site GMC. The alarms on antenna 15 have been well documented, there are some issues below the water line. 10/09/2007 12:33 Alan A GMC was performed 10/9/2007. All transceivers were checked and tuned as necessary. Both PCs clocks were set to within one second of atomic time. No activity was observed on PC2 during PC1's downtime. No other problems found. 10/08/2007 07:44 alan@ree 15:TestTagFailure: Noted. 10/07/2007 08:53 alan@ree 15:TestTagFailure: Noted 10/06/2007 07:36 alan@ree 15:TestTagFailure: Noted 10/05/2007 07:39 alan@ree 11:Overrun,15:TestTagFailure: Noted, the issues with these transceivers are well documented. 10/04/2007 07:42 alan@ree 15:TestTagFailure: Noted 10/04/2007 07:27 darren@r 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: Alarms were generated by a brief power outage. The outage did not last more than one (1) minute. 10/03/2007 07:49 alan@ree 15:TestTagFailure: Noted. 10/01/2007 08:18 alan@ree 15:TestTagFailure: Alarms on these two systems have been well documented and are being maintained as well as equipment will allow. 09/30/2007 08:32 troy@ree 15:TestTagFailure: Known issue. 09/29/2007 09:20 troy@ree 15:TestTagFailure: Noted 09/28/2007 08:12 troy@ree 15:TestTagFailure: Noted 09/27/2007 08:20 troy@ree 15:TestTagFailure: Known issue, clearing TASS 09/26/2007 08:03 alan@ree 15:TestTagFailure: Noted 09/25/2007 07:36 troy@ree 15:TestTagFailure: This is a known issue. 09/24/2007 13:00 Troy A site GMC was performed 09/24/2007. All transcievers were checked for tune and no problems were found other than previously documented issues. PC1 is 18 seconds behind PC2. 09/18/2007 07:08 scottl@r 15:TestTagFailure: Noted 09/15/2007 08:37 darren@r 15:TestTagFailure: Alarm and system have been well documented for this failure. The problem is below the waterline. 09/13/2007 07:35 troy@ree 15:TestTagFailure: Well documented issue, clearing TASS. 09/12/2007 08:21 darren@r 06:LowExcCurrent,15:LowExcCurrent,15:TestTagFailure: Alarms on these two systems have been well documented and are being maintained as well as equipment will allow. 09/11/2007 13:04 Darren A site GMC was performed today (9-11-07). All transceivers were checked for tuning, noise, and detection ability. The pc clocks are within 13 seconds of each other and 20 seconds of atomic time. No problmes were discovered. 09/11/2007 07:10 troy@ree 15:TestTagFailure: This alarm will be looked into today during a scheduled GMC. 09/10/2007 07:33 darren@r 15:TestTagFailure: Alarm noted. 09/09/2007 09:24 troy@ree 15:TestTagFailure: A GMC is scheduled for early this week. This alarm will ba addressed at that time. 09/08/2007 08:35 troy@ree 15:TestTagFailure: This alarm will be addressed on the next site visit. 09/05/2007 08:02 alan@ree 18:TestTagFailure: Noted. 09/04/2007 07:30 troy@ree 15:TestTagFailure: This alarm will be investigated on the next site visit. 09/03/2007 07:50 darren@r 15:TestTagFailure,18:TestTagFailure: Alarms will be addressed on the next site visit. 09/02/2007 08:26 darren@r 15:TestTagFailure: This alarm has been well documented. 09/01/2007 08:20 darren@r 15:TestTagFailure: Alarm will be addressed on the next site visit. 08/31/2007 08:46 darren@r 15:TestTagFailure: This system has been well documented throughout this season. PSMFC will inspect this system this year if the ladder is de- watered. 08/30/2007 17:05 Alan_Bro Sprint confirms a DSL outage with a return of service estimated to "8 or 8:30 tonight." 08/30/2007 10:26 Scott_Li The DSL connection has been resolved by Embark. Remote access has been restored to all sites at this location. 08/30/2007 09:41 Scott_Li The DSL connection for all these sites is down. Called Embark (DSL Provider) and they have indicated that the entire Hood River area is experiencing an outage. The ETR according to them is 12:30 pm PST. Will monitor situation and follow up if necessary. 08/30/2007 08:30 Alan A GMC was performed 8/28/2007. All transceivers were checked and tuned as necessary, no problems found. 08/30/2007 08:16 darren@r 06:LowExcCurrent,15:TestTagFailure: These two detection systems have been well documented throughout the year. We will be investigating the root cause when the ladder is de-watered. 08/27/2007 08:49 darren@r 15:TestTagFailure: This system has been well documented but will be investigated during the next site visit. 08/23/2007 08:05 darren@r 08:ReaderReset,15:TestTagFailure: These alarms will be addressed during the next site visit. 08/21/2007 08:02 darren@r 18:TestTagFailure: This alarm will be addressed on the next site visit. 08/20/2007 08:08 darren@r 15:TestTagFailure,22:InputSyncDetect,22:InputSyncLost,26:InputSyncDetect,2 6:InputSyncLost,28:ReaderReset: Alarms will be addressed on the next site visit. The reader resets are a common occurance in the juvenile transceivers. 08/18/2007 10:25 scottl@r 15:TestTagFailure,18:TestTagFailure: Noted 08/17/2007 11:27 Alan A GMC was performed 8/17/2007. All transceivers were checked and tuned as necessary. PC1 is ten seconds behind atomic time, PC2 is eight seconds behind atomic time. No problems found. 08/16/2007 08:30 scottl@r 15:TestTagFailure: Problem noted, not of concern at this time. 08/15/2007 08:09 scottl@r 15:Overrun,15:TestTagFailure: This antenna has had ongoing problems, not of concern at this time. 08/14/2007 08:09 alan@ree 15:TestTagFailure: This transceiver is reading PIT Tags. These alarms will be investigated Friday during a site visit. 08/13/2007 16:06 Dave Reset PC clocks to within 1 second of each other and atomic time. Archived all files outstanding on PC2. 08/13/2007 09:15 troy@ree 15:TestTagFailure: Alarms will be addressed on the next site visit. 08/12/2007 10:20 scottl@r 15:Overrun,15:TestTagFailure: Noted 08/11/2007 08:12 scottl@r 15:TestTagFailure: roblem noted, not of concerna at this time, will monitor 08/10/2007 08:11 darren@r 15:TestTagFailure: PSMFC will investigate this alarm during the next site visit. 08/02/2007 08:41 alan@ruf 15:TestTagFailure: Noted 08/01/2007 08:25 troy@ruf 15:TestTagFailure: Noted 07/31/2007 08:17 troy@ruf 15:TestTagFailure,24:InputSyncDetect,24:ReaderReset: Reader Reset is a common error that occurs. Test Tag Failure noted. 07/13/2007 16:19 Dave Eric Johnson from U of I called earlier today and notified me they were shutting down their sampling operation for the year and no longer needed SxC support. I updated the map file to BO307194.MAP, which changed the DU status from ON to SP0 (monitor only) for DU1 and DU2. The PC clocks are within 6 seconds of each other and 13 seconds of atomic time. 07/13/2007 08:16 darren@r 18:TestTagFailure: 18:TestTagFailure: The alarm will be investigated on the next site visit. 07/13/2007 08:15 darren@r 18:TestTagFailure: The alarm will be investigated on the next site visit. 07/11/2007 09:03 troy@ruf 15:TestTagFailure: Noted 07/10/2007 13:06 Dave While on-site, I reset the PC clocks to within 1 second of each other and atomic time, and archived all outstanding PC2 data files. 07/04/2007 09:03 alan@ruf 15:TestTagFailure: Noted 07/03/2007 13:23 Darren A site GMC was performed today (7-3-07). All transceivers were checked for tuning, noise, and detection ability. No problems were found. 07/02/2007 08:50 alan@ruf 15:TestTagFailure: Noted 07/01/2007 07:44 Darren_C I PCA'd into the site and found that the missing files had been archived. I retrieved them and manually pushed them to the server. 07/01/2007 05:34 darren@r 15:TestTagFailure: alarm noted on a well documented system. 06/30/2007 09:04 darren@r 15:TestTagFailure: This system has been well documented for test tag failures. PSMFC will optimize the system to the best of it's abilities on the next site GMC. 06/27/2007 09:05 troy@ruf 15:TestTagFailure: Noted 06/26/2007 08:39 scottl@r 11:Overrun,15:TestTagFailure: These units have chronic problems and have been noted in the past. 06/24/2007 10:50 darren@r 15:TestTagFailure: PSMFC is aware of this system and its activities. 06/23/2007 06:11 darren@r 15:TestTagFailure: This system has known issues. It will investigated on the next site visit. 06/22/2007 08:10 darren@r 15:TestTagFailure: No direct cause for this failure. The analog board was recently replaced in this transceiver but all indications are that the system is operating normally. 06/20/2007 08:18 darren@r 11:ReaderReset,12:ReaderReset,12:TestTagFailure,13:ReaderReset,14:LowExcCu rrent,14:ReaderReset,15:ReaderReset,15:TestTagFailure,16:ReaderReset,17:Re aderReset,17:TestTagFailure,18:ReaderReset,18:TestTagFailure: These alarms were generated by PSMFC personnel during the re-install of the upgraded analog boards for these transceivers. 06/20/2007 08:17 Darren_C A site GMC was performed yesterday (6-19-07). The original analog boards for transceivers 11 through 18 were re-installed after being upgraded with NPO capacitors. The systems were retuned and checked for detection ability. No problems were found. 06/19/2007 08:23 troy@ruf 12:TestTagFailure: A GMC is scheduled for today. This will be looked into then. 06/17/2007 08:06 alan@ruf 12:TestTagFailure: No apparent reason for this alarm. PTAGIS Field Operations will continue to monitor. 06/15/2007 08:19 alan@ruf 18:TestTagFailure: Noted 06/14/2007 08:26 alan@ruf 18:TestTagFailure: Noted 06/13/2007 08:07 darren@r 05:LowExcCurrent,05:ReaderReset,06:LowExcCurrent,06:ReaderReset: Alarms were generated by PSMFC personnel during a site GMC. 06/12/2007 13:12 scottl The system clocks are within 6 seconds of each other and 32 seconds behind atomic time. 06/12/2007 13:09 scottl Performed GMC, all transceivers were retuned and calibrated as necessary. The diagnosis of unit 06 indicates that the problem lies within the antenna/capacitor bank and or cable below the water line. No further action can be taken at this time. No other problems to report. 06/11/2007 16:35 Alan Manually pushed BO307162.105 to PTAGIS via PCA. 06/11/2007 09:32 alan@ruf 18:TestTagFailure: No apparent reason for this alarm. PTAGIS Field Operations will investigate during a site visit tomorrow. 06/10/2007 08:46 troy@ruf 18:TestTagFailure: Noted 06/09/2007 09:29 Troy The signal level has risen on 06 which is causing the TT to be missed. The transceiver is still reading fish at a high efficiency. 06/09/2007 09:23 troy@ruf 18:ReaderReset: Random Reader Reset 06/08/2007 16:26 Darren It appears that transceiver/antenna 06 have developed noise again. The timer tag is not firing due to "system activity" we are still receiving detections but probably not at the most optimum efficiency. PSMFC will adjust the transceiver on the next site visit. This system has been somewhat problematic this year and the noise does follow the antenna. 06/08/2007 08:07 darren@r 01:LowExcCurrent,03:LowExcCurrent,06:LowExcCurrent,22:TestTagFailure,24:Te stTagFailure,32:TestTagFailure,34:TestTagFailure,36:TestTagFailure,38:Test TagFailure: Alarms were generated by PSMFC personnel during a site GMC. 06/07/2007 13:54 Darren A site GMC was performed today (6-7-07). All transceivers were checked for tuning, noise and detection ability. No problems were found 06/07/2007 09:36 Dave Performed a cursory status check. PC clocks are within 5 seconds of each other and 20 seconds of atomic time. I almost uploaded 63 redundant data files from PC2 because PTTP-Uploader on that machine had been left in "Upload" mode. Fortunately, I caught the error before I initiated the operation. PTTP-Uploader on BO3-PC2 was closed in the default "archive only" mode. 05/31/2007 08:30 darren@r 01:LowExcCurrent: Alarm was cleared by PSMFC personnel during a site GMC. 05/30/2007 12:16 Alan A GMC was performed 5/30/2007. All transceivers were checked and tuned as necessary. The clocks on both PCs had drifted ~00:01:15 behind and were set to within one second of atomic time. File BO307150.206 was created on PC2 during PC1's downtime. No other problems found. 05/30/2007 08:22 darren@r 06:ReaderReset: This condition is not uncommon with this transceiver. PSMFC is aware of the random reader resets. 05/24/2007 07:57 darren@r 10:LowExcCurrent,18:TestTagFailure: Alarm on antenna 10 was generated by PSMFC personnel while performing a site GMC. The alarm on antenna 18 has no direct cause. The system was checked during the GMC and no problems were found. 05/23/2007 13:16 Darren A site GMC was performed today (5-23-07). All transceivers were checked for tuning, noise, and detection ability. No problems were found. 05/23/2007 08:19 troy@ree 36:InputSyncDetect,36:ReaderReset: Possible Random Reader Reset. PSMFC will be on site today to perform a GMC. 05/21/2007 08:59 troy@ree 18:TestTagFailure: This will be addressed on the next site visit. 05/20/2007 09:29 darren@r 18:TestTagFailure: Alarm will be investigated on the next site visit. 05/19/2007 09:41 darren@r 0F:ReaderReset: This alarm was generated by a random reader reset. This alarm is known by PSMFC. 05/12/2007 07:54 alan@ree 18:ReaderReset: This alarm was generated by PTAGIS Field Operations personnel during a site visit. 05/11/2007 08:09 alan@ree 18:TestTagFailure: This will be investigated on the next site visit. 05/09/2007 09:04 alan@ree 18:BadExcFreq: This will be investigated today during a site visit. 05/08/2007 09:14 alan@ree 18:BadExcFreq,18:TestTagFailure: PTAGIS Field Operations will investigate on the next site visit. 05/05/2007 08:16 darren@r 18:TestTagFailure: This alarm will be addressed on the next site visit. 05/02/2007 08:20 darren@r 18:BadOscFreq,18:TestTagFailure: These alarms occurred only once and could not be explained directly through raw files. We will monitor for future alarms. 05/01/2007 11:24 Troy A GMC was performed 05/01/2007. All transcievers were checked for tune and adjusted where needed. PC1 was 44 seconds behind atomic time and PC2 was 57 seconds behind atomic time. Both PC's were set to within one second of atomic time. The gap file BO307121.205 was manually pushed to pitagis after archiving the files on PC2. 04/30/2007 08:36 darren@r 18:TestTagFailure: This alarm will be addressed during the next site visit. 04/27/2007 08:34 darren@r 18:TestTagFailure: This detection system will be addressed during the next site visit. 04/22/2007 10:07 troy@ree 18:TestTagFailure: Noted 04/20/2007 08:11 troy@ree 05:BadOscFreq,05:LowExcCurrent,06:LowExcCurrent,06:ReaderReset,10:LowExcCu rrent: These alarms were generated during a GMC. 04/19/2007 08:27 troy@ruf 18:TestTagFailure: 18:TestTagFailure: This will be looked into today. 04/19/2007 08:27 troy@ruf 18:TestTagFailure: This will be looked into today. 04/18/2007 08:53 troy@ruf 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,16:ReaderReset,17:ReaderReset,18:ReaderReset,18:TestTag Failure,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: These alarms are most likely due to a brief power outage. 04/15/2007 07:35 alan@ruf 18:TestTagFailure: No apparent reason for this alarm. PTAGIS Field Operations will continue to monitor. 04/14/2007 07:58 alan@ruf 04:LowExcCurrent,16:LowExcCurrent,17:LowExcCurrent: These alarms were generated by PTAGIS Field Operations personnel during a site visit. 04/13/2007 13:51 Alan A GMC was performed 4/13/2007. All transceivers were checked and tuned. Both PCs clocks are within 30 seconds of atomic time. No problems found. 04/13/2007 08:09 troy@ruf 34:InputSyncDetect,34:ReaderReset: Random reader reset. 04/04/2007 09:48 Dave I updated the map file to BO307093.MAP. This version swaps the labels for AC-92 (now SHD_UI) and AC-93 (now WW_UI). The labels were previously associated with the wrong Action Code. The underlying database contents were correct. This is a cosmetic correction. The PC clocks are within 2 seconds of each other and 12 seconds of atomic time. 04/02/2007 17:05 Dave I reset the MultiMon file creation schedule on BO3-PC1 and PC2. The PC clocks are within 1 second of each other and 7 seconds of atomic time. 04/01/2007 09:13 Darren I was able to PCA into this site and adjust the platform according to the Daylight Savings Time SOP. 03/30/2007 10:23 Dave I installed the first SxC configuration of the season, with the BO307089.DB and BO308089.MAP database and map files, respectively. This configuration enables a "yellow light" alert in the AFF for U of I's SF Salmon targets (AC-91), and "red light" alerts for shad (AC-93) and CTUIR's fish tagged in the Walla Walla (AC-92). I encountered a memory error in MultiMon on PC1 while I was downloading the new configuration files. I exited and restarted MultiMon, and did not observe any further problems. I reset the PC clocks to within 1 second of each other and atomic time. 03/26/2007 07:15 darren@r 34:InputSyncDetect,34:ReaderReset: Reader reset caused this alarm. 03/23/2007 16:01 scottl Performed GMC, all transceivers were retuned as necessary, no problems to report. 03/09/2007 08:10 darren@r 03:LowExcCurrent,09:LowExcCurrent,0B:ReaderReset,10:LowExcCurrent: Alarms were generated by PSMFC personnel while performing a site GMC. 03/08/2007 11:11 Darren A site GMC was performed today (3-8-07). All transceivers were checked for tuning, noise and detectability. No problems were found. PC clocks were checked and found to be with 10 seconds of atomic time and 1 second of each other. 03/08/2007 09:07 scottl Performed GMC, all transcievers were checked and retuned as necessary, only problem that was not resolved was antenna/xcvr 15, noise levels vary and cannot be effectively tuned. System is still somewhat operational. 03/06/2007 13:02 Dave Reset BO3 SxC to the generic configuration. Zipped last year's data files. Cleared counters. Reset PC clocks to within 1 second of each other and atomic time. 03/06/2007 07:12 darren@r 0C:ReaderReset,0E:LowExcCurrent: These alarms will be addressed during site maintenance visits tomorrow and Thursday. 03/05/2007 07:36 darren@r 0E:LowExcCurrent: PSMFC will adjust the current alarm threshold via PCA. 03/03/2007 10:16 scottl@r 0E:LowExcCurrent: Noted 03/02/2007 08:45 dlwarf@r 12:LowExcCurrent,16:TestTagFailure,18:TestTagFailure: Clearing alarms from GMC. 03/01/2007 12:38 Darren The site was visited because of the alarms and timer tag misfires on antennas 09, 16, 18. The timer tag voltage was turned down on transceivers 11 through 18 due to testing of the HDX systems a couple of weeks ago. All the voltages were adjusted to achieve 100% hit rates on the systems. Transciever 09 was out of tune and was also adjusted. The only timer tag that is not firing at 100% is transceiver 15 which has a well documented elevated noise floor. 02/28/2007 07:23 darren@r 16:TestTagFailure,18:TestTagFailure: Alarms will be addressed today during a site visit. 02/27/2007 07:20 troy@ree 16:TestTagFailure,18:TestTagFailure: These alarms will be looked into today during GMC. 02/26/2007 11:46 Dave I updated obs_site_dates to reflect water-up on Feb. 21. 02/26/2007 07:39 darren@r 16:TestTagFailure,18:TestTagFailure: The timer tag level will be checked on the next site visit. 02/25/2007 08:50 alan@ree 16:TestTagFailure,18:TestTagFailure: Transceiver 18 is showing some noise in the exciter report, possibly causing the TT problems. TTs for transceivers 16 and 18 were fired manually via PCA. The hit rate for transceiver 16 is ~20 and for transceiver 18 is ~30. PTAGIS Field Operations will adjust these on the next site visit. 02/24/2007 08:39 alan@ree 16:TestTagFailure,18:TestTagFailure: Transceivers 09 and 18 are showing some noise in the exciter report, possibly causing the TT problems. TTs for transceivers 09, 16 and 18 were all fired manually via PCA. PTAGIS Field Operations will continue to monitor. 02/24/2007 08:14 alan@ree 09:LowExcCurrent,0D:LowExcCurrent,12:TestTagFailure,14:TestTagFailure: These alarms were generated by PTAGIS Field Operations personnel during a site visit. 02/23/2007 12:15 scottl Start of season activities included syncing of the data collection pc clocks, Archiving 2006 data into a 2006 archive directory,purging erronious backup files generated through out the season in the Multimon\System directory. Other platform tasks that include manipulating Hardware,Map and seasonal counters will be performed at a later date by the data analyst and or PTAGIS Field O&M.Tuned and calibrated all transcievers. PC clocks are within 1 second of each other and within 2 seconds atomic time. No other current unresolved issues to report. No fish activity was observed on either PC during the time the above tasks were being performed. 02/23/2007 07:20 troy@ree 12:TestTagFailure,14:TestTagFailure,16:TestTagFailure: These will be addressed today during a GMC. 02/22/2007 08:41 darren@r 0E:LowExcCurrent,12:TestTagFailure,14:TestTagFailure,16:TestTagFailure,18: TestTagFailure,22:InputSyncDetect,22:InputSyncLost,26:InputSyncDetect,26:I nputSyncLost,28:ReaderReset: These alarms were generated when the ladder was watered up yesterday at 09:00. PSMFC will be on site to retune the detection systems and do necessary pre-season platform work tomorrow. 02/21/2007 07:22 Darren I was informed today by Jon Rerecich site biologist that the ladder would begin water up at 09:00. 01/22/2007 08:06 Scott_Li This entry is for work done on Thursday, Jan 18th, 07. The firewall issues have been corrected but not resolved. Apparently, the configuration of the firebox in the AFF PIT room became corrupted in a way that did not allow incoming traffic and shutdown remote access and BB alerts. Todd K and I restored the configuration in the firewall and things started working correctly. At this time, there is no real good explanation for why this happen and how it was corrected. Todd I believe has a support thread started with Watch Guard in order to better understand these unknown phenomenons. 01/18/2007 13:16 Darren_C On Tuesday 1-16-07 PSMFC traveled to Bonneville to inspect all antennas and conduits on Cascade Island (BO2) and Washington Shore (BO3) and Washington Shore Slots (BO4). All antennas at Cascade Island were inspected on Tuesday and Washington Shore antennas were inspected on Wednesday. All problems that were discovered were reported to COE representative Jonathan Rerecich with the work to be performed by COE mechanics. The old timer tag cable was removed from the exciter conduit on antenna 11 and the connector was checked, cleaned and reseated. The connector on antenna 15 was checked, cleaned and reseated. 01/15/2007 09:05 Darren These sites along with BCC are still being indicated as not connected to the Portland office but the files are being submitted on the scheduled intervals. It is possible that something has changed in Portland that is not this connection. I am also having trouble with my VPN service from home so I cannot verify the status of PC2. I will have to dig further when I am in the office on Tuesday. 01/14/2007 08:34 darren@r 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,0E:TestTagFa ilure,0F:ReaderReset,10:ReaderReset,11:Overrun,11:ReaderReset,12:ReaderRes et,13:ReaderReset,14:ReaderReset,15:Overrun,15:ReaderReset,16:ReaderReset, 17:ReaderReset,18:ReaderReset,22:InputSyncDetect,22:ReaderReset,24:InputSy ncDetect,24:ReaderReset,26:InputSyncDetect,26:ReaderReset,28:ReaderReset,3 2:InputSyncDetect,32:ReaderReset,34:InputSyncDetect,34:ReaderReset,36:Inpu tSyncDetect,36:ReaderReset,38:ReaderReset: Clearing alarms from power outage. 01/13/2007 09:24 Darren I received a message from chum root indicating that the platforms at Bonneville are not able to be pinged by big brother. I have checked and found that the platforms are indeed sending files into PSMFC but I cannot find the source of the problem. I will continue to monitor this situation and report any changes in the status of big brother. 01/02/2007 07:25 darren@r 11:Overrun,15:Overrun: Site is currently OOS. 01/01/2007 00:00 PTOC_Bot Annual log file initiation for BO3 #### End of Event Log for BO3 ###