EVENT LOG FOR SITE MC1 Most recent activity to be listed first. First line of each entry lists date, time and who is reporting. Subsequent lines of each entry aligned under Time column. Do not use tabs, only spaces. Date Time Who What ---------- ----- -------- ----------------------------------------------- 12/31/2003 11:37 troy Files MCJ03364.108-MCJ03365.103, MC103364.H-MC103365.C,and MC203364.H- MC203365.C were manually pushed due to the PTTP uploader not being able to connect to the Portland server. All settings in the PTTP uploader were check and appear to be correct. PTOC will monitor the 12pm upload to ensure that it is working correctly. 12/22/2003 07:57 alan@ree 07:LowExcCurrent: This transceiver appears to have drifted out of tune a little bit. This will be fixed on the next site visit. 12/22/2003 07:57 troy@ree 07:LowExcCurrent: It appears that this coil has drifted out of tune and will be addressed during the next sight visit. 12/21/2003 10:15 Troy PCAnywhere'd into these sites to check on them as file submission has not been turned back on due to the moving of servers from Gladstone to Portland. 12/15/2003 08:31 darren@r 07:LowExcCurrent: Alarm is being generated by the fact that the current threshold and current are equal. It appears that the transceiver has drifted in tune and will be addressed on the next site visit. 11/23/2003 10:09 alan@ree 07:LowExcCurrent: Clearing the TASS panel, PTOC will continue to monitor. 11/22/2003 10:34 alan@ree 07:LowExcCurrent: The current has dropped to 3500mA. I PCA'd in and lowered the alarm threshold to 3300mA from 3500mA. PTOC will continue to monitor. 11/20/2003 08:21 alan@ruf 07:LowExcCurrent,08:TestTagFailure: The exciter for coil 07 is putting out 3500mA which is where the alarm threshold is set. The test tag for 08 is firing most of the time. PTOC will investigate these on the next site visit. 11/19/2003 08:12 darren@r 07:LowExcCurrent,10:LowExcCurrent: We will investigate the low current alarms on the next site visit. I do not see anything in the status reports that indicates any problems with the transceiver. 11/18/2003 15:00 Scott_Li PCA'd to the sites and verified that the PTTP loader was sucessfull in transfering files during the last upload interval. No problems to report. 11/18/2003 09:11 Scott_Li PCA's into each of the sites and manually pushed files to PTAGIS. The Minimon application was stopped then restarted in order to syncronize the PTTP loader and close the current files being built. This manual process will continue up until the problems with the firewall in Gladstone are corrected. 11/18/2003 08:41 darren@r 10:LowExcCurrent: No direct cause for the brief drop in current. transceiver will be looked into on the next site visit. 11/18/2003 08:40 alan@ruf 10:LowExcCurrent: There is no apparent reason for this alarm, PTOC will continue to monitor. 11/17/2003 09:39 Darren_C Site was checked for loading and file generation due to the firewall issues that we have been experiencing at Gladstone. The current file is: MC103321.D and there were no files to send. 11/15/2003 14:26 Dave The ftp.pittag.org server failed at 11:15 AM. Coincident with this failure, interrogation site data files were not received at noon today. The FTP server was restored at 1:35 PM. Subsequently, I manually retrieved all outstanding files from the active interrogation sites maintained by PSMFC (BO1, BO2, BO3, MC1, MC2, IHA, and GRA). At BO3, PTTP-Uploader was observed to be in a suspended state. This was corrected. No problems were observed at the other sites polled. No data were lost at any site. 11/14/2003 14:28 Alan_Bro I PCA'd into these sites to assess the file loading of these sites. I found BO1 and MC2 in a normal state. BO2 and MC1 had not changed or uploaded files since yesterday. I stopped and restarted Minimon, verified that all data had been collected properly, and sent the files to PTAGIS. BO3 was manually sent by Darren as he was onsite. IHA and GRA were fixed by Scott this morning. We are continuing to monitor these sites as well as the inactive sites for proper file changes and uploads. 11/14/2003 14:02 Dave Had not heard from site since 6:00pm last night, as a result of a firewall failure this AM. pcA'd into site at 1:50pm this afternoon. Found Minimon operational, but still writing to MC103318.A. Closed that file, opened MC103318.B. Transferred MC103318.A to PTAGIS. No data appear to have been lost. 11/12/2003 11:21 Darren_C I spoke with Brad Eby today and he informed that the Backdrop for the counting window was not pulled on N0V. 01 like in years past. They will doing video counts up until the end of Dec. of this year. He did tell me that there have been two (2) different contractors doing some conduit work and installing J-Boxes around the general area of the counting window. We will inspect what is going on during the next site visit. 11/07/2003 11:07 alan@ruf 05:LowExcCurrent,08:LowExcCurrent,09:LowExcCurrent,0D:LowExcCurrent,0E:Bad ExcFreq,0E:BadOscFreq,0E:LowExcCurrent,0E:Overrun: These alarms were caused by PTOC personel during a site visit. 11/06/2003 15:49 alan@ree 0E:Overrun: This transceiver was replaced 11-6-2003. 11/06/2003 15:40 Alan A GMC was performed 11-6-2003. All transceivers were tuned. Transceiver 0E developed a problem that made it susceptible to overruns and was replaced. It will be sent to Destron for evaluation. No other problems found. 11/05/2003 08:35 darren@r 0E:Overrun: This will be checked on the next site visit. 10/28/2003 08:33 Alan On 10-27-2003 I retuned Transceiver 0E in an effort to reduce the overrun errors we have been seeing lately. 10/27/2003 10:46 darren@r 0E:Overrun: Alarm will be addressed today during the site visit. 10/26/2003 10:40 alan@ruf 0E:Overrun: This will be addresed tomorrow. 10/25/2003 10:01 alan@ree 0E:Overrun: PTOC will investigate on Monday 10-27-2003. 10/23/2003 12:38 Darren Asite gmc was performed on all adult transceivers. The noise levels and tuning was checked and no problems were found. 10/21/2003 09:03 darren@r 01:ExcessiveNoise,02:ExcessiveNoise,0B:ExcessiveNoise,0C:ExcessiveNoise,0D :ExcessiveNoise,0E:ExcessiveNoise,0F:ExcessiveNoise,10:ExcessiveNoise: Noise levels and tune will be checked on the next site visit. 10/12/2003 09:29 darren@r 0A:LowExcCurrent: Alarm was generated by PTOC personnel while doing site GMC. 10/09/2003 16:24 Darren Site GMC's were performed. All transceivers were checked for tuning and noise. No Problems were found. 09/29/2003 08:53 alan@ruf 0C:LowExcCurrent: No direct cause for the low exc current alarm. We will investigate on the next site visit 09/22/2003 12:42 scottl Gmc on both sites found no problems to report. All transceivers were checked for calibration. 09/21/2003 09:13 darren@r 0C:LowExcCurrent: No direct cause for the low exc current alarm. We will investigate on the next site visit. 09/04/2003 15:36 PTOC_Bot A GMC was performed 9-4-2003. All transceivers were tuned, no problems found. 08/27/2003 18:33 ptagdev@ 0F:LowExcCurrent: Acknowledged in order to test AcknowledgeAndPost. Doug Clough 08/27/2003 18:31 ptagdev@ 0F:LowExcCurrent: Testing PostMessageOnly. Doug Clough 08/26/2003 08:32 darren@r 0F:LowExcCurrent: Alarm was generated by PTOC perosnnel while performing a site GMC. While I was on-site I noticed a rather interesting phenomenon going on in the ladder and I was able to see the affects on almost all the trnasceivers. The flow through the ladder was causing the pools between weirs to swell and fall. I spoke with Terry Zirb and he asked me to contact Brady Eby on this matter. Sometimes if the control weirs above the ladder get out of calibration it can cause the flow in the ladder to rise and fall. I will contact Brad Eby today to find out if this was the actual cause or not. 08/25/2003 08:50 scottl@r 01:ExcessiveNoise,02:ExcessiveNoise,07:ExcessiveNoise,09:ExcessiveNoise,0B :ExcessiveNoise,0C:ExcessiveNoise,0D:ExcessiveNoise,0E:ExcessiveNoise,0F:E xcessiveNoise,10:ExcessiveNoise,11:ExcessiveNoise,12:ExcessiveNoise: These alarms will be addressed on the next site visit. 08/25/2003 08:19 darren@r 0C:LowExcCurrent: No direct cause for the alarm. I checked the raw files and the following status dump show no signs of the exciter current being low. We will monitor for this alarm in the future. 08/20/2003 11:17 Alan A GMC was performed 8/19/2003. All transcievers were tuned and checked for issues since the last visit. No problems found. 08/02/2003 10:56 alan@ree 09:HighTemp,0D:LowExcCurrent,11:BadOscFreq,11:LowExcCurrent: Coil 09 has shown to give this error before the other coils when the temperature approaches 100 deg F. PTOC will investigate further. The other alarms were caused by PTOC personel during a site visit. 07/31/2003 15:39 PTOC_Bot A GMC was performed 7/31/2003. All transcievers were tuned. 07/31/2003 08:37 alan@ruf 03:HighTemp,04:HighTemp,06:HighTemp,07:HighTemp,09:HighTemp,0A:HighTemp,11 :HighTemp: We know HiTemp errors can occur when outside ambient approaches 100 deg F as they did yesterday. 07/24/2003 08:04 darren@r 09:HighTemp: Alarm acknowledged. The temperature was over 100 degrees on this particular day. We will monitor for future alarms. 07/21/2003 08:27 scottl@r 03:TestTagFailure,09:HighTemp,0C:LowExcCurrent: Coil 09 was the only xcvr that overtempt during the extreme temperatures this weekend. Not bad considering, although why only 09? 07/17/2003 15:45 darren@r 08:TestTagFailure: It appears that there was a site wide event that caused excessiver noise on all in ladder transceivers. There is no direct cause for the site wide noise. We will monitor for another site wide event. 07/15/2003 09:33 darren@r 07:TestTagFailure: This alarm was taken care of yesterday during the site GMC. The timer tag was not turned "on". I turned it on and calibrated the hit rate for 100%. 07/14/2003 15:27 darren@r 07:TestTagFailure: Site was visited fro a GMC. The timer tag on coil 07 was turned "off" when the analog boards were re-installed. The tag was turned "on" and the hit rate was calibraed for 100%. 07/14/2003 14:56 Darren A site GMC was performed today. All transceivers were checked for tune and noise. the timer tag on coil 07 had been turned "off", this probably happened when the analog boards were replaced. It was turned back on and the hit rate was calibrated for 100% hit rate. No problems were found. 07/14/2003 10:46 darren@r 01:ExcessiveNoise,02:ExcessiveNoise,03:ExcessiveNoise,04:ExcessiveNoise,05 :ExcessiveNoise,06:ExcessiveNoise,07:ExcessiveNoise,08:ExcessiveNoise,09:E xcessiveNoise,0A:ExcessiveNoise,0C:ExcessiveNoise,0D:ExcessiveNoise,0E:Exc essiveNoise,0F:ExcessiveNoise,10:ExcessiveNoise: Site will be visited today for site GMC. All transceivers will be checked for tune. 07/10/2003 09:24 darren@r 07:TestTagFailure: I PCA'd into site and checked the hit rate for coil 07. I found it to be 0 which would indicate that the timer tag switch may be in the "off" position. This will be addressed on Monday when PTOC personnel are scheduled to be on site for GMC's. 07/09/2003 08:13 scottl@r 07:TestTagFailure: TT failure will be corrected on the next site visit. 07/07/2003 08:24 scottl@r 07:TestTagFailure: Possable cause for the TT to not be firing is the VTT switch may have been inadvertently turned off during the replacement of the analog pcb's. Will correct on the next site visit. 07/04/2003 09:44 alan@ree 07:TestTagFailure: This issue will be addressed Monday. It appears that the timer tag was accidently turned off while replacing the analog boards. 07/03/2003 08:03 darren@r 07:TestTagFailure: This issue will be addressed today.It appears that the timer tag was accidently turned off while replacing the analog boards. 07/02/2003 10:57 darren@r 07:TestTagFailure: This alarm is probably a result of yesterdays board swap. It will be investigated either today or tomorrow. The transceiver is operating properlyas far as detectablity goes. 07/02/2003 08:18 troy@ruf 07:LowExcCurrent,07:Overrun,08:TestTagFailure,0A:LowExcCurrent,0B:TestTagF ailure,0C:LowExcCurrent,0E:LowExcCurrent,0F:LowExcCurrent,11:LowExcCurrent ,12:LowExcCurrent: Alarms generated as a result of PTOC personel swapping loaner Analog pcb's with upgraded orginal pcb's that now are fitted with NPOs 07/01/2003 16:17 scott_li Reinstalled the original analog pcb's that were modified with NPO style capacitors at MC1 and retuned. Swapped out all analog pcb's with the loaner pcb's at MC2 until the originals can be modified with the NPO style caps. Per Darren and Dan (DA) the lead time for this mod may be several months due the long lead time from the cap manufacturer. 06/28/2003 08:26 darren@r 01:TestTagFailure: alarm caused by PTOC personnel while performing site GMC. 06/24/2003 08:36 Darren A site maintenance GMC was performed on 6/18/03. No problems found. 06/20/2003 08:27 scott_li The primary interrogation computers were reconfigured with new DNS I/P addresses yesterday afternoon in order to satisfy the latest COE firewall rules that were implemented on or around 6/17/03. Due to this reconfig, the primary computers had to be rebooted in order for the setting to take effect and therefore creating a gap in the data set. All efforts were made to minimize this gap and efforts will be made today to restore the missing records . 06/08/2003 09:53 darren@r 05:BadOscFreq: Will have to check the next raw file to further investigate this alarm but it appears that it only happened the one time and there is no apparent reason for the failure. 06/04/2003 09:32 darren@r 03:TestTagFailure,04:TestTagFailure,05:BadOscFreq,05:TestTagFailure,06:Low ExcCurrent,06:TestTagFailure,07:LowExcCurrent,07:TestTagFailure,09:LowExcC urrent,0A:LowExcCurrent,0F:LowExcCurrent,11:LowExcCurrent: All alarms were generated by PTOC personnel while performing site GMC. 06/04/2003 08:39 Darren_C All sites were visited and GMC's were performed. All the analog boards that were replaced at MC1 were retuned and timer tag hit rates were checked. No problems found. 05/30/2003 22:10 darren@r 03:LowExcCurrent,04:LowExcCurrent,05:LowExcCurrent,06:BadOscFreq,06:LowExc Current,09:LowExcCurrent,09:TestTagFailure,0A:BadOscFreq,0A:LowExcCurrent, 0A:Overrun,0A:TestTagFailure,0B:LowExcCurrent,0B:TestTagFailure,0C:TestTag Failure,0D:TestTagFailure,0E:BadExcFreq,0E:BadOscFreq,0E:LowExcCurrent,0E: TestTagFailure,0F:LowExcCurrent,0F:TestTagFailure,11:TestTagFailure,12:Low ExcCurrent,12:TestTagFailure: 03:LowExcCurrent,04:LowExcCurrent,05:LowExcCurrent,06:BadOscFreq,06:LowExc Current,09:LowExcCurrent,09:TestTagFailure,0A:BadOscFreq,0A:LowExcCurrent, 0A:Overrun,0A:TestTagFailure,0B:LowExcCurrent,0B:TestTagFailure,0C:TestTag Failure,0D:TestTagFailure,0E:BadExcFreq,0E:BadOscFreq,0E:LowExcCurrent,0E: TestTagFailure,0F:LowExcCurrent,0F:TestTagFailure,11:TestTagFailure,12:Low ExcCurrent,12:TestTagFailure: All alarms were generated by PTOC personnel while changing out the analog boards with boards that contain NPO capacitors. These analog boards will be sent back to Destron-Fearing for installation and testing of the NPO capacitors and then placed back into the original transceivers. These new boards will need to be fine tuned next week as they will change as they burn in. 05/30/2003 22:10 darren@r 03:LowExcCurrent,04:LowExcCurrent,05:LowExcCurrent,06:BadOscFreq,06:LowExc Current,09:LowExcCurrent,09:TestTagFailure,0A:BadOscFreq,0A:LowExcCurrent, 0A:Overrun,0A:TestTagFailure,0B:LowExcCurrent,0B:TestTagFailure,0C:TestTag Failure,0D:TestTagFailure,0E:BadExcFreq,0E:BadOscFreq,0E:LowExcCurrent,0E: TestTagFailure,0F:LowExcCurrent,0F:TestTagFailure,11:TestTagFailure,12:Low ExcCurrent,12:TestTagFailure: All alarms were generated by PTOC personnel while changing out the analog boards with boards that contain NPO capacitors. These analog boards will be sent back to Destron-Fearing for installation and testing of the NPO capacitors and then placed back into the original transceivers. These new boards will need to be fine tuned next week as they will change as they burn in. 05/30/2003 15:56 scott Analog pcb's on all transceivers were replaced today so that Digital Angel can modifiy the production pcb's with NPO capacitors. All xcvrs were retuned but will to need to be re-calibrated on Monday after the PCB's have had a chance to warm up to operating temp. 05/30/2003 09:34 Alan On 5/20/2003 the rip-ties were placed on the doors and then doors were secured at MC1 coils 03-12 and MCJ coils 01-04. 05/22/2003 08:21 darren@r 01:TestTagFailure: PTOC personnel used this site for testing Minimon Messaging. There were no alarms. 05/18/2003 09:12 darren@r 07:TestTagFailure: Alarm should not have been an alarm the message "ALARM MESSAGE: Test aborted due to system activity." was displayed. There was quite a bit of information trying to be displayed for this coil including pittag information at once. 05/12/2003 22:50 D._Chase Today Site GMC's were performed. All transceivers were checked for tune. No problems were found. 05/07/2003 09:27 Scott_Li A GMC was performed on 5/7. Transceivers were checked for optimum tune, no significant problems to report. The PTTP interface on MC1-PC1 was reconfigured in order to Syncronize on the hour and the AboutTime NIST app. configuration was also checked for accuracy. No changes to this application were made. Suggestions about how to effectively use the AboutTime App. will be discussed within ithe PTOC group via e-mail. 04/30/2003 16:49 Alan I performed a GMC on these sites 4/29/2003. Transceivers were checked for tune and any major concerns that have been noted since the last visit. No problems were found. 04/30/2003 08:49 alan@ruf 07:LowExcCurrent,09:LowExcCurrent: These alarms were generated by PTOC personel during a general maintenance visit. 04/27/2003 08:42 troy@ree 01:ExcessiveNoise,02:ExcessiveNoise,03:ExcessiveNoise,04:ExcessiveNoise,05 :ExcessiveNoise,06:ExcessiveNoise,07:ExcessiveNoise,08:ExcessiveNoise,09:E xcessiveNoise,0A:ExcessiveNoise,0B:ExcessiveNoise,0C:ExcessiveNoise,0D:Exc essiveNoise,0E:ExcessiveNoise,0F:ExcessiveNoise,10:ExcessiveNoise,12:Exces siveNoise: Transceiver for coils 10 was replaced last week. Will monitor situation. All other noise alarms are not of concern. 04/25/2003 07:49 darren@r 10:LowExcCurrent,10:Overrun,10:TestTagFailure: This transceiver was replaced during a site GMC yesterday. We will monitor for noise alarms. 04/24/2003 16:34 Alan I performed a GMC on these three sites today. Transceivers were checked for tune and any major concerns that have been noted since the last visit. I replaced the transceiver for coil 10 at MC1 to narrow down the possibilities for our noise problems there. PTOC will continue to monitor that coil. No problems were found. 04/23/2003 09:32 scottl@r 01:ExcessiveNoise,02:ExcessiveNoise,03:ExcessiveNoise,04:ExcessiveNoise,05 :ExcessiveNoise,06:ExcessiveNoise,07:ExcessiveNoise,08:ExcessiveNoise,09:E xcessiveNoise,0A:ExcessiveNoise,0C:ExcessiveNoise,0D:ExcessiveNoise,0E:Exc essiveNoise,0F:ExcessiveNoise,10:ExcessiveNoise,11:ExcessiveNoise,12:Exces siveNoise: Clearing panel, site visit scheduled for 4/24. 04/23/2003 08:58 scottl@r 10:LowExcCurrent: This coil has a history of being intermittently noisey. PTOC will address this tomorrow by replacing the transceiver that has the NPO capacitors on the analog pcb. The NPO caps will not correct the noise issue, but will provide stability due to extreme ambient temperature swings. 04/17/2003 13:53 scottl The less than desirable efficiencies for Coils 01 and 02 appear to be related to fish behavior. As stated in the last entry, the transceivers for the counting window were extremely quite and have no reason to believe they are not performing as expected. 04/17/2003 09:08 scottl@r 01:TestTagFailure,02:TestTagFailure,0B:TestTagFailure,0E:LowExcCurrent,0F: TestTagFailure,10:LowExcCurrent,12:TestTagFailure: A GMC was performed 4/16/03. Coils 01 and 02 were extremely quite and performing well. Coil 10 had evevated noise levels from 20 to 30 percent.Retuned transceiver and got the noise floor down to 10 to 15 with periodic spikes to 25 percent or higher. We have had problems with this coil in the past and ave decided replace the transceiver and monitor the situation . 04/16/2003 12:45 scottl@r 01:ExcessiveNoise,02:ExcessiveNoise,0B:ExcessiveNoise,0C:ExcessiveNoise,0D :ExcessiveNoise,0E:ExcessiveNoise,0F:ExcessiveNoise,10:ExcessiveNoise,11:E xcessiveNoise,12:ExcessiveNoise: As site visit is being conducted today to correct Coil 10 and 02. 04/11/2003 07:58 Darren_C These sites were visited yesterday for general maintenance checks all transceivers were checked for tuning and the gates at the JFF were checked for timing. We changed all Adult transceivers timer tag delays to 61 minutes to try and avoid the timer tag and status report being sent at the same time. This may put a damper on some of the timer tag failures. If this works we will implement this on all adult transceivers. No problems were found. 04/04/2003 08:25 alan@psm 03:TestTagFailure,04:TestTagFailure,05:TestTagFailure,06:TestTagFailure,07 :TestTagFailure,08:TestTagFailure,09:TestTagFailure: Alarms were caused by PTOC personel during site visit. 03/31/2003 08:51 darren@p 04:TestTagFailure,08:LowExcCurrent,08:TestTagFailure,0D:LowExcCurrent,0F:L owExcCurrent,11:LowExcCurrent: These alarms were generated by PTOC personnel while performing maintenance checks. I tried to post TASS earlier but it did not clear. 03/28/2003 13:55 Darren A maintenance check was performed today 3-28-03. All transceivers were tuned and check for a hit rate on the timer tags. No problems were found. 03/25/2003 10:40 darren@p 10:LowExcCurrent: The transceiver is running above the threshold but is showing signs of "excessive noise" it will be addressed on the next site visit. 03/17/2003 09:45 alan@psm 08:TestTagFailure: ~08-11 03/16/03 01:02:40 ALARM PROBLEM: Test Tag Failed No apparent reason for failure. We will investigate during our next General Maintenance Check. 03/14/2003 11:15 Scott_Li Reviewed entire status of these sites and did not detect any significant events that warrants attention. 03/14/2003 09:17 darren@p 08:TestTagFailure: There does not seem to be any apparent reason for the tag failure. We will check this unit on the next site visit. 03/13/2003 09:04 darren@p 08:TestTagFailure,0C:LowExcCurrent: Test tag failure is unknown as far as cause we will investigate on the next visit. The alarm for low current is also unknown in that both status reports before and after show no signs of the current dropping below the alarm threshold. We will investigate this also on the next visit. 03/07/2003 14:47 Dave I updated the ptagis3.test_tags table to associate each (previously- missing) coil_id value with each virtual timer tag at this site. This essentially enables the validation routines for the Timer Tag reports. 03/07/2003 08:31 darren@p 06:LowExcCurrent,08:LowExcCurrent: These transcecivers were tuned just after these time stamps. The site will need to be fine tuned and have data compiled. 03/06/2003 08:53 Darren_C The site was visited and the transceivers were tuned and checked for the PSMFC SOP of firing the Timer Tag every 60 min. and sending the Status Reports every 60 min. The noise report was turned "off". The DCP was also set for PSMFC SOP generating 8 files per day and sending 8 times per day with a delay of 120 seconds. The site will need to be fine tuned and have Data collected for the start of the 2003 season. 03/05/2003 08:34 darren@p 01:TestTagFailure,06:LowExcCurrent,06:TestTagFailure: I will be on site for fine tuning today. I will take care of alarms. 03/04/2003 15:47 scott Coils 01 and 02 (counting Windows ) were returned to the read mode at ~1510 hrs 3/4/03. 03/03/2003 22:11 darren@p 06:LowExcCurrent,06:TestTagFailure,08:LowExcCurrent: This site was put into a "scan" mode this morning and has not yet been fine tuned. I will address this on my next visit on Wednesday. The DCP (Data Collection Platform) has not yet been set nor have any of the transceiver parameters. 03/03/2003 15:08 Don_Warf All transceivers were put into read mode at 9:00am. The ladder was watered up on the 24th around 11:00am. PTOC Kennewick was not notified by the COE of the early water up date. Seven days of detection have been lost on this ladder. The Kennewick office will take steps to make sure this does not happen in the future. 02/05/2003 10:33 darren@p 01:Overrun,02:LowExcCurrent,03:LowExcCurrent,04:LowExcCurrent,05:LowExcCur rent,05:TestTagFailure,06:LowExcCurrent,07:LowExcCurrent,08:LowExcCurrent, 08:TestTagFailure,09:LowExcCurrent,0A:LowExcCurrent,0C:LowExcCurrent,0D:Lo wExcCurrent,0E:LowExcCurrent,0F:LowExcCurrent,10:LowExcCurrent,11:LowExcCu rrent,12:LowExcCurrent: This site was dewatered on Monday 2-3-03 around 10:00. We were not notified until Tuesday 2-4-03 at about 10:30. All transceivers have been placed in "standby" and the ladder will be inspected. 02/04/2003 09:55 PTOC_Bot We were informed today by Brad Eby that this site was dewatered between 9:30 and 10:30 yesterday. PSMFC personnel will be on site later this week to do antenna inspection and take photographs. I PCA'd in and placed the readers in standby mode. 01/03/2003 08:31 darren@p 08:TestTagFailure: Alarm may have been caused by the timer tag firing when the status reports is being sent by the transceiver. I tried to alter this time frame but it does not seem to have worked. 01/02/2003 11:13 darren@p 08:TestTagFailure,10:LowExcCurrent: The alarms on coil 08 may be caused by the timer tag firing at the same time as the status report being sent to the computer. I will PCA into site and shift the report by sending a status report to the CPU. I can't find a reason for the low exc current on coil 10. This coil has been doing some interesting things over the last two weeks, we will monitor this to see if there are any more failures. When the ladder is de-watered we will be inspecting this coil. 01/01/2003 12:19 Dave Initialized new event log for 2003. 2002 event log has been archived. ####End of Event Log for MC1###