EVENT LOG FOR SITE MC1 Most recent activity to be listed first. First line of each entry lists date, time & who is reporting. Subsequent lines of each entry aligned under Time column. Do not use tabs, only spaces. Date Time Who What -------- ----- -------- ----------------------------------------------- 12/27/2002 12:19 Alan Bobby Johnson called to confirm work (relay changing) being done that probably caused a power outage on 12/24/02. 12/26/2002 09:19 Alan MC102358.C 12/24/02 10:58 12/24/02 17:00 LOADED 4 hrs 58 mins 01 12/25/02 00:29 This is probably a power outage that outlasted the UPS due to the fact that there is no file MC102358.B. We will verify with site personnel and post actual times when available. 12/23/2002 10:46 darren@p 10:TestTagFailure: Alarm acknowledged. Will check this transceiver on the next site visit. . 12/22/2002 22:52 darren@p 10:LowExcCurrent,10:TestTagFailure: 10:LowExcCurrent,10:TestTagFailure: 11-17 12/20/02 14:28:42 ALARM MESSAGE: Reader reset! ~11-17 12/20/02 14:28:42 ALARM MESSAGE: Reader is in scan mode. Although this was not an alarm, this is the first time I have seen a reader reset on an adult transceiver. This is very interesting because the theory was that it had something to do with the timer tag firing on the juvenile transceiver but the timer tag on the adult is setup differently. As for the alarm I can't find any distinct reason for the current to drop .7A and then return to normal. 2002/12/20 15:28:42 2.4A 7% 16.0V 12% 28C 2002/12/21 09:28:58 3.1A 5% 16.0V 30% 26C This one is hard to understand. We will monitor for further deviances. The transceiver will be addressed on the next site visit. . 12/22/2002 22:52 darren@p 10:LowExcCurrent,10:TestTagFailure: 11-17 12/20/02 14:28:42 ALARM MESSAGE: Reader reset! ~11-17 12/20/02 14:28:42 ALARM MESSAGE: Reader is in scan mode. Although this was not an alarm, this is the first time I have seen a reader reset on an adult transceiver. This is very interesting because the theory was that it had something to do with the timer tag firing on the juvenile transceiver but the timer tag on the adult is setup differently. As for the alarm I can't find any distinct reason for the current to drop .7A and then return to normal. 2002/12/20 15:28:42 2.4A 7% 16.0V 12% 28C 2002/12/21 09:28:58 3.1A 5% 16.0V 30% 26C This one is hard to understand. We will monitor for further deviances. The transceiver will be addressed on the next site visit. . 12/20/2002 08:39 darren@p 08:TestTagFailure,10:TestTagFailure: 10-13 12/19/02 21:13:26 ALARM MESSAGE: Single-shot test with Test Tag. ~10-13 12/19/02 21:13:27 ALARM MESSAGE: Test aborted due to system activity. This is the message that was received from transceiver 10. I noticed that most of the timer tags are firing at the same time as the status reports on most transceivers. This could be some of the cause for the timer tag failures. I will PCA into this site and fire the timer tag and try to offset this occurrance. . 12/20/2002 08:16 darren@p 0C:HighTemp: 2002/12/14 01:12:54 4.3A 1% 13.3V 3% 32C 2002/12/14 07:12:53 4.3A 1% 13.3V 4% 34C 2002/12/14 13:12:53 4.3A 1% 13.3V 4% 40C 2002/12/14 19:12:52 4.3A 1% 13.3V 3% 40C 2002/12/15 01:12:52 4.3A 1% 13.3V 3% 34C I do not see any overtemp conditions. There was no indicators in the "raw" file either. This could be a "glitch" in the system. I will try and look deeper in the files to try and confirm this. . 12/11/2002 09:17 darren@p 0F:LowExcCurrent,10:LowExcCurrent,10:Overrun: These alarms were generated by PTOC personnel while on site performing maintenance. . 12/06/2002 08:23 darren@p 10:LowExcCurrent: This transceiver has drifted out of tune and will be re- tuned. PTOC personnel is investigating the drifting of the transceivers to find out what may be causing this drastic change in the tune of the circuit. . 12/06/2002 08:19 darren@p 08:TestTagFailure: This transceiver looks to be tuned when looking at the "raw" data status dumps and the exciter reports. We will look at the timer tag adjustments on the next site visit. . 12/04/2002 15:55 Don_Warf From a message received from Brad Eby, MCN Site Biologist: Oregon fish ladder picketed leads and backboard went back into place yesterday, (Dec 3. 02) about lunch time. 12/03/2002 16:15 darren@p 08:TestTagFailure: Will probably visit site this week. The test tag failures may be due to high noise at times. The unit may need to be retuned or the excite voltage adjusted. 12/02/2002 08:45 scottl@p 05:ExcessiveNoise,07:ExcessiveNoise,08:ExcessiveNoise,09:ExcessiveNoise,0A :ExcessiveNoise,0F:ExcessiveNoise,10:ExcessiveNoise,11:ExcessiveNoise: Will monitor for excessive noise. 12/02/2002 08:41 scottl@p 08:TestTagFailure: Will check into this. 11/27/2002 09:43 Don_Warf From: "Baxter, Rex D NWW" To: "Eby Brad W NWW" Subject: Counting Slot PIT Detector Date: Tue, 26 Nov 2002 12:46:54 -0800 Brad/Bobby: Dave H says you should put the picketed leads back in the Oregon ladder. You can pull them after Dec 31 to minimize maintenance needs. There are still some fish moving in the meantime. At least 2 of the Snake projects have to keep their picketed leads in most of the year, due to year-round fish counting. Rex 11/27/2002 08:51 darren@p 01:ExcessiveNoise,02:ExcessiveNoise,06:ExcessiveNoise,07:ExcessiveNoise,0B :ExcessiveNoise,0F:ExcessiveNoise,10:ExcessiveNoise,11:ExcessiveNoise: These alarms have been cleared more than once. The panel will not clear so we cannot look to see if the maintenance and tuning is making any difference. I will send a message to the help desk. 11/27/2002 08:38 darren@p 08:TestTagFailure: Alarm may have caused the reader having excessive noise. This will be addressed on site visit. 11/26/2002 08:16 darren@p 08:TestTagFailure: There is no obvious reason for the test tag failure. The status report show good parameters as well as the exciter report. I will monitor for further alarms. 11/25/2002 13:04 Darren_C When I was at the counting window on Thursday (11-21-02) I noticed that the backdrop for the counting window was gone. After thinking about this I wondered if the screens had also been pulled to allow fish to pass by the counting window coils without any detection. I spoke with Brad Eby at McNary today (11-25-02) and he confirmed that the counting was finished on 10-31-02 and that the backdrop and picketed leaves were pulled on 11-2-02 sometime in the morning hours, he was not sure of the exact time, this does allow for a clear path to the exit of the ladder. Brad did suggest that these could be replaced if there was a significant number of detection's on the lower coils and no detection's on the counting window coils. I will confirm the dates for the initial counting to begin. 11/25/2002 11:50 Darren_C On Thursday 11-21-02 I was on site to check and retune all transceivers. All coils were megohmed to find out if there were anymore failures. There were some issues that were taken care of while also on site: Coil 08 at MC2 had to have the ground wire from the door to the transceiver enclosure replaced. It was found to have been cut somehow during the installation process. 11/25/2002 09:29 darren@p 01:TestTagFailure,05:TestTagFailure,08:TestTagFailure,0E:TestTagFailure: Alarms were generated by PTOC personnel while performing tuning and maintenance on transceivers. The timer tag failure on coil 08 will be looked into. 11/07/2002 14:13 Don_Warf Brad Eby has given me the following water down dates for the adult ladders: Washington Shore: Starting Jan 6th and lasting for 4 weeks. Work in the ladder will include control weir repairs and the installation of new water level controls. Oregon Shore: Starting February 3rd and lasting for 4 weeks. 11/07/2002 08:18 darren@p 10:Overrun: This alarm could have been caused by PTOC personnel who were on site performing routine maintenance. 11/07/2002 08:17 darren@p 0E:LowExcCurrent,0E:Overrun: These alarms were cleared. The transceiver was replaced but that was not the cause for the drop in current or phase. I checked the coil with a megohmmeter and found that the coil has degraded even more since 8-9-02. The current meg readings are as follows: Pins 1-7 11Mohm Pins 1-6 12.2Mohm Pins 6-7 .6Mohm After the new transceiver was in place the max current was only 2.9A The noise was around 5-6%. 11/06/2002 08:25 darren@p 10:Overrun: Unit will be checked out today while I am on site for trnasceiver 0E. 11/06/2002 08:08 darren@p 0E:LowExcCurrent,0E:Overrun,0E:TestTagFailure: Alarms will be addressed today. The unit will be tuned or replaced if it is found to be the transceiver that has caused the current to drop so drasticly. 11/05/2002 08:14 darren@p 01:ExcessiveNoise,02:ExcessiveNoise,06:ExcessiveNoise,07:ExcessiveNoise,0B :ExcessiveNoise,0F:ExcessiveNoise,10:ExcessiveNoise,11:ExcessiveNoise: These alarms were cleared yesterday by PTOC personnel. 11/04/2002 15:45 scottl@p 01:ExcessiveNoise,02:ExcessiveNoise,06:ExcessiveNoise,07:ExcessiveNoise,0B :ExcessiveNoise,0F:ExcessiveNoise,10:ExcessiveNoise,11:ExcessiveNoise: Clearing panel and will monitor. Need to know if alarms were generated after the site was tuned on Oct. 24th. This will tell PTOC how well the system performed after maint. was done. 11/04/2002 15:40 scottl@p 01:ExcessiveNoise,02:ExcessiveNoise,06:ExcessiveNoise,07:ExcessiveNoise,0B :ExcessiveNoise,0F:ExcessiveNoise,10:ExcessiveNoise,11:ExcessiveNoise: Clearing panel and will monitor. Need to know if alarms were generated after the site was tuned on Oct. 24th. This will tell PTOC how well the system performed after maint. was done. 10/25/2002 11:55 Darren_C All transceivers were re-calibrated for optimum performance. The hit rates for the timer tags were also checked to ensure they were 100%. 10/24/2002 08:48 darren@p 0E:Overrun: Alarms acknowledged. 10/19/2002 08:41 darren@p 0E:Overrun: Alarm acknowledged. 10/18/2002 09:00 dlwarf@p 0E:Overrun: Acknowledged. 10/16/2002 08:44 dlwarf@p 0E:Overrun,10:LowExcCurrent: Acknowledged. 10/12/2002 09:35 dlwarf@p 0E:Overrun: Acknowledged. 10/10/2002 09:16 Dave Figured out that the file upload failure for the past 24 hours is somehow linked to a failure to generate files every six hours as scheduled. pcA'd back into MC1-PC1, stopped and restarted data collection. This action closed the current data file, which had been open for 26:05. Uploaded that file to Gladstone without incident. This action cleared the FTP message on the status line, and generated an "Error Downloading Ack File..." message in the log file. 10/10/2002 08:55 Dave Responded to persistent notices of missing data files. When I logged in I saw, but didn't record, a reference to FTP activity on the status bar. Switched to PTTP upload screen, didn't see any ongoing FTP session, but did find one outstanding file to upload. Did so, without incident. 10/02/2002 08:09 dlwarf@p 03:TestTagFailure,05:BadExcFreq,05:BadOscFreq,05:LowExcCurrent,05:TestTagF ailure,06:TestTagFailure,0A:TestTagFailure,0E:Overrun: Alarms acknowledged. Some caused by recent site visit. 09/30/2002 08:59 Darren_C I visited the site on Friday to check on coil 03. The "Hits per Tag" was around 3.00 and some concern was raised about the coil. I retuned the coil and checked the "Equalizer" circuit and found that it was not adjusted to optimum performance. I retuned and watched for the next 3 days and found that the H/T rate has increased to an average of 7.00. I also remegged the site. I will post the readings to the Master Sheet. 09/23/2002 08:26 dlwarf@p 0E:Overrun: Acknowledged. 09/22/2002 11:57 dlwarf@p 0E:Overrun,12:BadExcFreq: Acknowledged. 09/21/2002 12:56 dlwarf@p 01:Overrun,0E:Overrun: Acknowledged. Site to be visited next week. 09/19/2002 08:36 darren@p 01:Overrun,0E:Overrun: The overruns on the counting window are not attributed to tuning. I could not see any type of pittag that may have been just outside the feild. The transceiver status report did not show any kind of degredation. We will watch to see if this occurs again. The overruns on coil 0E have been an ongoing failure. We have played with the tuning but have not been able to find any fix to the failure. 09/16/2002 08:37 darren@p 0E:Overrun: Alarm acknowledged. 09/15/2002 12:41 dlwarf@p 01:Overrun,0E:Overrun: Acknowledged. 09/09/2002 09:05 darren@p 0E:Overrun,10:LowExcCurrent: Alarms acknowledged. 09/06/2002 11:37 darren@p 0E:Overrun: Alarm acknowledged. 09/02/2002 08:19 dlwarf@p 0E:Overrun: Acknowledged. 09/01/2002 08:33 dlwarf@p 0E:Overrun: Acknowledged. 08/31/2002 09:40 dlwarf@p 0E:Overrun: Acknowledged. 08/30/2002 08:38 dlwarf@p 0B:HighTemp,0E:Overrun: Acknowledged. 08/29/2002 14:29 Don_Warf All transceivers were set to "Unique Off" at 13:15 PST today. 08/29/2002 08:11 darren@p 0B:HighTemp,0E:Overrun: Alarms acknowledged. 08/27/2002 09:09 dlwarf@p 0E:Overrun: Acknowledged. 08/20/2002 10:11 scottl@p 0E:Overrun: Error does not require immediate attention. 08/20/2002 10:10 scottl@p 0E:Overrun: Error does not require immediate attention. 08/17/2002 08:59 darren@p 07:TestTagFailure,0E:Overrun,10:LowExcCurrent: Alarms acknowledged. 08/16/2002 08:11 scottl@p 01:LowExcCurrent,02:LowExcCurrent,03:HighTemp,04:HighTemp,05:HighTemp,06:H ighTemp,07:HighTemp,08:HighTemp,09:HighTemp,0A:HighTemp,0B:HighTemp,0C:Hig hTemp,0D:HighTemp,0E:HighTemp,0E:Overrun,0F:HighTemp,10:HighTemp,11:HighTe mp,12:HighTemp: Problem is being addressed 08/14/2002 14:29 Carter_S Sean Casey reports that he replaced the mica capacitors on new counting window antennas (coil 01, 02) with NPO capacitors. These capacitors have a tighter high voltage rating relative to temperature changes. Although the mica capacitors were a bit noisy, they were not de-tuning. The NPO caps seem to be even better. 08/14/2002 10:30 scottl@p 03:HighTemp,05:HighTemp,06:HighTemp,07:HighTemp,07:TestTagFailure,08:HighT emp,09:HighTemp,0A:HighTemp,0B:HighTemp,0E:HighTemp,0E:Overrun,0F:HighTemp ,11:HighTemp: The cooling compressor may not being providing enough convection cooling to overcome the extreme heat. PTOC is looking into utilizing the plant air system for continuous air supply. 08/09/2002 08:05 scottl@p 03:TestTagFailure,04:BadExcFreq,04:BadOscFreq,04:LowExcCurrent,05:TestTagF ailure,07:BadExcFreq,07:BadOscFreq,07:LowExcCurrent,0A:BadExcFreq,0A:BadOs cFreq,0A:LowExcCurrent,0A:TestTagFailure,0D:Overrun,0E:Overrun,0F:LowExcCu rrent,12:BadExcFreq,12:BadOscFreq,12:LowExcCurrent: These messages were caused by PTOC while performing the meger readings on the antennas. 08/08/2002 11:46 Scott_Li Meger tests on all the antennas were taken 8/7/02. Results were recorded in the master spreadsheet archive on the Kennewick server. 08/05/2002 08:25 darren@p 07:TestTagFailure,0E:Overrun: The test tag failure on coil 07 was not due to any outside interference. The overrun condition on coil 0E did not hamper detection the reader had 9 hits on a tag at 17:57. 08/04/2002 09:11 dlwarf@p 0E:Overrun: Acknowledged. 08/03/2002 12:04 dlwarf@p 0E:Overrun: Acknowledged. 08/02/2002 08:48 Scott_Li 8/1/02, All transceivers were checked for tune and readjusted as nessesary. 08/02/2002 07:58 scottl@p 01:LowExcCurrent,02:BadOscFreq,02:LowExcCurrent,02:Overrun,07:LowExcCurren t,0E:Overrun,0F:LowExcCurrent: most of these erros was generated by PTOC during a routine site visit. 08/01/2002 10:53 Carter_S The fiberglass counting window antennas were successfully replaced on 7/31/02 without de-watering the Oregon Shore ladder at McNary Dam. The new antennas are constructed from a Coplymer Polyproplyene material. --Carter 07/30/2002 08:04 scottl@p 07:TestTagFailure,0B:HighTemp,0E:HighTemp,0E:Overrun,0F:HighTemp: Will continue to work on a final solution to this heat problem. May adjust comparator on Coil 0E in order to try and eliminate overrun condition. Suspect that this problem is directly related to heat. 07/29/2002 08:07 scottl@p 0E:Overrun: Chronic overruns maybe attributed to the antenna leaking. Adjustments have been made to try and correct this problem. Will pursure other options. 07/27/2002 08:23 darren@p 06:HighTemp,0A:HighTemp,0B:HighTemp,0E:HighTemp,0E:Overrun,0F:HighTemp: PTOC personnel are in the process of dealing with the overtemp alarms. We tried a few things to eleviate the Overrun alarms. will monitor 07/25/2002 14:40 scottl@p 07:LowExcCurrent,0B:HighTemp,0D:LowExcCurrent,0E:Overrun,0F:HighTemp,0F:Lo wExcCurrent,12:LowExcCurrent: Low current alarms were generated by ptoc personel, High temp alarms were generated while ptoc was installing air cooling . Will continue to monitor in order to gage the effectiveness of the air cooling method. 07/23/2002 08:16 scottl@p 06:HighTemp,09:HighTemp,0A:HighTemp,0B:HighTemp,0E:HighTemp,0E:Overrun,0F: HighTemp,10:LowExcCurrent: High temp alarms are being addressed 07/22/2002 09:50 scottl@p 06:HighTemp,09:HighTemp,0A:HighTemp,0B:HighTemp,0E:HighTemp,0E:Overrun,10: LowExcCurrent: Temp preoblems are being addressed today... 07/19/2002 16:06 dlwarf@p 0E:HighTemp,0E:Overrun,10:LowExcCurrent: Working on the problems. 07/18/2002 11:35 scottl@p 0E:Overrun: Overruns are not ewxcessive and should be a problem. 07/18/2002 09:31 dlwarf@p 06:HighTemp,09:HighTemp,0A:HighTemp,0B:HighTemp,0E:HighTemp,0E:Overrun,0F: HighTemp,11:HighTemp: Air flow to panels will be ajusted to lower box air temps. 07/17/2002 14:06 scottl@p 0E:Overrun: Not significant 07/17/2002 13:53 Scott_Li As a test to try and alleviate the high temperature alarms at this site, compressed air was plumbed to each set of transceiver enclosures. The air enters the cabnet through the bottom , adjacent to the chase nipple connecting the two enclosures together. Only one air line per set of cabinets was installed. Temperature data was collected from the last two weeks and the data loggers were relaunched.Will evaluate after 1 week of testing and compare temperature data to determine the effectivness of this test. This test began at 1230 pm , 7/17/02. 07/17/2002 09:21 darren@p 03:HighTemp,04:HighTemp,06:HighTemp,09:HighTemp,0A:HighTemp,0B:HighTemp,0E :HighTemp,0E:Overrun,0F:HighTemp,10:LowExcCurrent: The issue of the overtemp is being addressed at this site. We are trying a solution for the heat. I believe the overrun conditions may be heat related. We will watch and see if the overrun conditions subside when the temperature is regulated. 07/15/2002 15:38 darren@p 0E:Overrun: Will check site tomorrow. This alarm has become tough to trace. We will check all aspects of the site. 07/14/2002 12:56 dlwarf@p 03:HighTemp,04:HighTemp,05:HighTemp,06:HighTemp,07:HighTemp,08:HighTemp,09 :HighTemp,0A:HighTemp,0B:HighTemp,0D:HighTemp,0E:HighTemp,0E:Overrun,0F:Hi ghTemp,10:HighTemp,11:HighTemp,12:HighTemp: High temp alarms will be addressed next week. 07/13/2002 16:06 dlwarf@p 03:HighTemp,04:HighTemp,05:HighTemp,06:HighTemp,07:HighTemp,08:HighTemp,09 :HighTemp,0A:HighTemp,0B:HighTemp,0D:HighTemp,0E:HighTemp,0E:Overrun,0F:Hi ghTemp,10:HighTemp,11:HighTemp: High Temp alarms to be addressed next week. 07/06/2002 14:07 darren@p 01:Overrun,0E:Overrun: Inadvertent noise. These coils were looked at on 7-5-02 at about 11:00. There did not seem to be any overrun conditions at that time. 07/05/2002 08:43 scottl@p 01:Overrun,0E:Overrun,10:LowExcCurrent: Will respond to these overruns today. 07/02/2002 08:49 Darren_C I was on site yesterday. I removed the HOBO temp from coil 01 at MCX. I will download this data for Earl. I replaced transceiver 0B at MC2, the transceiver had failed, it will be checked out in the lab but it appears that the RAM for the +VE has failed. The unit was tuned and the buffer was cleared. I placed two (2) HOBO temps at MC1, one outside underneath the sunshield and one inside the enclosure of coils 0B,0C. The data will be collected for 6 days. 06/29/2002 10:16 scottl@p 01:TestTagFailure: acknoledged 06/26/2002 08:24 scottl@p 10:HighTemp: Currently working on possable fixes to the high temp situation 06/26/2002 08:23 scottl@p 0F:HighTemp: Currently working on possable fixes to the high temp situation 06/26/2002 08:21 scottl@p 0E:HighTemp: Currently working on possable fixes to the high temp situation 06/26/2002 08:14 scottl@p 0B:HighTemp: Currently working on possable fixes to the high temp situation 06/26/2002 08:12 scottl@p 0A:HighTemp: Currently working on possable fixes to the high temp situation 06/26/2002 08:11 scottl@p 09:HighTemp: Currently working on possable fixes to the high temp situation 06/26/2002 08:10 scottl@p 07:TestTagFailure: No appearent reason for the testag failure 06/26/2002 08:09 scottl@p 06:HighTemp: Currently working on possable fixes to the high temp situation 06/17/2002 14:32 Scott_Li The transceiver status report interval was changed to report every 60 minutes on all transceivers at ~1420 , 6/17/02 06/17/2002 13:34 prentice 12:ExcessiveNoise: 12:ExcessiveNoise: 12:ExcessiveNoise: 12:ExcessiveNoise: 12:ExcessiveNoise: 12:ExcessiveNoise: 12:ExcessiveNoise: 12:ExcessiveNoise: 12:ExcessiveNoise: 12:ExcessiveNoise: 12:ExcessiveNoise: 12:ExcessiveNoise: 12:ExcessiveNoise: corrected 06/17/2002 13:34 prentice 12:ExcessiveNoise: 12:ExcessiveNoise: 12:ExcessiveNoise: 12:ExcessiveNoise: 12:ExcessiveNoise: 12:ExcessiveNoise: 12:ExcessiveNoise: 12:ExcessiveNoise: 12:ExcessiveNoise: 12:ExcessiveNoise: 12:ExcessiveNoise: 12:ExcessiveNoise: 12:ExcessiveNoise: 12:ExcessiveNoise: 12:ExcessiveNoise: corrected 06/17/2002 13:34 prentice 12:ExcessiveNoise: 12:ExcessiveNoise: 12:ExcessiveNoise: 12:ExcessiveNoise: 12:ExcessiveNoise: 12:ExcessiveNoise: 12:ExcessiveNoise: 12:ExcessiveNoise: 12:ExcessiveNoise: 12:ExcessiveNoise: 12:ExcessiveNoise: corrected 06/17/2002 13:34 prentice 12:ExcessiveNoise: 12:ExcessiveNoise: 12:ExcessiveNoise: 12:ExcessiveNoise: 12:ExcessiveNoise: 12:ExcessiveNoise: 12:ExcessiveNoise: 12:ExcessiveNoise: 12:ExcessiveNoise: 12:ExcessiveNoise: corrected 06/17/2002 13:34 prentice 12:ExcessiveNoise: 12:ExcessiveNoise: 12:ExcessiveNoise: 12:ExcessiveNoise: 12:ExcessiveNoise: 12:ExcessiveNoise: 12:ExcessiveNoise: 12:ExcessiveNoise: 12:ExcessiveNoise: 12:ExcessiveNoise: 12:ExcessiveNoise: 12:ExcessiveNoise: 12:ExcessiveNoise: 12:ExcessiveNoise: corrected 06/17/2002 13:34 prentice 12:ExcessiveNoise: 12:ExcessiveNoise: 12:ExcessiveNoise: 12:ExcessiveNoise: 12:ExcessiveNoise: 12:ExcessiveNoise: 12:ExcessiveNoise: 12:ExcessiveNoise: corrected 06/17/2002 13:34 prentice 12:ExcessiveNoise: 12:ExcessiveNoise: 12:ExcessiveNoise: 12:ExcessiveNoise: 12:ExcessiveNoise: 12:ExcessiveNoise: 12:ExcessiveNoise: 12:ExcessiveNoise: 12:ExcessiveNoise: 12:ExcessiveNoise: 12:ExcessiveNoise: 12:ExcessiveNoise: 12:ExcessiveNoise: 12:ExcessiveNoise: 12:ExcessiveNoise: 12:ExcessiveNoise: corrected 06/17/2002 13:34 prentice 12:ExcessiveNoise: 12:ExcessiveNoise: 12:ExcessiveNoise: 12:ExcessiveNoise: 12:ExcessiveNoise: 12:ExcessiveNoise: 12:ExcessiveNoise: 12:ExcessiveNoise: 12:ExcessiveNoise: corrected 06/17/2002 13:34 prentice 12:ExcessiveNoise: 12:ExcessiveNoise: 12:ExcessiveNoise: 12:ExcessiveNoise: 12:ExcessiveNoise: 12:ExcessiveNoise: 12:ExcessiveNoise: corrected 06/17/2002 13:34 prentice 12:ExcessiveNoise: 12:ExcessiveNoise: 12:ExcessiveNoise: 12:ExcessiveNoise: 12:ExcessiveNoise: 12:ExcessiveNoise: corrected 06/17/2002 13:34 prentice 12:ExcessiveNoise: 12:ExcessiveNoise: 12:ExcessiveNoise: 12:ExcessiveNoise: 12:ExcessiveNoise: corrected 06/17/2002 13:28 prentice 12:ExcessiveNoise: 12:ExcessiveNoise: 12:ExcessiveNoise: 12:ExcessiveNoise: corrected 06/17/2002 13:28 prentice 12:ExcessiveNoise: 12:ExcessiveNoise: 12:ExcessiveNoise: corrected 06/17/2002 13:28 prentice 12:ExcessiveNoise: 12:ExcessiveNoise: corrected 06/17/2002 13:27 prentice 12:ExcessiveNoise: correcte 06/17/2002 07:44 scottl@p 07:TestTagFailure: No appearent reason for testtag failure. Noticed that Coil 0B has High temperature alarm. This is not good . Will look into alternate ways of cooling the enclosures and also install a hobo temp to verify what the internal temp is. 06/14/2002 15:59 Don_Warf Coils 01 and 02 were randomly turned off and on between the hours of 5pm and 7pm on 6/11/02 and between the hours of 1pm and 4pm on 6/12/02. This was done for maintenance and evaluation purposes. 06/14/2002 12:13 Carter_S On Tuesday, June 11, 2002, the counting window transceivers were cycled on and off between 18:00 and 19:00 to observe fish behavior. The next day, there was a meeting at the McNary Oregon Shore Ladder on Wednesday around 14:00. Steve Richards, Paul Ocker, Earl Prentice, Sandy Downing, Don Warf and Carter Stein were there. In addition, Sean Casey and John Mueller from Digital Angel (aka Destron/Fearing) were there. All power to the counting window PIT tag antennas was removed around 14:10. Steve Richards remarked that the fish were still exhibiting the same behavior as when the antenna were on. He took video of the fish when the antennas were turned off to compare to the video he took when the antennas were turned on. To be safe, some electrical measurements were made on the structures that surround the counting window. A ground strap was installed on the steel, white, back-board for safety reasons. All power to the counting window PIT tag antennas was restored around 14:45. The distance between the back board and the window was 16.5 inches. An adjustment was made to increase the width to 16.75 inches. A 'bubble vortex' was observed that moved variably from the upper left hand corner of the window down into the middle of the window. Some of the observers hypothesized that this may affect fish behavior in some way. The new antennas have not been installed yet. Other issues related to pre- existing electrical equipment were brought to Brad Eby's attention and he will work with the project to determine any course of action deemed necessary. 06/12/2002 08:12 darren@p 01:TestTagFailure,02:BadOscFreq,02:LowExcCurrent: It appears that there may have beeen some personnel on site. I will confirm this with Don and Sean today. 06/05/2002 08:22 Darren_C Utility PC'S were installed yesterday. I verified communications via PCA. 05/31/2002 08:51 Darren_C The TR2010 copper to fiber media converters have been installed and the phone lines are hooked up. The numbers are as follows: MC1 (541) 922-3430 and MC2 (541) 922-3653. These have not yet been hooked up to PC1 at either site. This will be done next week when the Utility PC's are installed. The transceivers have all been set send status reports every 360 minutes or (1) once per file. 05/26/2002 13:28 Darren_C The site finally loaded. Two files were loaded. I still can't explain why we can't get into any site at McNary via PCA. I will try and get to the bottom of this. 05/26/2002 09:46 Darren_C I am unable to PCA into anything at McNary. I will check the next load to see if it loads by itself. If not actions will be taken to ensure Data collection. 05/25/2002 08:58 darren@p 02:BadOscFreq,02:LowExcCurrent: Alarms were generated by site personnel performing maintenance. 05/23/2002 16:59 Carter_S Date: Thu, 23 May 2002 12:02:24 -0700 From: Darren Chase To: "sandy.downing" CC: Carter Stein , Don Warf , scott livingston Subject: Reader Unique settings Sandy, I have turned all of the transceiver unique settings to "off" on the coils that you had requested. They are as follows: Bradford "A" branch: 01,01,03,04,09,0A,0F, and 10 Branch "B": 11,12,13,14,17,18,1F, and 20 Cascade Island: 01,02,0B,0C,0D,0E,0F, and 10 McNary Or.:03,04,07,08,0B,0C,0D, and 0E McNary Wa: 05,06,07,08,0D,0E,0F, and 10 If these are not correct please let me know. 05/21/2002 08:49 darren@p 07:TestTagFailure: The test is firing. It may need to be adjusted on the hit rate for 100% to verify constant firing. 05/20/2002 10:38 darren@p 01:TestTagFailure,02:BadOscFreq,02:LowExcCurrent,02:TestTagFailure: Alarms were generated while personnel was performing maintenance. 05/19/2002 16:06 Don_Warf Still no IP connection to Mcnary. PCAed into MCJ via modem to verify that data is being collected. 05/19/2002 14:02 Don_Warf Could not establish PCA session with any Mcnary machine. Will contact the COE in the morning. 05/17/2002 17:49 Dave Hadn't heard from MC1 since this morning. pcA'd in and manually uploaded one outstanding file. 05/17/2002 08:12 Darren_C A Data logger was placed in line with the AC that is supplying the transceivers at the counting window. It was set to collect Data every 15 seconds giving us about 29 hrs. of Data. I will be downloading this Data today. Before I placed the Data logger in line I had to retune transceiver 01, it had shifted from 3% phase, and 1-3% sig to 1% phase, and 15-20%sig. To retune I had remove a 1000pf jumper and adjust the capacitor. After talking to the site personnel at the window it was brought to my attention that water level had dropped yesterday after I had left about 4 inches but it was at the same level as the day before when I arrived yesterday yet the transceiver needed to be tuned. I will post the findings of the AC monitoring. 05/16/2002 11:30 Darren_C After a conference call it was decided that we would install the 75W power supply into transceiver 01. I replaced the mother board and retuned the transceiver. I had to add an additional 1000pf to the capacitor bank to tune the transceiver. I noted the Input AC and set the +VE accordingly. The current settings are as follows: Input +VE Phase Sig Current 121.7Vac 14.1V 3% 1-3% 4.4A The Phase, Sig, and Current measurements were taken while the door was closed. I was present for about an hour and did not witness any deviation from those readings. When I got to the Pittag room on the oregon shore I noticed that the noise reports for coil 01 was showing peak and FDXB levels in the high 60's I checked tune on all ladder transceivers and then returned to the counting window, but when I got there the transceivers were back to the original readings? We will continue to monitor this phenomenon. 05/12/2002 10:09 scott Noticed a drastic decline on the number of detections on counting window coil 01. visited the site on 5/12 as an ongoing effort to try and understand the characteristics of this monitor. Slightly retuned the transceiver and and noted the parametrics. Water level in the ladder had dropped by about 2 inches from the previous day.Looking at efficiencies for today, both antennas are reading at 72 percent. Also fastened down some of the removable railing located southwest of the Coil 02 to minimize the possability of vibration through out the facility during windy conditions. 05/12/2002 08:48 darren@p 01:LowExcCurrent,01:TestTagFailure,02:LowExcCurrent,02:TestTagFailure: Alarms were caused when the water levels changed. This site is being monitored by PTOC personnel very closely. I believe some adjustments were made yesterday. 05/10/2002 14:37 Anthony On 5/8/02 I delivered a parts locker and fold up table to the MC1 pit tag room. Check tuning on all transceiver and made minor tuning adjustment to transceiver I.D. 0D (14:41:44). 05/10/2002 13:46 Scott_Li Returned to the counting window at 1330 hrs on 5/9/02. Transceiver 02 noise floor was low~ 2-6 percent on average but was spiking every 10 seconds or so up to 50,60,70 % the entire time that I was there. Could not isolate what was causing the problem. Without anything else to try, I replaced the analog pcb and retuned antenna. This fixed the sensitivity problem that we have reported in the past, but did not fix the periodic noise spikes. Thought that it might be the DC converter becomming unstable at the voltage setting , 14.7 Vdc but the noise was persistent throughout the entire adjustment range. Will venture down again today and check on the lastest phenomenon. 05/09/2002 12:04 Scott_Li It was noticed yesterday 5/8/02 , that in a ~ 4.5 hr time span , the antenna phase had drifted on coil 01 from 2% to 7 percent and coil 02 from 2% to 5%. Anthony Carson retuned the antennas at 1620 hrs and brought the antennas back to 1 % phase and 1-3 % noise. It appears that water flunctuations in the ladder are having a big effect on the tune of the antennas but only require a very slight adjustment to bring them back into tune. On 4/8/02 1030 hrs, it was noticed that the water level had dropped in the ladder from the previous day by about 2 inches and another inspection at 1430 hrs indicated that the water had dropped about another inch. Talked with Roger Clark ( Digital Angel ) this moring about how these antennas respond to water level flunctuations and he indicated that testing was done with the antenna completely dry and then completely submerged and noticed about 1000 pf difference between the two conditions. This maybe why when the water level changes in the ladder , only a slight adjustment is required to retune the antenna. Another issue that we are dealing with is excessive noise in the reader at random times in a day, but no phase shift. This behaviour could be related to the instablity of the DC-DC , 50 watt converter that sean wants upgraded to the 75 watt module. Roger indicated that he only has one of these 75 watters and will be sending it out today. In the mean time, we continue to try and make improvements were we can. 05/08/2002 15:47 Scott_Li Re visited the counting window today due to low efficiency on coil 01. The electrical parametrics had not changed from the previous day , but did notice a slight phase shift indicating slight detuning of the antenna. Looking at the noise reports for the previous day 5/7 , notice the drastic change in noise levels after the reader was tuned and enclosure backpanel was grounded to the AC. 2002/05/07 09:40:44 11% ==*====------------- 2002/05/07 09:42:44 2% *=|====------------- 2002/05/07 09:36:45 10% ==*====------------- 60% =======|===*======== 60% ======|====*======== 2002/05/07 09:38:44 12% ==*====------------- 100% =======|===========* 79% ======|========*==== 2002/05/07 09:40:44 11% ==*====------------- 86% =======|=========*== 86% ======|==========*== 2002/05/07 09:42:44 2% *=|====------------- 58% =======|===*======== 13% ==*===|============= 2002/05/07 09:44:44 2% *=|====------------- 20% ===*===|============ 16% ==*===|============= 2002/05/07 09:46:44 2% *=|====------------- 49% =======|=*========== 49% ======|==*========== 2002/05/07 09:48:44 2% *=|====------------- 91% =======|==========*= 71% ======|=======*===== 2002/05/07 09:59:00 0% *=|====------------- 47% =======|=*========== 39% ======|*============ 2002/05/07 10:01:00 3% *=|====------------- 59% =======|===*======== 47% ======|==*========== 2002/05/07 10:03:00 1% *=|====------------- 69% =======|=====*====== 69% ======|======*====== 2002/05/07 10:05:00 0% *=|====------------- 28% =====*=|============ 28% =====*|============= 2002/05/07 10:07:00 0% *=|====------------- 55% =======|==*========= 42% ======|=*=========== 2002/05/07 10:09:00 0% *=|====------------- 17% ==*====|============ 17% ==*===|============= 2002/05/07 10:11:00 0% *=|====------------- 59% =======|===*======== 16% ==*===|============= 2002/05/07 10:13:00 0% *=|====------------- 27% ====*==|============ 21% ===*==|============= 2002/05/07 10:15:00 0% *=|====------------- 63% =======|====*======= 48% ======|==*========= The FDXB noise levels is what bothers me about this. Today I did find a hand rail next to this coil that was slopping around and could very well be the source of noise during incliment weather conditions. This what imediately corrected. Also noticed the lowered water level in the ladder through the counting window and the behaviour of the fish moving through the antenna. The fish are virtually sliding their bellies across the bottom of the antenna as they pass through. Desirable? This may be the reason that the antennas need to be constantly , slightly optimized. Will check noise reports tomorrow morning along with efficiencies while trying to understand what could be at the root of this antenna. 05/07/2002 13:11 window_a Hello!! Heres the status on the counting window antennas... As of this morning when I first arrived, Reader 01: Phase: 1 , Signal: 8-12 %, Current: 4.3 Amps. Reader 02: Phase: 1, Signal: 4-8 %, Current 4.2 Amps. Noticed that reader 02 was very sensitive in the fact that barely tapping on the reader enclosure would cause a drastic , sharp incline in noise. From past experience , this problem is caused by , not soley, but can be attributed to loose grounds or power supply back plane screws not tight, or just not tuned well. I checked and tightened all mounting screws in the transceiver enclosure, Established better continuity from the reader door to chassis ground. This seemed to help the reader not be so sensitive to vibration. One drastic change that I did make is, I ran a ground strap from the AC duplex outlet ground to the transceiver enclosure backpanel. This panel needs to be securely grounded, not only for the counting window but for all the adult enclosures. After I did that, reader 02 was not nearly as sensitive to vibration and tuned very well. Retuned both coils with the following results. As of 10:45 PST Coil 01 : Phase 3, Noise: 3 % Current 4.4 Amps , Exciter: 14.2 Vdc Coil 02 : Phase 3, Noise: 0-3 % Current: 4.6 Amps Exciter: 14.6 Vdc. Bottom Line, Both Coils 01,02 tuned up very nicely and are extremely quiet and stable for the time being. Keep in mind that over the last week , it has been extremely windy at the facility. This has been proven to be the cause of excessive noise levels in the instruments . We have done about everthing we can do to prevent vibration at the facility but cant control mother nature. I hope what I have done helps improve the reading efficiency for coil 02. I will be monitoring these two coils to see if we have made any long term improvements. Scott... 05/06/2002 11:06 Scott_Li Set the file submission frequency to upload 4 times per day. 05/06/2002 08:26 scottl@p 02:BadOscFreq,02:LowExcCurrent,02:TestTagFailure: These alarms were generated due to maintenence being perfromed on the readers. Will monitor for re occurring problem. 05/06/2002 08:23 scottl@p 01:LowExcCurrent,01:TestTagFailure: These alarms were generated due to maintnence being performed on the readers. Will monitor for re occurring problem. 05/03/2002 10:09 Darren_C Files are set to 4 per day on PC1 and PC2. 05/02/2002 17:13 scott Found that the antenna cables for counting window antennas ( coil 01,02 ) were backwards. Corrected problem and changed out analog pcb on xcvr 02 and retuned both coils. This was done at 1:45 pst. Periodic noise spikes were suspected to be caused by high winds creating fibrations in the facility. Will revisit the site tomorrow for more diagnostics. Turned the reader unique setting to off on coils 03,04,05,06 as per Sean Casey's request. This was done at 3:20 pst. Also, set the reader status dump interval to 120 mins on coils 01,02. 05/02/2002 08:11 Darren_C This an amendment to the previous entry in that the reports were set to every 12 (720 min) hours not every 6 hours as first reported. 05/01/2002 21:28 Darren_C The site was visited while pittag room floors were being cleaned. I checked all transceivers on both sides. I changed all transceivers so they would only send status reports every 6 hours. The noise reports were already turned off. I also looked at the counting window transceivers and was able to retune without replacing the analog board on transceiver 02. I will talk with Sean Casey tomorrow about this and if necessary rectify the situation. 04/30/2002 09:35 dlwarf@p 08:TestTagFailure: Will watch for further alarms. 04/29/2002 08:35 darren@p 01:TestTagFailure: Will check this on the next site visit. 04/28/2002 09:04 darren@p 08:TestTagFailure: The timer tag is firing on a regular basis but I don't see any reason for the misfire. We will keep an eye on this for further alarms. 04/27/2002 07:36 darren@p 01:TestTagFailure: Unit will be looked at on the next site visit. 04/26/2002 20:19 scottl_l Responded to the data submission problem and found the fiber optic comms devices in the power house phone room had been completely dismantled. Obviously the COE personell decided to try and help us in some way and never completed the task for whatever reason. re-established comms links for both interrogation sites and manually submitted files for mc1 but not mc2. Will reensure that comms have been established and is stable. The communications installation in th power house phone room will be brought up to PSMFC standards one way or the other starting on Wednesday of next week to avoid this interruption in the future. The initial installation was botched from the beginning and was patched on the fly due to other commitments. 04/26/2002 19:03 scott_li Responded to the data submission problem and found that the fiber optic media converters and connecting devices had been completely dismantled in the phone room located in the power house. Suspect that COE employees decided to help in some way and never finished what they setout to do. Reconnected devices and and re-established links to mc1 and 2. manually sent cued files from mc1 and was successful but submit mc2 data allthough the fiber link to the mc2 pitt room was verified. Will ensure that mc2 data link and file submission is back online via PCA. The phone room pittag nutshell needs to completely revisited and done to PSMFCstandards and will get a big face lift on wednesday of next week to completely severe all possabilities of this occurance happening again. I, Scott, new that this installation was a complete failure by the contractors and other people involved but patched things up too at least get online until we could do this right. 04/26/2002 10:29 Dave Haven't received data files from MC1 or MC2 since noon yesterday (4/25). Could not establish a pcA connection to MC1-PC1, MC1-PC2, MC2-PC1 or MC2-PC2. MCJ and MCX are sending files and are accessible through remote control. 04/25/2002 20:32 ptagdev@ 01:ExcessiveNoise,02:ExcessiveNoise,07:ExcessiveNoise,08:ExcessiveNoise,09 :ExcessiveNoise,0A:ExcessiveNoise,0D:ExcessiveNoise,0F:ExcessiveNoise,10:E xcessiveNoise,11:ExcessiveNoise,12:ExcessiveNoise: Acknowledged 'Noise' alarms to clear red lights on 'MinList' annunciator panel. (These will now show up on the new 'NoiseEventsOnly' panel) Doug Clough 04/21/2002 18:08 carters@ 01:ExcessiveNoise,02:ExcessiveNoise,0B:ExcessiveNoise,0F:ExcessiveNoise,10 :ExcessiveNoise,11:ExcessiveNoise,12:ExcessiveNoise: noise, noise, noise 04/16/2002 11:51 Dave I added BO1, BO2, MC1, and MC2 to the 2002 log menu in the Interrogation Site Event Logs web page, accessible by the public at "www.pittag.org/Ptoc_OM/event_log/index.html". 04/15/2002 17:15 carters@ 12:LowExcCurrent: Cleared remaining lights. Previous test OK. Doug Clough 04/15/2002 17:13 carters@ 01:ExcessiveNoise,01:LowExcCurrent,01:TestTagFailure,02:ExcessiveNoise,03: ExcessiveNoise,03:LowExcCurrent,03:TestTagFailure,04:ExcessiveNoise,04:Tes tTagFailure,05:ExcessiveNoise,05:LowExcCurrent,06:ExcessiveNoise,06:LowExc Current,06:TestTagFailure,07:LowExcCurrent,07:TestTagFailure,08:ExcessiveN oise,09:TestTagFailure,0A:ExcessiveNoise,0A:LowExcCurrent,0A:TestTagFailur e,0B:ExcessiveNoise,0B:LowExcCurrent,0C:ExcessiveNoise,0C:LowExcCurrent,0D :ExcessiveNoise,0D:LowExcCurrent,0E:ExcessiveNoise,0E:LowExcCurrent,0F:Exc essiveNoise,0F:LowExcCurrent,0F:TestTagFailure,10:ExcessiveNoise,11:Excess iveNoise,12:ExcessiveNoise: Acknowledged WEIR 279 LowExcCurrent to make sure permissions problem is fixed. Doug Clough 15Apr2002 04/15/2002 08:43 Carter set file checking on for mcx, mc1, mc2 at 8:45 4/15/02. 04/13/2002 09:07 dlwarf@p 01:ExcessiveNoise,01:LowExcCurrent,01:TestTagFailure,02:ExcessiveNoise,03: ExcessiveNoise,03:LowExcCurrent,03:TestTagFailure,04:ExcessiveNoise,04:Tes tTagFailure,05:ExcessiveNoise,05:LowExcCurrent,06:ExcessiveNoise,06:LowExc Current,06:TestTagFailure,07:LowExcCurrent,07:TestTagFailure,08:ExcessiveN oise,09:TestTagFailure,0A:ExcessiveNoise,0A:LowExcCurrent,0A:TestTagFailur e,0B:ExcessiveNoise,0B:LowExcCurrent,0C:ExcessiveNoise,0C:LowExcCurrent,0D :ExcessiveNoise,0D:LowExcCurrent,0E:ExcessiveNoise,0E:LowExcCurrent,0F:Exc essiveNoise,0F:LowExcCurrent,0F:TestTagFailure,10:ExcessiveNoise,11:Excess iveNoise,12:ExcessiveNoise,12:LowExcCurrent: Alarms generated during install. 04/09/2002 14:56 Carter_S Automated data collection and pttp submission from the McNary Oregon Shore adult ladder (and counting window) began today around 14:00 PDT. Data that has been collected since 16:00 on 4/3/02 was downloaded and submitted in interrogation file MC102099.S. 04/05/2002 08:47 Scott_Li Pittag data is being collected as of 1600 4/3/02. Data is being stored on the xcvr buffers and will be periodically downloaded via the maintenance port and submitted to PTAGIS while the pittag room is being configured. 03/30/2002 18:13 Darren_C As Friday 3-29-02 the Oregon ladder does not have any other failures as far as coils go. The antenna cables have been dressed and all were re megoohm tested. We did not get to attach a transceiver to the antennas but given that there were no new failures the tuning should not have changed. 03/28/2002 14:55 Carter_S Virtual timer tags set up for all coils. 03/11/2002 09:23 Carter_S Brad Eby reports that the Oregon Shore ladder at McNary watered up last Friday, 3/8/02 at 9:00 am. The picket leads and backboard to the counting window should be installed today. 03/07/2002 15:34 Carter_S Set up coil configuration in ptagis3 database. 03/07/02 15:23 carters Initial log creation for MC1 ####End of Event Log for MC1###