EVENT LOG FOR SITE BO1 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/30/2003 08:43 darren@r 1F:LowExcCurrent: The alarm threshold and the current are equal. I will adjust the threshold until PTOC personnel can get down to re-tune this and any other transceivers that require tuning. 12/29/2003 09:32 darren@r 1F:LowExcCurrent: It appears that the current is equazl to or just below the threshold for the current alarm. The transceiver is out of tune and will be addressed on the next site visit. 12/24/2003 09:17 alan@ree 13:LowExcCurrent,15:LowExcCurrent,1D:LowExcCurrent,1F:LowExcCurrent: PTOC will investigate on the next site visit. 12/15/2003 08:12 darren@r 13:LowExcCurrent: Problem will be addressed on Tuesday on the site visit. 12/14/2003 08:31 darren@r 13:LowExcCurrent: Alarm acknowledged. It will be corrected on Tuesday during site visit. 12/13/2003 08:50 darren@r 13:LowExcCurrent: The current alarm and the current are equal. It appears that the transceivers has drifted slightly in tune and will be retuned on Tuesday during the next site visit. 12/12/2003 10:30 alan@ruf 13:LowExcCurrent,15:LowExcCurrent,1C:LowExcCurrent,1D:LowExcCurrent: These coils appear to have drifted slightly off tune. These will be taken care of on the next site visit. 12/07/2003 11:11 dlwarf@r 13:LowExcCurrent,1C:LowExcCurrent: Issues to be addressed this week. 12/05/2003 08:32 alan@ruf 1C:LowExcCurrent: The threshold for this transceiver is 3600mA which is where this coil has drifted to. PTOC will investigate on the next site visit. 12/04/2003 07:53 alan@ree 1C:LowExcCurrent: The threshold for this transceiver is 3600mA which is where this coil has drifted to. PTOC will investigate on the next site visit. 11/20/2003 13:57 Darren New AC adapter power supplies were purchased and installed for the Multimode to Singlemode converters inside PH2. The upload process was tested at both Cascade and Bradford Island. No Problems were found. Scott and I will be monitoring the sites over the Holiday and will be watching for any disturbances at these two sites. 11/19/2003 16:06 Darren_C Jon Thomas from COE Bonneville contacted me and informed me that he will be picking up some new AC adapters for the media converters tonight. He will be giving them to the electrician tomorrow morning to install. I will be on site about 10:00 to 10:30 a.m. and will asses the situation on our communications. If the AC adapters do not solve the problem and the media converters are damaged we will have to obtain the assistance of on-site PSMFC personnel to help in verifying the operations of Data Collection Platforms at Bradford and Cascade Islands until the media converters can be replaced. I will post my findings tomorrow from the site. 11/19/2003 10:30 Darren_C It was brought to the attention of PSMFC that communications between both Bradford and Cascade Island Data Collection Platform have been lost. It sounds like there was a power problem in the second powerhouse and the Singlemode to Multimode fiber converters may have been damaged. I am trying to verify this with Jon Thomas from the electrical shop at bonneville. I will be traveling to the sight to evaluate the situation, we may or may not be able to switch the platforms over to dial-up connections, if not we will have to develop another plan. I will post more information when it becomes available to the PTOC staff. 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:29 alan@ruf 09:LowExcCurrent: The tune appears to have drifted slightly. The alarm threshold was set to 2200mA and the exciter current is approximately 2300mA, occasionally dropping to 2200mA. I PCA'd into PC2 and set the alarm threshold to 2000mA. PTOC will investigate further on the next site visit. 11/17/2003 09:37 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: BO103321.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/07/2003 12:03 Alan A GMC was performed 11-7-2003. All transceivers were tuned. No problems found. 10/24/2003 11:53 darren@r 1C:LowExcCurrent: Alarm will be checked and cleared today during site GMC. 10/23/2003 08:55 alan@ree 1C:LowExcCurrent: The alarm threshold is set to 3900mA which is what the exciter is currently putting out. We will check this transceiver during a GMC tomorrow. 10/21/2003 09:01 darren@r 0A:ExcessiveNoise,18:ExcessiveNoise: Noise levels and tune will be checked on the next site visit. 09/29/2003 08:36 alan@ruf 18:LowExcCurrent: This coil is having problems at the capacitor bank. It will be investigated further when the ladder is de-watered. 09/26/2003 13:32 Darren A GMC was performed, all transceivers were tuned. Coil 06's timer tag failure was addressed by tuning. Coil 18 is currently in an excessive noise state due to a capacitance change which affected the capacitance bank inside of the coil. PTOC is aware of this problem and will be addressing this when the ladder is de-watered. 09/18/2003 08:20 scott_li BO1 LEFT BRANCH WEIR 48 06 3E7.0000001D06 0 This will be fixed on the next site visit. 09/08/2003 09:22 Don_Warf The site utility machine has stopped communicating. This will be checked on the next GMC. 08/20/2003 12:11 Alan A GMC was performed 8/20/2003. All transceivers were tuned. Coil 18 was improved from 22% to 17%. The VTT was adjusted to 100% on Coil 09. No other problems found. 08/18/2003 10:49 darren@r 09:TestTagFailure: No apparent reason for failure. This will be investigated on the next site visit. 08/06/2003 08:08 troy@ree 16:TestTagFailure: The timer tag has been turned back on. 08/05/2003 15:14 darren@r 16:TestTagFailure: This alarm was repaired. The test tag switch was placed back into the "ON" position and the test tag was fired. 08/05/2003 08:21 darren@r 16:TestTagFailure: This alarm will be addressed today. The test tag was inadvertently turned "off" while performing a hit rate test with a test stick. 08/04/2003 08:54 Darren_C On Friday I was on site to a GMC and investigate the rising noise on antenna 18. I found that the noise was a little elevated so I retuned the transceiver. I tried to megohm the antenna but and I found that the antenna was bad from pins 1-7, the resistance was 4.0 Mohm, the others were infinite. After the test was done I reconnected the antenna to the transceiver and the noise was at 100% and would not respond to anything that I could do to the tuning. It appears that the noise levels have receded to a level that is allowing the timer tags to fire so I would assume there is some detection ability for pittag's. I think that the capacitor bank is damaged or weakened in that when I applied the DC voltage for the test the capacitors seem to have broken down. It could be that the dielectric is breaking down. I will be onsite Tuesday to retune the antenna the best I can but I feel that this antenna will need to be evaluated and possibly replaced this next year during the de-watering period. 08/04/2003 08:31 darren@r 16:TestTagFailure: The timer tag was mistakenly left in the "off" position. While performing hit rates for a test stick it was turned off. I will be on site Tuesday so I will check the switch setting. 08/02/2003 10:46 troy@ruf 16:TestTagFailure: This testtag was turned off when doing a hit rate test while performing a site GMC. It will be turned back on, on 8/5/03 08/02/2003 10:16 troy@ruf 18:BadExcFreq,18:BadOscFreq,18:LowExcCurrent,18:TestTagFailure: PTOC personel are aware of the situation with this coil and will be addressing this on monday. 08/01/2003 13:11 Darren A site GMC was performed on each site no problems were found on BO2. BO1 was having problems with coil 18 not firing it's timer tag all the time so I checked the transceiver and foudn that the noise was elevated so I retuned the transceiver. I then wanted to check the coil for leakage, I megged the coil and found pins 1 and 7 had 4.0M ohms of resisteance but after the antenna was megged the noise levels elevated to near 100% and have not returned to normal. It is possible that when the megohm test was performed that it damaged a weakend capacitor I will check this coil on my way out of the facility but if it does not return to normal the problem will have to be dealt with when the ladder is de-watered. 07/24/2003 08:11 darren@r 0C:TestTagFailure: The test tag and the status report are being sent almost simultaneously. This could be causing some of the test tag failures. We will monitor for future failures. 07/22/2003 09:03 Darren_C I checked the timer tag report and found that coil 18 at BO1 wasn't firing the timer tag. I checked the raw files and found that it was reporting the following messages: >~18-32 07/22/03 03:48:41 ALARM MESSAGE: Single-shot test with Test Tag. >~18-32 07/22/03 03:48:41 ALARM MESSAGE: Test aborted due to system activity. >~18-32 07/22/03 03:48:41 ALARM Reader info: Version: FS1001A 3.11 >~18-32 07/22/03 03:48:41 ALARM Active: On Unique: Off >~18-32 07/22/03 03:48:41 ALARM Reader ID#: 18 Master: Off > I will try to alter the times for the timer tag firing so that it does not conflict with the status dump. 07/21/2003 08:23 darren@r 09:LowExcCurrent,0C:TestTagFailure,0F:LowExcCurrent,0F:Overrun,0F:TestTagF ailure,14:LowExcCurrent,18:LowExcCurrent: The alarms that were generated on 7-16-03 were generated by PTOC personnel while performing site GMC. The alarms on 7-18-03 were also generated by PTOC personnel but this time the transceiver for coil 0F was being replaced. 07/21/2003 08:23 scottl@r 09:LowExcCurrent,0C:TestTagFailure,0F:LowExcCurrent,0F:Overrun,0F:TestTagF ailure,14:LowExcCurrent,18:LowExcCurrent: Most of these alarms were caused by PTOC during GMC, Others are not of concern. 07/20/2003 10:56 Don_Warf Transceiver 18 came back to life after having no detections or timer tags fire on Friday. Will check this closer on Monday. -------- Original Message -------- Subject: bo1 Date: Sat, 19 Jul 2003 11:11:14 -0700 From: Don Warf To: pitevent Transceiver 18 appears to have died. It will be checked out on Monday. 07/19/2003 11:11 Don_Warf Transceiver 18 appears to have died. It will be checked out on Monday. 07/18/2003 12:24 Alan The new transceiver for coil 0F was installed and calibrated at 12:15. 07/17/2003 11:42 scott_li All transceivers were recalibrated during the GMC. Coil 0F was found to be dead but did not have spare replacement transceiver. A site visit is scheduled for 7/18 to bring 0F back online. Corrected the timertag problem with Coil 18 and 06. No other problems detected. 07/11/2003 08:32 Darren_C I PCA'd into this site and fired the test tag it fired. I tested the hit rate and got only 90% but still it was firing. I then put the reader in standby and then back into scan. I fired the tag again and everything seems to be o.k. I am not sure why the timer tag report shows that the test tag has not fired. I received no TASS alarms on this subject. We will be on site next week and we will investigate this phenomenon. 07/03/2003 07:57 darren@r 05:LowExcCurrent,15:LowExcCurrent,15:Overrun: Alarms were generated by PTOC personnel while performing site GMC. 07/02/2003 13:25 Alan_Bro A GMC was performed 7-2-2003. Tranceivers were tuned, no problems found. 06/25/2003 15:10 troy@ruf 18:LowExcCurrent: This alarm was caused by PTOC personel performing a site GMC 06/25/2003 08:11 Darren_C Sites were visited during weekly GMC. No Problems were found. 06/20/2003 08:33 Darren_C These sites were visited yesterday for site GMC's. All transceivers were checked for tuning and noise. No Problems were found. Sticks were passed through the separator at B2J and the results are as follows: Coils A1-A4= 19 of 20 Coils E1-E2= 9 of 10 CoilsF1-F2= 10 of 10 I believe that there is one stick code that is not in the Watch.Tag file because all sticks were diverted properly. 06/11/2003 23:31 D._Chase All sites were visited today for site GMC's. although no problems were found with transceivers or gates we did notice a very high volume of chad going through all the ladders, this may be causing some of the obscure numbers on some of the ladders. 06/07/2003 06:59 darren@r 0A:TestTagFailure: Alarm caused by PTOC personnel while performing site GMC. 06/05/2003 09:14 Dave File uploads were suspended for 18 hours due to a glitch with Sprint. pcA'd into BO1 and BO2 at ~9:00am today and grabbed outstanding files without incident. pcA'd into BO3 and had to reset PTTP account password before I could successfully transmit the outstanding files. Don't know why. 06/04/2003 08:14 darren@r 18:LowExcCurrent: The current alarm threshold and the current are equal. I will change the threshold until we can get there tomorrow. 05/30/2003 13:48 Carter_S BO1 communications went down on 5/29. Todd noticed the RX light of the high-speed fiber switch on steady. He disconnected the connector and the problem went away. As a precaution we power-cycled the high-speed fiber switch, tested connectivity to Gladstone, then uploaded the seven files that had collected since communications stopped yesterday. 05/30/2003 10:29 Scott_Li Carter and Todd are in route to the facility to try and repair the link from bo1 to the router at bo3. Suspect that a fiber pair has been unplugged or a network connection is broke in some way. 05/30/2003 09:26 Alan A site GMC was performed. All transceivers were checked for tune and operation. No problems were found. The rip-ties were placed on the doors and then doors were secured. 05/30/2003 08:12 troy@ree 1E:LowExcCurrent: Alarm generated by PTOC personel performing a site GMC 05/22/2003 08:09 darren@r 15:Overrun,15:TestTagFailure,18:LowExcCurrent,18:TestTagFailure: Alarms were generated by PTOC personnel while performing site GMC. 05/21/2003 12:43 darren@r 15:Overrun: This site will be checked and retuned if necessary today. A GMC will be performed by Alan. 05/18/2003 08:48 darren@r 15:Overrun: This condition will be rectified on the next site visit. 05/15/2003 09:36 darren@r 09:TestTagFailure,15:Overrun,16:TestTagFailure,1A:TestTagFailure,20:TestTa gFailure: All alarms except for the overruns on coil 15 were generated by PTOC personnel while performing GMC's. Coil 15 will be addressed on next site visit. 05/14/2003 11:24 Alan_Bro A GMC has been performed, all transcievers checked for tune and any other concerns since the last visit. Sean Casey and Earl Prentice helped with the flat plate, the results being that turning down the exciter power yielded a quieter signal. 05/12/2003 10:31 alan@ruf 14:LowExcCurrent,1A:LowExcCurrent: These errors were generated by PTOC personel during a site visit. 05/08/2003 13:21 D.Chase All Sites were visited for site GMC's. No problems were found. At BO2 transceiver 03 was replaced with a new transceiver that contains the NPO capacitors. The reason it was replaced was because the timer tag kept failing. We will watch to see how the NPO cap's do at this site. 05/05/2003 08:19 darren@r 14:LowExcCurrent: There are no direct causes for this alarm. We will monitor for future alarms. 04/23/2003 15:45 Alan_Bro Test2 04/23/2003 15:40 Alan_Bro ---Executing: shownonascii 04/23/2003 10:16 Alan I performed a GMC on these three sites yesterday (4/22/2003). I replaced the transceiver on Coil 03 at BO2 in an effort to resolve our timer tag issues with that transceiver. Transceivers were checked for tune and any major concerns that have been noted since the last visit. No problems were found. 04/23/2003 10:10 Alan_Bro ---Executing: shownonascii 04/17/2003 15:32 Dave There was a temporary lapse in communication with the Bonneville Adult Ladder sites. Communications were restored at approximately 2:30 pm DST, after the firewall was rebooted. I manually transferred all outstanding files to Gladstone at ~2:45 pm DST. 04/17/2003 11:33 darren@r 1A:LowExcCurrent: Alarm was generated by PTOC personnel while on site for GMC . 04/16/2003 22:54 D._Chase Site was checked by PTOC personnel for noise. Transceiver 18 was in a unresponsive state when we checked on it's status. We have had noise problems with since this season started. After cycling the power it was retuned and the noise levels were o.k. I still suspect that there may be some broken conduit below the water line because of the intermittent noise alarms that are being received. We will monitor this transceiver and if the problems persist we may choose to replace the transceiver to verify that the problem is not electronic. 04/16/2003 12:42 scottl@r 02:ExcessiveNoise,03:ExcessiveNoise,04:ExcessiveNoise,05:ExcessiveNoise,07 :ExcessiveNoise,08:ExcessiveNoise,09:ExcessiveNoise,0C:ExcessiveNoise,0E:E xcessiveNoise,11:ExcessiveNoise,12:ExcessiveNoise,13:ExcessiveNoise,14:Exc essiveNoise,15:ExcessiveNoise,16:ExcessiveNoise,17:ExcessiveNoise,18:Exces siveNoise,19:ExcessiveNoise,1A:ExcessiveNoise,1C:ExcessiveNoise,1D:Excessi veNoise,1E:ExcessiveNoise,20:ExcessiveNoise: Coil 18 will be addressed today. If not, then definitely on the next scheduled site visit... 04/09/2003 08:28 scottl@p 01:ExcessiveNoise,03:ExcessiveNoise,04:ExcessiveNoise,05:ExcessiveNoise,07 :ExcessiveNoise,08:ExcessiveNoise,09:ExcessiveNoise,0A:ExcessiveNoise,0B:E xcessiveNoise,0C:ExcessiveNoise,0D:ExcessiveNoise,0E:ExcessiveNoise,0F:Exc essiveNoise,10:ExcessiveNoise,11:ExcessiveNoise,12:ExcessiveNoise,13:Exces siveNoise,14:ExcessiveNoise,15:ExcessiveNoise,16:ExcessiveNoise,17:Excessi veNoise,18:ExcessiveNoise,19:ExcessiveNoise,1A:ExcessiveNoise,1B:Excessive Noise,1C:ExcessiveNoise,1D:ExcessiveNoise,1E:ExcessiveNoise,1F:ExcessiveNo ise,20:ExcessiveNoise: Coil with excessive noise alarms will be re-tuned on the next site visit. 04/08/2003 22:49 D._Chase All three sites were visited for General Maintenance on 4-8-03. Transceivers were checked for tune and any major concerns that have been noted since the last visit. No problems were found. 03/31/2003 08:49 Alan_Bro Coil 0E needs to be tuned. This will be addressed on the next site visit. Coil 0E PARAMS: 2003/03/31 05:05:09 | 6% | 16.1V | 0 | 60 min 2003/03/31 04:05:07 | 27% | Slave | NO | 2264 03/23/2003 20:00 darren@p 11:Overrun: This transceiver was addressed on Thursday 3-20-03. It was in an overrun condition but after retuning and adjusting the power supply I was able to unlock the overrun condition. We will monitor for further alarms. I also noticed that antenna 18 was noisy and could not be brought back to a normal level although the level is acceptable it appears that there may be the possibility that there may be broken conduit. We will have to further inspect for this situation. 03/22/2003 10:26 scottl@p 02:ExcessiveNoise,09:ExcessiveNoise,0E:ExcessiveNoise,11:ExcessiveNoise,14 :ExcessiveNoise,18:ExcessiveNoise: 02:ExcessiveNoise,09:ExcessiveNoise,0E:ExcessiveNoise,11:ExcessiveNoise,14 :ExcessiveNoise,18:ExcessiveNoise: This site was recently tuned. The noise on coil 18 is of concern.Will look into this on Monday and consult with PTOC staff on what may be happening. 03/22/2003 10:22 scottl@p 02:ExcessiveNoise,09:ExcessiveNoise,0E:ExcessiveNoise,11:ExcessiveNoise,14 :ExcessiveNoise,18:ExcessiveNoise: This site was recently tuned. The noise on coil 18 is of concern.Will look into this on Monday and consult with PTOC staff on what may be happening. 03/17/2003 10:28 alan@psm 11:Overrun: We will investigate the overrun issue on our next General Maintenance Check. 03/14/2003 11:11 Scott_Li Reviewed entire status of these sites and did not detect any significant events that warrants attention. 03/14/2003 09:59 scottl@p 11:Overrun: Overruns not excessive, warrants no action. 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:28 darren@p 18:LowExcCurrent: I pca'd into site and changed the current alarm until PTOC personnel are down at the site for maintenance. 03/07/2003 08:15 darren@p 11:Overrun: This transceiver has not detuned as far as I can tell. It will be addressed on the next site visit. 03/06/2003 09:25 darren@p 18:LowExcCurrent: I will adjust the current alarm on transceiver until PTOC personnel can get to site and find out why the current dropped .3A shortly after site was tuned. 03/05/2003 08:33 darren@p 18:LowExcCurrent: The unit has dropped .3A since fine tuning. I will PCA into site and change the alarm level until I can get on site to find the problem. 03/03/2003 22:09 darren@p 18:LowExcCurrent: 2003/02/27 13:41:05 3.5A -------------=====|* 1% *=====-------------- 15.9V =================|=* 3% *===|============- -- 36C ---========|===*==== 2003/02/27 14:41:06 3.5A -------------=====|* 2% *=====----------- --- 15.9V =================|=* 5% *===|============--- 38C --- ========|====*=== 2003/02/27 15:41:07 3.5A -------------=====|* 2% *=====----------- --- 15.9V =================|=* 3% *===|============--- 38C --- ========|====*=== 2003/02/27 16:41:07 3.2A -------------=====*= 1% *=====----------- --- 15.9V =================|=* 70% ====|========*===--- This transceiver appears to have gone out of tune only three hours after being fine tuned. This is what is causing the alarms. I will PCA into site tomorrow and reset the current alarm. There may be a problem with this unit. It will be monitored and addressed on the next visit. 03/02/2003 21:10 darren@p 01:TestTagFailure,02:TestTagFailure,03:LowExcCurrent,03:TestTagFailure,04: LowExcCurrent,04:TestTagFailure,05:LowExcCurrent,05:TestTagFailure,06:LowE xcCurrent,07:LowExcCurrent,07:TestTagFailure,08:TestTagFailure,09:TestTagF ailure,0A:LowExcCurrent,0D:LowExcCurrent,0D:TestTagFailure,0E:LowExcCurren t,0E:TestTagFailure,0F:LowExcCurrent,0F:TestTagFailure,10:TestTagFailure,1 2:LowExcCurrent,16:LowExcCurrent,17:LowExcCurrent,18:LowExcCurrent,1B:LowE xcCurrent,1D:LowExcCurrent,1F:LowExcCurrent,1F:Overrun,20:LowExcCurrent: These alarms were generated while PSMFC personnel was performing the fine tuning of transceivers after the ladder was watered up for the 2003 season. 02/27/2003 08:48 darren@p 03:LowExcCurrent,0A:LowExcCurrent,0C:Overrun,0E:LowExcCurrent,0E:Overrun,1 3:LowExcCurrent,18:LowExcCurrent,1B:LowExcCurrent,1D:LowExcCurrent,20:LowE xcCurrent: The ladder was watered up last night at 17:05 and was rough tuned for Data Collection. We will be going through the site today and fine tuning all transceivers and recording the data. 02/26/2003 17:41 Darren The ladder watered up at 17:05 on Wednesday the 25th of february. The transceivers were rough tuned and the buffers were cleared. The trnasceivers will be fine tuned in the morning. The DCP was set for SOP on file generation and upload. The first file after water up and tune is BO103057.H. I will update more information after fine tuning tomorrow. 02/21/2003 08:13 Dave It looks like power to (and communications with) the Bradford Island PIT tag detection system was restored just after 3:00 pm yesterday, Feb. 20. 02/20/2003 09:02 Darren_C I spoke with Tammy Mackey yesterday and she told me that there was work being done on pumps and difussers at Bradford Island and that power has been turned off in that area. She said that it should be restored sometime today (2-20-03). She also informed me that Bradford Island water-up has been pushed back until next Thursday (2-27-03), this may be subject to change, of course. I apologize for not getting this in sooner. 02/19/2003 16:13 Scott_Li Called Dean B. and asked him to pop into the Pittag room to check on things in order to help identify why the platform is not reporting. This will be done first thing tomorrow morning, 2/20/03. 02/05/2003 10:28 darren@p 0B:LowExcCurrent,13:LowExcCurrent,20:LowExcCurrent: This site has been dewatered and will not return to production data collection until the end of the month. 02/03/2003 08:34 DChase The site was de-watered at approx. 08:00 on Monday 2-3-03. The transceivers were turned "Off" and tagged out by PSMFC with the Bonneville operators watching. The last Data Collection File for "2002" was BO103034.B and was submitted to Gladstone at approx. 08:15 on Monday 2-3-03. The ladders both "A" and "B" branches will be out approx. 25 days. PSMFC will do inspections in that time frame. 02/01/2003 23:19 darren@p 0A:Overrun,0B:LowExcCurrent,13:LowExcCurrent,20:LowExcCurrent: 0A:Overrun,0B:LowExcCurrent,13:LowExcCurrent,20:LowExcCurrent: This site will be de-watered on Monday 2-3-03 at approxiamtely 7:00. The ladder will be inspected before it is watered up for the upcoming year. We will inspect all conduit that is inside the ladder for breakage that may have contributed to noise problems that were seen in the last year. 02/01/2003 23:19 darren@p 0A:Overrun,0B:LowExcCurrent,13:LowExcCurrent,20:LowExcCurrent: This site will be de-watered on Monday 2-3-03 at approxiamtely 7:00. The ladder will be inspected before it is watered up for the upcoming year. We will inspect all conduit that is inside the ladder for breakage that may have contributed to noise problems that were seen in the last year. 01/29/2003 09:06 Darren_C I spoke with Tammy Mackey this morning and was informed the both branches will be dewatered at Bradford Island on Monday Feb 3rd. The "A" branch will be taken down to tailwater and the "B" branch will be "dry". I will be on site at 07:30 on monday to walkthrough with Tammy and turn off power and tagout the breaker at the transceiver distribution panel so they can do maintenance. 01/24/2003 16:12 Darren_C I spoke with Tammy Mackey yesterday while I was down there and found out that Bradford Island will be de-watered on Feb. 3rd but that they will only be de-watering the "B" branch the "A" branch will not go down at all so we will not be inspecting that branch. 01/02/2003 10:11 alan@psm 09:TestTagFailure: Alarm appears to be caused by sychronization of the timer tag being fired and the status dump being sent. The problem is being addressed by PTOC personnel. 01/01/2003 12:07 Dave Initialized new event log for 2003. 2002 event log has been archived. ####End of Event Log for BO1###