EVENT LOG FOR SITE BO2 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 22:56 Darren Both sites have had the transceivers powered on with no water in the ladder. The ladders are to be watered up on Jan. 5th. PTOC personnel will be on site shortly after to fine tune all transceivers and adjust the Data Collection Platforms for the upcoming 2004 season. 12/24/2003 09:39 Alan Manually submitted BO203356.F through BO203358.B. Stopped and restarted Minimon to re-establish automatic uploads. 12/04/2003 08:15 darren@r 01:LowExcCurrent,03:LowExcCurrent,05:LowExcCurrent,0B:LowExcCurrent,0C:Low ExcCurrent,0F:LowExcCurrent,10:LowExcCurrent: This site was decomissioned yesterday at 10:30. All transceivers were powered down for upcoming ladder inspection by PTOC personnel. 12/03/2003 10:29 Darren This site has been de-watered and the transceivers have been powered down for ladder inspections by both COE and PTOC personnel. The ladder is scheduled to be watered up on 12-22-03. The transceivers will be powered up and site tuned for the next season. 12/03/2003 07:38 alan@ruf 04:LowExcCurrent,0E:TestTagFailure: These errors will be corrected on the next site visit. 12/02/2003 09:13 scottl@r 04:LowExcCurrent,0E:TestTagFailure: These errors will be corrected on the next site visit. 11/30/2003 08:18 darren@r 0E:TestTagFailure: This alarm will be checked 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/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: BO203321.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 13:39 Alan A GMC was performed 11-7-2003. All transceivers were tuned. No problems found. 10/25/2003 09:19 alan@ruf 04:LowExcCurrent: Alarm caused by PTOC personel during a GMC. 10/25/2003 08:33 troy@ree 04:LowExcCurrent: This alarm caused by PTOC personnel during site GMC 10/24/2003 13:50 Alan A GMC was performed 10-24-2003. All transceivers were tuned, no problems found. 10/23/2003 09:01 alan@ruf 0C:HighTemp: The ambient temperature only reached 75 degrees F. The direct sunlight may have caused the overtemp alarm. We will investigate during a GMC tomorrow. 10/21/2003 09:02 darren@r 03:ExcessiveNoise,09:ExcessiveNoise,0C:ExcessiveNoise,10:ExcessiveNoise: Noise levels and tune will be checked on the next site visit. 10/21/2003 08:57 darren@r 03:Overrun: There was no direct cause for this alarm. We will inspect this transceiver on the next site visit for "overrun" conditions. 10/18/2003 08:24 darren@r 03:Overrun: Alarm will be investigated on the next site visit. 10/10/2003 12:31 Alan A GMC was performed 10/10/2003. All transceivers were tuned, no problems found. 09/29/2003 10:11 Dave I pcA'd into BO2-PC2, hoping to retrieve the 17 minutes of data missing between BO203269.D & E on BO2-PC1. Unfortunately, these data don't exist on BO2-PC2, either. As long as I was logged in to BO2-PC2, I moved 1857 data files (the entire year, to date) from the PC2-Data directory to the Archive directory. That's a lot of files. 09/29/2003 08:37 alan@ree 03:HighTemp,04:HighTemp,05:HighTemp,06:HighTemp,07:HighTemp,08:HighTemp,0B :HighTemp,0C:HighTemp,0F:HighTemp: alarms are ongoing particular at this site. Not of concern. 09/27/2003 09:30 scottl@r 01:HighTemp,02:HighTemp,03:HighTemp,04:HighTemp,05:HighTemp,06:HighTemp,07 :HighTemp,08:HighTemp,08:LowExcCurrent,09:HighTemp,0A:HighTemp,0B:HighTemp ,0C:HighTemp,0D:HighTemp,0E:HighTemp,0F:HighTemp,10:HighTemp: High temp alarms are ongoing particular at this site. Not of concern. 09/26/2003 10:56 Darren When I arrived for the site GMC I checked the clocks on both PC1 and PC2 and found them to be 16 minutes off of "real" time. I adjusted both PC's for the correct time. The time to reset PC1 was 1min. 32 sec. and there were no PITtag detections during this time. There was no delay setup in the upload process which could even more delay in sending of the files. I will check all transceivers for tune and noise as well as noting the temperature's. I cleared the TASS panel for this site this morning of all the "high temp" alarms and would expect to see even more over the weekend. This could be due to the unseasonably warm weather and the position of the sun. 09/26/2003 10:50 darren@r 01:HighTemp,02:HighTemp,03:HighTemp,04:HighTemp,05:HighTemp,06:HighTemp,07 :HighTemp,08:HighTemp,09:HighTemp,0A:HighTemp,0B:HighTemp,0C:HighTemp,0D:H ighTemp,0E:HighTemp,0F:HighTemp,10:HighTemp: Due to the unseasonably warm weather we will probably see high temp alarms over the next couyple of days. I will note the temp's of each transceiver today during my site GMC. 09/25/2003 16:48 Alan I PCA'd into PC1 to to see why the files hadn't loaded and found all in order. I then checked Recent Interrogation File Load Status and saw that the tardy files had been processed at 16:20. We will be on site tomorrow and will investigate further. 09/25/2003 16:33 Don_Warf PTOC will be on site tomorrow to check this out. -------- Original Message -------- Subject: Problems with remote data sites... Date: Thu, 25 Sep 2003 16:15:55 -0700 (PDT) From: pittag@psmfc.org To: sitemaint@psmfc.org The following problems with remote sites were detected; bo2: Last data submission was received on Thu Sep 25 6:17:00 PST 2003 Please check this out. . 09/22/2003 08:20 scott_li Noticed in the Recent Interrogation File Load stats that not upload the 265.b file. Checked the Files Received but Loaded folder and the.B and C files are sitting in the cue waiting to be processed. No other action required. 09/04/2003 12:42 dlwarf@r 01:HighTemp,02:HighTemp,03:HighTemp,04:HighTemp,05:HighTemp,06:HighTemp,07 :HighTemp,08:HighTemp,09:HighTemp,0A:HighTemp,0B:HighTemp,0C:HighTemp,0D:H ighTemp,0E:HighTemp,0F:HighTemp: High temp alarms noted. 09/03/2003 09:03 alan@ruf 0C:HighTemp: The ambient temperature only reached 62 degrees F. The direct sunlight may have caused the overtemp alarm. We will investigate during our visit Friday. 08/31/2003 09:38 darren@r 01:HighTemp,02:HighTemp,03:HighTemp,04:HighTemp,05:HighTemp,06:HighTemp,07 :HighTemp,08:HighTemp,09:HighTemp,0A:HighTemp,0B:HighTemp,0C:HighTemp,0E:H ighTemp: The high temps lasted about two hours and although it is not very hot ambient wise the sun has changed it's position in the horizon and this may have a little to do with getting the high temp's. we will watch for future alarms. 08/29/2003 07:52 darren@r 0C:HighTemp: Although the temperature was not all that high on this day the direct sunlight may have caused the overtemp alarm. The temp only reached 61 F and receeded within the next hour. 08/21/2003 10:01 alan@ruf 01:TestTagFailure: These alarms were generated before yesterday's GMC. 08/20/2003 12:12 Alan A GMC was performed 8/20/2003. All transceivers were tuned and the VTT re-enabled on Coil 01. No problems found. 08/20/2003 12:07 alan@ree 01:TestTagFailure: The VTT has been re-enabled. 08/19/2003 08:37 alan@ree 01:TestTagFailure: This will be addressed during a GMC tomorrow. 08/18/2003 10:41 darren@r 01:TestTagFailure: Test tag is not currently turned "on". This will be rectified on the next site visit. 08/15/2003 08:28 alan@ree 03:HighTemp,04:HighTemp,05:HighTemp,07:HighTemp,08:HighTemp,0B:HighTemp,0C :HighTemp: The temperature was 95 degrees F in Cascade Locks yesterday. We've learned that high temp failures can occur when outside ambient approaches 100 degrees F. 08/11/2003 10:18 scottl@r 01:TestTagFailure: More than likely the reason for the TT not firing is the VTT was manually turned OFF at the mechanical switch. Will check this out on the next GMC 08/08/2003 21:48 troy@ruf 01:TestTagFailure: This TT will be turned on during the next site visit. 08/08/2003 08:35 darren@r 0C:HighTemp: This alarm was generated by warm weather. PTOC staff is aware of the potenetial high temp alarms when the temperature outside rises near 90-100 degrees F. 08/08/2003 08:33 darren@r 01:TestTagFailure: This alarm will be addressed on the next site visit. The timer tag was turned off during a tuning test and was not turned back on. The tag that was in the field has left the ladder so this unit will need to be retuned for maximum read range at that time as well. 08/07/2003 15:51 Darren_C The test tag for coil 01 is also not firing, if you see this on the TASS panel do not worry the test tag has not failed. I was doing reader tuning using the hit rate and I turned the test tag "off". It will be turned back "on" on the next site visit. 08/07/2003 15:48 Darren_C I was viewing the "raw" files for this ladder to find out how the noise levels were doing on coil 01 and I found information that points to the "mystery" tag leaving the ladder. This is the stream of Data from report BO203219.C. The last time stamp is 07:03:26. We will keep an eye out for this tag on coil 0F. 0B 08/07/03 06:58:27 3D9.1BF13E29ED XX 05 0F 08/07/03 06:58:30 3D9.1BF13E29ED XX 07 05 08/07/03 06:58:58 3D9.1BF13E29ED XX 09 09 08/07/03 06:59:02 3D9.1BF13E29ED XX 0B 0D 08/07/03 06:59:07 3D9.1BF13E29ED XX 0D 12 08/07/03 07:03:26 3D9.1BF13E29ED XX 0F 08/07/2003 13:45 Darren_C On Tuesday I went to the site and looked into the coil 01 mystery tag and found that the tag is in the field but not completely. I was able to use the comparator to allow the processor to stop reading the tag, for now, and still read tags that pass through the antenna. I checked the read range and was still able to get a usable distance, if the tag does "move" however this could all change as the tag will begin to start reading again. We will be getting into the ladder with a hand reader when it is de-watered to find and remove this tag from the ladder. 08/06/2003 08:21 troy@ruf 01:TestTagFailure: PCA'd into this site and checked the hit rate of this coil. It went from 10% to 1%. Toggled the reader in and out of scan and the test tag failed. A noise report showed elevated noise levels. This will be addressed on the next site visit. 08/04/2003 15:04 Carter_S BO2 Coil ID 01 Tag Code: 3D9.1BF13E29ED has generated over 1.2 million records in interrogation files and over 75,000 in the obs_data table in PTAGIS. Turned 'unique on' for this coil. This antenna should be inspected for a tag in the vicinity and the tag removed next time the ladder is de-watered. This message contains data in an unrecognized format, image/gif, which is being decoded and written to the file named "/tmp/Blank Bkgrd.gif". If you do not want this data, you probably should delete that file. Wrote file /tmp/Blank Bkgrd.gif GIF89a- - , - - @ p n Z'6) H"bʶ*rlβgx 06/06/2003 08:14 Alan A GMC was performed 6/5/2003. Transcievers were tuned, no problems found. 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. 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/27/2003 10:55 darren@r 0C:HighTemp: This site will refitted with the PTOC cooling tool on next site visit. 05/21/2003 12:41 darren@r 03:Overrun: This transceiver was retuned last week to optimize hit rate. Today I had to adjust power and comparator to reoptimize hit rate. 05/18/2003 08:50 darren@r 03:Overrun: This condition will be rectified on the next site visit. 05/15/2003 09:46 darren@r 01:TestTagFailure,03:LowExcCurrent,03:Overrun,03:TestTagFailure,04:TestTag Failure,0D:TestTagFailure,0E:TestTagFailure: All alarms were generated by PTOC personnel while performing site GMC. 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/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/08/2003 08:27 dlwarf@r 03:TestTagFailure: Issue to be addressed today. 05/06/2003 08:36 darren@r 03:TestTagFailure: This transceiver will be replaced on the next site visit. We tried to replace it once before but the analog boards on the replacement was bad so we had to swap analog boards as well as V.T.T. boards and there is where the problem lies. 05/05/2003 08:46 darren@r 03:LowExcCurrent,03:TestTagFailure,05:LowExcCurrent: Alarms were generated by PTOC personnel while performing site GMC. 04/29/2003 08:18 darren@r 03:TestTagFailure: This alarm will be addressed on Wednesday during the site GMC. 04/25/2003 07:59 darren@r 03:TestTagFailure: This transceiver was replaced on 4-22-03, but the new transceiver was missing the VTT board and had a bad analog board so we had to swap it out with the old one. We are verifying the analog board in the lab. We will replace what is necessary on Wednesday of next week. 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 09:18 scottl@r 03:Overrun,03:TestTagFailure: The overrun and TT failure has been corrected by PTOC. Per Darren, the analog PCB was Swapped in the reader to correct this problem. 04/22/2003 10:42 darren@r 03:TestTagFailure: This transceiver will be replaced during routine GMC. We will monitor new transceiver for similar failures. 04/21/2003 08:33 darren@r 03:TestTagFailure: This alalrm will be checked on the next site visit. This has been an ongoing alarm. We may replace the analog board if the connector cannot be fixed. 04/19/2003 07:39 darren@r 03:TestTagFailure: This alarm has been addressed in the past. We may have to swap an analog board on this unit or check the connector. The unit is working and is tuned. 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:37 darren@r 03:TestTagFailure,09:TestTagFailure: These transceiver failures will be checked on the next site visit. The failure on coil 03 has happened in the past and may be caused by the connector to the VTT (virtual Timer Tag). This may need to be replaced. 04/16/2003 12:43 scottl@r 05:ExcessiveNoise,06:ExcessiveNoise,07:ExcessiveNoise,08:ExcessiveNoise,09 :ExcessiveNoise,0B:ExcessiveNoise,0C:ExcessiveNoise,0D:ExcessiveNoise,0E:E xcessiveNoise,0F:ExcessiveNoise,10:ExcessiveNoise: Alarms are not of immediate concern. 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. 04/08/2003 07:35 alan@psm 03:TestTagFailure: No apparent reason for failure, I will investigate later today. 04/05/2003 07:09 darren@p 03:TestTagFailure: No direct cause found. This site will be visited on Tuesday 4-8-03 for a Maintenance check and all transceiver issues will be addressed at that time. 04/04/2003 12:35 darren@p 03:TestTagFailure: Unit may need retuning. The site visit is scheduled for next Tuesday. The alarm will be addressed at that time. 04/02/2003 09:03 ptagdev@ 10:ExcessiveNoise: Attempting to clear red light as test of reset functionality. Doug Clough 03/25/2003 09:53 darren@p 03:TestTagFailure: The alarm has no direct cause. The unit will be checked for tuning on next site visit. 03/21/2003 13:46 Dave I enabled site polling. 03/14/2003 11:11 Scott_Li Reviewed entire status of these sites and did not detect any significant events that warrants attention. 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. 02/27/2003 08:46 darren@p 03:TestTagFailure: The Timer Tag circuit was adjusted and the cable was re-routed. The connection appeared to intermitten on the cable. Unit was checked for hit rate on the timer tag and then it was tested. It seems to have stabilized. 02/26/2003 15:55 Darren A general maintenance check was performed on this site. All transceiver "Timer Tag", "Status", and "Noise" report settings were verified for standard PSMFC SOP. The file generation and upload settings on the DCP were changed to reflect the SOP. The settings are as follows: Timer Tag= 60 min. File Generation= 8 per day Status Report= 60 min. File upload= 8 per day Noise Report= 0 min. Upload Delay= 120 seconds. 02/26/2003 13:56 darren@p 03:TestTagFailure: 03:TestTagFailure: This transceiver will be addressed today during the general maintenance check of site. 02/26/2003 13:56 darren@p 03:TestTagFailure: This transceiver will be addressed today during the general maintenance check of site. 02/24/2003 08:17 darren@p 03:TestTagFailure: This will be investigated this week while I am on site for BO1 water-up. The transceiver appears to be in tune and the noise is low. 02/20/2003 09:18 darren@p 08:Overrun: This transceiver will be addressed next week on the site visit. PTOC personnel are working on finding a solution for this equipment parameter. 02/19/2003 11:05 darren@p 08:Overrun: This transceiver will be addressed on the next site visit. 02/19/2003 10:53 darren@p 03:Overrun,03:TestTagFailure: This transceiver will be addressed on the next site visit. I should be down there next week. 02/06/2003 10:16 darren@p 09:TestTagFailure: We will monitor for further alarms. There does not appear to be any direct cause for this one (1) failure. 02/05/2003 10:30 darren@p 01:LowExcCurrent,04:LowExcCurrent,05:LowExcCurrent,07:LowExcCurrent,08:Low ExcCurrent,0A:LowExcCurrent,0A:Overrun,0B:Overrun,0D:LowExcCurrent,0E:LowE xcCurrent,10:LowExcCurrent,10:Overrun: This site was fine tuned on Monday 2-3-03. I will monitor for further alarms but these have all been addressed. 02/01/2003 23:17 darren@p 01:LowExcCurrent,05:LowExcCurrent,0A:LowExcCurrent,0A:Overrun,0B:Overrun,0 D:LowExcCurrent,10:LowExcCurrent,10:Overrun: 01:LowExcCurrent,05:LowExcCurrent,0A:LowExcCurrent,0A:Overrun,0B:Overrun,0 D:LowExcCurrent,10:LowExcCurrent,10:Overrun: I will be on site Monday 2- 3-03 to re-tune the transceivers now that water is in the ladder. I will also be taking the measurements for the coils again. 02/01/2003 23:16 darren@p 01:LowExcCurrent,05:LowExcCurrent,0A:LowExcCurrent,0A:Overrun,0B:Overrun,0 D:LowExcCurrent,10:LowExcCurrent,10:Overrun: I will be on site Monday 2- 3-03 to re-tune the transceivers now that water is in the ladder. I will also be taking the measurements for the coils again. 01/30/2003 00:30 Dave I updated the current BO2 record in the 'obs_site_dates' table to reflect a facility 'start_date' of 1/28/03 15:00, and indicated in the 'obs_notes' field that the transceivers were switched from standby to active at 8:00 on 1/29/03. 01/29/2003 08:54 Darren_C After having a conversation with Tammy Mackey yesterday morning I believed that the ladder was to water up this morning. I got back into the office this morning and found e-mail and a voice message from Tammy that indicated that the ladder watered back up yesterday at 15:00. I PCA'd into the site this morning and turned the transceivers from "standby" to "read". The Data collection Platform was already setup on Thursday the 23rd on January. The site is considered in Production mode as of 8:06 this morning. I will visit the site to fine tune the transceivers on Monday the 3rd of February. 01/24/2003 08:13 Darren_C I was onsite yesterday to turn the power back on to the transceivers and set the data collection platform for the upcoming season. I restored the power but since there was some concern about this site actually watering up, the transceivers were tuned and then placed in "standby" mode. I was told by Tammy M that they may water up on Monday but they may wait until the end of February. I will call her on Monday and if there is water I will PCA into the site and remotely turn on the transceivers. Bradford Island is still scheduled to be dewatered on Feb. 3 but they are only doing the "B" branch they do not intend to dewater the "A" branch at all. I will know more on Monday. 01/09/2003 12:50 Darren Troy Humphrey and I did a walk through inspection of these 2 ladders. We did notice some coils at BO3 that are showing signs of delamination. Also the conduit that was fixed at BO3 was on coil DB/11, it may explain the noise problems that we were seeing with this particular coil. No unusual sightings at BO2. 01/01/2003 12:07 Dave Initialized new event log for 2003. 2002 event log has been archived. ####End of Event Log for BO2###