EVENT LOG FOR SITE BO1 Most recent activity to be listed first. First line of each entry lists date, time and who is reporting. Subsequent lines of each entry aligned under Time column. Do not use tabs, only spaces. Date Time Who What ---------- ----- -------- ----------------------------------------------- 12/20/2009 08:12 Troy Manually pushed the delinquent file. 12/18/2009 07:12 Troy Manually pushed the delinquent file. First attempt failed. Deleted a .ack file in the temp directory and the next attempt worked. 12/10/2009 07:07 darren@b 01:TestTagFailure,02:TestTagFailure,03:TestTagFailure,10:TestTagFailure,17 :TestTagFailure: Site is currently de-watered. Clearing TASS 12/09/2009 07:27 darren@b 01:TestTagFailure,02:TestTagFailure,03:TestTagFailure,17:TestTagFailure: This site is in the process of being de-watered. I spoke with site Bio Jon Rerecich yesterday and he informed me that they have the exit slightly open to try and encourage some sturgeon to leave the ladder. The ladder was de-watered but it may be a few days before we can consider the site to be out of service for winter maintenance. When the site is completely de- watered the site status page will be updated. 12/08/2009 08:19 Alan File BO109334.D9 was created from BO109334.D1.TMP found on PC1. It was submitted to help fill the data gap created by a power outage 11/30/2009. There is no data to fill the remaining 31 minute gap. 12/08/2009 07:33 darren@b 01:LowExcCurrent,01:TestTagFailure,02:LowExcCurrent,02:TestTagFailure,03:L owExcCurrent,03:TestTagFailure,17:TestTagFailure,1C:LowExcCurrent: This ladder is in the process of being completely de-watered. 12/07/2009 09:02 Dave I updated the obs_site_dates table to reflect the suspension of operations on Dec. 7, and updated the etc/sites file to constrain site-checking notifications to Kennewick staff only. 12/07/2009 07:43 darren@b 01:TestTagFailure,03:TestTagFailure: This site has begun the process for taking the ladder out of service for winter maintenance. 12/07/2009 07:23 Darren I was able to confirm from site Biologist Jon Rerecich that the ladder was brought to an orifice flow on Friday afternoon and will be completely de-watered this morning. The ladder is scheduled to remain out of service until 2/28/10. 12/06/2009 07:32 alan@bay 02:TestTagFailure,03:TestTagFailure,1B:TestTagFailure: These alarms will be investigated during the next site visit. 12/05/2009 08:04 Alan The ladder went to orifice flow 12/4/2009 at 1700 PST and is slated for full dewatering on 12/7/2009. 12/05/2009 06:59 alan@bay 01:TestTagFailure,02:TestTagFailure,03:TestTagFailure,04:TestTagFailure: It appears as though the ladder was dewatered 12/4/2009 at ~1700 PST. I am attempting to confirm this and will post an update later. 12/04/2009 07:18 alan@bay 03:TestTagFailure,04:TestTagFailure: These alarms will be investigated during the next site visit. 12/03/2009 07:21 alan@bay 03:TestTagFailure,04:TestTagFailure: These transceivers appear to have drifted slightly out of tune. This will be addressed during the next site visit. 12/02/2009 08:39 alan@bay 02:TestTagFailure,04:TestTagFailure,1E:TestTagFailure: These will be investigated during the next site visit. 11/30/2009 07:24 Scott_Li Things changed a bit with this work and the Brad. Is. PIT will be affected this morning. This should be from 7:30 to 9:30 at the longest, most likely much less. Sorry for the last minute notification. Call with any questions. Ben 11/25/2009 07:16 scottl@b 01:TestTagFailure,02:TestTagFailure,03:TestTagFailure,04:TestTagFailure: Problems have been corrected. Clearing TASS. 11/24/2009 11:15 Alan A GMC was performed 11/24/2009. All transceivers were checked and tuned as necessary. All outstanding files on PC2 were archived. The temp folders on both PCs were emptied. The clocks on both PCs were set to within one second of atomic time. No problems found. 11/23/2009 10:58 Don_Warf Per site EE: Next week, I am going to try to take down the SMF facility here at Bonneville briefly. It might be down for less than a 1/2 hour--that's including clearance time and the actual work time. We are starting to replace the Station Service Bus 1 and Bus 2 Switchgears in PH2 and that will have an impact on a lot of the Bonn fish facilities when changing over from one bus to another. The SMF will be about the first facility to be affected. If we wind up replacing both of the buses' switchgear, then we will have 3 more fairly "brief" interruptions at SMF during this IWWP. If we only wind up doing 1 bus's switchgear then we should only have one more interruption after the first one for SMF for this IWWP. Additionally, we will have at least a at least 2--maybe 4--fairly "brief" interruptions of the power for B2CC, Cascade Island, and Bradford Island pit tag antennas during this upcoming IWWP time. I can talk to you about it in more detail--hopefully sometime next week. The B2CC and Cascade Island interruptions should be really brief. It should just involve opening and closing the two buses' circuit bkrs in the North Tower ATS. I should be up to my neck in clearances fairly shortly. There's really no way to get around these interruptions, but we can hope to make them as brief as possible. I have already talked to our Project head biologist, Ben Hausmann about the SMF clearance. I've also talked with Gene Ballinger of SMF. They are both alright with the planned outage. I am hoping to do the SMF outage next Tuesday (11/24), but it willl depend on electrician availability. 11/23/2009 10:18 Don_Warf DLW email test _____________________________________________ From: Don Warf Sent: Monday, November 23, 2009 9:26 AM To: 'pitevent@psmfc.org'; 'pitevent@ptagis.org' Subject: gra,grj,goj,rpj,lmj,ich,mcj,mc1,mc2,jdj,pro,esj,jcj,cfj,bcc,bo1,bo2,bo3,b2 j,rzf Email test 11/23/2009 09:39 Troy_Hum Email Test from Troy 11/22/2009 07:11 alan@bay 01:TestTagFailure,02:TestTagFailure,03:TestTagFailure: These transceivers appear to have drifted slightly out of tune, but are reading PIT tags well. This will be remedied during the next site visit. 11/21/2009 07:11 alan@bay 01:TestTagFailure,02:TestTagFailure,03:TestTagFailure,04:TestTagFailure: These transceivers appear to have drifted slightly out of tune, but are reading PIT tags well. This will be remedied during the next site visit. 11/19/2009 07:41 alan@bay 01:TestTagFailure,02:TestTagFailure,03:TestTagFailure,04:TestTagFailure: These transceivers appear to have drifted slightly out of tune, but are reading PIT tags well. This will be remedied during the next site visit. 11/17/2009 07:24 alan@bay 01:TestTagFailure,02:TestTagFailure,03:TestTagFailure,04:TestTagFailure: These transceivers appear to have drifted slightly out of tune, but are reading PIT tags well. This will be remedied during the next site visit. 11/16/2009 07:56 alan@bay 01:TestTagFailure,02:TestTagFailure,03:TestTagFailure,04:TestTagFailure: These transceivers appear to have drifted slightly out of tune, but are reading PIT tags well. This will be remedied during the next site visit. 11/15/2009 09:14 troy@bay 01:TestTagFailure,02:TestTagFailure,03:TestTagFailure,04:TestTagFailure: These alarms will be addressed on the next site visit. 11/14/2009 07:46 troy@bay 01:TestTagFailure,02:TestTagFailure,03:TestTagFailure,04:TestTagFailure: These transceivers are in need of a tune and will be addressed on the next site visit. They are still reading PIT Tags. 11/13/2009 07:21 troy@bay 01:TestTagFailure,02:TestTagFailure,03:TestTagFailure,04:TestTagFailure,0C :Overrun: These alarms will be addressed on the next site visit. 11/12/2009 08:20 troy@bay 01:TestTagFailure,03:TestTagFailure,04:TestTagFailure: This alarm will be addressed on the next site visit. 11/11/2009 09:06 troy@bay 01:TestTagFailure,03:TestTagFailure,04:TestTagFailure: These alarms will be addressed on the next site visit. 11/10/2009 07:30 troy@bay 01:TestTagFailure,03:TestTagFailure,04:TestTagFailure: These alarms will be addressed on the next site visit. 11/09/2009 07:55 troy@bay 01:TestTagFailure,03:TestTagFailure,04:TestTagFailure,20:TestTagFailure: These alarms will be addressed on the next site visit. 11/09/2009 07:49 Troy Manually pushed the delinquent files. 11/07/2009 09:52 scottl@b 01:TestTagFailure,03:TestTagFailure,04:TestTagFailure: Noted 11/05/2009 07:18 scottl@b 01:TestTagFailure,03:TestTagFailure,04:TestTagFailure: Noted 11/03/2009 07:17 scottl@b 01:TestTagFailure,04:TestTagFailure: Noted 10/30/2009 08:26 alan@bay 04:TestTagFailure: This will be addressed during the next site visit. 10/27/2009 08:09 alan@bay 04:TestTagFailure: This will be addressed during the next site visit. 10/25/2009 11:02 scottl@b 04:TestTagFailure: Noted 10/22/2009 07:14 scottl@b 04:TestTagFailure: Noted 10/21/2009 07:42 troy@bay 04:TestTagFailure: This alarm will be addressed on the next site visit. 10/18/2009 08:16 alan@bay 04:TestTagFailure: This will be investigated during the next site visit. 10/16/2009 08:00 alan@bay 04:TestTagFailure: This alarm will be addressed today. 10/15/2009 08:05 alan@bay 17:TestTagFailure: This will be addressed today. 10/15/2009 07:49 Darren A site GMC was performed yesterday 10-14-09. The slot transceivers were tuned and adjusted for maximum reading efficiency. They had drifted about 3% on the signal. 10/14/2009 13:35 alan@bay 17:TestTagFailure: This transceiver appears to have drifted slightly out of tune. It will be investigated during the next site visit. 10/11/2009 09:18 darren@b 17:TestTagFailure: This system will be addressed during the next site visit. 10/11/2009 09:17 darren@b 04:TestTagFailure: This system was de-tuned due to something in the ladder, the current droped by 1.5A and the noise was very high, this phenomenon was observed earlier this season. The object was pushed outside the antenna on 10-7-09 at around 18:30. Now the system needs to be retuned. 10/10/2009 08:35 darren@b 17:TestTagFailure: Alarm will be addressed during the nest site visit. System needs to be tuned. 10/08/2009 07:51 alan@bay 04:TestTagFailure,17:TestTagFailure: These alarms will be investigated during the next site visit. 10/07/2009 07:16 darren@b 03:TestTagFailure,04:BadOscFreq,04:LowExcCurrent,04:TestTagFailure,17:Test TagFailure: These alarms were generated by PSMFC personnel during a site GMC. 10/06/2009 07:41 darren@b 04:TestTagFailure,17:TestTagFailure: These alarms will be investigated during a site GMC tomorrow. It appears that the systems have drifted out of tune. 10/05/2009 07:36 darren@b 04:TestTagFailure,17:TestTagFailure: These alarms will be investigated during the next site visit. 10/04/2009 09:25 troy@bay 17:TestTagFailure: Known problematic system, clearing TASS. 10/03/2009 08:09 troy@bay 04:TestTagFailure,17:TestTagFailure: A GMC was performed yesterday, clearing TASS. 10/02/2009 12:19 Scott_Li Performed site GMC , all slot antennas were retuned and calibrated as necessary, no problems to report. 10/01/2009 07:50 darren@b 17:TestTagFailure: Alarm will be addressed this week during the site GMC. 09/30/2009 07:40 alan@bay 04:TestTagFailure,17:TestTagFailure: These transceivers appear to have drifted slightly out of tune. They will be investigated during the next site visit. 09/28/2009 07:54 troy@bay 04:TestTagFailure,17:TestTagFailure: 17 is a known problematic system. 04 will be addressed later this week on a scheduled GMC. 09/27/2009 07:48 alan@bay 17:TestTagFailure: No apparent reason for this alarm. PTAGIS Field Operations will continue to monitor. 09/27/2009 07:46 alan@bay 04:TestTagFailure: No apparent reason for this alarm. PTAGIS Field Operations will continue to monitor. 09/26/2009 07:38 alan@bay 04:TestTagFailure: This transceiver was experiencing noise but now appears fine. PTAGIS Field Operations will continue to monitor. 09/23/2009 08:57 alan@bay 17:TestTagFailure: No apparent reason for this alarm. PTAGIS Field Operations will continue to monitor. 09/21/2009 13:47 Alan I traveled to the sites to investigate recent low efficiencies on the slot antennas. The transceivers at both sites were only slightly out of tune. No noise issues are apparent. I noticed that the water level was very high at BO4, so much so that it spills from upstream to downstream weirs at times. While tuning 02 at BO4, a fish jumped into the grating that I was standing on. I suspect that fish are traversing the ladder without passing through our antennas. I spoke with Jon Rerecich, he informed me that the forebay is (and will continue to be) maintained higher than normal for construction being performed at The Dalles. The water level upstream of the counting window is dependant upon forebay level, but Jon said he will see if something can be done. I tuned the slots at both sites and verified that the panel heaters are on in each transceiver enclosure. No other problems to report. 09/21/2009 07:55 alan@bay 17:TestTagFailure: No apparent reason for this alarm. PTAGIS Field Operations will continue to monitor. 09/20/2009 08:48 troy@bay 17:TestTagFailure: Noted 09/18/2009 07:43 troy@bay 17:TestTagFailure: Noted 09/17/2009 07:36 troy@bay 04:TestTagFailure: This alarm may have been the result of a GMC being performed. PSMFC will monitor. 09/15/2009 07:24 troy@bay 04:TestTagFailure: This alarm will be addressed today or tomorrow by PSMFC personnel. 09/14/2009 07:36 troy@bay 17:TestTagFailure: Noted 09/11/2009 08:17 Don_Warf Manually pushed 2 late files. 09/09/2009 08:32 Darren A patch file was created for a couple of missed detections during the time frame on Monday that PC1 was out of data collection for removing a .zip file out of the temp directory so that auto upload would submit files to PTAGIS. The file BO109250.H9 is the name of the file in which the detections reside. 09/08/2009 07:20 scottl@b 04:TestTagFailure: Noted 09/07/2009 08:51 darren@b 04:TestTagFailure: This alarm has no direct cause. The system is operating at very high efficiencies. We will continue to monitor for future alarms. 09/07/2009 08:37 Darren The site had not loaded since the 09:00 load yesterday. I PCA'd into the iste and manually pushed the files. I checked the temo directory and found a compressed zip file, but I could only remove the file by stopping Minimon and restarting it. I placed a file marker in at 07:27:51 and again when it was restarted 07:28:33 at which time there was a detection coming through on antenna 02. 09/04/2009 07:20 darren@b 04:TestTagFailure: No direct cause for this failure. We will monitor this system for performance. 09/03/2009 13:19 Darren A site GMC was performed today 9-3-09. All transceivers were checked for tuning, noise and detectability. The noise that was on antenna 04 has disappeared and the current jumped from 5.8A to 7.0A since Tuesday afternoon. The transceiver was retuned and is not showing signs of noise jumps. The files on PC2 were archived. No problems were discovered during this visit. 09/03/2009 07:05 darren@b 04:TestTagFailure: Alarm will be addressed today during a site GMC. 09/02/2009 07:04 darren@b 17:TestTagFailure: Alarm will be investigated during the next site visit. 08/31/2009 07:08 darren@b 04:TestTagFailure: This alarm has been noted. PSMFC is looking into the noise issues with this particular system. 08/28/2009 07:43 troy@bay 04:LowExcCurrent,04:Overrun,04:TestTagFailure: The majority of these alarms were generated during troubleshooting of the system. The system is still experiencing noise and PSMFC is still in the process of trying to determine the exact cause of the noise. 08/27/2009 19:25 Darren I checked the TASS exciter report and found that 04 is already back to 48% noise. I checked the raw files and the noise was o.k. until about a half hour after I left at which time it started to increase and the timer tags started to fail due to system activity. This system will be investigated early next week. The other three systems are working with very if not perfect efficiency. 08/27/2009 19:07 Darren_C PSMFC was on site today to do some testing on antenna 04. We are experiencing some noise issues that are trying to be isolated. Any TASS alarms that occurred between 10:30 and 14:30 PST were generated by PSMFC personnel. 08/27/2009 07:41 troy@bay 03:LowExcCurrent,03:Overrun,04:LowExcCurrent,04:TestTagFailure: PSMFC personnel generated these alarms while troubleshooting 04. PSMFC will be on site again today to try and bring the reading efficiency of 04 up. 08/26/2009 12:43 Darren PSMFC was on site today to investigate noise issues with antenna 04. The system was worked on and different test were performed for evaluate the source of the noise. There may TASS alarms that were generated due to this testing. The system is a little quieter as of 11:42 PDT, we will monitor this system carefully and make any necessary changes and adjustments. 08/26/2009 07:59 troy@bay 04:TestTagFailure: This will be addressed today. 08/25/2009 07:47 troy@bay 01:TestTagFailure,04:TestTagFailure: Both antenna's are experiencing high fish traffic and are reading at 93.38% and 96.03% respectively. PSMFC will monitor for future TT failures. 08/24/2009 08:37 troy@bay 01:TestTagFailure,04:TestTagFailure: Noted 08/23/2009 08:21 alan@bay 04:TestTagFailure: This will be investigated during the next site visit. 08/22/2009 07:46 alan@bay 04:TestTagFailure: This will be investigated during the next site visit. 08/21/2009 08:02 alan@bay 04:TestTagFailure: Transceiver 04 is experiencing noise. It will be addressed during a site visit today. 08/20/2009 07:36 alan@bay 04:TestTagFailure: This transceiver is experiencing noise. We are continuing to track the source down. This transceiver is reading PIT tags well. 08/19/2009 09:03 Darren A site GMC was performed today 8-19-09. All transceivers were checked and adjusted for tuning, noise, and detectabiity. Transceiver 01 was slightly out of tune and was easily restored by retuning. The noise and antenna 04 is 2-3% signal still the current was verified with a scope to be 5.7A and the capacitor bank area was checked for moisture or corrosion, neither existed. The transceiver was retuned to the best of its ability. No other problems were discovered during this visit. 08/18/2009 07:50 alan@bay 01:TestTagFailure: This alarm will be investigated during the nextsite visit. This transceiver is reading PIT tags well. 08/17/2009 11:02 alan@bay 01:TestTagFailure: This alarm will be investigated during the next site visit. This transceiver is reading PIT tags well. 08/16/2009 10:46 alan@bay 01:TestTagFailure: Noted 08/15/2009 10:09 alan@bay 01:TestTagFailure,04:TestTagFailure: These transceivers appear to have drifted slightly out of tune. They will be investigated during the next site visit. These transceivers are reading PIT tags well. 08/13/2009 07:41 alan@bay 01:TestTagFailure: This transceiver appears to have drifted slightly out of tune. It will be investigated during the next site visit. This transceiver is reading PIT tags well. 08/12/2009 07:47 alan@bay 01:TestTagFailure: This transceiver appears to have drifted slightly out of tune. It will be investigated during the next site visit. This transceiver is reading PIT tags well. 08/12/2009 07:33 Alan Manually pushed BO109224.B1 to PTAGIS via PCA. MiniMon was bounced on PC1 in order to improve automated uploading. BO109224.C1 was manually uploaded, BO109224.H2 was submitted to fill the gap during PC1's downtime. 08/11/2009 16:36 Alan Manually uploaded delinquent files. 08/11/2009 07:39 alan@bay 01:TestTagFailure: A PIT tag was in the field when the timer tag was fired. 08/10/2009 07:39 alan@bay 01:TestTagFailure: No apparent reason for this alarm. PTAGIS Field Operations will continue to monitor. 08/09/2009 09:01 darren@b 01:TestTagFailure: It appears that the transceiver has slightly drifted out of tune. It will be addressed during the next site visit. 08/08/2009 08:38 darren@b 01:TestTagFailure,04:TestTagFailure,17:TestTagFailure: These alarms will be investigated during the next site visit. 08/04/2009 07:19 darren@b 04:TestTagFailure: There was no direct cause for this failure. It appears that the noise elevated slightly last night and the timer tag did not fire. We are currently investigating the source of the noise. The efficiencies are still in the high 90% range. 08/03/2009 13:43 Darren A site GMC was performed today 8-3-09. All transceivers were checked for tuning, noise and detectability. They were adjusted as necessary for optimum efficiency. I checked the noise on transceiver 04, and even replaced it with another FS1001B transceiver but found that the noise was still present so the original transceiver was reinstalled. I checked the cap bank area but it did not contain any moisture and the connections appeared to be fine. The efficiencies for the transceiver have had occasional drops but over the last two weeks it has been 97% or better. We will continue to monitor this transceiver and adjust or replace as necessary. No other problems were found. 08/03/2009 07:53 alan@bay 04:TestTagFailure: This will be investigated today during a site visit. 07/30/2009 09:54 troy@bay 04:TestTagFailure: Noted 07/29/2009 08:21 troy@bay 04:TestTagFailure: Noted 07/25/2009 09:48 Darren All sites were checked for loading and efficiencies BO1 had not loaded but when I checked via PCA the files had been sent and are in the received but not loaded file. No other problems were found. 07/22/2009 13:10 Darren A site GMC was performed today. All transceivers were checked and adjusted as necessary for tuning, noise, and detectability. There was a little noise (0-3%) on transceiver 04. I tried to replace the transceiver as a test but the "new" transceiver would not tune to the antenna, the noise was very high, whne using the tuning procedure. I replaced the original transceiver and retuned. The timer tag voltage is normal for a 100% read and at a 1/4 turn on the potentiometer I was still getting 40-50% hit rates so the transceiver was left in place. We will monitor for detection efficiencies and make any necessary adjustments. No other problems were found. 07/20/2009 08:20 Alan Manually pushed BO109201.B1 to PTAGIS via PCA. 07/19/2009 11:38 scottl Coil 04 is low in efficiencies, will monitor and respond when necessary 07/16/2009 13:53 scottl Performed site GMC, all transceivers were retuned and calibrated as necessary. Transceiver 04 has slightly elevated noise levels and could not be tuned out. Reduced some of the noise by adjusting the exciter voltage pot but noise levels are not as low as desired. As a test, removed the unit from UPS power but no effect. Turned on noise report for 04, will monitor. Could be the transceiver has an issue. 07/11/2009 09:36 troy@bay 04:TestTagFailure: 04:TestTagFailure: This will be addressed on the next site visit. 07/11/2009 09:35 troy@bay 04:TestTagFailure: This will be addressed on the next site visit. 07/09/2009 11:29 Troy A site GMC was performed 07/09/2009. All transceivers were checked for tune and adjustments made where needed. PC1 and PC2 were set to within one second of atomic time and of each other. The 'temp' directory was emptied on both PC1 and PC2. No problems to report. 07/03/2009 08:34 troy@bay 04:TestTagFailure: Noted 06/30/2009 13:44 Darren A site GMC was performed today 6-30-09. All transceivers were checked for tuning, noise, and detectability. Antenna 0A was showing sings of noise but after adjusting the power supply and retuning the noise went away and the tag detectability improved. No problems were discovered during this visit. 06/29/2009 08:32 scottl@b 04:TestTagFailure: TT did not fire use to excessive noise that has since gone away. 06/25/2009 08:21 alan@bay 04:TestTagFailure: This transceiver may have drifted slightly out of tune, but is reading PIT tags well. This will be investigated during the next site visit. 06/22/2009 10:44 Darren A site GMC was performed today 6-22-09. All transceivers were checked for tuning, noise and detectability. No problems were discovered during this visit. 06/19/2009 08:10 darren@b 01:LowExcCurrent: No direct cause for this one event of an alarm. PSMFC will monitor and investigate during the next site GMC. 06/17/2009 11:39 Alan A GMC was performed 6/17/2009. All transceivers were checked and tuned as necessary. All outstanding files on PC2 were archived. The clocks on both PCs were set to within one second of atomic time. No problems found. 06/15/2009 09:57 darren@b 04:LowExcCurrent: This alarm has been addressed via PCA. I lowered the alarm threshold to 5200mA to avoid large files. 06/11/2009 13:42 Darren A site GMC was performed today 6-11-09. The UPS that was associated with antenna 03 was replaced due to some noise that it was introducing into the system. All transceivers were checked for tuning, noise, and detectability.The system clock on PC2 was 56 seconds behind PC1 so it was adjusted to be within 1 second of PC1 and 3 seconds of atomic time. No other problems were discovered during this visit. 06/03/2009 11:58 Darren A site GMC was performed today 6-3-09. All transceivers were checked for tuning, noise, and detectability, they were adjusted for maximum detection ability when necessary. The Fiber to Ethernet converter was replaced with a new one from Black Box. The communications appears to be a little better and a test upload proved to be very quick. No problems or adjustements were necessary during this visit. 06/01/2009 08:20 troy@bay 01:TestTagFailure,04:LowExcCurrent: These alarm will be addressed on the next site visit. 05/31/2009 09:38 alan@bay 04:LowExcCurrent: This will be investigated during the next site visit. 05/28/2009 08:31 alan@bay 01:TestTagFailure: This was addressed yesterday during a site visit. 05/27/2009 11:50 Darren A site GMC was performed today 5-27-09. All transceivers were checked for tuning, noise and detectability. Slot antennas 01 and 03 were out of tune and were optimized for maximum reading efficiencies. No problems were discovered during this visit. 05/25/2009 11:04 scottl@b 01:TestTagFailure,04:TestTagFailure: Noted. 05/21/2009 08:07 Scott_Li Manually pushed the .B1 file and removed the check from "Save Acknowledgment File" No .zip was found. 05/20/2009 13:09 Darren A site GMC was performed today 5-20-09. All transceivers were checked for tuning, noise, and detectability. No problems were discovered during this visit. 05/16/2009 08:43 Darren All outstanding files were submitted manually via PCA. 05/14/2009 12:41 Alan A GMC was performed 5/14/2009. All transceivers were checked and tuned as necessary. All outstanding files on PC2 were archived. The clocks on both PCs were set to within one second of atomic time. No problems found. 05/13/2009 09:01 Don_Warf Jon Thomas reports that there will be a comms outage at BO1 and BO2 today from 8:00 to 1:00. The fiber converts in the PH2 will lose power due to a electrical upgrade. 05/08/2009 09:05 Troy PCA'ed in and pushed the delinquent file. 05/07/2009 10:44 Darren A site GMC was performed today 5-7-09. All transceivers were checked for tuning, noise, and detectability. They were adjusted as necessary. No problems were discovered during this visit. 05/04/2009 14:56 Darren With the assistance of Jon rerecich I was able to restore the communications to the platform. The outstanding files were uploaded to PTAGIS. The power was cycled on the network interface cabinet and allowed the fiber/ethernet converter to be restored. 04/25/2009 10:55 alan@bay 04:TestTagFailure: This transceiver experienced noise for a short duration. PTAGIS Field Operations will continue to monitor. 04/23/2009 09:32 Troy A site GMC was performed 04/23/2009. All transceivers were checked for tune and adjustments made where needed. No problems to report. 04/23/2009 08:54 darren@b 01:TestTagFailure: Site was retuned during a site GMC. 04/23/2009 08:43 Darren Manually pushed the 09113.B1 files to PTAGIS. 04/16/2009 10:02 scottl Performed site GMC, all transcievers were tuned and calibrated as necessary. No problems to report. 04/14/2009 17:09 Alan Data collection on PC1 was apparently terminated at ~7:11 PST 4-13-2009 according to BO109103.C1.TMP. The reason is unknown (possibly an OS issue?). Files BO109103.G2 and BO109103.H9 from PC2 were tailored to fit the gap and uploaded to PTAGIS via PCA. 04/10/2009 09:03 alan@bay 0A:LowExcCurrent: This alarm was generated by PTAGIS Field Operations personnel during a site visit. 04/09/2009 11:17 Troy A site GMC was performed 04/09/2009. All transceivers were checked for tune and adjustments made where needed. The clocks on PC1 and PC2 were set to within 1 second of each other and atomic time. PC1 was then re-booted. The gap file on PC2 and the outstanding files on PC1 were manually pushed to PTAGIS. No other problems to report. 04/09/2009 08:30 alan@bay 01:TestTagFailure: This transceiver appears to have drifted slightly out of tune. It will be investigated during a site visit today. 04/08/2009 11:54 alan@bay 01:TestTagFailure: This transceiver appears to have drifted slightly out of tune. It will be investigated during a site visit tomorrow. 04/03/2009 11:26 Troy A site GMC was performed 04/03/2009. All transceivers were checked for tune and adjustments made where needed. The fiber to copper converter was replaced in the pit tag room. The old one will be returned to Kennewick. 04/03/2009 08:36 darren@b 01:TestTagFailure: This system will be addressed during a site GMC today. 03/31/2009 14:56 Alan Fileas BO109085.D2 and BO109085.E9 were submitted from PC2 to help fill the data gap on 3-26-2009. No further data exist. 03/30/2009 08:32 Troy Manually pushed the 2 delinquent files 03/26/2009 08:34 Don_Warf BO1 is down due to a scheduled COE power outage. It should be back online within 4 hours. 03/20/2009 08:49 Don_Warf Hello Don and Scott, Right now, it's looking like we'll be taking down the Bradford Island PIT Tag Bldg for around 1/2 day next Thursday (3/26). This is due to the new transformer for BIVC and the BPA Towers being brought on line that day. Thanks, --Jon 03/18/2009 08:56 Don_Warf Manually pushed files. 03/14/2009 08:42 troy Had trouble PCA'ing into site, finally got in and first attempt to push BO109073.B1 stalled in the process. Got out of PCA, went back in and cancled the upload process. Tried again and the file went. 03/09/2009 08:37 troy@bay 01:TestTagFailure: This alarm will be investigated on the next site visit. 03/05/2009 08:21 Troy A site GMC was performed 03/02/2009. All transceivers were checked for tune and adjustments made where needed. 03/04/2009 08:16 Darren This message was sent to PSMFC regarding the PITtag building at Bradford Island. The Bradford Island PIT building was de-energized per the message below. It went out at 8:06 pm on March 3 and should be powered up by this afternoon. Jon Rerecich Fisheries Biologist USACE Bonneville Lock and Dam 541-374-7984 jonathan.g.rerecich@usace.army.mil -----Original Message----- From: Smith, David B NWP Sent: Tuesday, March 03, 2009 8:29 PM To: Hausmann, Ben J NWP; Mackey, Tammy M NWP; Rerecich, Jonathan G NWP; Welch, Kasey M NWP Cc: Thomas, Jon B NWP; Witham, Robert W NWP; Fauth, Jeffrey D NWP Subject: BI PIT In preparation of transferring the main dam power over - bus 1 supply - we have de-energized the InterTie Line #1 and along with it the Pit Tag Building at the 'Y'. Dave 03/04/2009 08:16 Scott_Li The site has not loaded data files since the 162.f. Cannot remote into either PC1 or PC2. Will call site personnel for assistance. If they are not available or will not be able to assist in a timely manner, other arrangements will be made in order to correct the situation. 03/03/2009 08:22 darren@b 18:LowExcCurrent: Alarm generated by PSMFC personnel during a site GMC. 02/28/2009 07:48 darren@b 04:TestTagFailure: This alarm will be addressed during Mondays site GMC. 02/26/2009 07:39 darren@b 04:TestTagFailure: This alarm will be investigated during the next site visit. 02/25/2009 14:50 darren@b 04:TestTagFailure: Alarm will be investigated during the next site visit. 02/25/2009 14:50 troy@bay 04:TestTagFailure: 04:TestTagFailure: Noted 02/25/2009 14:50 troy@bay 04:TestTagFailure: Noted 02/25/2009 14:50 troy@bay 04:TestTagFailure: Noted 02/25/2009 14:50 troy@bay 04:TestTagFailure: NOTED 02/25/2009 09:20 Darren The file open and close times jumped ahead by 1 hour but the timestamps and the clock time are correct. I closed the file and stopped and started Minimon. We will check to see that the next file opens at 12:00. We are unsure what caused this jump at Midnight but we will monitor for future failures. 02/24/2009 07:32 Troy Manually pushed BO109055.B1 to PTAGIS. 02/15/2009 11:45 Alan For unknown reasons, we lost network connectivity to BO1 at ~8:00 2/14/2009. Site personnel cycled the power to the network rack at 11:35 2/15/2009 and communications were restored. I then manually pushed BO109045.C1 through BO109046.C1 to PTAGIS via PCA. 02/13/2009 07:37 Alan Manually pushed BO109044.B1 to PTAGIS via PCA. 02/07/2009 08:38 Troy Manually pushed BO109038.A1 and .B1 02/06/2009 13:23 Scott_Li Manually pushed data files, cleared the contents of the temp directory at BO1, no zip files were present. 02/04/2009 15:51 Troy pushed BO109035.E1 to ptagis. 02/01/2009 13:24 scottl Manually pushed data files, no other problems to report with site. Will monitor for reoccurrences 01/18/2009 08:10 Troy Checked for a .zip file but did not find one. Manually pushed BO109018.B1 to PTAGIS. 01/17/2009 09:46 Troy Pushed the 2 outstanding files to ptagis. 01/14/2009 10:56 Dave I updated the Current BO1 record in obs_site_dates with a start date of 1/9/09, and changed the status to Active. 01/14/2009 09:41 Darren This is a post event entry. The site was watered back up on Friday 1-9- 09. There are no gaps in the data due to the fact that the site has been collecting and submitting data to PTAGIS. 01/12/2009 08:51 Darren PSMFC was alerted to a file upload issue this morning and with the help of COE personnel were able to re-establish the network communications with both PC's on the platform. It appears that the power on the fiber to copper converter for the network needed to have th e power cycled. During this process there did not seem to be any indication that there was a failed connection. The outstanding files were pushed to PTAGIS via PCA. We will monitor this connection and may need to possibly remove the power supply for the "phone" converter inside the network interface panel in the PITtag room. 01/05/2009 07:25 darren@b 01:TestTagFailure,02:LowExcCurrent,02:TestTagFailure,03:LowExcCurrent,03:T estTagFailure,04:TestTagFailure,17:TestTagFailure,1C:LowExcCurrent,1E:Test TagFailure,20:TestTagFailure: Site Down Clearing TASS. 01/01/2009 00:00 PTOC_Bot Annual log file initiation for BO1 ####End of Event Log for BO1###