EVENT LOG FOR SITE BO4 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/29/2010 07:51 Troy Manually pushed the delinquent file. 12/12/2010 06:53 Troy@bay 04:LowExcCurrent: A GMC is scheduled for tomorrow and this alarm will be addressed then. 12/11/2010 23:43 Dave I retrieved the truncated BO410341.H1 file from BO4-PC1. I appended a CLOSED record and submitted the completed file to PTAGIS. There is a ten-minute gap between the CLOSE record of this file and the OPEN record of the subsequent BO410342.A1 file. This gap is inconsequential as the ladder is dewatered for the winter. 12/11/2010 06:28 Troy@bay 04:LowExcCurrent: This alarm will be addressed on the next site visit. 12/07/2010 18:28 Dave Per the facility operators, the Washington Shore and Cascades Island fish ladders went to orifice flow on 01 December, and were dewatered to tailwater on 03 December. Per Darren's 12/06/10 event log entry for BO2, both ladders will remain Out of Service until the last week of February 2011. 12/07/2010 07:20 Troy@bay 04:LowExcCurrent: This alarm will be addressed on the next site visit. 12/06/2010 07:47 Troy@bay 01:TestTagFailure,02:LowExcCurrent,03:LowExcCurrent,04:LowExcCurrent: These alarms will be addressed on the next site visit. 11/28/2010 09:06 darren@b 01:TestTagFailure: This system has drifted slightly in tune and will be addressed during the next site visit. 11/27/2010 09:15 darren@b 01:TestTagFailure: This system has drifted slightly otu of tune and will be addressed during the next site visit. 11/26/2010 08:45 darren@b 01:TestTagFailure: This system has drifted slightly out of tune. It will be addressed during the next site visit. 11/25/2010 07:50 darren@b 01:TestTagFailure: This systems has drifted slightly out of tune. It is detecting PITtags with a very high efficiency. It will be addressed during the next site visit. 11/24/2010 07:02 darren@b 01:TestTagFailure: This system has drifted slightly out of tune. It will be addressed during the next site visit. It is detecting PIT tags with very high efficiency. 11/22/2010 08:19 darren@b 01:TestTagFailure: This system has drifted out of tune but is detecting PITtags ata very high efficiency. 11/21/2010 10:45 Troy@bay 01:TestTagFailure: Transceiver appears to have drifted slightly in tune, will be addressed on next site visit. 11/20/2010 08:42 Troy@bay 01:TestTagFailure,04:TestTagFailure: This system has drifted slightly out of tune. It is detecting PIT tags at a very high efficiency. It will be addressed during the next site visit. 11/18/2010 07:25 alan@bay 01:TestTagFailure: This system has drifted slightly out of tune. It is detecting PIT tags at a very high efficiency. It will be addressed during the next site visit. 11/17/2010 07:24 darren@b 01:TestTagFailure: This system has drifted slightly out of tune. It is detecting PITtags at avery high efficiency. It will be addressed during the next site visit. 11/16/2010 07:45 Troy@bay 01:TestTagFailure: Noted 11/14/2010 08:01 darren@b 01:TestTagFailure: This system will be addressed during the next site visit. 11/13/2010 08:17 darren@b 01:TestTagFailure: This system has drifted slightly in tune. It will be addressed during the next site visit. 11/08/2010 07:28 darren@b 01:TestTagFailure: No direct casue for this alarm. IT will be investigated during this weeks site visit. 10/29/2010 06:07 scottl@b 01:TestTagFailure: Noted 10/28/2010 06:52 darren@b 01:TestTagFailure: Alarm was addressed yesterday during a site GMC. 10/27/2010 12:23 scottl All 4 transceivers were very much out of tune. Retuned transceivers but unit 02,03,04 were extremely noisy and could not be tuned out. Will do more investigating in the AM. Although there is an exceptional amount of noise, the transceivers hit rate is not effected as much as one might think. Fish detection should still be at a very high detection rate. 10/27/2010 06:30 darren@b 01:TestTagFailure: These failures are due to tuning of the system. PSMFC personnel will be on site today to resolve this issue. 10/14/2010 06:38 Troy@bay 01:Overrun: It is unclear what may have caused these overruns. They all happened in a brief period of time. ~01-4 10/13/10 04:23:11 ALARM PROBLEM: Overrun ~01-4 10/13/10 04:23:14 ALARM PROBLEM: Overrun ~01-4 10/13/10 04:23:16 ALARM PROBLEM: Overrun ~01-4 10/13/10 04:23:17 ALARM PROBLEM: Overrun ~01-4 10/13/10 04:23:23 ALARM PROBLEM: Overrun ~01-4 10/13/10 04:23:27 ALARM PROBLEM: Overrun So it may have been an environmental problem. PSMFC will continue to monitor. This transceiver is reading fish and TT at a high efficiency. 10/06/2010 07:50 scottl@b 04:TestTagFailure: Noted 09/23/2010 07:53 alan@bay 04:TestTagFailure: There was a PIT-tagged fish in the field causing a tag collision with the timer tag. PTAGIS Field Operations will continue to monitor. 09/23/2010 07:52 alan@bay 01:TestTagFailure: There was a PIT-tagged fish in the vicinity possibly causing a tag collision with the timer tag. PTAGIS Field Operations will continue to monitor. 09/15/2010 07:32 Troy@bay 04:TestTagFailure: No obvious cause for this missed TT. PSMFC will continue to monitor. 09/08/2010 08:18 darren@b 01:TestTagFailure: Alarm was addressed yesterday during the site GMC. 09/07/2010 11:54 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 undocumented problems found. 09/06/2010 11:21 scottl@b 01:Overrun,01:TestTagFailure: Noted, will correct on the next GMC 09/03/2010 10:02 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. 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:14 darren@b 01:TestTagFailure,02:TestTagFailure: These systems have drifted slightly in tune. They will be addressed during the next site GMC. They are detecting PITtags at a very high efficiency. 08/23/2010 08:50 darren@b 03:TestTagFailure: The system has drifted slightly out of tune. It will be addressed during the next site GMC. 08/22/2010 09:35 alan@bay 01:TestTagFailure: This will be investigated during the next site visit. 08/21/2010 09:24 alan@bay 01:TestTagFailure: This transceiver might a bit out of tune, but is reading PIT tags well. PTAGIS Field Operations will continue to monitor. 08/19/2010 07:59 Alan The transceivers were tuned 8-18-2010, no problems found. 08/16/2010 09:30 alan@bay 02:HighTemp,03:HighTemp: Alarms common this time of year. 08/06/2010 08:32 darren@b 02:LowExcCurrent: Alarms were generated by PSMFC personnel during a site GMC. 08/05/2010 13:01 Darren A site GMC was performed today (8-5-10). All transceivers were checked and adjusted for tuning, noise, and detectability. No problems were discovered during this visit. 08/05/2010 08:26 Troy@bay 01:TestTagFailure: This will be investigated today during a scheduled GMC. 07/24/2010 09:08 alan@bay 04:TestTagFailure: No apparent reason for this one-time alarm. PTAGIS Field Operations will continue to monitor. 07/24/2010 09:07 alan@bay 01:TestTagFailure: A PIT tag was in the field when the timer tag was fired. 07/22/2010 13:06 Darren A new phone with speakerphone capabilities was installed. 07/22/2010 13:04 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 and the clocks are within 20 seconds of each other and atomic time. No problems were discovered during this visit. 07/19/2010 08:34 alan@bay 04:TestTagFailure: No apparent reason for this one-time alarm. PTAGIS Field Operations will continue to monitor. 07/18/2010 10:38 scottl@b 04:TestTagFailure: Noted 07/16/2010 08:11 scottl@b 01:TestTagFailure: Noted 07/10/2010 08:44 darren@b 04:TestTagFailure: No direct causde for this alarm. We will investigate during the next site GMC. 07/09/2010 08:39 darren@b 03:HighTemp: Alarms not uncommon this time of year. 07/09/2010 08:38 darren@b 04:TestTagFailure: No direct cause for this failure. The system may have drifted slightly in tune and will be addressed during the next site visit. 07/07/2010 13:12 Alan A GMC was performed 7-7-2010. All transceivers were checked and tuned as necessary. All of the transceivers have quiet signal levels. 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. 07/04/2010 09:46 alan@bay 02:TestTagFailure: No apparent reason for this one-time alarm. PTAGIS Field Operations will continue to monitor. 07/01/2010 12:48 Darren A site GMC was performed today (7-1-10). The transceivers were adjsuted for tuning, noise, and detectability. Although the noise levels on BO3-01 have increased back to 100% there is still a little noise rolling through all 4 transceivers with 03 being the worst. Efficiencies have been high for this site so we will continue to monitor for the noise and adjust as necessary. The files on PC2 were archived. No problems were discovered during this visit. 06/26/2010 07:57 Troy@bay 04:TestTagFailure: Noted 06/23/2010 12:57 Darren The GMC did not uncover anything new, but the noise although very minimal is still rolling through all 4 transceivers with 03 being the worst case at anywhere from 3-9%. The timer tags are firing and the efficiencies are high. 06/23/2010 12:55 Darren A site GMC was performed today (6-23-10). All transceivers were checked for tuning, noise, and detectability, adjustments were made when necessary. The files on PC2 were archived. No problems were discovered during this visit. 06/21/2010 14:20 troy@bay 01:TestTagFailure: Noted 06/18/2010 08:07 scottl@b 04:TestTagFailure: Noted 06/17/2010 13:54 Troy A site GMC was performed 06/17/2010. All transceivers were checked for tune and adjustments made where needed. No problems to report. 06/13/2010 08:33 darren@b 04:TestTagFailure: No real cause for this failure. The system is detecting PITtags at a very high efficiency rate 06/12/2010 08:46 darren@b 04:TestTagFailure: there is no direct cause for this alarm. It will be investigated during the next site visit. 06/08/2010 12:15 Alan A GMC was performed 6-8-2010. All transceivers were checked and tuned as necessary. Transceiver 01 is quiet, transceivers 02 & 04 are showing slight noise and transceiver 03 is showing noise spiking up to 4%. 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. 06/08/2010 08:56 troy@bay 01:TestTagFailure: Noted, a GMC is scheduled for today and this will be investigated then. 06/05/2010 08:49 alan@bay 01:TestTagFailure: This system will be investigated during a site visit next week. 06/05/2010 08:38 Alan The transceivers were tuned ~1300 PST 6-4-2010. All transceivers were experiencing noise from low single digits into the high teens. At that time BO3-01 was tuned and showing noise into the 40's. The exciter reports show that by 1800 PST 6-4-2010 the noise had cleared up at BO4, but the noise did not increase at BO3-01 suggesting another source of noise. PTAGIS Field Operations will be further investigating this on Monday. 05/26/2010 13:06 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/25/2010 08:22 troy@bay 01:TestTagFailure: Noted 05/21/2010 08:33 darren@b 01:TestTagFailure: There was no direct cause for the failure. This site will be visited during a GMC today. 05/18/2010 08:16 Scott_Li Manually pushed the delinquent data files, restarted Minimon. The reason for the delay was that Minimon was not restarted after reconfigured. 05/17/2010 12:55 scottl On site to replace all associated components relating to the recent problems with 01 communications on PC1. The problems previously reported were only observed on PC1, PC2 has never had this problem. So reasoning says that the problem is not at the transceiver but rather with components down stream of the modem nest. Replaced Rocket port card, Modem in nest and Y cable. Will monitor for re occurring problem. Manually sent files from PC2 and returned PC1 to the primary role. 05/14/2010 17:57 Dave There is a persistent problem with PC1 that occasionally results in the loss of data from transceiver/antenna 01. The data are correctly and completely recorded to PC2. At noon today, Scott switched our BO4 upload source from PC1 to PC2. I subsequently reviewed the PC2 data set for the last week (since midnight May 7) and found one instance on May 11 and five instances between 4:15 and 6:00 AM this morning where PC2 recorded previously-unreported detections at antenna 01. I packaged these new detections in dedicated data files and submitted the data to PTAGIS. The issue with BO4-PC1 will be addressed next week. 05/14/2010 09:12 Darren During the investigation into the invalid coil i.d. PC1 screen locked up and the system again was in need of a reboot. While monitoring PC2 the system was rebooted and no PITtag detections were logged during the re- boot. 05/14/2010 08:06 Darren I had to PCA into PC1 and stop Minimon and reboot the computer. There were communication problems with transceiver 01. I believe the communication problem began around 04:22 this morning. I was able to verify with PC2 that there were no interrogations missed during the reboot. 05/13/2010 15:45 Dave I created and uploaded BO410131.TOO, a compilation of detections from xceiver "01" recorded to BO4-PC2 between midnight and 1500h on May 11 that were not recorded to (or reported from) BO4-PC1. 05/13/2010 13:13 scottl Replaced RP expansion chassis due to previous and recent errors relating to unit 01. No data whatsoever was lost during this repair. If the Unknown BPA Protocol errors return, Will replace modem in the transceiver. Transceiver 03 was a bit noisy, tuned transceiver but could not completely rid the unit of all noise. Levels at 1-3 % Timer tag hit rate at 100%, detection efficiencies good. Worked with Dave M. about back filling the data that was not collected on PC1 for transceiver 01. Dave to retrieve data from PC2 and correct any issues. No problems to report. 05/11/2010 16:35 Darren It was noticed that there was some communications issues with transceiver 01 since yesterday afternoon. PSMFC will be onsite on Thursday for site GMC's and will attempt to find and submit all necessary data at that time. I was able to PCA into the site and tried to stop and restart Minimon but this did not solve the "unknown BPA protocol" that was being witnessed on PC1. I then rebooted the PC and the communications was re-established. There are two small file gaps but there was not PIttag activity observed on PC2 during this period of time. 05/03/2010 13:07 Scott While checking the noise reports for the 4 transceivers, noticed that the transmit line for PC1 was not responding. After further troubleshooting, found that port 12 on the RP interface was the culprit. Switched 01 to port 4, reconfigured Minimon to reflect this change, stopped and started minimon, no other problems to report, noise levels on the ladder antennas is very low. 04/27/2010 11:09 Scott_Li Turned OFF noise reporting for all transceivers that were involved in monitoring noise levels during the Sea Lion Electrical Deterrence System (SLEDS) evaluation. The SLEDS system is being removed at this time, the study has been discontinued. 04/26/2010 13:06 scottl Tried to tuned the noise out of all 4 transceivers with little to no positive effect. The noise issues of the past are still present, detection efficiencies for the antenna group are extremely good. 04/21/2010 08:19 darren@b 02:TestTagFailure: This alarm will be investigated during the next site visit. The system is detecting PITtags at a high efficiency and this may have been the result of a tag in close proximity of the field. 04/17/2010 12:03 Troy@bay 04:TestTagFailure: This will be investigated on Monday during a scheduled site visit. 04/07/2010 14:33 Darren A site GMC was performed today (4-7-10). The transceivers are still experiencing increased noise. I was able to meet up with U of I personnle and re-test the HDX and Radio Tracking equipment in the same area as the antennas and neither of these systems has a direct effect on our detection systems. PSMFC is going to be putting together some noise data and using this in conjunction with COE site assistance to try and find the source of this noise. The timer tags were checked and appear to firing at 100%. No other problems were discovered during this visit. 04/03/2010 09:37 alan@bay 01:TestTagFailure: This issue is being investigated. This TASS alarm was for 2 TT events, the last one occurring at 2010/04/02 15:25:55. 04/02/2010 13:58 Darren A site GMC was performed today(4-2-10). When I arrived I found that all of the transceivers had elevated noise levels with 01 being the worst case, up to 26% noise, I checked the timer tag report and found that the noise jumped from 0% to 43% at 19:00 hrs on 4-1-10. I tried to tune out the noise but had no success. I will investigate the possibler surroundings to see if there is an outside source. PSMFC is currently working with Jon Thomas to try and get some ideas on what the possibilities of the source might be. The lower ladder (BO3) is extremely quiet including 01 which is at 30-40% and reading some timer tags. 04/02/2010 08:36 troy@bay 01:TestTagFailure: This will be addressed today during a site visit. 03/20/2010 08:08 darren@b 01:TestTagFailure: There does not appear to be any direct cause for this alarm. We will investigated during Mondays visit. 03/19/2010 08:07 darren@b 01:TestTagFailure: This alarm will be addressed during next weeks site GMC. It may have drifted slightly in tune, but has been recording PITtag's with high efficiency. 03/17/2010 08:21 darren@b 03:TestTagFailure: This system was optimized by psmfc personnel yesterday during a site visit. 03/16/2010 08:48 alan@bay 03:TestTagFailure: This will be investigated today during a site visit. 03/15/2010 11:16 Alan The antennas were tuned 3/15/2010. Transceivers 01, 02 and 04 are showing signal levels of 0% - 1%. Transceiver 03 is showing signal levels of 2% -6%. For comparison, BO3-01 is showing signal levels of ~30%. The hit rate on BO3-01 was set to 100% for it's current operating state to aid in tracking down noise correlations. 03/15/2010 08:20 darren@b 01:TestTagFailure: This system will be investigated during the next site visit. 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/06/2010 08:06 Troy@bay 01:TestTagFailure: The tune on this transceiver appears to have drifted. It is still reading pit tagged fish and will be addressed on the next site visit. 03/05/2010 07:40 troy@bay 01:TestTagFailure: Noted 02/22/2010 11:08 scottl@b 04:TestTagFailure: Noted, system needs slight tuning 02/22/2010 07:15 Scott_Li Xcvrs 03,04 timer tags are stuttering, Will correct on the next site visit. 02/16/2010 07:56 Scott_Li Replace modem IP's in Hobbit for JCJ with the new addresses after the dish was realigned. Commented out the modem addresses for LMJ,PRO,JDJ and BO4. Scott Livingston PSMFC-PTAGIS 7103 W. Clearwater Ave. Suite H. Kennewick, Wa. 99336 Office: 509.735.2773 x.2 Mobile: 509.539.0894 Scottl@psmfc.org 02/08/2010 07:34 troy@bay 01:TestTagFailure: This alarm will be addressed on the next site visit. 01/20/2010 07:56 alan@bay 01:TestTagFailure: No apparent reason for this alarm. PTAGIS Field Operations will continue to monitor. 01/19/2010 12:17 Darren A site GMC was performed today (1-19-10). All transceivers were checked for tuning, noise, and detectability. The transceivers on antennas 0B and 12 (BO3) were out of tune and were adjusted for optimization. No other problems were discovered during this visit. 01/01/2010 00:00 PTOC_Bot Annual log file initiation for BO4 #### End of Event Log for BO4 ###