EVENT LOG FOR SITE MC2 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/20/2002 08:48 darren@p 08:TestTagFailure,09:TestTagFailure: After checking the files I cannot find any direct cause for these failures. We will be on site soon for maintenance the transceivers will all be addressed at that time. . 12/11/2002 09:58 darren@p 01:LowExcCurrent,01:Overrun: Alarms were generated by PTOC personnel while performing maintenance. . 12/09/2002 08:44 darren@p 01:Overrun,01:TestTagFailure,08:TestTagFailure: The "overrun" condition on coil 01 will be looked at today . The test tag failure on coil 08 does not have a distinct reason for failure the timer tag will be adjusted for 100% hit rate while we are on site. . 12/06/2002 08:15 darren@p 01:Overrun: After viewing the exciter report it looks as if the transceiver is drifting out of tune. The capacitor will need to be adjusted. . 11/27/2002 08:55 darren@p 01:ExcessiveNoise,02:ExcessiveNoise,03:ExcessiveNoise,04:ExcessiveNoise,05 :ExcessiveNoise,06:ExcessiveNoise,07:ExcessiveNoise,08:ExcessiveNoise,0B:E xcessiveNoise,0C:ExcessiveNoise,0E:ExcessiveNoise,0F:ExcessiveNoise,10:Exc essiveNoise: Alarms will be cleared to see what changes have been made to the performance of the transceivers since the site was visited on 11-22- 02. . 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:32 darren@p 03:LowExcCurrent,05:BadExcFreq,05:BadOscFreq,05:LowExcCurrent,06:TestTagFa ilure,07:LowExcCurrent,08:LowExcCurrent,0C:LowExcCurrent,0C:Overrun,0E:Tes tTagFailure,0F:LowExcCurrent,10:LowExcCurrent,10:TestTagFailure: Alarms were generated by PTOC personnel while performing tuning and maintenance on transceivers. . 11/20/2002 09:13 darren@p 09:TestTagFailure: The unit will be looked at Thursday when the site is visited. There does not appear to be any significant indicators for the failure. . 11/19/2002 16:01 darren@p 08:Overrun: Alarm is being investigated by PTOC personnel. Unit will be addressed on next site visit. The exciter report did not show any indications as to the alarm. . 11/18/2002 08:17 scottl@p 08:Overrun,08:TestTagFailure: Will monitor for excessive overruns. . 11/12/2002 08:30 darren@p 08:TestTagFailure,09:TestTagFailure: Alarm acknowledged. . 11/08/2002 08:53 scottl@p 01:ExcessiveNoise,02:ExcessiveNoise,03:ExcessiveNoise,04:ExcessiveNoise,0C :ExcessiveNoise: Alarms for excessive noise are being investigated by PTOC. . 11/08/2002 08:14 darren@p 09:TestTagFailure: Alarm was caused by the status report and timer tag firing at the same time. I have tried to alter the firing time but for some reason the time does not seem to be changing. I will check into this and try to alter one of the two again. . 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:23 darren@p 08:Overrun,09:TestTagFailure: The overrun condition on coil 08 is being investigated. I will try to alter either the status report or the firing of the timer tag to try and separate the times. . 11/06/2002 14:11 darren@p 08:Overrun: Overrun acknowledged. . 11/06/2002 08:14 darren@p 0F:LowExcCurrent: The alarm level was lowered to 2300mA yesterday. This is 200 mA lower than the tuned amperage. . 11/05/2002 11:15 scottl@p 01:ExcessiveNoise,02:ExcessiveNoise,03:ExcessiveNoise,04:ExcessiveNoise,0C :ExcessiveNoise: Will be monitored for future instances and or elevated counts. . 11/05/2002 09:39 darren@p 08:Overrun,08:TestTagFailure,09:TestTagFailure,0C:LowExcCurrent,0F:LowExcC urrent: The overrun condition on coil 08 is ongoing. The test tag failures do not have any direct cause we will monitor for further failures. The lowExcCurrent alarms need to changed on the transceivers to reflect changes sinces last tuning. . 11/04/2002 15:39 scottl@p 01:ExcessiveNoise,02:ExcessiveNoise,03:ExcessiveNoise,04:ExcessiveNoise,06 :ExcessiveNoise,07:ExcessiveNoise,08:ExcessiveNoise,0A:ExcessiveNoise,0C:E xcessiveNoise,0E:ExcessiveNoise,10: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 09:38 darren@p 08:Overrun,09:TestTagFailure: Overrun alarm acknowledged. I will check into the test tag failure as site is tuned. 10/19/2002 20:38 Darren_C I have not been able to PCA into any Walla Walla district site for the year, but only from home. I will check again in the morning to find out what is happening with the site. 10/19/2002 08:42 darren@p 08:Overrun: Alarm acknowledged. 10/18/2002 09:01 dlwarf@p 08:Overrun: Acknowledged. 10/16/2002 08:46 dlwarf@p 08:Overrun: Acknowledged. 10/12/2002 09:30 dlwarf@p 08:Overrun,09:TestTagFailure: Acknowledged. 10/02/2002 08:10 dlwarf@p 08:Overrun,08:TestTagFailure,09:TestTagFailure: Acknowledged. 09/23/2002 08:28 dlwarf@p 08:Overrun: Acknowledged. 09/21/2002 12:58 dlwarf@p 08:Overrun,09:TestTagFailure: Acknowledged. 09/19/2002 08:39 darren@p 08:Overrun,09:TestTagFailure: Alarm on coil 08 are an ongoing failure. We have played with the tuning of the transceiver and have not been able to find a suitable solution. We will investigate other avenues for fixing the overruns. The test tag failure is unknown. 09/16/2002 08:17 darren@p 08:Overrun: Alarm acknowledged. 09/15/2002 12:42 dlwarf@p 08:Overrun,08:TestTagFailure: Acknowledged. 09/14/2002 13:42 Darren After veiwing the information from Sean Casey it was determined that coil 03 was in need of being looked at. Sean felt that the Equalizer circuit may be out of tolerance. I inspected this circuit and found that he was correct. I retuned the equalizer for optimim performance. Although the coil is shorted the hits per fish may go up. We will watch this coil for that reason. 09/14/2002 07:57 dlwarf@p 03:TestTagFailure,08:Overrun,08:TestTagFailure: Alarms caused by maint. activities. 09/09/2002 09:08 darren@p 08:Overrun,09:TestTagFailure: Temperature: 42C Exciter power: 15.2V ~08-16 09/09/02 00:59:20 ALARM Exciter current: 4.0A Signal level: 6% ~08-16 09/09/02 00:59:20 ALARM Exciter phase: 2% Sync input: NO ~08-16 09/09/02 00:59:21 ALARM Battery: OK Status: Slave ~08-16 09/09/02 00:59:21 ALARM TestTag delay: 60 min Report delay: 60 min ~08-16 09/09/02 00:59:21 ALARM Current gain: 112% Current alarm: 3500mA This is the status report for coil 08 it does show any apparent reason for all of the overruns. We will address on the next trip down. 09/06/2002 11:42 darren@p 08:Overrun,08:TestTagFailure,09:TestTagFailure: Alarms acknowledged. 09/01/2002 08:36 dlwarf@p 08:Overrun: Acknowledged. 08/31/2002 09:38 dlwarf@p 08: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:31 darren@p 08:Overrun,09:TestTagFailure: Alarms acknowledged. 08/27/2002 09:11 dlwarf@p 08:Overrun,09:TestTagFailure: Acknowledged. 08/23/2002 09:04 scottl@p 08:Overrun: 08 has a history of chronic overruns. Attempts have been made to correct this condition but did not significantly reduce the daily counts. 08/21/2002 08:51 darren@p 08:Overrun,09:TestTagFailure: Alarms have been acknowledged. 08/20/2002 10:07 scottl@p 08:Overrun,08:TestTagFailure,09:TestTagFailure: Errors do not require immediate attention. 08/17/2002 09:01 darren@p 08:Overrun,08:TestTagFailure: Alarm acknowledged. 08/16/2002 08:22 scottl@p 08:Overrun,09:TestTagFailure: Errors no eccessive 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/04/2002 09:14 dlwarf@p 08:Overrun,09:TestTagFailure: Acknowledged. 08/03/2002 12:07 dlwarf@p 08:Overrun,09:TestTagFailure: Acknowledged. 08/02/2002 08:48 Scott_Li 8/1/02, All transceivers were checked for tune and readjusted as nessesary. 08/02/2002 08:47 darren@p 01:TestTagFailure,07:LowExcCurrent,07:Overrun,08:LowExcCurrent,08:Overrun, 0C:LowExcCurrent,10:LowExcCurrent,10:Overrun: Alarms were generated by PTOC personnel and Digital Angel personnel while on site performing some maintenance. 07/30/2002 08:11 scottl@p 01:TestTagFailure,08:Overrun: These two problem will be addressed sometime this week... 07/23/2002 09:31 scottl@p 01:TestTagFailure,08:Overrun,09:TestTagFailure: The overrun condition for coil 08 will be addressed sometime this week. 07/18/2002 11:34 scottl@p 01:TestTagFailure: Status report indicates that the noise level for this coils is at 25 percent. Could possably be the reason for the testag failures. Will respond 7/19. 07/15/2002 15:35 darren@p 01:TestTagFailure,08:Overrun: There is no apparent reason for either failure. The site will be visited tomorrow. 07/06/2002 14:13 darren@p 08:Overrun: Inadvertent noise. This site was visited on 7-5-02 at 11:30 for this problem. The transceivers were looked at and there did not appear to be any problems with the overrun condition. Transceiver was retuned and checked for overrruns none were present. Transceiver is reading test tags and pittags. Will monitor. 07/05/2002 08:47 scottl@p 01:TestTagFailure,08:Overrun,08:TestTagFailure,0B:TestTagFailure: Will address these overruns today, Tune transceivers and see if that will correct the situation, Maybe some broadcat interference. 07/02/2002 11:01 scottl@p 09:TestTagFailure: No appearent reason for the failure. 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/30/2002 09:38 scottl@p 0B:BadExcFreq,0B:BadOscFreq,0B:LowExcCurrent,0B:TestTagFailure: Looks as if transceiver has failed. Will respond Monday for repair. 06/28/2002 15:41 Scott_Li |0F| 83 | 53 |10| WEIR TOTAL: 136 +--+-------------------------+--+ |0D| 79 | 53 |0E| WEIR TOTAL: 132 +--+-------------------------+--+ |0B| 79 | 49 |0C| WEIR TOTAL: 128 +--+-------------------------+--+ |09| 85 | 47 |0A| WEIR TOTAL: 132 +--+-------------------------+--+ |07| 76 | 50 |08| WEIR TOTAL: 126 +--+-------------------------+--+ |05| 78 | 65 |06| WEIR TOTAL: 143 +--+-------------------------+--+ |03| 22 | 58 |04| WEIR TOTAL: 80 +--+-------------------------+--+ |01| 75 | 59 |02| WEIR TOTAL: 134 +--+-------------------------+--+ Coil 3 and 4 seem to suspiciously lower in detection efficiency than the rest of the ladder. Most recent information that we have on the condition of the antennas indicate no water damage. Scheduled meger testing for MC1 and MC2 is early next week. 06/28/2002 09:15 darren@p 08:TestTagFailure: Test tag is firing on regular intervals there is no apparent reason for failure. The VTT may not be adjusted to maximize hit rate now that the temperature has warmed up and tune may have drifted a little. 06/27/2002 11:40 scottl@p 01:TestTagFailure: ~01-3 06/25/02 20:31:10 ALARM MESSAGE: Test Tag Found. 06/27/2002 08:26 scottl@p 08:TestTagFailure: No appearent reason for the testag failure 06/19/2002 09:45 scottl@p 09:TestTagFailure: No appearent reason for the testag failure. 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:49 carters@ 01:ExcessiveNoise: ok 06/17/2002 13:49 carters@ 01:ExcessiveNoise: ok 06/12/2002 08:23 darren@p 09:TestTagFailure: There is no direct cause for this alarm. The tag is firing at it's scheduled intervals. This will be checked on the next site visit. 06/11/2002 08:48 scottl@p 09:TestTagFailure: Looking at the raw data files, no appearent reason for the test tag not to fire. VTT possably needs some adjusting. 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/23/2002 16:59 Carter_S From: Darren Chase To: "sandy.downing" 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/20/2002 10:41 darren@p 08:TestTagFailure: Tag was found and is firing at intervals. 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/16/2002 11:30 Darren_C A general site maintenance check was performed. All transceivers were checked for tune. 05/13/2002 08:37 darren@p 08:TestTagFailure: Test tag is firing at scheduled intervals. 05/12/2002 08:59 darren@p 08:TestTagFailure,09:TestTagFailure: Although the test tags failed once. The coils are detecting Pittags. Coil 08 was in an overrun condition when it tried to fire it's timer tag. Coil 09 did not show any immediate reason for it's failure. 05/10/2002 15:26 Anthony On 5/8/02 I delivered a parts locker and fold up table to the MC2 pit tag room. Around 08:30:00 at Kennewick shop transceiver ID# 01 was recording average noise levels around the 30% range. Once on site the levels had returned to optimum, around 1-5% with no adjustment done by either Scott or myself. The water levels were marked with tape and the transceiver was tuned: phase 2%, sig 1-4%, cur 4.5amp, exc 14.2v, & temp 40'C. Around 16:00:00 Scott notice transceiver ID# 01 noise levels had increased: phase 7%, sig 41%, cur 4.3amp, exc 14.2, & temp 44'C. While tuning I noticed the water level dipping below the top left corner of the viewing window. Water level mark showed a drop of 1.5 - 2 inches. I tuned transceiver ID# 01 and noted temp and water level. 05/06/2002 11:10 Scott_Li Turned the unique setting to off for coils 0d,0e at 9:45 pst per Carters suggestion. 05/06/2002 11:06 Scott_Li Set the file submission frequency to upload 4 times per day. 05/03/2002 10:09 Darren_C Files are set to 4 per day on PC1 and PC2. 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/29/2002 08:37 darren@p 08:TestTagFailure: Alarm will be checked 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/26/2002 09:31 darren@p 08:TestTagFailure,09:TestTagFailure: I believe that the timer tags not firing are due to noise. I found that coil 08 periodically goes into an overrun condition every once in a while. This will be checked on the next sight visit. 04/25/2002 20:35 ptagdev@ 01:ExcessiveNoise,02:ExcessiveNoise,03:ExcessiveNoise,04:ExcessiveNoise,07 :ExcessiveNoise,08: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/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:18 carters@ 01:ExcessiveNoise,01:LowExcCurrent,01:TestTagFailure,02:ExcessiveNoise,02: LowExcCurrent,02:TestTagFailure,03:ExcessiveNoise,03:TestTagFailure,04:Exc essiveNoise,04:LowExcCurrent,05:ExcessiveNoise,06:ExcessiveNoise,06:TestTa gFailure,07:LowExcCurrent,08:ExcessiveNoise,08:LowExcCurrent,09:ExcessiveN oise,09:LowExcCurrent,09:TestTagFailure,0A:ExcessiveNoise,0A:LowExcCurrent ,0B:ExcessiveNoise,0B:LowExcCurrent,0B:TestTagFailure,0C:ExcessiveNoise,0C :LowExcCurrent,0C:TestTagFailure,0D:ExcessiveNoise,0D:LowExcCurrent,0E:Exc essiveNoise,0E:LowExcCurrent,0E:TestTagFailure,0F:ExcessiveNoise,0F:LowExc Current,10:ExcessiveNoise,10:LowExcCurrent,10:TestTagFailure: Cleared all lights after fixing permissions problem. Doug Clough 04/15/2002 08:43 Carter set file checking on for mcx, mc1, mc2 at 8:45 4/15/02. 04/13/2002 09:05 dlwarf@p 01:ExcessiveNoise,01:LowExcCurrent,01:TestTagFailure,02:ExcessiveNoise,02: LowExcCurrent,02:TestTagFailure,03:ExcessiveNoise,03:TestTagFailure,04:Exc essiveNoise,04:LowExcCurrent,05:ExcessiveNoise,06:ExcessiveNoise,06:TestTa gFailure,07:LowExcCurrent,08:ExcessiveNoise,08:LowExcCurrent,09:ExcessiveN oise,09:LowExcCurrent,09:TestTagFailure,0A:ExcessiveNoise,0A:LowExcCurrent ,0B:ExcessiveNoise,0B:LowExcCurrent,0B:TestTagFailure,0C:ExcessiveNoise,0C :LowExcCurrent,0C:TestTagFailure,0D:ExcessiveNoise,0D:LowExcCurrent,0E:Exc essiveNoise,0E:LowExcCurrent,0E:TestTagFailure,0F:ExcessiveNoise,0F:LowExc Current,10:ExcessiveNoise,10:LowExcCurrent,10:TestTagFailure: Alarms generated during install. 04/12/2002 09:14 Scott_Li McNary Washington shore adult pittag system was completed on 4/11/02 at ~ 1600 hrs . Digital Angel performed on site modifications to all transceivers and final tuning of the xcvrs were complete. Transceiver buffer contents were downloaded to the computers at ~ 1600 hrs , 4/11/02 and then erased. Automated data file submission was engaged at 1600 hrs, 4/11/02. All Pittag data that was stored in the xcvr buffers can be found in file MC202101.0 04/06/2002 18:15 Darren_C On Friday (4-5-02) The transceivers were tuned and are collecting Data. There is a grounding issue that seems to be temporarily solved and the following is data shows were the transceivers are operating as far as current and noise. These figures may change after Sean Casey, Dan Johnson, and I visit this site and install the new standoffs in the transceivers. The grounding scheme is now as follows: The IG ground block in the Transceiver Power Distribution Panel is now connected to the EG ground block. This brought the noise down considerably on all transceivers. 04/05/2002 09:41 Darren_C On Wednesday 4-3-02 six (6) transceivers were in place and collecting data for the Washington ladder. The weir numbers and coil I.D.'s are as follows: Weir 309 - Coil I.D.'s 05,06 Weir 306 - Coil I.D.'s 09,0A Weir 305 - Coil I.D.'s 0B,0C They began collecting data around 16:30 on 4-3-02. 03/28/2002 14:55 Carter_S Virtual timer tags set up for all coils. 03/11/2002 09:31 Carter_S The Washington shore ladder at McNary MC2 watered-up on January 31, 2002. PIT Tag electronics should be operational by the first week in April, 2002 depending upon when the Corps contractors finish installation of electrical infrastructure. 03/07/2002 15:34 Carter_S Set up coil configuration in ptagis3 database. 03/07/02 15:23 carters Initial log creation for MC2 ####End of Event Log for MC2###