EVENT LOG FOR SITE RZF 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/15/2010 08:14 alan@bay 02:TestTagFailure: Noted. 12/14/2010 08:10 alan@bay 03:TestTagFailure: Noted 12/14/2010 08:09 Darren A site check was performed yesterday and it was found that the antennas are currently being overrun with water. I informed Mark Johnstone (YN Fisheries) who was going to contact Scott Kline (BOR) to see if the level could be adjusted. There is currently work being performed on the West drum gate and there is a significant amount of water traveling down river. The signal levels on all three transceivers are between 60-90%. 12/06/2010 07:51 Troy@bay 01:Overrun,01:TestTagFailure,02:Overrun,02:TestTagFailure,03:Overrun,03:Te stTagFailure: These alarms will be addressed on the next site visit. 12/01/2010 10:09 scottl@b 01:Overrun,01:TestTagFailure,02:Overrun,02:TestTagFailure,03:Overrun: Errors are generated due to the system is out of tune. 11/25/2010 08:19 darren@b 02:TestTagFailure: The noise on the system has dropped which was causing the tag failures. 11/24/2010 07:13 darren@b 02:TestTagFailure: The noise floor has risen which may be sue to the tune drifting. The system will be investigated during the next site visit. 11/16/2010 10:53 Don_Warf Site is currently unreachable. Darren will be there tomorrow. 10/25/2010 12:16 Darren PSMFC was on site today to perform a GMC as well as scope the conduit run for the new equipment. I met with Corkie and Howdy Forbes (BOR). The current project is entering the scaffolding phase, the scaffold construction is begining and may be completed as soon as Sunday. No problems were found during this visit. 10/23/2010 09:41 alan@bay 02:TestTagFailure: This will be addressed during the next site visit. 10/21/2010 06:45 alan@bay 02:TestTagFailure: This transceiver has drifted slightly out of tune. This will be addressed during the next site visit. 10/19/2010 06:42 alan@bay 02:TestTagFailure: This will be addressed during the next site visit. 10/12/2010 11:53 Darren A site GMC was performed today (10-12-10). All transceivers were checked for tuning, noise, and detectability. No problems were discovered during this visit. 10/07/2010 08:26 Alan Examination of both PCs showed a TMP file with some data. RZF10279.C9 was submitted to help fill the gap from yesterday's power outage. No further data exist to fill the remaining gap. 10/06/2010 13:20 Scott_Li The entire Roza site is without power due to work being done by the PUD. The outage is expected to last around 6 hrs starting at 0900 this morning. Will monitor for when power is restored to ensure all systems come back online. 09/03/2010 10:03 darren@b 02:HighTemp: Alarm not uncommon this time of year. 09/01/2010 08:40 alan@bay 03:BadExcFreq: This transceiver appears to be in tune and is reading timer tags well. This will be addressed during the next site visit. 08/29/2010 07:33 Troy@bay 02:HighTemp,03:BadExcFreq: BadExcFreq has been seen on this transceiver in the past. PSMFC will investigate further on the next site visit. The high temp alarms are not uncommon for this time of year. 08/26/2010 08:42 darren@b 01:HighTemp,02:HighTemp,03:HighTemp: Alarms not uncommon this time of year. 08/24/2010 16:32 Alan Remotely added the Biomark 23 MM tag to the country code list in both PC1 and PC2 registries. 08/24/2010 08:36 darren@b 02:HighTemp: Alarm not uncommon this time of year. 08/21/2010 09:28 alan@bay 01:HighTemp,02:HighTemp,03:BadOscFreq,03:HighTemp: Noted. 08/20/2010 08:36 alan@bay 01:HighTemp,02:HighTemp: Noted 08/19/2010 12:42 scottl Performed site GMC, all transcieversx were retuned and calibrated as necessary, no problems to report. 08/19/2010 08:26 alan@bay 01:HighTemp,02:HighTemp,03:HighTemp: Alarms not uncommon this time of year. 08/17/2010 09:02 darren@b 01:HighTemp,02:HighTemp,03:HighTemp: Alarms not uncommon this time of year. 08/16/2010 09:32 alan@bay 01:HighTemp,02:HighTemp,03:BadExcFreq,03:HighTemp: Alarms common this time of year. 08/15/2010 11:31 scottl@b 01:HighTemp,02:HighTemp,02:TestTagFailure,03:HighTemp: Noted, typical for this time of year 08/12/2010 09:19 Troy@bay 01:HighTemp,02:HighTemp,03:HighTemp: These alarms are not uncommon this time of year. 08/07/2010 08:01 darren@b 02:HighTemp: Alarms not uncommon this time of year. 08/06/2010 08:35 darren@b 01:HighTemp,02:HighTemp,03:HighTemp: Alarms not uncommon this time of year. 08/05/2010 08:31 Troy@bay 01:HighTemp,02:HighTemp,03:HighTemp: These alarms are not uncommon this time of year. 08/04/2010 08:40 darren@b 02:HighTemp: Alarm not uncommon this time of year. 08/03/2010 08:25 darren@b 02:HighTemp: Alarm not uncommon this time year. 07/31/2010 09:56 Troy@bay 01:HighTemp,02:HighTemp,03:HighTemp: These alarms are not uncommon for this time of year. 07/30/2010 08:42 troy@bay 01:HighTemp,02:HighTemp,03:BadExcFreq,03:HighTemp: The high temp alarms are not uncommon this time of year. The BadExcFreq alarm will be investigated on the next site visit. 07/28/2010 08:38 troy@bay 01:HighTemp,02:HighTemp,03:BadExcFreq,03:HighTemp: The HighTemp alarms are not uncommon for this time of year. The BadExcFreq is uncommon. PSMFC will monitor. 07/27/2010 08:38 troy@bay 01:HighTemp,02:HighTemp,03:HighTemp: These alarms are not un-common for this time of year. 07/26/2010 08:49 troy@bay 01:HighTemp,02:HighTemp,03:HighTemp: These alarms are not uncommon this time of year. 07/25/2010 07:48 alan@bay 01:HighTemp,02:HighTemp,03:HighTemp: These alarms are to be expected this time of year. 07/24/2010 09:26 alan@bay 01:HighTemp,02:HighTemp,03:HighTemp: Alarms are to be expected this time of year. 07/21/2010 08:11 Scott_Li Deleted .zip file in temp folder, manually pushed outstanding data files, no other problems to report. 07/20/2010 08:26 alan@bay 01:HighTemp,02:HighTemp,03:HighTemp: These alarms are to be expected this time of year. 07/19/2010 08:40 alan@bay 02:HighTemp: Noted 07/18/2010 10:39 scottl@b 01:HighTemp,02:HighTemp,03:HighTemp: Noted 07/16/2010 08:14 scottl@b 01:HighTemp,02:HighTemp,03:HighTemp: Noted 07/15/2010 08:15 scottl@b 01:HighTemp,02:HighTemp,03:HighTemp: noted, these alarms are expected for this time of the year. 07/14/2010 08:02 scottl@b 03:BadExcFreq: Noted 07/12/2010 08:31 darren@b 02:HighTemp: Alarm not uncommon this time of year. 07/11/2010 09:31 darren@b 01:HighTemp,02:HighTemp,03:HighTemp: Alarms not uncommon this time year. 07/10/2010 08:58 darren@b 01:HighTemp,02:HighTemp,03:HighTemp: Alarms not uncommon this time of year. PSMFC is monitoring for any equipment problems during this period. 07/03/2010 09:54 alan@bay 03:BadExcFreq: No apparent reason for this one-time alarm. PTAGIS Field Operations will continue to monitor. 06/29/2010 09:07 darren@b 02:HighTemp: Alarm not uncommon this time of year. 06/28/2010 09:58 darren@b 02:HighTemp: Alarms not uncommon this time of the season. 06/26/2010 08:04 Troy@bay 01:HighTemp,02:HighTemp: These alarms are common this time of year. 06/25/2010 09:04 troy@bay 03:BadExcFreq: Noted, PSMFC will monitor. 06/14/2010 08:23 scottl@b 01:HighTemp,02:HighTemp: Problems noted, not an issue at this time. 05/29/2010 09:28 Troy@bay 03:BadOscFreq: Noted, PSMFC will monitor. 05/26/2010 10:56 scottl Performed site GMC, transcievers were retuned and calibrated. One note is that xcvr 01 had "Bad Oscillator" message and was in an MS scan mode. Rebooted xcvr and the unit returned to normal operating mode. Will monitor, no other problems to report. 05/25/2010 08:33 troy@bay 03:BadExcFreq: This will be investigated on the next site visit. 05/11/2010 15:57 Scott_Li Remoted into the primary computer in order to delete the .zip file and also to manually submit delinquent data files. While performing this operation, the remote session just bombed for no reason and could not get back into the computer. Had site personnel assist with the reboot of PC1, monitored PC2 while this was in process to ensure that no PIT tag fish was missed. There will be a slight data gap in the data set due to this. 04/29/2010 14:57 Alan A GMC was performed 4/29/2010. All transceivers were checked and tuned as necessary. The clocks on both PCs were set to within one second of atomic time. The temp folders were cleared on both PCs. Outstanding files on PC2 were archived. No problems found. 04/29/2010 11:46 darren@b 01:TestTagFailure: This alarm was generated because the reader reset and tried to fire the timer tag and was unsuccessful. It did fire 3 seconds later. The reader reset was a random reader reset which PSMFC is aware can happen with these systems. 04/07/2010 14:05 Alan MiniMon was exited briefly on PC1 at ~1240 PDT 4-7-2010 to delete a zip file. PC1 was inadvertently set to central time while setting the clocks, causing the file closed timestamp to be ahead two hours for file RZF10097.E1. The file closed timestamp was manually corrected prior to submission to PTAGIS. File RZF10097.N2 covers the gap during PC1's downtime. Files RZF10097.C1 - E1 were manually pushed to PTAGIS. No outstanding problems to report. 03/26/2010 08:38 scottl@b 02:LowExcCurrent: This was corrected during the latest site visit. 03/25/2010 14:58 Darren A site GMC was performed today (3-25-10). All transceivers were checked for tuning, noise, and detectability. No problems were discovered during this visit. 03/25/2010 08:37 Alan@bay 02:TestTagFailure: No apparent reason for this one-time alarm. PTAGIS Field Operations will continue to monitor. 03/14/2010 14:28 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/01/2010 07:50 Troy Maually pushed the delinquent files. I had to stop Minimon in order to move the zip file. I then re-booted PC1 in hopes of eliminating this problem. I put a marker in PC2's file to show no data was recorded while PC1 was down. 02/27/2010 10:43 scottl Site had not submitted data files since yesterday's .E file. PCA to site and deleted .zip file in temp folder. Manually sent delinquent data files to PTAGIS. 02/24/2010 09:34 Alan Two separate power outages created data gaps on 2-17-2010 and 2-22-2010. Files RZF10048.D9 and RZF10053.D9 were created from TMP files found on PC1 and submitted manually. No further data exist on either PC to fill the remaining gaps. 02/21/2010 08:07 Darren The outstanding 5 files were uploaded to PTAGIS manually. The .ZIP file was deleted. 02/18/2010 11:24 Darren The site was visited today (2-18-10) for a site GMC. The transceivers were checked and adjusted as necessary. The file gap from yesterday (RZF10048.D1) was a temp file that appears to have been generated because of a loss of power. The file was opened at 09:00 and closed at 09:45, the .E1 file opened at 10:07 thus creating a 22 minute file gap. This was also the case on PC2. The file will be properly closed and submitted to PTAGIS. No other problems were discovered during this visit. 01/30/2010 08:49 Darren I was able to PCA into the site and push the delinquent files to PTAGIS. I had to remove the ZIP file which constituted shutting down Minimon. PC2 was monitored for PITtag detections and none were observed. No Patch file was created for the brief outage. 01/27/2010 07:12 Darren The site was not uploading files automatically. I PCA'd into the site and deleted the compressed zip file and submitted the 7 outstanding files to PTAGIS. 01/25/2010 07:14 Scott_Li Deleted the .zip file in the temp dir. Manually pushed 15 delinquent data files to PTAGIS. 01/06/2010 07:26 Alan MiniMon was bounced remotely in order to delete a zip file. No activity was observed on PC2 during PC1's downtime. Files RZF10005.D1 - RZF10006.C1 were pushed to PTAGIS. PTAGIS field Operations will continue to monitor. 01/05/2010 07:13 scottl Manually pushed delinquent data files, deleted .zip file in tempo folder. No other problems found. 01/01/2010 00:00 PTOC_Bot Annual log file initiation for RZF #### End of Event Log for RZF ###