EVENT LOG FOR SITE BO1 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/2010 08:35 darren@b 01:TestTagFailure,04:TestTagFailure: These systems have drifted slightly out of tune and will be addressed during the next site visit. 12/29/2010 07:53 Troy@bay 01:TestTagFailure,04:TestTagFailure: These alarms will be addressed on the next site visit. These transceivers are currently reading fish at 100% efficiency. 12/23/2010 07:16 scottl@b 04:TestTagFailure: Noted 12/22/2010 07:07 scottl@b 01:TestTagFailure,04:TestTagFailure: Noted 12/20/2010 08:09 Troy@bay 04:TestTagFailure: The tune appears to have drifted slightly but the system is still reading pittags at a high efficiency. 12/19/2010 06:40 alan@bay 04:TestTagFailure: Noted 12/18/2010 08:32 alan@bay 01:TestTagFailure,04:TestTagFailure: This will be addressed during the next site visit. 12/17/2010 10:29 dlwarf@b 04:TestTagFailure: Noted. 12/16/2010 07:59 alan@bay 04:TestTagFailure: This transceiver appears to have drifted slightly out of tune, but is reading PIT tags well. PTAGIS Field Operations will continue to monitor. 12/14/2010 08:07 alan@bay 01:TestTagFailure,02:TestTagFailure,03:LowExcCurrent,03:TestTagFailure: These alarms were addressed yesterday during a site visit. 12/13/2010 10:39 Troy A site GMC was performed 12/13/2010. All transceivers were checked for tune and adjustments made where needed. No problems to report. 12/13/2010 07:38 alan@bay 01:TestTagFailure,02:TestTagFailure,03:TestTagFailure,04:TestTagFailure: This will be addressed today during a site visit. 12/12/2010 06:52 Troy@bay 01:TestTagFailure,02:TestTagFailure,03:TestTagFailure,04:TestTagFailure: A GMC is scheduled for tomorrow and these alarms will be addressed then. 12/11/2010 06:26 Troy@bay 01:TestTagFailure,02:TestTagFailure,03:TestTagFailure,04:TestTagFailure: These alarms will be addressed on the next site visit. 12/07/2010 07:19 Troy@bay 01:TestTagFailure,02:TestTagFailure,03:TestTagFailure,04:TestTagFailure: This system has drifted out of tune and will be addressed on the next site visit. 12/06/2010 07:45 Troy@bay 01:TestTagFailure,02:TestTagFailure,03:TestTagFailure,04:TestTagFailure,23 :TestTagFailure: These alarms will be addressed on the next site visit. 11/29/2010 07:16 scottl@b 01:TestTagFailure,02:TestTagFailure,03:TestTagFailure,04:TestTagFailure,24 :TestTagFailure: System requires tuning, but is still detecting fish at an acceptable rate. 11/28/2010 09:04 darren@b 01:TestTagFailure,02:TestTagFailure,03:TestTagFailure,04:TestTagFailure,0D :TestTagFailure: The systems on antennas 01, 02, 03, and 04 are due to a slight drift in tune. The alarm on 0D has no direct cause, all will addressed during the next site visist. 11/27/2010 09:09 darren@b 01:TestTagFailure,02:TestTagFailure,03:TestTagFailure,04:TestTagFailure: These systems have drifted slightly out of tune. THey will be addressed during the next site visit. 11/26/2010 08:43 darren@b 01:TestTagFailure,02:TestTagFailure,03:TestTagFailure,04:TestTagFailure: These systems have drifted slightly out of tune. They will be addressed during the next site visit. 11/25/2010 07:45 darren@b 01:TestTagFailure,02:TestTagFailure,03:TestTagFailure,04:TestTagFailure: These systems have drifted slightly out of tune. They are detecting PItags at a very high efficiency. They will be addressed during the nexgt site visit. 11/24/2010 06:59 darren@b 01:TestTagFailure,02:TestTagFailure,03:TestTagFailure,04:TestTagFailure,21 :LowExcCurrent,23:TestTagFailure: These systems have drifted slightly out of tune. They will be addressed during the next site visit. They are detecting PIT tags with very high efficiency. 11/22/2010 08:05 darren@b 01:TestTagFailure,02:TestTagFailure,03:TestTagFailure,04:TestTagFailure: These systems have drifted out of tune. They are still detecting PITtags at a very high efficiency. They will be addressed during the next site visit. 11/21/2010 10:43 Troy@bay 01:TestTagFailure,02:TestTagFailure,03:TestTagFailure,04:TestTagFailure: These alarms will be investigated on the next site visit. 11/20/2010 08:38 Troy@bay 02:TestTagFailure,03:TestTagFailure: These antennas appear to have drifted slightly in tune but are still reading at a high efficiency. These will be addressed on the next site visit. 11/18/2010 07:22 alan@bay 03:TestTagFailure: This will be addressed during the next site visit. 11/17/2010 07:13 darren@b 01:TestTagFailure,03:TestTagFailure: Thee systems have drifted slightly out of tune. They are detecting PITtags at a very high efficiency. They will be addressed durign the next site visit. 11/16/2010 07:44 Troy@bay 03:TestTagFailure: Noted 11/15/2010 07:19 Troy@bay 03:TestTagFailure: Noted 11/14/2010 07:59 darren@b 01:TestTagFailure,03:TestTagFailure: These systems will be addressed during the next site GMC. 11/13/2010 08:15 darren@b 01:TestTagFailure,02:TestTagFailure,03:TestTagFailure: These systems have drifted slightly in tune. They will be addressed during the next site visit. They are performing with high efficiencies. 11/12/2010 08:30 darren@b 03:TestTagFailure: This system will be addressed during the next site GMC. 11/11/2010 07:07 darren@b 03:TestTagFailure: This system has drifted in tune. It will be addressed during the next site visit. 11/10/2010 07:24 alan@bay 04:TestTagFailure: This transceiver appears to have drifted slightly out of tune. This will be addressed during the next site visit. 11/09/2010 07:33 darren@b 03:TestTagFailure: It appears that this system has drifted slightly out of tune. It will be addressed during the next site visit. 11/06/2010 06:53 alan@bay 01:TestTagFailure: Noted 11/01/2010 06:53 alan@bay 03:TestTagFailure: No apparent reason for this one-time alarm. PTAGIS Field Operations will continue to monitor. 10/19/2010 06:39 alan@bay 02:TestTagFailure: This will be addressed during the next site visit. 10/19/2010 06:35 alan@bay 02:TestTagFailure,04:TestTagFailure: This will be addressed during the next site visit. 10/18/2010 07:09 alan@bay 02:TestTagFailure,04:TestTagFailure: These transceivers appear to have drifted slightly out of tune. These alarms will be addressed during the next site visit. 10/17/2010 07:50 Troy@bay 04:TestTagFailure: This alarm will be addressed on the next site visit. 10/16/2010 11:51 Troy@bay 02:TestTagFailure: These alarms will be addressed on the next site visit. 10/15/2010 06:31 Troy@bay 02:TestTagFailure: Noted. 10/14/2010 06:32 Troy@bay 02:TestTagFailure: Noted 09/25/2010 08:09 alan@bay 01:TestTagFailure: No apparent reason for this one-time alarm. PTAGIS Field Operations will continue to monitor. 09/12/2010 08:22 Darren The outstanding files for these sites were manually pushed to PTAGIS via PCA. 09/10/2010 12:57 Alan The slot transceivers were adjusted (tuning, 2-4K, HPF) 9-10-2010, no problems found. 09/08/2010 08:16 darren@b 01:TestTagFailure,02:TestTagFailure: These alarms were addressed during yesterdays site GMC. 09/07/2010 12:57 Alan A GMC was performed 9-7-2010. All transceivers were checked and tuned as necessary. Outstanding files on PC2 were archived. The temp folders on both PCs were emptied. The clocks on both PCs were set to within one second of atomic time. No problems found. 09/04/2010 10:38 scottl@b 01:TestTagFailure: Noted 09/03/2010 10:00 darren@b 01:TestTagFailure: Alarm will be addressed during the next site GMC. 09/01/2010 12:36 scottl All networking FO and copper converters and switches were replaced in lieu of the system wide network upgrades. The PSMFC network is now exclusively using black box products with the exception of the Sonicwall firewall and Dell managed switch in BO3. All Allied Telsyn products that were removed are being brought back to the Kennewick office for storage. Cleaned out the spiders webs underneath the level sensor in the transport flume at b2J. This was causing the level sensor to send false readings. 09/01/2010 08:27 alan@bay 01:TestTagFailure: This transceiver appears to have drifted slightly out of tune, but is reading PIT tags well. This will be addressed during the next site visit. 08/31/2010 08:17 alan@bay 01:TestTagFailure: No apparent cause for this alarm. The antenna and transceiver are reading fish at a high efficiency. This will be monitored and addressed on the next site visit. 08/29/2010 07:30 Troy@bay 01:TestTagFailure: Noted 08/28/2010 08:29 Troy@bay 01:TestTagFailure: No apparent cause for this alarm. The antenna and transceiver are reading fish at a high efficiency. This will be monitored and addressed on the next site visit. 08/26/2010 08:18 darren@b 01:TestTagFailure,04:TestTagFailure: These systems will be addressed during the next site visit. The detection efficiencies are very high. 08/25/2010 14:52 Alan Remotely added the Biomark 23 MM tag to the country code list in both PC1 and PC2 registries. 08/24/2010 08:16 darren@b 01:TestTagFailure: This system has drifted slightly in tune. It will be addressed during the next site GMC. It is detecting PITtags at a very high efficiency. 08/23/2010 08:40 darren@b 01:TestTagFailure: IT appears that this system has drifted slightly in tune. It will be addressed during the next site visit. The system is detecting tags at very high efficiencies. 08/22/2010 09:30 alan@bay 01:TestTagFailure: No apparent reason for this alarm. There was a fish detected 2 minutes prior. The transceiver appears in tune and is reading PIT tags well. This will be investigated during the next site visit. 08/21/2010 09:20 alan@bay 01:TestTagFailure: No apparent reason for this alarm. PTAGIS Field Operations will continue to monitor. 08/19/2010 08:19 alan@bay 04:TestTagFailure: No apparent reason for this alarm. PTAGIS Field Operations will continue to monitor. 08/16/2010 09:28 alan@bay 01:TestTagFailure: No apparent reason for this one time alarm. PTAGIS Field Operations will continue to monitor. 08/11/2010 08:19 darren@b 01:TestTagFailure: Alarm will be investigated during the next site GMC. 08/05/2010 13:25 Darren A site GMC was performed today (8-5-10). All transceivers were checked and adjusted for tuning, noise, and detectability. The files on PC2 were archived. No problems were discovered during this visit. 08/04/2010 08:17 darren@b 04:TestTagFailure: No direct cause for this alarm. It will be investigated during the next site visit. 07/22/2010 13:40 Darren A site GMC was performed today (7-22-10). All transceivers were checked and adjusted for tuning, noise, and detectability. The files on PC2 were archived. No problems were discovered during this visit. 07/18/2010 10:38 scottl@b 04:TestTagFailure: Noted 07/09/2010 08:31 darren@b 04:TestTagFailure: The system has drifted in tune and will be addressed during the next site visit. The detection efficiencies are very high. We will monitor for future alarms. 07/07/2010 13:08 Alan The slot transceivers were tuned 7-7-2010, no problems to report. 07/04/2010 09:42 alan@bay 04:TestTagFailure: No apparent reason for this one-time alarm. PTAGIS Field Operations will continue to monitor. 07/02/2010 08:28 alan@bay 03:LowExcCurrent: Alarm threshold was remotely lowered from 6400 to 6300mA. 07/01/2010 13:42 Darren A site GMC was performed today (7-1-10). All transceivers were checked and adjusted for tuning, noise, and detectability. The PC clock on PC1 was 2 min off from atomic time and PC2. The clock was adjusted for a period of 46 seconds at which time there were no detections on PC2. No problems were discovered during this visit. 06/28/2010 09:28 darren@b 03:LowExcCurrent: No direct cause for this alarm. PSMFC will investigate during this weeks site GMC. 06/27/2010 07:46 Troy@bay 03:LowExcCurrent: The current is swing ~200mA but the transceiver is at 100% detection efficiency. PSMFC will continue to monitor and adjust make adjustments to the Current Alarm Threshold on Monday. 06/26/2010 07:56 Troy@bay 03:LowExcCurrent: It appears the current has dropped close to the low current alarm threshold. PSMFC will address on the next site visit or change the threshold next week. 06/23/2010 13:55 Darren A site GMC was performed today (6-23-10). All transceivers were checked and adjusted for tuning, noise, and detectability. No problems were discovered during this visit. The files on PC2 were archived. 06/22/2010 08:20 darren@b 04:TestTagFailure: No direct cause for this alarm. The system is performing very well and is detecting to a high efficiency. Will monitor for future alarms. 06/09/2010 09:02 darren@b 04:BadOscFreq,04:LowExcCurrent,04:TestTagFailure: This detection system was worked on by PSMFC to make a connection that would make the system stable for the remainder of the season. We were able to make a hard connection to the antenna wires which should eliminate any future problems with current loss and increased noise. We will continue to watch for any changing conditions that cannot be rectified by simple tuning. 06/08/2010 08:54 troy@bay 04:LowExcCurrent,04:TestTagFailure: This issue will be addressed today. 06/07/2010 08:05 darren@b 04:LowExcCurrent,04:TestTagFailure: This system will be addressed during a site visit tomorrow. PSMFC has been mamking adjustments to this system all season due to a intermittent connection to one of the pins on the connector. We have made all attempts to ensure that this system has been working at top efficiencies. 06/06/2010 10:16 alan@bay 04:TestTagFailure: This system will be investigated during a site visit next week. 06/05/2010 08:43 alan@bay 04:BadOscFreq,04:LowExcCurrent,04:TestTagFailure: This system will be investigated during a site visit next week. 06/02/2010 08:39 darren@b 04:LowExcCurrent,04:TestTagFailure: This system will be investigated during tomorrow's site GMC. 05/26/2010 11:39 Alan A GMC was performed 5-26-2010. 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 were set to within one second of atomic time. No problems found. 05/21/2010 09:09 darren@b 24:LowExcCurrent: The alarm threshold is equal to the actual current. I will adjust the threshold via PCA. 05/21/2010 08:27 darren@b 04:LowExcCurrent: This system sis being addressed today during a site GMC. 05/19/2010 08:13 darren@b 04:TestTagFailure: No direct cause for this failure. The system is detecting PIT tags with high efficiency. 05/17/2010 08:24 darren@b 01:TestTagFailure: It appears that there multiple PITtags in the vicinity of the antenna at the time the timer tag tried to fire. This may have caused the failure. The system is detecting PITtags with a high efficiency. 05/13/2010 13:37 Alan A GMC was performed 5-13-2010. 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 were set to within one second of atomic time. No problems found. 05/13/2010 10:12 darren@b 04:TestTagFailure: Alarm is being investigated today during a site GMC. 05/10/2010 08:10 scottl@b 04:TestTagFailure: Noted 05/09/2010 09:40 alan@bay 04:TestTagFailure: This system has been well documented and is being monitored for performance. We will be checking and adjusting during the next site visit. 05/08/2010 08:59 alan@bay 04:TestTagFailure: This system has been well documented and is being monitored for performance. We will be checking and adjusting during the next site visit. 05/06/2010 08:59 darren@b 04:TestTagFailure: This system has been well documented and is being monitored for performance. We will be checking and adjusting during the next site visit. 05/05/2010 08:50 darren@b 04:TestTagFailure: PSMFC is monitoring this system. Repair attempts have been made to maintain this systems efficiencies for this season by PSMFC. It will be investigated during the next site visit. 05/03/2010 12:21 Alan A GMC was performed 5-3-2010. All transceivers were checked and tuned as necessary. Archived outstanding files on PC2 and emptied both temp folders. Both clocks are within one second of atomic time. No problems found. 05/03/2010 08:15 darren@b 04:TestTagFailure: This alarm will be addressed during todays site GMC. 05/02/2010 09:45 Troy@bay 04:TestTagFailure: Known problematic antenna, clearing TASS. 05/01/2010 08:32 Troy@bay 04:TestTagFailure: Noted, known problematic antenna. 04/27/2010 08:55 troy@bay 04:LowExcCurrent,04:TestTagFailure: These alarms have been addressed. 04/26/2010 08:42 troy@bay 04:TestTagFailure: PSMFC is aware of the problem, and this antenna will be investigated further today during a scheduled GMC. 04/25/2010 07:46 darren@b 04:TestTagFailure: This alarm will be addressed during the site GMC tomorrow. 04/24/2010 08:03 darren@b 01:LowExcCurrent: This system will be checked during Mondays site GMC. 04/23/2010 15:34 darren@b 04:LowExcCurrent,04:TestTagFailure: These alarms will be addressed on Monday during a site GMC. 04/23/2010 08:37 darren@b 04:LowExcCurrent,04:TestTagFailure: PSMFC is making every effort to maintain this system at this point. The noise is attributed to the pin on the connector that may be intermittently broken. We have made attempts to alleviate the pressure on the pin but appears that the noise comes and goes when the temperature rises and falls. We will continue to monitor this and make the necessary adjustments to try and maintain high efficiencies with this system. 04/22/2010 08:18 darren@b 04:LowExcCurrent,04:TestTagFailure: The system has been experiencing some periods of high noise and low current, PSMFC is aware of this and has implemented a new test cable that will allow us to manipulate the connector pins when this situation arises. We will be adjusting this during the next site visit. 04/20/2010 09:28 darren@b 1F:LowExcCurrent,20:LowExcCurrent: These alarms were generated by PSMFC personnel while testing antenna 1F. The situation with antenna 1F appears to be below the water line. 04/20/2010 09:15 darren@b 04:LowExcCurrent: These alarms were addressed yesterday. PSMFC was on site to install a different cable for the antenna, this cable will allows us to have access to the individual pins when it is necessary to adjust one of the pins. This is what is causing the antenna current to drop and the increase in noise. We hope that we can alleviate the pressure that was being put on the connector this way. We will monitor the performance of this cable style and we may need to reconfigure it at some time this season. 04/19/2010 13:54 scottl The problem with unit 1F is the antenna or a component underwater. Swapped antenna leads 1F and 20 and the excessive noise issue follows the antenna 1F. When 1F was applied to xcvr 20 and the voltage was increased, the antenna noise levels were jumping all over, very instable antenna. Returned everything back to the original configuration and increased the noise alarm for 1F to 50% to avoid massive amount of alarms. The replacement of the converters fixed the slow network performance issue, as measured at this time. Will monitor but have confidence that the issue has been resolved. 04/19/2010 13:10 Scottl Replaced SM to MM converter in power house and replaced SM to Copper converter in BO3 network cabinet. Connection was made without issues. Will stop at BO1 on the way out to see if the connection to the Internet is any better. 04/18/2010 08:33 Troy 1F is experiencing high noise which started between 2010/04/17 01:38:03 & 2010/04/17 04:38:03. PSMFC will investigate on Monday. 04/16/2010 08:31 troy@bay 04:LowExcCurrent: This will be addressed next week. 04/15/2010 08:43 darren@b 04:LowExcCurrent,04:TestTagFailure: PSMFC is aware of this antenna system. We have determined that there may be a problem with the connector (one of the pins may have an intermittent connection). We are investigating the best solution for operating this system for this season. 04/14/2010 08:22 darren@b 04:LowExcCurrent,04:TestTagFailure: Alarms will be addressed during the site GMC today. The pin on the connector will be adjusted. 04/11/2010 10:47 scottl Manually pushed delinquent data files, deleted ack file.Connection seemed more than adequate. 04/08/2010 08:16 darren@b 0D:BadExcFreq,0D:BadOscFreq,0D:LowExcCurrent: These alarms were created by PSMFC personnel during a site GMC. 04/07/2010 11:40 Darren A site GMC was performed today (4-7-10). All transceivers were checked forr tuning, noise, and detectability. The current on 01 was restored yesterday around 15:00 and it was verified and retuned today. The current is 6.7A, phase @50 and the noise at 0-1. The noise spikes that are being observed on antenna 0D are coming from the antenna or something below the water line. I swapped the transceivers and found that the spikes traveled with the antenna, the system is quiet (3-4% signal) with spikes as high as 40-50% but only occasionally. I checked the timer tag but I could only get it to read 100% sometimes but it was always above 90%. I believe the system will read PITtags with high efficiency but we will have to monitor this antenna throughout the season, this could be the result of debris which may eventually leave the system. No other problems were discovered during this visit. 04/07/2010 08:36 troy@bay 01:TestTagFailure,04:LowExcCurrent,04:TestTagFailure: These alarms will be addressed today during a site GMC. 04/05/2010 08:28 troy@bay 01:TestTagFailure,04:LowExcCurrent: Alarms are noted and PSMFC will monitor. Both transceivers are reading a 100% efficiency. 04/04/2010 09:59 alan@bay 04:LowExcCurrent: This will be addressed during the next site visit. 04/03/2010 09:31 alan@bay 04:TestTagFailure,24:TestTagFailure: These alarms were adressed yesterday during a site visit. 04/02/2010 08:33 troy@bay 04:LowExcCurrent,04:TestTagFailure: This will be investigated today during a site visit. 04/01/2010 08:20 alan@bay 04:LowExcCurrent,04:TestTagFailure,24:TestTagFailure: These alarms will be addressed during the next site visit. 03/31/2010 08:44 alan@bay 04:TestTagFailure,24:TestTagFailure: These alarms will be addressed during the next site visit. 03/30/2010 08:47 alan@bay 04:TestTagFailure,24:TestTagFailure: These alarms will be addressed during the next site visit. 03/29/2010 08:34 alan@bay 04:LowExcCurrent,04:TestTagFailure,24:TestTagFailure: These alarms will be addressed during a site visit 3-31-2010. 03/25/2010 08:25 Alan@bay 24:TestTagFailure: This transceiver appears to have drifted slightly out of tune. This will be addressed during the next site visit. 03/25/2010 08:20 Alan@bay 04:LowExcCurrent,04:TestTagFailure: This is being investigated. 03/23/2010 08:18 darren@b 24:TestTagFailure: This system will be addressed during the next visit. The system has slightly detuned but is reading PITtags with adequate efficiency. 03/23/2010 07:55 darren@b 04:LowExcCurrent: These alarms were generated by PSMFC personnel while performing some tests on this system. 03/18/2010 10:53 Darren This is a posting for previous activities. The site watered up in the evening on 2/28/2010. 03/18/2010 09:37 darren@b 24:TestTagFailure: This system will be addressed during the next site visit. 03/17/2010 08:18 darren@b 04:LowExcCurrent: This system is being investigated by PSMFC. We are aware of the alarms and are implementing a plan to address this issue. The system is experiencing some periodic current and noise problems. 03/16/2010 08:44 alan@bay 24:TestTagFailure: Transceiver 24 is slightly out of tune, but is now reading timer tags well. This will be investigated during the next site visit. 03/15/2010 11:20 Alan The slot antennas were tuned 3-15-2010. Transceivers 01 and 02 are operating properly. Transceiver 03 is showing signal levels of 0% - 1%. Transceiver 04 is showing signal levels of 1%-4%. The hit rate on BO1-04 was set to 100% for it's current operating state. 03/15/2010 08:12 darren@b 04:TestTagFailure: This alarm is being investigated by PSMFC personnel. We will be troubleshooting this system later this week. It appears that the current was restored at 12:34 on 3/11 and the noise soon subsided, but the system still needs to adjusted for tuning. 03/14/2010 14:26 Dave I manually modified the FILE CLOSED time from "03:00" to "04:00" to circumvent a processing error associated with the shift from PST to PDT. 03/13/2010 15:55 alan@bay 04:TestTagFailure,24:TestTagFailure: Transceiver 04 is reporting near normal signal levels as of ~2100 3-12-2010. The timer tag alarm was prior to that occurance. Transceiver 24 is slightly out of tune, but is now reading timer tags well. This will be investigated during the next site visit. 03/11/2010 07:13 alan@bay 24:TestTagFailure: This transceiver is slightly out of tune causing this one time alarm. This will be remedied during the next site visit. 03/09/2010 07:42 alan@bay 03:LowExcCurrent,04:LowExcCurrent,04:TestTagFailure: These alarms were generated by PTAGIS Field Operations personnel during a site visit. 03/08/2010 13:02 scottl Unit 04 is in extreme noise condition and cannot be tuned out. The following is what was eliminated to diagnose and or fix the problem. Swapped xcvr: problem followed cable\antenna Removed UPS and heater from operation: Still noisy Checked for moisture in cap pocket, caps and cavity were completely dry. Checked solder joint on antenna/capacitor bank leads: Still noisy Remove antennas connector, checked for moisture, bone dry, no signs of previous moisture or corrosion. Megger tested antenna, infinite resistance across all 3 pins. Note that when the antennas connector and cap bank were being evaluated, the noise levels actually went up after everything was reassembled. Moved cap bank around and reseated antenna connector, noise levels were reduced but noise issue is still very apparent. Suggested approach of repair: Noticed that the antenna drive connector at the antenna was a bit sloppy, try new cable and or install new capacitor bank. Don, if you are reading this, I have tried everything that I can with what I had, This needs to be revisited, we can talk in the AM.I'll call you from BCC 03/08/2010 07:32 alan@bay 04:TestTagFailure: This transceiver appears to have drifted out of tune and will be addressed during the next site visit. 03/05/2010 07:37 Troy Manually pushed the delinquent file. 03/03/2010 07:17 darren@b 03:TestTagFailure: This alarm was addressed on Monday 3-1-10 during a site GMC. 03/01/2010 14:43 scottl Performed site GMC, all transceivers were re tuned and calibrated, no problems to report. 03/01/2010 07:55 Dave The Bradford Island fishway returned to service late in the day on Feb. 28. 03/01/2010 07:54 cloughd@ TASS processing for BO1 has been reinstated. It had been suspended on 10 Dec 09, because the site had been dewatered and consequently was generating lots of alarms and noise data. -Doug- 02/25/2010 07:08 Alan The power outage on 2-24-2010 caused a 2:35 minute file gap. The gap will not be backfilled as the site was dewatered for the duration of the outage. 02/24/2010 09:56 Alan Site personnel report an unannounced planned power outage at BO1 2-24- 2010. The power went out at ~0740 with power expected to return at 1030. No data loss will occur as the site is dewatered. 02/14/2010 10:15 Troy Manually pushed the delinquent file. 01/08/2010 08:26 Troy Manually pushed the delinquent file. 01/01/2010 00:00 PTOC_Bot Annual log file initiation for BO1 #### End of Event Log for BO1 ###