EVENT LOG FOR SITE ICH 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/2008 07:11 troy@bay 07:TestTagFailure: This transceiver will be investigated on the next site visit. 12/30/2008 07:22 troy@bay 07:TestTagFailure: This may be the result of a tune drift, PSMFC will address on the next site visit. 12/29/2008 07:56 alan@bay 07:TestTagFailure: This will be addressed during the next site visit. This transceiver is reading PIT Tags. 12/28/2008 07:50 alan@bay 07:TestTagFailure: This will be addressed during the next site visit. 12/27/2008 08:19 alan@bay 07:TestTagFailure,A3:TestTagFailure: These will be addressed during the next site visit. 12/26/2008 10:05 alan@bay 07:TestTagFailure: This will be addressed during the next site visit. 12/25/2008 09:34 alan@bay 07:TestTagFailure: This will be addressed during the next site visit. 12/24/2008 07:41 alan@bay 07:TestTagFailure: This will be addressed during the next site visit. 12/23/2008 07:15 alan@bay 07:TestTagFailure,A3:TestTagFailure: These transceivers have drifted out of tune but are still reading PIT Tags. They will be tuned during the next site visit. 12/22/2008 07:45 alan@bay 07:TestTagFailure,A3:TestTagFailure: These systems have drifted out of tune but are reading PIT Tags. They will be addressed during the next site visit. 12/21/2008 08:37 Darren I investigated the test tag failures on antenna 0D. It appears that it has fallen out of tune. It will be addressed during the next site visit. 12/21/2008 08:22 darren@b A3:TestTagFailure: Alarm will be addressed during the next site visit. 12/21/2008 08:21 darren@b 07:TestTagFailure: This alarm will be addressed during the next site visit. 12/20/2008 08:58 darren@b 07:TestTagFailure: This alarm will be addressed during the next site visit. 12/19/2008 08:59 darren@b 07:TestTagFailure: There is no real direct cause for this alarm. The transceiver has drifted slightly out of tune and become a little noisy. PITtag detections are still very efficient. 12/18/2008 07:28 darren@b A3:TestTagFailure: This alarm will be addressed during the next site visit. There was not apparent cause for this failure. 12/18/2008 07:27 darren@b 07:TestTagFailure: This system has drifted in tune slightly. It will be addressed during the next site visit. 12/17/2008 07:35 darren@b A3:TestTagFailure: This alarm will be investigated during the next site visit. 12/16/2008 07:16 darren@b 07:TestTagFailure,A3:TestTagFailure: These alarms will be addressed during the next site visit. 12/11/2008 12:14 scottl@b 0B:TestTagFailure: Noted 12/10/2008 07:40 troy@bay 05:LowExcCurrent: This was the result of some testing being performed in the area. 11/25/2008 12:32 Alan Manually pushed ICH08330.D1 to PTAGIS via PCA. 11/19/2008 07:59 Alan No PIT Tag activity occurred during the time PC1 was down on 11/13/2008. While remoted in to both PCs, the clocks (approximately four minutes fast were set to within one second of atomic time. The data files on PC2 were archived. 11/13/2008 07:23 Darren I was able to PCA into the site and submit the outstanding files to PTAGIS. While I was checking the temp file I found several zip files that I tried to clear out of the directory. One of the files would not delete because it stated that it was being used by another program. I tried to stop and start the application so there may a slight gap in the files but I was finally able to delete the file and submitted the files generated. 11/12/2008 12:30 Dave pcA'd in and pushed two delinquent data files without incident. The clock on ICH-PC1 is 2:37 seconds fast relative to atomic time. 11/11/2008 08:23 Darren The outstanding files were manually uploaded to PTAGIS via PCA. There was another zip file in the temp directory at GOJ which was not allowing the files to upload. 11/06/2008 07:20 darren@b 0B:TestTagFailure: Alarm will be investigated today durign a site visit. 11/05/2008 07:21 darren@b 0B:TestTagFailure,A3:TestTagFailure: Alarms will be addressed during a site visit. tomorrow. 10/30/2008 08:47 Troy Pushed ICH08303.F1 - ICH08304.B1. 10/30/2008 07:51 Troy Verified with the site bio that the site network is down. No estimated repair time was known. PSMFC will monitor throughout the day. 10/30/2008 07:30 Troy Tried to establish a PCA connection and could not with any of the site's computers. Will try to contact site personnel and/or will visit site if neccessary. 10/29/2008 16:28 Troy manually pushed ICH08303.E1. There was a error message on the screen (windows error) I captured it and will discuss in staff meeting next week. 10/29/2008 08:39 troy@bay A3:TestTagFailure: Noted, PSMFC will monitor. 10/28/2008 07:39 darren@b A3:TestTagFailure: This alarm will be addressed during the next site visit. 10/26/2008 09:37 troy@bay A3:TestTagFailure: PSMFC will monitor. 10/25/2008 08:38 Troy Pushed ICH08299.B1 to ptagis. 10/24/2008 08:35 troy@bay A3:TestTagFailure: PSMFC will monitor. 10/22/2008 10:50 Alan Manually pushed ICH08296.C1 to PTAGIS via PCA. 10/22/2008 07:49 darren@b A3:TestTagFailure: The system has slightly detuned. It will be addressed during the next site visit. 10/21/2008 07:39 troy@bay A3:TestTagFailure: Noted, PSMFC will monitor. 10/20/2008 08:10 troy@bay 0B:TestTagFailure: Noted 10/19/2008 10:34 scottl@b 0B:TestTagFailure: Noted, will monitor 10/16/2008 07:08 scottl@b A3:TestTagFailure: Noted 10/15/2008 07:16 scottl@b 0B:TestTagFailure,A3:TestTagFailure: Noted 09/25/2008 07:54 alan@bay 01:TestTagFailure: No apparent reason for this one-time alarm. PTAGIS Field Operations will continue to monitor. 09/20/2008 07:59 darren@b A3:TestTagFailure: The alarm was generated by PSMFC personnel while performing tests on site. 09/19/2008 11:24 Darren PSMFC was on site to conduct some tests with the DF2020 transceiver. After the tests were completed communincations needed to be verified on the transceivers that were used for testing. I was adjusting the clocks on both PC's which were 2 minutes ahead of atomic time. After reseting the clock on PC1 I stopped and started minimon at which time I received and error message that stated that Minimon had encountered an eroor and need to shut down. This a slight file gap but because the clocks were adjusted backwards it may appear bigger than it was.No PITtag detections were observed on PC2 during this time. 09/18/2008 16:15 Darren The files were uploaded automatically at 16:00. 09/18/2008 15:13 Darren_C The firewall issues with the Portland District COE has finally been resolved. We were inadvertently blocked and Chris Sampier did not realize that we owned the whole block of addresses. He initially unblocked only one address which allowed us to PCA into the sites but we could not send any data to our servers. After he realized that we needed all the addresses we were able to get in and send the files via PTTP and PCA. We will monitor for the 16:00 upload to ensure that the sites are loading on their own and continue to watch fro any other aspects that may not be working. The sites appear to be functioning properly at this time. 09/18/2008 13:15 Darren_C The PCA connection has been resolved. Although we can get to the platforms we are still unable to send data or do any ftp sessions from the sites out. I am still working to resolve this issue. Dave Marvin has grabbed the outstanding files and uploaded them manually. Until this issue is fully resolved we not receive any files from the WW district sites. 09/18/2008 09:28 Darren_C I am currently in the process of trying to get in touch with Chris Sampier or Antonio Sanchez from the Portland District office to find out why the Walla Walla district sites have no communications. I am not able to get to any of the platforms and they are not able to send. I am not sure if this has anything to do with the line that was cut yesterday between Starbuck and Dayton but I will hopefully find out more when I speak with Portland District. 09/18/2008 07:34 Darren There appears to be some issue with the WW District network. I am currently trying to get in touch with Pete Peterson to verify what the problem may be. I will post more when the information becomes available. 09/09/2008 13:02 Darren A site GMC Was performed today (9-9-08). All transceeivers were checked fro tuning, noise, and detection ability. No problems were found. 08/16/2008 08:11 alan@bay A3:TestTagFailure: No apparent reason for this alarm. PTAGIS Field Operations will continue to monitor. 08/15/2008 08:26 alan@bay 0C:LowExcCurrent: These alarms were generated by PTAGIS Field Operations personnel during a site visit. 08/13/2008 10:25 scottl Performed site GMC, all transceivers were retuned and calibrated as necessary. The noise issue with unit 06 was resolved today by a slight tune adjustment. I appears that the ongoing problem maybe related to the transciever. A very slight,slight adjustment of the tune cap reduced the noise from 16 to 24 % to 2-4 %. If this is the case on the next site visit, it is suggested to replace the transceiver as a first step. Also, contacted the on-site locksmith about the south side gallery door not being accessable. He then replaced the entire assemably therefore this door will no longer require a key for enterance. The onsite lock smith indicated that it will remain this way so the issue has been resolved. 08/12/2008 13:49 Darren Manually pushed necessary files to PTAGIS. 08/08/2008 08:32 darren@b 0C:BadOscFreq: No direct cause for this alarm. PSMFC will continue to monitor for future alarms and investigate this during the next site GMC. 08/06/2008 09:45 darren@b A3:TestTagFailure: The test tag alarm occured during a period where the noise was slightly elevated. This will be investigated during the next site GMC> 08/05/2008 13:14 Darren Manually pushed the ICH08218.C1 and .D1 files via PCA. 08/05/2008 08:18 darren@b A3:TestTagFailure: here is no direct cause for this failure. PSMFC will continue monitor and address any future alarms when necessary. 07/30/2008 08:14 Alan Manually pushed ICH08212.B1 and MCJ08212.102 to PTAGIS via PCA. 07/25/2008 08:14 Alan Manually pushed ICH08207.B1 to PTAGIS via PCA. 07/24/2008 08:34 troy@bay 0B:TestTagFailure: Noted 07/23/2008 08:59 alan@bay A2:LowExcCurrent: This will be investigated during the next site visit. 07/22/2008 14:03 Dave Manually pushed ICH08204.C1 and ICH08204.D1 to PTAGIS. 07/22/2008 13:00 Darren A site GMC was performed today (7-22-08). All transceivers were checked for tuning, noise, and detection ability. On the north ladder the COE has a big fan running at the end of the walkway for removing heat this is causing some slight elevations in noise on antennas 09 and 0A. The signal levels are below 12%. The PC clock on PC1 was almost 2 miutes fast but 19 seconds slow of PC2 both clocks were adjusted to atomic time and each other no detections were seen on PC2 during the 19 seconds of time that PC1 was out of collection. No problems were found during this visit. 07/19/2008 07:45 darren@b 07:TestTagFailure: The test tag did not fire due to excessive noise. But the noise seems to have subsided. PSMFC will investigate this on the next site visit. 07/15/2008 08:33 alan@bay A3:TestTagFailure: No apparent reason for this one-time alarm. PTAGIS Field Operations will continue to monitor. 07/14/2008 13:23 Alan Manually pushed ICH08196.D1 to PTAGIS via PCA. 07/07/2008 13:38 scottl Performed site GMC, all transcievers were tuned and re adjusted as ncessary. No problems to report. 07/05/2008 10:31 troy@bay 07:TestTagFailure: This alarm will be addressed on the next site visit. 06/22/2008 07:41 alan@bay A3:BadOscFreq: This will be investigated during the next site visit. 06/21/2008 10:42 alan@bay 07:TestTagFailure: This will be investigated during the next site visit. 06/19/2008 16:23 Alan Manually pushed ICH08171.E1 to PTAGIS via PCA. 06/17/2008 12:43 Troy A site GMC was performed 06/17/2008. All transceivers were checked for tune and adjustments made where needed. No problems to report. 06/10/2008 11:04 Troy A site GMC was performed 06/10/2008. All transceivers were checked for tune and adjustments made where needed. No problems to report. 06/07/2008 08:01 alan@ree 0C:TestTagFailure: This will be investigated during the next site visit. 06/06/2008 09:51 alan@ree 0C:TestTagFailure: This will be investigated during the next site visit. 06/05/2008 08:41 alan@ree 0C:TestTagFailure: This will be investigated during the next site visit. 06/04/2008 07:10 darren@r 0C:TestTagFailure,A2:LowExcCurrent,A3:LowExcCurrent: Alarms were generated by PSMFC personnel during a site visit. 06/03/2008 16:35 Alan The full flow xcvrs were tuned 6/3/2008. The phase had risen from 3 to 5 since yesterdays visit. Xcvr A3 was replaced as it has been intermittently noisy during the last month. It was out of service from ~14:45 to 15:15. 06/02/2008 17:10 Alan A GMC was performed 6/2/2008. All transceivers were checked and tuned as necessary. The clocks on both PCs (~15 seconds fast) were set to within one second of atomic time. No problems found. 05/28/2008 09:23 Alan A GMC was performed 5/28/2008. All transceivers were checked and tuned as necessary. The clocks on both PCs (~40 seconds fast) were set to within one second of atomic time. No problems found. 05/27/2008 21:41 troy_hum RIGHT LADDER RADIO COMMUNICATIONS ACTIVE 05/27/2008 21:41 troy_hum RIGHT LADDER LEVEL ACTIVE 05/27/2008 21:28 troy_hum RIGHT LADDER RADIO COMMUNICATIONS DOWN 05/27/2008 01:27 troy_hum RIGHT LADDER RADIO COMMUNICATIONS ACTIVE 05/27/2008 01:27 troy_hum RIGHT LADDER LEVEL ACTIVE 05/27/2008 01:16 troy_hum RIGHT LADDER RADIO COMMUNICATIONS DOWN 05/26/2008 14:24 troy_hum RIGHT LADDER RADIO COMMUNICATIONS ACTIVE 05/26/2008 14:24 troy_hum RIGHT LADDER LEVEL ACTIVE 05/26/2008 14:11 troy_hum RIGHT LADDER RADIO COMMUNICATIONS DOWN 05/23/2008 12:02 Alan A GMC was performed 5/23/2008. All transceivers were checked and tuned as necessary. The clocks on both PCs are 23 seconds ahead of atomic time. No problems found. 05/21/2008 15:23 troy_hum RIGHT LADDER RADIO COMMUNICATIONS ACTIVE 05/21/2008 15:23 troy_hum RIGHT LADDER LEVEL ACTIVE 05/21/2008 15:22 troy_hum RIGHT LADDER RADIO COMMUNICATIONS DOWN 05/17/2008 10:03 alan@ree A3:LowExcCurrent: Already cleared TASS for this alarm. 05/17/2008 10:02 alan@ree A3:LowExcCurrent: This alarm was caused by PTAGIS Field Operations personnel during a site visit. 05/16/2008 09:23 alan@ree 0F:LowExcCurrent: This alarm was generated by PTAGIS Field Operations personnel during a site visit. 05/15/2008 09:40 Alan A GMC was performed 5/15/2008. All transceivers were checked and tuned as necessary. The clocks on both PCs (~2.5 min fast) were adjusted to within one second of atomic time. No problems found. 05/09/2008 14:58 Darren A site GMC was performed today (5-9-08). All transceivers were checked for tuning, noise and detection ability. No problems were discovered during this visit. 05/06/2008 05:56 troy_hum RIGHT LADDER LEVEL ACTIVE 05/06/2008 05:53 troy_hum RIGHT LADDER LEVEL HIGH OR LT DISCONNECTED 05/06/2008 05:53 troy_hum LEFT LADDER LEVEL HIGH OR LT DISCONNECTED 05/06/2008 05:53 troy_hum LEFT LADDER RADIO COMMUNICATIONS ACTIVE 05/06/2008 05:53 troy_hum RIGHT LADDER RADIO COMMUNICATIONS ACTIVE 05/06/2008 05:52 troy_hum LEFT LADDER RADIO COMMUNICATIONS DOWN 05/06/2008 05:52 troy_hum RIGHT LADDER RADIO COMMUNICATIONS DOWN 05/02/2008 08:00 scottl@r 0B:TestTagFailure: Noted 05/01/2008 15:02 Darren A site GMC was performed today (5-1-08). All transceivers were checked for tuning, noise and detection ability. No problems were discovered during this visit. 04/27/2008 08:40 darren@r 0B:TestTagFailure: Alarm will be investigated during the next site GMC. 04/25/2008 13:27 Darren A site GMC was performed today (4-25-08). All transceivers were checked for tuning, noise, and detection ability. No problems were discovered during this GMC. 04/25/2008 08:32 darren@r 0B:TestTagFailure: Problem will be investigated by PSMFC personnel during the next site visit. 04/18/2008 08:22 troy@ruf 0B:TestTagFailure: These alarms will be addressed on the next site visit. 04/17/2008 08:17 troy@ruf 0B:TestTagFailure: Noted 04/14/2008 08:27 troy@ruf 0B:TestTagFailure: This will be looked into on the next site visit. 04/11/2008 10:12 alan@ruf 03:LowTemp,0B:TestTagFailure: These alarms will be investigated during the next site visit. 04/01/2008 15:23 Alan A GMC was performed 4/1/2008. All transceivers were tuned. The output of the VTT was adjusted on transceiver 06. The clocks on both PCs were adjusted to within one second of atomic time. No problems found. 03/27/2008 07:07 scottl@r 0A:LowLithium,0B:LowLithium,0D:LowLithium,0E:LowLithium: Problem noted. 03/26/2008 21:21 scottl@r 01:LowLithium,02:LowLithium,03:LowLithium,04:LowLithium,05:LowLithium,06:L owLithium,07:LowLithium,08:LowLithium,0A:LowLithium,0B:LowLithium,0D:LowLi thium,0E:LowLithium,0F:LowLithium,A1:LowLithium,A2:LowLithium,A3:LowLithiu m,A4:LowLithium: Reset readers (Scott) 03/26/2008 07:36 darren@r 01:LowLithium,02:LowLithium,03:LowLithium,04:LowLithium,05:LowLithium,06:L owLithium,07:LowLithium,08:LowLithium,0A:LowLithium,0B:LowLithium,0D:LowLi thium,0E:LowLithium,0F:LowLithium,A1:LowLithium,A2:LowLithium,A3:LowLithiu m,A4:LowLithium: These alarms will be addressed during the next site GMC. Power needs to be cycled on alll the transcievers. 03/25/2008 07:17 darren@r 01:LowLithium,02:LowLithium,03:LowLithium,04:LowLithium,05:LowLithium,06:L owLithium,07:LowLithium,08:LowLithium,0A:LowLithium,0B:LowLithium,0D:LowLi thium,0E:LowLithium,0F:LowLithium,A1:LowLithium,A2:LowLithium,A3:LowLithiu m,A4:LowLithium: PSMFC is aware of these alarms and they will be cleared during the next site visit. The batteries were recently replaced and the alarm is in memeory and can only be cleared by cycling the power. 03/24/2008 07:25 darren@r 01:LowLithium,02:LowLithium,03:LowLithium,04:LowLithium,05:LowLithium,06:L owLithium,07:LowLithium,08:LowLithium,0A:LowLithium,0B:LowLithium,0D:LowLi thium,0E:LowLithium,0F:LowLithium,A1:LowLithium,A2:LowLithium,A3:LowLithiu m,A4:LowLithium: These alarms will be investigated by PSMFC. The batteries were recently replaced and these alarms could be stuck in memory and will need to be cleared by cycling the power of the transceivers. 03/23/2008 09:28 alan@ruf 01:LowLithium,02:LowLithium,03:LowLithium,04:LowLithium,05:LowLithium,06:L owLithium,07:LowLithium,08:LowLithium,0A:LowLithium,0B:LowLithium,0D:LowLi thium,0E:LowLithium,0F:LowLithium,A1:LowLithium,A2:LowLithium,A3:LowLithiu m,A4:LowLithium: This will be investigated tomorrow. 03/22/2008 10:01 alan@ruf 01:LowLithium,02:LowLithium,03:LowLithium,04:LowLithium,05:LowLithium,06:L owLithium,07:LowLithium,08:LowLithium,0A:LowLithium,0B:LowLithium,0D:LowLi thium,0E:LowLithium,0F:LowLithium,A1:LowLithium,A2:LowExcCurrent,A2:LowLit hium,A3:LowLithium,A4:LowLithium: These alarms were generated by PTAGIS Field Operations personnel during a site visit. 03/22/2008 09:42 Alan Manually pushed ICH08081.D9 to PTAGIS via PCA. 03/21/2008 11:17 scottl All transcievers were tuned and calibrated as necessary. No problems to report. All internal transceiver batteries were replaced along with the UPS's in the PIT room. The patch file for PC1 is 08081.l2 and resides on the BU computer. For all its worth, no fish traffic was observed while PC1 was down for maintenance. 03/17/2008 14:10 Troy Mark Plummer called to report that the FF watered up for the season at 2 pm PDT on 03/17/2008. 03/14/2008 11:13 scottl@r A2:TestTagFailure: Noted 03/04/2008 08:03 troy@ruf 0F:LowExcCurrent: PCA'ed into PC2 and did a status dump on OF. The current is running at 3.3 and the LowExcCurrent Alarm threshold is at 3.0? PSMFC will monitor for future occurances. 02/24/2008 09:01 troy@ruf 0F:LowExcCurrent: The tune may have shifted on this transceiver. PSMFC will monitor for future occurances of this alarm and make adjustments where needed. 02/14/2008 07:39 alan@ruf 01:LowExcCurrent,0A:LowExcCurrent,0B:LowExcCurrent,0D:LowExcCurrent,0E:Low ExcCurrent,0F:LowExcCurrent: The alarm on 01 occurred before yesterday's actions (clearing TASS). The other alarms occurred prior to yesterday's water-up. 02/13/2008 13:52 troy_hum RIGHT LADDER LEVEL ACTIVE 02/13/2008 07:28 alan@ruf 01:LowExcCurrent: The transceiver appears to have drifted out of tune. Both the alarm threshold and the operating current is 4.1A. I remotely lowered the threshold to 3.8A. This will be investigated during the next site visit. 02/12/2008 07:21 alan@ruf 01:LowExcCurrent: This will be investigated during the next site visit. 02/08/2008 07:44 darren@r 01:LowExcCurrent: This problem will be addressed on the next site visit. It appears that the transceiver has drifted slightly out of tune. 02/05/2008 07:22 darren@r 01:TestTagFailure,09:LowExcCurrent,0A:LowExcCurrent,0A:TestTagFailure,0B:L owExcCurrent,0C:LowExcCurrent,0D:LowExcCurrent,0E:LowExcCurrent,0F:LowExcC urrent,10:LowExcCurrent: The North (Right) ladder was de-watered yesterday around 09:00. 02/04/2008 10:00 troy_hum RIGHT LADDER LEVEL LOW 01/30/2008 07:31 darren@r A2:TestTagFailure,A4:LowExcCurrent: Full Flow is de-watered for the season. 01/25/2008 07:37 alan@ruf A4:LowExcCurrent,A4:Overrun: The FF is currently de-watered. 01/23/2008 12:00 Dave From the PLC alerts reported previously, PTOC staff contacted the Corps biologist and confirmed that the left (south) ladder was dewatered from approximately 10AM on Jan. 9 until 10AM on Jan. 19. 01/22/2008 07:42 alan@ruf A4:LowExcCurrent: Clearing TASS, the FF is currently dewatered. 01/21/2008 09:43 troy@ruf 01:LowExcCurrent,04:LowExcCurrent,07:TestTagFailure,08:LowExcCurrent. It appears the left ladder watered up 01/19/2008. PSMFC will verify tomorrow with the site biologist. Clearing TASS. 01/19/2008 10:13 troy_hum LEFT LADDER LEVEL ACTIVE 01/18/2008 09:18 troy@ruf 07:TestTagFailure,0D:TestTagFailure,A1:LowExcCurrent,A2:LowExcCurrent,A3:L owExcCurrent,A4:LowExcCurrent,A4:Overrun: The FF and the left ladder are de-watered. The only alarm of some concern is 0D. PSMFC will monitor for future TT failures. 01/09/2008 09:47 troy_hum LEFT LADDER LEVEL LOW 01/02/2008 08:13 troy@ruf 0D:TestTagFailure: This will be looked into on the next site visit. 01/01/2008 00:00 PTOC_Bot Annual log file initiation for ICH #### End of Event Log for ICH ###