EVENT LOG FOR SITE BO1 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/30/2002 11:18 Alan The Utility computer at BO1 (Bradford) is back online as of 11:20AM, 12-30-2002. 12/29/2002 12:39 Darren_C I PCA'd into the site to find out why it was not loading. I found something rather interesting. Minimon was collecting data with the right date and time stamp. Under status however the time for next file and upload time both said 0 seconds and at the bottom of the screen it said "waiting for host to acknowledge transfer". I stop and restarted minimon and the times came back on screen i.e. 5 hrs. 59 min. and counting. I will send the log file to John when I get down there on Monday. 12/18/2002 17:08 darren@p 06:Overrun,09:TestTagFailure,11:Overrun: Transciever 11 was retuned on 12-16-02. The test tag failures will be addressed. The overrun condition on coil 06 is probably because of tuning. . 12/18/2002 12:35 Don_Warf -------- Original Message -------- Subject: ladder outages and such Date: Wed, 18 Dec 2002 11:55:58 -0800 From: "Mackey, Tammy M NWP" To: "'Chase Darren'" , "'Livingston Scott'" , "'Warf Don'" Washington Shore and Cascade Island will be coming back in service on 09 January unless contractors request an extension. Bradford Island will be coming out of service on 21 January. Tammy 12/11/2002 13:32 scottl@p 11:Overrun: This problem will be addressed the week of Dec. 16th. . 12/11/2002 10:02 darren@p 11:Overrun: This alarm will be inspected next wekk while PSMFC pPTOC personnel are on site. . 12/09/2002 08:48 darren@p 11:Overrun: The "overrun" condition is being investigated by PTOC personnel. This transceiver will be addressed on the next site visit. The exciter report does show some degradation of the "antenna/transceiver" system so by optimizing the system we may be able to eleviate the error. . 12/06/2002 08:38 darren@p 06:Overrun,11:Overrun: These trasnceivers will be checked out on the next site visit. The "overrun" condition is being investigated by PTOC personnel. . 12/05/2002 08:08 darren@p 11:Overrun: This unit will be looked at on the 16th when we are on site. I will check the coil for failures. . 12/04/2002 15:08 scottl@p 11:LowExcCurrent,11:Overrun,12:BadExcFreq,12:BadOscFreq,12:LowExcCurrent: These errors were corrected by PTOC. Will monitor for future occurances.. . 12/03/2002 16:03 darren@p 09:TestTagFailure,11:Overrun: Site was visited today. Will report findings in tomorrows TASS report. . 12/02/2002 09:44 darren@p 11:LowExcCurrent,11:Overrun: After viewing the Exciter report it appears that the transceiver has de-tuned since 11-26-02 at about 14:00hrs. This will verified on next onsite visit. The mystery is why the system has de- tuned so drastically. The site was visited on 11-22-02 and all transceivers and antenna's were checked and optimized. . 12/02/2002 09:38 darren@p 09:TestTagFailure: Alarm may be caused by the test tag firing at the same time that the status report is being sent to the computer. Although the message "aborted due to system activity" is never seen. . 12/02/2002 09:32 darren@p 1D:Overrun: This alarm condition is being investigated by PTOC personnel. . 11/27/2002 08:44 darren@p 04:ExcessiveNoise,08:ExcessiveNoise,09:ExcessiveNoise,0A:ExcessiveNoise,0C :ExcessiveNoise,13:ExcessiveNoise,14:ExcessiveNoise,16:ExcessiveNoise,18:E xcessiveNoise,1A:ExcessiveNoise,1B:ExcessiveNoise,1D:ExcessiveNoise,20:Exc essiveNoise: Alarms were caused by PTOC personnel performing maintenance on all transceivers. . 11/25/2002 11:50 Darren_C On Friday 11-22-02, Scott and I traveled to Bonneville to check and retune all transceivers. We also megged out all coils and tried to get rough estimates on cable lengths. We did address a few issues that were in need of attention: Coil 03 at BO2 was not firing it's timer tag, The connector to the VTT was loose and not making good connection, this has happened in the past and is due to the wires and the pins that are used for the timer tag. At BO1 we looked at coils 0A,17 that were alerting us to overrun conditions on a quite frequent basis, coil 0A was out of tune and once it was retuned and the power supply adjusted the overrun condition went away,coil 17 was also retuned. 11/25/2002 09:20 darren@p 01:Overrun,03:BadExcFreq,03:BadOscFreq,03:LowExcCurrent,08:LowExcCurrent,0 9:LowExcCurrent,09:TestTagFailure,0A:LowExcCurrent,0A:Overrun,0B:LowExcCur rent,14:LowExcCurrent,17:Overrun,18:BadExcFreq,18:BadOscFreq,18:LowExcCurr ent,18:TestTagFailure,1A:LowExcCurrent,1B:BadExcFreq,1B:BadOscFreq,1B:LowE xcCurrent,1B:Overrun,1B:TestTagFailure,1E:BadExcFreq,1E:BadOscFreq,1E:LowE xcCurrent,1E:TestTagFailure: Alarms were generated by PTOC personnel while performing tuning and maintenance on transceivers. . 11/22/2002 07:13 darren@p 0A:Overrun,0B:LowExcCurrent,17:Overrun: Overrun conditions will be addressed by PTOC personnel today. The LowExcCurrent on coil 0B will also be fixed. The alarm and current are equal, the transceiver current has not changed since 11-12-02. . 11/20/2002 09:03 darren@p 0A:Overrun: The alarm condition will be looked at Friday when the site will visited. The Exciter report does indicate that the Phase has drifted by 2% but the noise "signal" has been elevated since 11-12-02. This unit will be retuned to try and bring the signal level back to a normal operating range. . 11/20/2002 08:59 darren@p 17:Overrun: The overrun condition will be looked at on Friday when the site is visited. The Exciter report does not indicate any outstanding problems. . 11/19/2002 13:25 darren@p 0C:Overrun: This alarm is being investigated by PTOC personnel. Unit will be addressed on next site visit. The exciter report did not show any deviations on Phase or Current. . 11/19/2002 13:21 darren@p 0A:Overrun: This condition is being investigated by PTOC personnel. This unit will be looked at on next site visit. This status report was pulled from the latest file. The noise is high but all else seems to be normal. 0A-6 11/19/02 06:37:40 ALARM MESSAGE: Test Tag Found. ~0A-6 11/19/02 06:37:40 ALARM Reader info: Version: FS1001A 3.11 ~0A-6 11/19/02 06:37:40 ALARM Active: On Unique: Off ~0A-6 11/19/02 06:37:40 ALARM Reader ID#: 0A Master: Off ~0A-6 11/19/02 06:37:40 ALARM Communication (N,8,1) ~0A-6 11/19/02 06:37:40 ALARM COM1 baud rate: 9600 COM2 baud rate: 115200 ~0A-6 11/19/02 06:37:40 ALARM Buffer: Active On Tag Count: 10646 ~0A-6 11/19/02 06:37:40 ALARM Local: COM1 tag codes: Off ~0A-6 11/19/02 06:37:40 ALARM Diagnostics for 0A: ~0A-6 11/19/02 06:37:41 ALARM Temperature: 34C Exciter power: 16.9V ~0A-6 11/19/02 06:37:41 ALARM Exciter current: 3.2A Signal level: 20% ~0A-6 11/19/02 06:37:41 ALARM Exciter phase: 3% Sync input: NO ~0A-6 11/19/02 06:37:41 ALARM Battery: OK Status: Slave ~0A-6 11/19/02 06:37:41 ALARM TestTag delay: 60 min Report delay: 60 min ~0A-6 11/19/02 06:37:41 ALARM Current gain: 120% Current alarm: 2600mA ~0A-6 11/19/02 06:37:41 ALARM Bit counters ~0A-6 11/19/02 06:37:41 ALARM Preambles: 14057 Bad CRC: 496 ~0A-6 11/19/02 06:37:41 ALARM Good reads: 3131 Overruns: 2600 ~0A-6 11/19/02 06:37:41 ALARM Alarms for 0A: ~0A-6 11/19/02 06:37:42 ALARM Memory full After veiwing the exciter report I found that the Current and Pase have remained relatively unchanged. . 11/19/2002 13:00 darren@p 17:Overrun: This unit was giving "overrun conditions earlier in the year and then was adjusted to optimum performance on 7-23-02. There have been a few overrun conditions since but it looks like the condition is back. We will monitor this site and make any adjustments that are necessary on next site visit. . 11/12/2002 08:36 darren@p 17:Overrun: This alarm is being investigated by PTOC personnel. We will be monitoring for further alarms. . 11/08/2002 09:20 darren@p 17:Overrun: Overrun conditions are being investigated by PTOC personnel. . 11/07/2002 08:28 darren@p 17:Overrun: Overrun condition is being investigated by PTOC personnel. . 11/06/2002 10:38 darren@p 0C:TestTagFailure,17:Overrun: The test tag was fired remotely to try and alter the test tag firing and the status dump being sent by the transceiver. This seems to be the cause of the failure will monitor. Overrun condition an unknown. Unit seems to be tuned cannot tell what outside interference there may be. . 11/04/2002 15:33 scottl@p 09:ExcessiveNoise,0F:ExcessiveNoise,17:ExcessiveNoise,20:ExcessiveNoise: Counts not excessive enough to warrant attention. . 11/02/2002 09:01 dlwarf@p 04:Overrun,0C:Overrun,11:BadOscFreq,17:Overrun: Acknowledged. . 10/24/2002 08:18 darren@p 17:Overrun: Alarms acknowledged. 10/23/2002 13:26 scottl@p 01:Overrun,01:TestTagFailure,02:LowExcCurrent,02:TestTagFailure,06:TestTag Failure,17:Overrun: Problems acknowledged 10/19/2002 08:24 darren@p 01:TestTagFailure: Alarm acknowledged. 10/18/2002 08:59 dlwarf@p 01:TestTagFailure,17:Overrun: Acknowledged. 10/16/2002 08:28 dlwarf@p 01:TestTagFailure,17:Overrun: Acknowledged. 10/12/2002 09:33 dlwarf@p 01:TestTagFailure,17:Overrun: Acknowledged. 10/11/2002 08:22 scottl@p 01:TestTagFailure,02:Overrun,02:TestTagFailure,09:TestTagFailure,0A:TestTa gFailure,0E:LowExcCurrent,10:TestTagFailure,11:TestTagFailure,12:TestTagFa ilure,13:TestTagFailure,17:Overrun,17:TestTagFailure,19:TestTagFailure,1A: LowExcCurrent,20:TestTagFailure: These alarms were generated by PTOC during a complete reutend and adjustment of all transceivers. The testtag failures were also corrected. 10/09/2002 11:32 Scott_Li This entry is for maintenance done on Monday Oct.7th. PTOC personnel retuned and calibrated ( set equalization )on all adult transceivers. Also readjusted VTT pcb on coil 10 , bo1 and coil 03 , b02. Timertags for these coils were not being detected. Hit rate after adjustments was at 100 percent. No other problems to report. 10/02/2002 08:41 dlwarf@p 02:Overrun,10:TestTagFailure,15:HighTemp: All coils will be tuned during a site visit on either 10/4 or 10/7. 09/24/2002 08:46 dlwarf@p 10:TestTagFailure,15:HighTemp,1A:HighTemp: Acknowledged. 09/23/2002 08:30 dlwarf@p 10:TestTagFailure: Acknowledged. 09/22/2002 11:54 dlwarf@p 10:TestTagFailure: Acknowledged. 09/21/2002 12:53 dlwarf@p 10:TestTagFailure: Acknowledged. 09/19/2002 08:17 darren@p 10:TestTagFailure: Alarms acknowledged. 09/15/2002 12:33 dlwarf@p 10:TestTagFailure: Acknowledged. 09/14/2002 07:54 dlwarf@p 10:TestTagFailure: 10:TestTagFailure: Acknowledged. 09/14/2002 07:52 dlwarf@p 10:TestTagFailure: Acknowledged. 09/12/2002 08:41 scottl@p 0E:LowExcCurrent,10:TestTagFailure,1E:BadExcFreq,1E:BadOscFreq,1E:LowExcCu rrent,20:LowExcCurrent: These errors were generated by PTOC during a GMC. 09/12/2002 08:28 Scott_Li Noticed in the New Cummulative Efficiency Report, that coil A1 had not detected any fish for the last two day's. PCA'd to the site and the reader was in Standby mode. This was an oversite by me Scott while doing the megger tests. Returned the reader to scan mode. 09/10/2002 10:06 Scott Megger measerments were taken yesterday on all coils. Data from these tests will be entered into the master document and posted to the PSMFC FTP server. Two of the coils of particular interest were 16 and 0E. Coil 0E was drastically detuned. Phase 8 %, Noise ~45% . Retuned xcvr with course adjustment to bring variable cap back to mid-throw, then fine tuned antennae. The megger readings indicates that this antennae is not leaking. Pins 1-6, 1-7, 6-7 were all infinite resistance. Coil 16 required only slight adjustments to bring antennae back in tune. Antennae 16 resistance was 1-6: Inf, 1-7: Inf., 6-7: 500 MegOhms. The resistance across pins 5-7 had not changed from the last reading so we cannot relate the detunig to a change in the antennae resistance. Details will be commented in the master document. 09/09/2002 08:51 darren@p 10:TestTagFailure,1D:Overrun: The test tag failures appear to be caused by the transceiver firing the test tag and exporting a status report at virtually the same time. I will have Scott fire the timer tags while he is down there today. There was no apparent reason for the overrun. 08/29/2002 14:29 Don_Warf All transceivers were set to "Unique Off" at 13:15 PST today. 08/23/2002 09:06 scottl@p 09:TestTagFailure,10:TestTagFailure: Failure not a concern 08/21/2002 10:40 scottl@p 10:TestTagFailure,1D:Overrun: Errors do not require immediate attention 08/21/2002 08:56 darren@p 10:TestTagFailure,1D:Overrun: Alarms have been acknowledged. 08/16/2002 08:27 scottl@p 06:HighTemp,06:TestTagFailure,1A:HighTemp,1F:Overrun: Alarms have been acknowledged 08/13/2002 08:19 darren@p 1D:Overrun: Overrun condition noted. Will monitor for further alarms. 08/02/2002 08:31 darren@p 10:TestTagFailure,1D:Overrun: Problems will be addressed on the next site visit. 07/27/2002 08:19 darren@p 10:Overrun,20:LowExcCurrent: Alarms occurred while PTOC personnel were performing site maintenance. 07/25/2002 09:22 darren@p 10:Overrun,17:Overrun: This problem is being addressed system wide. These 2 particular units have had cronic overrun problems. 07/23/2002 09:26 scottl@p 10:Overrun,17:Overrun,18:LowExcCurrent,18:Overrun,1A:LowExcCurrent,1B:LowE xcCurrent,1B:Overrun,1D:BadOscFreq,1D:LowExcCurrent,1F:Overrun: Most problems in this report were generated by PTOC retuning the transceivers. Course adjustments were made in order to bring the tuning cap back into mid throw so that fine adjustments can be made with minimal effort. 07/23/2002 08:17 scottl@p 10:Overrun,17:Overrun,18:LowExcCurrent,18:Overrun,1A:LowExcCurrent,1B:LowE xcCurrent,1B:Overrun,1D:BadOscFreq,1D:LowExcCurrent,1F:Overrun: Alarms acknoledged 07/20/2002 09:23 scottl@p 10:Overrun,10:TestTagFailure: Excessive overruns, will investigate problem. 07/17/2002 09:12 Scott_Li General maintenance check found that several transceivers were slightly out of tune. Checked all instruments and retuned what was nessesary. No major problems t report 07/06/2002 13:53 darren@p 10:Overrun: Inadvertent noise. Problem has subsided. 07/06/2002 13:51 darren@p 17:Overrun: Inadvertent noise. Problem has subsided. 07/05/2002 08:36 scottl@p 10:Overrun,17:Overrun,18:Overrun: Aware fo this problem, Will tune all xcvrs on the next site visit. 07/03/2002 09:06 scottl@p 10:Overrun,17:Overrun,18:Overrun: Will monitor. 07/02/2002 11:11 scottl@p 10:TestTagFailure: The testtag failure was caused by the reader being in an overrun condition. The reader definitely has something going on. Will investigate this error conditon. 07/01/2002 08:28 scottl@p 10:TestTagFailure: No appearent reason for testag failure 06/28/2002 11:27 Darren_C On Tuesday I met with COE personnel to get the phone lines for BO1, and BO2 installed to the Fiber to Copper converters in the AFF. The lines were tied into the AFF but I could not establish any Dial tone to either pittag room. I verified that dial tone was present at the converters. I called and talked to Roger at EC Electric to find out what was done when dial tone was verified after their work was performed. He explained that there is still one piece of the system that is not right for communications to either pittag room. He said he has passed this information onto the proper people to make a decision on what to do to rectify this situation. Brandt was e-mailed and replied that the vendor IFS has been contacted about replacing the equipment and should know something in a couple of weeks. 06/24/2002 10:19 darren@p 08:BadExcFreq,08:BadOscFreq,08:LowExcCurrent,11:BadOscFreq: Alarms on coil 08 were generated by PTOC personnel while performing maintenance. There was no apparent reason for the alarm on coil 11 we will monitor this and check it out on the next site visit. 06/19/2002 10:39 Darren_C On Monday and Tuesday (6-17,6-18-02) I was on site to perform test and tuning on all transceivers and coils. All coils had a Megohm test performed and the transceivers were noted as to whether or not the analog boards had been modified, they were subsequently tuned. We have placed the trailer at Cascade Island for some shading on the enclosures for Transceivers 09-10 we will monitor this for the overtemp alarms we were seeing on Saturday. The Sunshields will be looked at next week to try and determine what can be done to make them useful in protecting the enclosures from the direct sun. 06/19/2002 10:06 scottl@p 10:TestTagFailure: No apperant reason for the testtag failure. 06/19/2002 10:03 scottl@p 1E:TestTagFailure: 1E-26 06/18/02 10:52:42 ALARM Diagnostics for 1E: ~1E-26 06/18/02 10:52:42 ALARM Temperature: 36C Exciter power: 12.7V ~1E-26 06/18/02 10:52:42 ALARM Exciter current: 4.4A Signal level: 7% ~13-15 06/18/02 10:52:42 ALARM Temperature: 36C Exciter power: 15.7V ~13-15 06/18/02 10:52:42 ALARM Exciter current: 4.0A Signal level: 4% ~13-15 06/18/02 10:52:42 ALARM Exciter phase: 1% Sync input: NO Excessive noise levels at the time that the testag fired was probably the root cause of the testtag 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:42 carters@ 01:ExcessiveNoise: 01:ExcessiveNoise: 01:ExcessiveNoise: ok 06/17/2002 13:42 carters@ 01:ExcessiveNoise: 01:ExcessiveNoise: ok 06/17/2002 13:42 carters@ 01:ExcessiveNoise: ok 06/17/2002 12:12 Don_Warf Found PC1's ethernet cable unplugged due to someone moving the platform cart. It looks like some type of electrical work was performed in the room last Friday. Manually sent all files. 06/16/2002 09:45 Don_Warf PC1 still unreachable. PCAed into PC2 to verify data collection. Will visit the site tomorrow. 06/15/2002 08:59 Don_Warf PC1 has not sent files since Friday. PCA remote session was unsuccessful. PCAed into PC2 to verify data collection. Will visit site on Monday. 06/10/2002 10:54 Scott_Li PCA'd to PC1 and manually sent files with out problem. 06/03/2002 08:30 darren@p 0C:TestTagFailure: Unsure of cause of failure. Tag is firing. 05/31/2002 15:14 Carter_S Turned on Check_Submit flag. 05/29/2002 08:33 Darren_C A General Maintenance Check was performed on each site. No Problems were found. I changed the Status Report send times to 360 min. or once per file. I will do BWL and B2A remotely. 05/28/2002 09:00 darren@p 05:ExcessiveNoise,09:ExcessiveNoise,0A:ExcessiveNoise,10:ExcessiveNoise,14 :ExcessiveNoise,15:ExcessiveNoise,16:ExcessiveNoise,17:ExcessiveNoise,18:E xcessiveNoise,1C:ExcessiveNoise: All will be checked on site visit today (5-28-02). 05/27/2002 08:27 darren@p 04:TestTagFailure: Test tag is firing. This will be checked out on the next site visit. 05/24/2002 08:11 darren@p 04:TestTagFailure: Will check the VTT board on the next site visit. The timer tag is firing . 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/22/2002 08:32 Anthony Tuned all transceivers on site. 05/22/2002 08:14 darren@p 15:LowExcCurrent: The alarm was generated while personnel were performing site maintenance. 05/20/2002 09:34 darren@p 04:TestTagFailure: Test tag was eventually found. It appears to be firing on scheduled intervals. 05/15/2002 08:32 darren@p 09:TestTagFailure: Can't explain the one failure. The timer tag is being seen at regular intervals. 05/13/2002 08:32 darren@p 09:TestTagFailure: Test tag is firing on scheduled intervals. 05/07/2002 09:32 Scott_Li The PCA computer name on PC1 has been corrected to reflect the proper PC I.D. 05/06/2002 11:19 Scott_Li BO1-PC1 PCA machine name has been corrected. Was supposed to be corrected last week but did not get done. PCA will have to restarted before the changes will be reflected. This will done tomorrow, 5/7/02 05/06/2002 11:12 Scott_Li Turned the reader unique setting to off on coils 10.0f,1f,20 at 8:45 pst per Carters suggestion. 05/06/2002 11:06 Scott_Li Set the file submission frequency to upload 4 times per day. 05/05/2002 21:44 Dave The original BO102123.D from BO1-PC1 is non-existent. A 0-byte TMP file exists in the MiniMon DATA directory, but I couldn't locate the actual data file anywhere on PC1. The original file spanned the interval 8:13-9:24 AM (PST) on May 3. I retrieved the BO102123.D file from PC2, spanning the interval 9:00-9:26 AM. I also retrieved BO102123.C from PC2, and excised the duplicate data prior to 8:15 AM. (The clock on BO1-PC2 was 3:40 faster than PC1 during this period). I annotated the "snipped" version of BO102123.C from PC2, and renamed it BO102123.XC. I also internally documented the origin (PC2) of BO102123.D, and renamed it to BO102123.XD. Both files have been loaded to PTAGIS. 05/03/2002 09:53 Scott_Li Changed the number of files generated per day to 4 on both primary and backup computers at 0850pst. 05/03/2002 08:59 darren@p 10:TestTagFailure: It appears that unit is in an overrun condition. This will be addressed on the next site visit. 05/01/2002 13:13 Scott_Li This entry is an appendage to the previous enrty on 4/29/02 refering to when the Pittag interrogation computers starting collecting data from all 32 transceivers. All transceiver breaker panels were turned on along with all 32 xcvrs to the best of my recollection at ~ 1100 hrs. 05/01/2002 08:59 Darren_C The reason for the time differences at this site are due to the fact that when I was there yesterday I noticed that PC1 was off in time. It was readjusted so there shows a time difference in the log. 04/30/2002 14:03 DChase This site is now sending files automatically. I sent the files that needed to be sent and configured PC1 to Autoupload. The site also has the Utility PC online as does BO2. 04/29/2002 09:54 Scott_Li Pittag room installations were completed on 4/26/02. Interrogation computers are actively collecting data and awaiting the I/P connection to be completed by the contractor. The I/P connection should be online sometime on 4/29/02. All network interfaces and the PTTP client on the data collection computers have been preconfigured. The test submission switch in the PTTP client is enabled at this time and auto upload setting is disabled. 04/29/2002 07:04 developm I just noticed that the PTTP transaction submitted at about 14:45 PDT on 28 April contained two files with bogus names, B0102116.A and B0102116.B. Note that these names contain a '0' instead of an 'O' in the 'site code'. Because there is no 'B01' site, the files were not processed by IDL, and they're still sitting in the 'hold' directory. Incidentally, these files contain no data (just the 'header' and 'file close'). 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 08:47 Dave Per Darren, 4/12/02: All transceiver tuning was finished. Destron-Fearing made all the necessary changes to the enclosures as well as a board modification on the analog board. All cable termination's have been completed and the transceivers were tuned by Destron-Fearing and PSMFC. 04/05/2002 13:14 Don_Warf Re-tuned all temporary transceivers on both legs. Replaced transceiver for coil 05 due to high noise. Unit was not collecting data. It was back online at 16:30. Tuning notes on each unit will be posted soon. 03/28/2002 09:55 Carter_S Temporary configuration of BO1: Bradford Island Left Branch A, Weir 48 (coils 05, 06) & Weir 49 (coils 03, 04) Bradford Island, Right Branch B Weir 45 (coils 1B, 1C) & Weir 46 (coils 19, 1A) These coils began interrogation at noon on 3/27/02. Data to be submitted manually Monday, Wednesday and Friday until permanent installation is completed. 03/27/2002 12:53 Carter_S BO1 (Bradford Island) is collecting PIT tag data in a 'temporary, off-line configuration' as of noon today. 8 coils = 2 branches * 2 weirs * 2 coils 03/26/2002 16:25 Carter_S Virtual timer tags set up for all coils. 03/14/2002 09:50 Carter_S From: "Ebberts, Blaine D NWP" To: "'carters@psmfc.org'" , "'Fodrea Kimberly - KEWI-4'" Cc: "Clugston David A NWP" Subject: FW: DACW57-02-C-0003/BONNEVILLE PIT TAG PRODUCTION CONTRACT Date: Thu, 14 Mar 2002 08:41:45 -0800 From: Nomie, Naameh A NWP Sent: Wednesday, March 13, 2002 5:03 PM To: Bannister, Brandt D NWP; Thomas, Jon B NWP; Dasso, Joseph M NWP Cc: Ebberts, Blaine D NWP; Tyrrell, Michael E NWP; Wegner, Brian C NWP; McDowell, Jeffrey R NWP Subject:DACW57-02-C-0003/BONNEVILLE PIT TAG PRODUCTION CONTRACT To All: The Contractor advised the Govt. in writing that he will not be able to complete the work out side the in-water work by April 8, 2002. He projects to complete all work by 22 April 2002 instead. He site the following reasons for being behind schedule: 1. Delay in delivery of PIT TAG Buildings. The Manufacturer needed 6-8 weeks after approval of submittals which was approved on February 6, 2002.. 2. Delay in GFM (Transformer FTQ3) which was supposed to be delivered on February 1, 2002 but, has not been delivered as of this date. The requested time extension is at no costs to the Govt. Please let me know if the requested time extension is ok. I need to hear from you by COB Monday March 18, 2002. Thanks. Naameh 03/07/2002 15:32 bo2_mc1_ Set up coil configuration in ptagis3 database. 03/07/02 15:23 carters Initial log creation for BO1 ####End of Event Log for BO1###