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/20/2006 07:16 darren@r 05:TestTagFailure,0E:LowExcCurrent,15:Overrun: The ladder is currently out of service until 2-1-07. 12/13/2006 07:25 darren@r 05:TestTagFailure,0E:LowExcCurrent,15:Overrun: The ladder was de-watered on Monday around 08:00. These alarms will be cleared from TASS. 12/12/2006 12:03 Dave I updated the Obs_Site_Dates table to reflect the termination of fish passage activity in the Washington Shore ladder. I changed the distribution list for site-checking notifications to ptoc_ken only in etc/sites. 12/12/2006 11:10 Darren The ladder was de-watered yesterday at around 08:00. PSMFC and Digital angel are on site to modify the analog boards for all the FS1001A-B transceivers. 12/12/2006 08:35 Dave The Corps reports that the Washington Shore Ladder went to orifice flow at 0945 on 09 December. The AFF was also dewatered on 09 December. 12/12/2006 07:11 troy@ree 03:LowExcCurrent,05:LowExcCurrent,11:LowExcCurrent,12:LowExcCurrent,15:Ove rrun: These alarms are most likely the result of the ladder de-watering. PSMFC personnel are on site with DA to correct the overrun problem. These other alarms will be looked into as well. 12/11/2006 07:22 scottl@r 15:Overrun: Problem has been noted 12/10/2006 08:52 darren@r 15:Overrun: Alarms will be addressed on the next site visit. 12/09/2006 07:53 darren@r 15:Overrun: This transceiver will be addressed next week while PSMFC is on site for modifications. 12/06/2006 07:32 darren@r 0D:LowExcCurrent,0E:LowExcCurrent: Alarms were addressed yesterday during a site GMC. 12/05/2006 12:56 Alan A GMC was performed 12/5/2006. All transceivers were checked and tuned as necessary. Transceiver 0A appeared to be fine. I adjusted the exciter to 4.3A and set the alarm threshold to 4000mA. No problems found. 12/03/2006 10:04 troy@ree 15:Overrun: Known issue, clearing TASS 12/02/2006 10:55 troy@ree 0A:LowExcCurrent,15:Overrun: These alarms will addressed on the next site visit. 12/01/2006 07:43 troy@ree 11:TestTagFailure: Noted 12/01/2006 07:42 troy@ree 0A:LowExcCurrent: PCA'ed into PC2 and lowered the current alarm threshold from 3900 to 3600 as the transceiver current had dropped to 3600. This will be looked into on the next site visit. 11/30/2006 10:15 troy@ree 0A:LowExcCurrent: The exciter current is curretnly at the exciter current low alarm threshold. If this continues to be a problem the current low alarm threshold will be lowered remotely otherwise this will be addressed on the next site visit. 11/30/2006 10:15 troy@ree 11:TestTagFailure: Noted 11/30/2006 10:04 alan@ree 11:TestTagFailure: Noted 11/29/2006 07:25 troy@ree 0A:LowExcCurrent,11:TestTagFailure: These alarms will be addressed on the next site visit. 11/28/2006 07:31 darren@r 16:ReaderReset: Known problem with transceivers. Site will be addressed during the next site visit. 11/27/2006 07:24 alan@ree 15:Overrun: Noted 11/26/2006 09:53 alan@ree 15:Overrun: Noted 11/25/2006 09:50 alan@ree 15:Overrun: Noted 11/24/2006 07:17 alan@ree 15:Overrun: Previously cleared, attempting to turn red light green on TASS. 11/24/2006 07:13 alan@ree 15:Overrun: Noted 11/21/2006 08:35 alan@ree 0D:ReaderReset: This alarm was generated by a random reader reset. PSMFC and DA are aware of the problem. 11/20/2006 07:36 alan@ree 15:Overrun: Noted 11/20/2006 07:35 alan@ree 09:TestTagFailure: No apparent reason for this alarm. It occurred during a ststus dump. PTAGIS Field Operations will continue to monitor. 11/19/2006 08:30 darren@r 11:Overrun,15:Overrun: These systems have been well documented throughout the season and will be checked during the de-water period. 11/18/2006 08:28 darren@r 02:LowExcCurrent,04:ReaderReset,15:Overrun: Alarms were either generated or cleared by PSMFC personnel during a site GMC. 11/17/2006 12:55 Alan A GMC was performed 11/17/2006. All transceivers were checked and tuned as necessary. The clocks on both PCs were set to within one second of atomic time. No activity was observed on PC2 during PC1's downtime. No problems found. 11/16/2006 07:35 darren@r 15:Overrun: Alarms will be addressed on Friday during a site GMC. 11/13/2006 07:28 darren@r 15:Overrun: This detection system has been well documented over the last season and will be checked during the de-watering period this winter. 11/09/2006 07:18 darren@r 15:Overrun: This is an ongoing problem antenna and will be addressed during the de-water period. 11/05/2006 08:27 alan@ruf 15:Overrun: Noted 11/04/2006 07:58 alan@ruf 11:TestTagFailure: Noted 11/03/2006 07:53 alan@ruf 11:LowExcCurrent,11:Overrun,15:Overrun: Noted 11/02/2006 08:29 alan@ruf 15:Overrun: Noted 11/02/2006 08:18 Alan A GMC was performed 11/2/2006. All transceivers were checked and tuned as necessary. The clocks on both PCs are within seven seconds of atomic time, no problems found. 10/31/2006 09:11 Dave Monday afternoon, October 30, I reset the clocks on both PCs to within 2 seconds of each other and atomic time. I took MultiMon out of data collection mode momentarily to update the clock on each machine; this re-synched MultiMon's internal counters, which had been affected by the shift out of Daylight Savings Time, with the (updated) system clock. 10/29/2006 09:07 troy@ruf 15:Overrun: These alarms will be addressed on the next site visit. 10/27/2006 08:44 troy@ruf 15:Overrun: This antenna is suspected to have problems below the water line. 10/25/2006 08:08 Alan_Bro This is being reposted as the original posting yesterday didn't make it to the event logs: All primary data collection computers auto upload functions were re-engaged at 12:43 PST. Delinquent files were not manually pushed to PTAGIS. The uploader will submit files in the next 3 hrs. 10/24/2006 09:45 Alan_Bro Automated file loading has been disabled. 10/21/2006 09:10 scottl@r 12:ReaderReset: Noted 10/18/2006 10:50 Troy A site GMC was perform 10/18/06. All transceivers were checked for tune and adjustments made where needed. 15 is at 100% noise and the problem is suspected to be below the water line. PC1 was 27 seconds behind PC2 and PC2 2 min 45 seconds behind atomic time. The times were adjusted and PC1 is 1 second ahead of PC2 and 1 second behind atomic time. BO306291.205 was used to cover for PC1 while the time was being set. It was manually pushed after the files on PC1 were manually pushed. The remaining files on PC2 where then archived. 10/18/2006 10:33 Alan_Bro Sites have been verified online. Will monitor for 13:00 load. 10/16/2006 10:20 Scott_Li Per Dean Ballinger and Sprint, there is a main break in the phone line at North Bonneville and Sprint is currently performing repairs. No estimation on when the repairs will be completed. Will post information when available. 10/16/2006 08:02 Scott_Li Called Sprint and placed trouble ticket on the DSL line. Ticket # 1325900 marked as urgent. To check status of ticket, call 877. 677.7596. All indications are the problem is the phone line coming into the facility. Called Dean B at the SMP office to check on Modem status. Will post more info as become available. 10/16/2006 07:45 darren@r 15:Overrun: These alarms will be addressed this week by PSMFC personnel. 10/16/2006 07:37 Scott_Li Big Brother reports the Gateway for this site is down. Called Sprint and they confirmed that the DSL modem for Bonn cannot be seen on the network indicating the modem is either dead or needs rebooted or the copper line for the DSL connection is the problem. Called the telephone number associated with the DSL connection and get a fast busy signal. No confirmation as of yet to what the problem is. Will post more information as it becomes available. 10/12/2006 12:48 scottl Responded to the LAN outage for all Bonneville sites including the SMP facility. Isolated problem to a faulty network switch in AFF network cabinet. Moved all patch cables from this switch to an alternate network switch to repair the problem. Web access was restored at ~ 11:30 am PST. 10/12/2006 08:31 Scott_Li Big Brother reports all Bonneville data collection computers are unreachable. The gateway for this site is accessible, in the process of troubleshooting the problem. More soon. 10/04/2006 16:19 troy@ruf 15:Overrun: This will be looked into on the next site visit. This transciever is still reading pittags. 09/30/2006 08:46 alan@ruf 15:Overrun: Noted 09/26/2006 08:25 alan@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,22:InputSy ncDetect,22:ReaderReset,24:InputSyncDetect,24:ReaderReset,26:InputSyncDete ct,26:ReaderReset,28:ReaderReset,32:InputSyncDetect,32:ReaderReset,34:Inpu tSyncDetect,34:ReaderReset,36:InputSyncDetect,36:ReaderReset,38:ReaderRese t: Alarms are the result of a power outage. 09/22/2006 07:19 troy@ruf 09/22/2006 04:05 DGE_Robo AC_Power (AC_Power) changed from 'ON' to 'OFF' at 2006/09/22 02:26:23 09/22/2006 04:05 DGE_Robo AC_Power (AC_Power) changed from 'OFF' to 'ON' at 2006/09/22 02:32:28 The above power outage was at the JFF, the time is very close to the alarms seen at the AFF. It is safe to assume that the AFF was down for the same duration as the JFF 09/22/2006 07:15 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,22:InputSy ncDetect,22:ReaderReset,24:InputSyncDetect,24:ReaderReset,26:InputSyncDete ct,26:ReaderReset,28:ReaderReset,32:InputSyncDetect,32:ReaderReset,34:Inpu tSyncDetect,34:ReaderReset,36:InputSyncDetect,36:ReaderReset,38:ReaderRese t: These alarms are most likely the result of a power outage. 09/21/2006 08:20 troy@ruf 11:Overrun: Noted 09/19/2006 07:17 troy@ruf 22:InputSyncDetect,22:ReaderReset: These alarms were most likely generated during a GMC. PSMFC will monitor for future failures. 09/17/2006 11:40 scottl@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,16:ReaderReset,17:ReaderReset,18:ReaderReset,22:InputSy ncDetect,22:ReaderReset,24:InputSyncDetect,24:ReaderReset,26:InputSyncDete ct,26:ReaderReset,28:ReaderReset,32:InputSyncDetect,32:ReaderReset,34:Inpu tSyncDetect,34:ReaderReset,36:InputSyncDetect,36:ReaderReset,38:ReaderRese t: Alarms were generated by an assumed power glitch. All systems appear to be back in working order. 09/16/2006 08:08 alan@ruf 15:Overrun: Noted 09/14/2006 07:09 scottl@r 15:Overrun: Problem noted 09/07/2006 13:16 Darren A site GMC was performed today (9-7-06). All the transceivers were checked for tuning, noise, and detection ability. No problems were found. The locker was stocked and the new site maps were installed. 09/05/2006 07:54 darren@r 0E:ReaderReset: Alarm was generated by a random reader reset. PSMFC and D. A. are aware of this condition. 09/02/2006 08:07 alan@ruf 15:Overrun: Noted 08/31/2006 07:31 alan@ruf 15:Overrun: Noted 08/30/2006 08:02 alan@ruf 15:Overrun: Noted 08/29/2006 07:39 alan@ruf 15:Overrun: Noted 08/28/2006 07:55 alan@ruf 11:Overrun,15:Overrun,15:TestTagFailure: Noted 08/24/2006 08:03 darren@r 0F:ReaderReset,0F:TestTagFailure,10:ReaderReset,10:TestTagFailure,14:Reade rReset,14:TestTagFailure,15:Overrun,24:InputSyncDetect,24:ReaderReset: Alarms were generated by PSMFC personnel while performing site maintenance. 08/23/2006 10:58 Darren A site GMC was performed today (8-23-06). All the transceivers were checked for tuning, noise, and detection ability. The upgraded analog boards on antennas 01-10 were retuned for maximum detection performance. No problems were found. 08/23/2006 07:26 alan@ruf 01:ReaderReset,02:LowExcCurrent,02:ReaderReset,03:LowExcCurrent,03:ReaderR eset,04:LowExcCurrent,04:ReaderReset,05:ReaderReset,06:LowExcCurrent,06:Re aderReset,07:LowExcCurrent,07:ReaderReset,08:LowExcCurrent,08:ReaderReset, 09:LowExcCurrent,09:ReaderReset,0A:LowExcCurrent,0A:ReaderReset,0B:ReaderR eset,0C:ReaderReset,0D:LowExcCurrent,0D:ReaderReset,0E:LowExcCurrent,0E:Re aderReset,0F:LowExcCurrent,0F:ReaderReset,10:LowExcCurrent,10:ReaderReset, 11:ReaderReset,11:TestTagFailure,12:LowExcCurrent,12:ReaderReset,13:LowExc Current,13:ReaderReset,14:LowExcCurrent,14:ReaderReset,15:Overrun,15:Reade rReset,16:LowExcCurrent,16:ReaderReset,17:LowExcCurrent,17:ReaderReset,18: ReaderReset: These alarms were generated by PTAGIS Field Operations personnel during a site visit. 08/22/2006 16:02 Darren The upgraded analog boards were put back into transceivers 01 through 10 and the analog boards on 11 through 18 were removed and the test boards were installed so the NPO capacitors can be installed by Digital Angel. The test boards will be removed when the upgraded boards are returned to PSMFC. 08/22/2006 07:19 darren@r 11:TestTagFailure: Alarm has been noted and the detection system has been well documented. 08/21/2006 07:37 darren@r 11:TestTagFailure,15:Overrun: The problems with these detection systems have been well documented. PSMFC will be able to inspect the antennas during the de-watering period this winter. 08/18/2006 11:32 dlwarf@r 03:LowExcCurrent,06:BadExcFreq,0C:LowExcCurrent,11:TestTagFailure,15:Overr un: Reseting alarms after GMC. 08/17/2006 13:22 Darren A site GMC was performed today (8-17-06). All the transcievers were checked for tuning, noise, and detection ability. The PC clocks were within 40 seconds of atomic time and 14 seconds of each other. No problems were found. 08/14/2006 07:28 scottl@r 11:TestTagFailure,15:Overrun: Due to Antenna problems, errors on 11 and 15 are to be expected 08/13/2006 08:38 alan@ree 11:TestTagFailure: Noted 08/12/2006 10:11 alan@ree 06:BadExcFreq: No apparent reason for this alarm. It will be investigated on Thursday's site visit. 08/12/2006 10:07 alan@ree 11:TestTagFailure,15:Overrun: These antennas have issues below the waterline. 08/11/2006 08:12 dlwarf@r 11:TestTagFailure: To be investigated during a GMC on Thursday. 08/10/2006 07:27 alan@ree 11:TestTagFailure: Noted 08/09/2006 07:36 alan@ree 11:TestTagFailure: Noted 08/08/2006 07:52 alan@ree 11:TestTagFailure,15:Overrun: Noted. These antennas have documented problems and will be investigated when the ladder is de- watered. 08/07/2006 07:34 alan@ree 11:TestTagFailure: Noted 08/06/2006 09:07 troy@ree 11:TestTagFailure,15:Overrun,15:TestTagFailure: These problems are well documented. 08/05/2006 18:51 troy@ree 11:TestTagFailure,15:Overrun: Noted 08/04/2006 08:28 dlwarf@r 11:TestTagFailure,15:Overrun: Noted. 08/03/2006 07:18 troy@ree 11:TestTagFailure,15:Overrun: These problems are well documented. 08/02/2006 08:31 darren@r 11:TestTagFailure: Alarm noted. 08/02/2006 07:14 darren@r 11:TestTagFailure,15:Overrun: Alarms have been noted and these detection systems well documented. 08/01/2006 07:17 darren@r 11:TestTagFailure,15:Overrun: Detection systems have been well documented. 07/31/2006 07:38 darren@r 06:BadOscFreq,11:TestTagFailure,15:Overrun: These alarms will be addressed on the next site visit. 07/27/2006 07:24 troy@ree 11:TestTagFailure,15:Overrun: Noted 07/26/2006 09:50 troy@ruf 11:TestTagFailure,15:Overrun: These are known problem transceivers. It has been verified that they are still reading pit tagged fish. 07/25/2006 10:12 troy@ruf 11:TestTagFailure,15:Overrun: These alarms are well documented. 07/20/2006 08:00 Darren_C I spoke with Bill Daigle from the U of I yesterday and he informed me that as of July 15th the HDX system at the transition pool was set up with a laptop computer and is being turned on and off automatically at the scheduled intervals. The computer is tracking this action with a log file. He was entering the start and stop times each day into the event log but now he will only post an event if the system fails to run on the scheduled time. PSMFC will assume that the system is running unless otherwise informed. Darren R. Chase PSMFC Systems Engineer (509) 735-2773 ext.3 darren@psmfc.org 07/20/2006 07:37 darren@r 11:TestTagFailure,15:Overrun: Detection systems well documented. 07/20/2006 07:32 darren@r 11:TestTagFailure,15:Overrun: Detection systems have been well documented. 07/19/2006 08:45 darren@r 11:TestTagFailure,15:Overrun: Alarms are noted and these detection systems have been documented as to there problems. 07/18/2006 13:52 Darren A site GMC was performed today (7-18-06). All transceivers were checked for tuning, noise, and detection ability. No problems were found. 07/18/2006 12:50 Darren Transceiver 01 was removed for testing purposes at the B2J Full Flow. It will remain there for a few days. 07/18/2006 08:55 Darren The automated upload process has been re-established. The previous file were manually submitted by PSMFC personnel. 07/17/2006 15:10 Alan_Bro The auto upload process was disengaged until further notice due to the scheduled outage of the central database. The sites will not upload files until possibly Monday the 17th or 18th or when the central database resumes normal operations.. 07/17/2006 15:09 PTOC_Bot The auto upload process was disengaged until further notice due to the scheduled outage of the central database. The sites will not upload files until possibly Monday the 17th or 18th or when the central database resumes normal operations.. 07/14/2006 09:05 alan@ruf 11:TestTagFailure,15:Overrun: These two detection systems have been well documented by PSMFC as having problems that could possibly be beneath the water line. 07/13/2006 07:47 alan@ruf 11:TestTagFailure: Noted 07/12/2006 10:34 Dave Replaced BO3-GEN.DB with current version from PTAGIS file server. Updated database to BO306193.DB. Reset PC clocks to within 1 second of each other and atomic time. 07/12/2006 09:24 darren@r 11:TestTagFailure,15:Overrun: These two detection systems have been well documented by PSMFC as having problems that could possibly be beneath the water line. 07/11/2006 09:15 William_ Washington Shore Half Duplex Site Hours of Operation: 9Jul06 22:05 - ??? PDT ***Reader not transmitting when I arrived at 06:02 on 10Jul06 10Jul06 22:00 - 22:16 PDT ***Troubleshooting and reconfiguration 10Jul06 22:13 - 11Jul06 05:59 PDT ***Normal operation 07/11/2006 07:25 troy@ruf 11:TestTagFailure,15:Overrun: Noted 07/10/2006 08:14 alan@ruf 11:TestTagFailure,15:Overrun: Known issues - will continue to monitor 07/09/2006 14:56 William_ Washington Shore Half Duplex Site Hours of Operation: 8Jul06 22:05 - 9Jul06 05:55 PDT 07/09/2006 11:22 troy@ruf 11:TestTagFailure,15:Overrun: Noted. 07/08/2006 10:08 troy@ruf 11:LowExcCurrent,11:TestTagFailure,15:Overrun: Clearing TASS. These are known problem antennas. 07/08/2006 06:10 William_ Washington Shore Half Duplex Site Hours of Operation: 7Jul06 22:05 - 8Jul06 06:00 PDT ------------------------------------------------ Bill Daigle Research Support Scientist Dept. of Fish and Wildlife Resources University of Idaho Moscow, Idaho Office:  208-885-4222 Cell:  208-596-1517 wrdaigle@uidaho.edu ------------------------------------------------ 07/07/2006 06:48 William_ Washington Shore Half Duplex Site Hours of Operation: Antenna Tuning and Configuration 6Jun06 12:30-12:37 PDT 6Jun06 21:56-22:10 PDT Normal Operation: 6Jun06 22:10 - 7Jun06 06:01 PDT 07/06/2006 08:27 Darren The noise reports for detection systems 11 thru 18 have been set to send every 10 minutes starting with file number BO306187.104. This was done to help evaluate the performance of the FDX systems during periods when the HDX system located in the transition pool are in operation. Bill Daigle (U of I) will be turning the HDX system on at 22:00 and off at 06:00pdt. The HDX system will start running on 07-06-2006 at 22:00pdt. The HDX system will only be operating two (2) orifice antennas that are multiplexed. PSMFC is aware that we have at least one detection system (15) that is currently showing signs of degradation and high noise. 07/06/2006 07:44 scottl@r 11:TestTagFailure,15:Overrun: Known problems with antennas are the cause of the alarms 07/05/2006 13:29 Troy A site GMC was performed today (07/05/06). All transcievers were checked for tune and adjustments made where needed. 07/05/2006 07:20 troy@ruf 11:TestTagFailure,15:Overrun: These alarms will be addressed today. These two antennas are known to have problems. 07/04/2006 08:23 darren@r 11:TestTagFailure,15:Overrun,15:TestTagFailure: These two systems have been well documented. PSMFC will check them out and do what can be done. 07/03/2006 07:48 darren@r 24:InputSyncDetect,24:ReaderReset: This alarm was generated by a random reader reset. 07/02/2006 08:46 darren@r 15:Overrun: Alarm noted. 06/29/2006 07:13 darren@r 11:TestTagFailure,15:Overrun: These detection systems have been well documented by PSMFC. 06/28/2006 14:13 troy@ruf 17:LowExcCurrent: This alarm was genereated during a site GMC. 06/28/2006 12:58 Troy A site GMC was performed today (06/28/06). All transceivers were checked for tune and adjustments made where needed. 11,15 and 17 are noisy. These antenna's have been known to have problems. 15 and 17 could read tags even though noisy, 11 could not be tuned to that point. PSMFC will inspect these antennas the next time the ladder is de-watered. 06/28/2006 07:17 darren@r 15:Overrun: Site will be visited today for site GMC. 06/27/2006 07:46 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,16:ReaderReset,17:ReaderReset,18:ReaderReset,22:InputSy ncDetect,22:ReaderReset,24:InputSyncDetect,24:ReaderReset,26:InputSyncDete ct,26:ReaderReset,28:ReaderReset,32:InputSyncDetect,32:ReaderReset,34:Inpu tSyncDetect,34:ReaderReset,36:InputSyncDetect,36:ReaderReset,38:ReaderRese t: These alarms were generated by a scheduled COE power outage. We were informed as to the outage by Tammy Mackey on Saturday. 06/26/2006 06:56 Scott_Li E-Mail from Tammy.. On 24 and/or 25 June- operators will be doing switching in the evening. There will be a loss of power to the AFF, possibly the PIT tag equipment. Operators will restart the raw water booster pump. On 26 June- please see the attached clearance and email. Orifice lights, lamprey PIT tag equipment, fishway diffuser valves may all experience a loss of power. This is expected to begin at 1300 and end approximately 8 hours later. 06/25/2006 09:18 scottl@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,11:TestTagFailure,12:Overrun,12:ReaderRes et,13:ReaderReset,14:ReaderReset,15:ReaderReset,15:TestTagFailure,16:Reade rReset,17:ReaderReset,18:ReaderReset,22:InputSyncDetect,22:ReaderReset,24: InputSyncDetect,24:ReaderReset,26:InputSyncDetect,26:ReaderReset,28:Reader Reset,32:InputSyncDetect,32:ReaderReset,34:InputSyncDetect,34:ReaderReset, 36:InputSyncDetect,36:ReaderReset,38:ReaderReset: Site appearently experienced a brief power outage. 06/22/2006 16:01 Alan_Bro The transceivers have all been verified as operating with "unique off" in preparation for the FDX lamprey test. 06/22/2006 07:15 scottl@r 11:TestTagFailure: Known problem antenna, TT failures are to be expected. 06/21/2006 13:30 Alan A GMC was performed 6/21/2006. All transceivers were checked and tuned as necessary. The clocks on both PCs are within four seconds of each other and 22 seconds of atomic time. No problems found. 06/21/2006 08:56 troy@ruf 11:TestTagFailure: This alarm will be addressed today (6/21/06) during a scheduled GMC. 06/20/2006 07:22 darren@r 11:TestTagFailure,15:Overrun: Detection systems have been well noted by PSMFC. We will make every effort to optimize these systems on the next site visit. 06/19/2006 08:23 scottl@r 11:TestTagFailure: Antenna 11 has known problems, TT failures are expected. 06/18/2006 10:33 troy@ruf 11:TestTagFailure: These alarms are not affecting readability. They will be addressed on the next site visit. 06/17/2006 10:25 troy@ree 11:TestTagFailure,15:Overrun: These two antennas are known to be have issues. 06/13/2006 12:10 scottl@r 03:LowExcCurrent,11:TestTagFailure,15:LowExcCurrent,15:Overrun,17:LowExcCu rrent: Noted, alarms were generated by GMC 06/12/2006 14:35 Alan A GMC was performed 6/12/2006. All transceivers were checked and tuned as necessary. Both PCs clocks were set to within one second of atomic time. File BO306163.209 was manually submitted from PC2 to fill the gap during PC1's downtime. No other problems found. 06/12/2006 07:52 troy@ree 11:TestTagFailure,15:Overrun: These two antennas are known to have problems. 06/11/2006 09:07 alan@ree 11:TestTagFailure: Noted 06/10/2006 09:11 alan@ree 11:TestTagFailure: Noted 06/09/2006 07:53 alan@ree 11:TestTagFailure: Noted 06/08/2006 07:49 alan@ree 11:TestTagFailure: Noted 06/08/2006 07:35 alan@ree 11:TestTagFailure: Noted 06/07/2006 08:21 alan@ree 11:TestTagFailure: Noted 06/07/2006 08:10 alan@ree 11:TestTagFailure,15:Overrun: Noted 06/06/2006 08:33 troy@ree 11:TestTagFailure,15:Overrun: These two antenna's are known to have problems. 06/04/2006 08:45 darren@r 11:TestTagFailure,15:Overrun: Alarms noted. 06/03/2006 08:56 darren@r 11:TestTagFailure,15:Overrun: Alarms noted. 06/02/2006 09:01 dlwarf@r 11:TestTagFailure,15:Overrun: Noted. 06/01/2006 07:28 darren@r 11:TestTagFailure,15:Overrun: Problematic antennas. 05/31/2006 13:45 Alan A GMC was performed 5/31/2006. All transceivers were checked and tuned as necessary. The clocks on both PCs were set to within one second of atomic time. No activity was observed on PC2 during PC1's downtime. No other problems found. 05/31/2006 13:36 Scott_Li Responding to Problem with Remote Data Sites message, manually pushed files via PCA to PTAGIS with no problems. The BO4 log file indicates the recent attempt to auto upload failed due to " Error transmitting PTTP package" Auto upload failed. Looks as if this problem was just a hick-up at the right time, or wrong time. 05/31/2006 07:25 darren@r 11:TestTagFailure,15:Overrun: Alarm noted. These detection systems are suspect and have been for some time. 05/30/2006 07:57 darren@r 11:TestTagFailure,15:Overrun: These two detection systems have been progressively getting harder and harder to drive. PSMFC suspects that the problem is the antennas or something below the water line. This ladder was de-watered this past season and will not do so until this December. PSMFC is doing what can be done to try and optimize these systems. 05/26/2006 08:35 darren@r 11:TestTagFailure: Alarms will be addressed on the next site visit. 05/25/2006 07:40 scottl@r 09:TestTagFailure: Noted 05/23/2006 12:25 Darren A site GMC was performed today (5-23-06). All transceivers were checked for tuning, noise, and detection ability. The PC's are within 30 seconds of atomic time and 5 seconds of each other. No problems were found. 05/23/2006 08:27 alan@ruf 0F:ReaderReset: This alarm was generated by a random reader reset. PSMFC and Digital Angel are aware of the problem. 05/22/2006 07:46 scottl@r 15:TestTagFailure: Noted 05/21/2006 09:48 troy@ruf 11:Overrun,15:TestTagFailure: These alarms will be looked into on the next site visit. 05/19/2006 07:26 troy@ruf 15:TestTagFailure: Noted 05/18/2006 15:03 Darren A site GMC was performed today (5-18-06). All transceivers were checked for tuning, noise and detection ability. No problems were found. The PC clocks are witn 40 seconds of atomic time and 3 seconds of each other. 05/17/2006 07:58 troy@ruf 15:Overrun: Noted 05/16/2006 08:13 troy@ruf 15:Overrun,15:TestTagFailure: This antenna is known to have problems that most likely exist below the water line. 05/14/2006 10:13 alan@ruf 11:Overrun: Noted 05/13/2006 11:22 alan@ruf 15:TestTagFailure: Noted 05/13/2006 11:02 Alan Manually pushed BO306133.102 and BO306133.103 to PTAGIS via PCA. 05/11/2006 13:46 Alan A GMC was performed 5/11/2006. 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. 05/11/2006 07:16 darren@r 15:TestTagFailure: This alarm will be addressed today during a site GMC. This detection system has been troublesome and is well documented by PSMFC. 05/10/2006 07:20 darren@r 15:TestTagFailure: Alarm will be addressed tomorrow during site GMC's. 05/04/2006 08:18 troy@ruf 03:LowExcCurrent,15:ReaderReset: These alarms were generated during a site GMC. 05/03/2006 14:52 Darren A site GMC was performed today (5-3-06). All transceivers were checked for tuning, noise and detection ability. No problems were found. The PC clocks are within 1 minute of atomic time and 10 seconds of each other. 05/02/2006 08:23 troy@ruf 24:TestTagFailure: Noted 04/27/2006 12:51 Alan A GMC was performed 4/27/2006. All transceivers were checked and tuned as necessary. Both PCs clocks are within 16 seconds of atomic time. No problems found. 04/26/2006 09:39 darren@r 02:Overrun,15:TestTagFailure: Alarms will be addressed on the next site visit. 04/25/2006 08:15 darren@r 02:Overrun: Problem will be addressed on the next site visit. 04/24/2006 08:28 darren@r 02:Overrun: This alarm will be investigated by PSMFC personnel on the next site visit. 04/21/2006 08:20 darren@r 01:LowExcCurrent,01:ReaderReset,02:LowExcCurrent,02:Overrun,02:ReaderReset ,03:LowExcCurrent,03:ReaderReset,04:LowExcCurrent,04:ReaderReset,05:LowExc Current,05:ReaderReset,06:LowExcCurrent,06:ReaderReset,07:LowExcCurrent,07 :ReaderReset,08:LowExcCurrent,08:ReaderReset,09:LowExcCurrent,09:ReaderRes et,09:TestTagFailure,0A:ReaderReset,0B:LowExcCurrent,0B:ReaderReset,0C:Low ExcCurrent,0C:ReaderReset,0D:LowExcCurrent,0D:ReaderReset,0E:LowExcCurrent ,0E:ReaderReset,0F:LowExcCurrent,0F:ReaderReset,10:LowExcCurrent,10:Reader Reset,15:TestTagFailure: Alarms were generated by PSMFC personnel while performing a site GMC. 04/20/2006 14:03 Dave I updated the map and database files to BO306110.MAP and BO306110.DB, respectively. This configuration includes "signal-by-code" instructions for four salmon groups (yellow light/horn) and two shad groups (red light/horn). The clocks on the two PCs are within 1 second of each other and atomic time. 04/20/2006 13:01 Darren A site GMC was performed today (4-20-06). All the transceivers were checked for tuning, noise and detectability. The analog boards on antennas 01-10 were swapped with the test boards and will be sent back to Digital Angel for the NPO upgrade. They will be returned to the proper transceiver when they are returned. 04/16/2006 11:25 troy@ruf 22:InputSyncDetect,22:InputSyncLost,26:InputSyncDetect,26:InputSyncLost,28 :ReaderReset: Random Reader Reset 04/11/2006 16:42 Troy A site GMC was performed today. All transcievers were checked for tune and adjusted where necessary. No problems were found. 04/10/2006 08:15 darren@r 15:Overrun: PSMFC will address this detection system this week. This system has had trouble over the last year. We will investigate the antenna and connection when the ladder is de-watered next season. 04/09/2006 09:06 alan@ruf 15:Overrun: Noted 04/08/2006 09:16 alan@ruf 15:Overrun: Noted 04/06/2006 09:13 alan@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:Overrun,15:ReaderReset,16:ReaderReset,17:ReaderReset,18:ReaderReset ,22:InputSyncDetect,22:ReaderReset,24:InputSyncDetect,24:ReaderReset,26:In putSyncDetect,26:ReaderReset,28:ReaderReset,32:InputSyncDetect,32:ReaderRe set,34:InputSyncDetect,34:ReaderReset,36:InputSyncDetect,36:ReaderReset,38 :ReaderReset: Apparently, a power event occurred 4/6/2006 at approximately 00:29:09. We are awaiting confirmation of this from site personnel. 04/05/2006 08:51 alan@ruf 15:Overrun: Noted 04/04/2006 10:50 Dave The BO3-PC1 computer locked up on Saturday, April 1, due to an apparent memory leak. The BO3-PC2 computer was not affected, and data files were collected and transferred from this machine until Scott and Troy arrived at BO3 on April 3 and rebooted BO3-PC1. After restoring this machine, and ensuring that all data files were complete and synchronized, the BO3-PC2 machine was also rebooted. I theorize that this situation occurred because the BO3 platform has not been rebooted (intentionally or otherwise) for over a year. This installation is also unique in that much more memory is allocated for the SbyC database at this site than elsewhere, and the SbyC signals are activated through the parallel port rather than a serial port. This situation has not been observed in the previous eight years; if it occurs again, I would suspect a hardware issue. 04/04/2006 09:16 alan@ruf 15:Overrun: Noted 04/03/2006 08:47 alan@ruf 15:Overrun: This problem has been addressed. The problem appears to be with the antenna or cabling, we will check the status when the ladder is de-watered next year. 04/02/2006 11:03 darren I PCA'd into this site and found an error message concerning Multimon and memory. The error stated that if this application continued to run the system could become unstable. I tried to remotely reboot the PC and now I have lost communications via PCA. I checked and found that PC2 is diverting and is collecting Data. PSMFC will be on site tomorrow to solve this problem. Darren R. Chase PSMFC Systems Engineer (509) 735-2773 ext.3 darren@psmfc.org 03/31/2006 13:45 Dave Initialized site platform for 2006 field season. Reset all counters. Reinstalled BO3-GEN.MAP and BO3-GEN.DB map and database files, respectively. Archived and cleared counters. Cleared log files. Data files has not been archived on BO3-PC2 since last fall; they should have been archived programmatically each month. Manually archived the data files without incident. Corrected the MultiMon parameters on BO3-PC2 to start in a "minimized" window, rather than "maximized". Reset the clocks on both PCs to within one second of atomic time and each other. The site has been monitoring fish passage continuously over the winter. No SbyC activity is currently scheduled at BO3. 03/28/2006 08:13 darren@r 15:Overrun: This problem has been addressed. The problem appears to be with the antenna or cabling, we will check the status when the ladder is de-watered next year. 03/23/2006 08:33 darren@r 15:Overrun: This alarm will be checked by PSMFC sometime today. This antenna has been troublesome since the last year. The problem may be beneath the water line. PSMFC will every adjustment to optimize the detection efficiency. 03/22/2006 08:25 darren@r 15:Overrun: This alarm will be investigated by PSMFC personnel today (3- 22-06). We have had some trouble with this detection system in the past, the problems may be with the antenna. The ladder was not de-watered this year so it could not be inspected. 03/20/2006 15:03 scottl Corrected the problem with the DSL service this morning. Problem was a poor connection at the demark. Verified that data services for all bonn sites was restored and also to the SMP office. Removed all the party lines from the DSL POT line in order to avoid any potential interuption in service. The BO4 server was restarted at 2:56 pm 3/20 in order to resyncronize co servers and Ftv and to flush the socket connections. Some hidden process was still running effecting the remote access capabilites to Ftv,CS1 and 2. 03/19/2006 10:22 dlwarf@r 15:Overrun: Noted. 03/18/2006 11:55 Don_Warf We are currently dealing with DSL problems. The modem has been rebooted and has re-established connectivity. 03/15/2006 15:26 scott The DSL data services were briefly interrupted around 10:00 AM this morning for reconfiguration and phone line consolidation purposes. Telephone service at BO1,2,3,4 all share a common party line therefore eliminating 2 unique analog lines. FYI.. The Copper to Fiber converter at BO2 is not working and a long term problem at BO1 is still being investigated. Trouble ticket was submitted to the COE with regards to these two problems.PSMFC will help facilitate repairs if necessary but replacement od the devices are the COE responsibility. As of 3:21 pm, it appears data services are up and running. 03/10/2006 08:06 troy@ruf 02:LowExcCurrent: This was addressed 3/9/06. 03/09/2006 08:37 troy@ruf 02:LowExcCurrent: The current had dropped to 3400 and the current alarm threshold was at 3400. The alarm threshold was lowered to 3100 via PCA. The cause of the current drop will be investigated on the next site visit. 03/04/2006 12:31 alan@ruf 15:TestTagFailure: This transceiver was experiencing noise at the time of this failure. PTAGIS Field Operations will continue to monitor. 03/02/2006 11:18 dlwarf@r 10:ReaderReset: Common reader reset. 02/24/2006 08:29 troy@ruf 15:Overrun: This antenna is suspected to have a problem below the water line. 02/18/2006 09:24 dlwarf@r 0D:LowExcCurrent: Will be addressed during the next GMC. 02/10/2006 08:25 alan@ruf 15:Overrun: This transceiver is exhibiting noise spikes. This antenna has trouble below the waterline. PTAGIS Field Operations will continue to monitor. 02/04/2006 08:53 troy@ruf 15:Overrun: It is suspected that this unit has problems below the water line. 02/03/2006 18:27 Troy None of these sites are 'green' in PCA. This site and another DSL site PRO are not responsive to PCA. PRO was visited this evening and internet connectivity is good. 02/01/2006 11:13 Troy Manually pushed delinquint files. Each site attempted to load but ran into what looked to be a timeout error. PSMFC will monitor for future errors. 01/31/2006 08:06 troy@ruf 15:Overrun: This antenna is suspected to have issues below the water line. Tuning adjustments will be made on the next site visit to try and eliminate the overruns 01/22/2006 08:30 darren@r 15:Overrun: This antenna detection system was checked on the last site visit. It appears that there may be problems that are below the water line. PSMFC can only investigate these problems next year during the de- watering period. PSMFC will try to maintain the systems optimization throughout the year. 01/20/2006 11:34 Scott_Li The data services for these sites were converted from the T-1 to DSL on 1/19/06 at 1600 hrs. A comprehensive function test was completed on all data collection computers. This included testing of the remote access PCA application to all sites. Will revise the site I/P address table on Monday 23rd, 06 to reflect the new adressing scheme. Buffers were dumped on the BO4 transcievers and the records are contained in file BO406020.E1. This was done due to recent outages incurred on the BO4 plaform. 01/20/2006 08:27 darren@r 0D:LowExcCurrent: Alarm was generated by PSMFC personnel while performing a site GMC. 01/18/2006 08:27 darren@r 15:TestTagFailure: This antenna could possibly be failing. The noise and tune has shifted severly and will be addressed on the next site visit. The antenna could be leaking to the point that it could fail. PSMFC will discuss the potential fixes for this site. 01/13/2006 08:08 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: Alarm was probably generated by a COE power outage (2). PSMFC will try to verify with site personnel. 01/10/2006 08:29 scottl@r 06:LowExcCurrent: The current alarm for this xcvr is set to 3700 mA and the actual current is 4 amps. it is unclear as to why this alarm was triggered. 01/09/2006 12:48 scottl The data services for the interrogation platform were switched over to DSL today at 12:15 hrs. This is the first phase of the global change over from the T-1 line. No PIT tagged fish were observed transiting the system as the I/P configuration took place on both PC1 and 2. The patch file for PC1 will be BO306009.206 FYI.. For whatever reason., we have no long distance phone service in the BO3/BO4. Probably associated with the DSL install. Will call Sprint and put in a trouble ticket. 01/09/2006 08:11 darren@r 06:LowExcCurrent: The alarm threshold was equal to the current value. I PCA'd into the site and adjusted the threshold to 300mA below the current value. 01/07/2006 11:28 dlwarf@r 06:LowExcCurrent: To be investigated this Monday. 01/06/2006 08:06 scottl@r 06:LowExcCurrent,0B:ReaderReset: Errors will be addressed on the next visit. 01/01/2006 12:40 PTOC_Bot Annual log file initiation for BO3 #### End of Event Log for BO3 ###