EVENT LOG FOR SITE BO3 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/30/2003 08:16 darren@r 01:ReaderReset,02:ReaderReset,03:ReaderReset,04:ReaderReset,05:LowExcCurre nt,05:ReaderReset,06:ReaderReset,07:ReaderReset,08:ReaderReset,09:ReaderRe set,0A:LowExcCurrent,0A:ReaderReset,0B:ReaderReset,0C:ReaderReset,0D:Reade rReset,0E:LowExcCurrent,0E:ReaderReset,0F:ReaderReset,10:ReaderReset,11:Re aderReset,12:ReaderReset,13:ReaderReset,14:ReaderReset,15:LowExcCurrent,15 :Overrun,15:ReaderReset,16:ReaderReset,17:ReaderReset,18:ReaderReset: All transceivers in the ladder were powered up yesterday by COE personnel. The ladder will not have water until Jan. 5th. PTOC will be on site shortly after to fine tune all transceivers. 12/12/2003 10:04 darren@r 04:LowExcCurrent,05:LowExcCurrent,0A:LowExcCurrent: These transceiver were powered down at 08:39 on 12-10-03. The ladder has been inspected and all fixes have been turned over to COE personnel for rework. The ladder schedule has changed and it will not be watered up until 1-5-04, this is per Tammy Mackey. 12/12/2003 09:57 alan@ree 04:LowExcCurrent,05:LowExcCurrent,0A:LowExcCurrent: These alarms were generated as the ladder was being de-watered. 12/11/2003 15:06 Scott_Li All 400 Khz PIT-tag equipment has been eliminated in the AFF and converted to the ISO 134.2 Khz. The nessesary revised config files were uploaded to the FTP server in the appropriate folder.The ladder is de-watered and will remain that way until Dec. 22 ,03. Data collection platform will remain collecting diagnostic information from the AFF coils even while the site is inactive. The ladder antennas will remain powered off until further notice. More on this conversion topic tomorrow.. 12/10/2003 09:02 darren@r 04:LowExcCurrent,05:LowExcCurrent,0A:LowExcCurrent,20:InputSyncLost,30:Inp utSyncLost: Alarms on weirs 55,57, and 58 were due to the ladder being at oriface flow since Monday 12-8-03. The alarms on coils 20 and 30 were caused by PTOC personnel while changing out the 400Khz equipment for 4 new ISO transceivers (2) on the North Flume and (2) on the South Flume. 12/10/2003 08:59 Darren On Monday 12-8-03 the ladder was taken to an oriface flow at 08:00. On 12-10-03 at 08:39 all transceivers to the ladder were turned off by request of the Bonneville COE personnel. The ladder is b4eing de-watered and will be inspected by PSMFC PTOC staff today 12-10-03. 11/30/2003 08:26 Darren I noticed that there was a detection on only coils 03, and 04 for the last 24 hours. I checked the tag code and found that there were multiple hits on coil 02 on the 28th of november. We may possibly have an aborted tag in the ladder. The ladder is going to be de-watered next week and will be inspected for various things by PTOC personnel. 11/26/2003 08:21 alan@ruf 0E:LowExcCurrent: PTOC will investigate on the next site visit. 11/23/2003 10:10 alan@ree 0E:LowExcCurrent: CLearing the TASS panel, PTOC will continue to monitor. 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 11:06 Darren_C -------- Original Message -------- Subject: BO3 Date: Mon, 17 Nov 2003 09:38:46 -0800 From: Darren Chase To: Pittag event log Site was checked for loading and file generation due to the firewall issues that we have been experiencing at Gladstone. The current file is: BO303321.104 and there were no files to send. 11/17/2003 09:38 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: BO303321.104 and there were no files to send. 11/17/2003 08:23 darren@r 01:RocketPortNoEOT,02:RocketPortNoEOT,03:RocketPortNoEOT,05:RocketPortNoEO T,06:RocketPortNoEOT,0C:RocketPortNoEOT,0D:RocketPortNoEOT,0E:RocketPortNo EOT,12:RocketPortNoEOT,13:RocketPortNoEOT,14:RocketPortNoEOT,16:RocketPort NoEOT,20:RocketPortNoEOT: These alarms were either created or cleared on Friday 11-14-03 at which time PC1 was replaced. PTOC personnel are testing the no EOT problem in the lab and are working with the vendor Comtrol for solutions to this problem. 11/15/2003 14:34 Dave I pcA'd into BO3-PC2 and retrieved BO303318.209. This fills a 73-minute gap in data collection resulting from a site visit by PTAGIS staff yesterday. No data were lost. 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 13:51 Darren Due to the high number of "No EoT" errors we were seeing on PC1 and the fact that the hard drive failed to boot twice on the last visit it was decided to replace the PC. I replaced the PC and the files BO303318.205,206,207, and 208 were sent in for filling the gap of time. There is an eight (8) minute gap between .207 and .208 when PC2 was taken out of data collection for copying files. Up until that time there were no pittag detections. 11/13/2003 10:02 Dave I located and uploaded one outstanding data file, BO303076.104. All available 2003 data files for BO3 have now been loaded to the PTAGIS database. Also discovered that, on both PC1 and PC2, the generic site configurations files were named 'b03-gen.*' (with a zero) rather than the correct 'bo3-gen.*' (with an "oh"). I corrected the names of the 'bo3-gen.map' and 'bo3-gen.db' files, as these files are not in current use. As the 'b03-gen' hardware files ARE currently in use, I simply copied the existing 'b03-gen.hw1' and 'b03-gen.hw2' files to 'bo3-gen.hw1' and 'bo3-gen.hw2', respectively. PTAGIS staff will be on site tomorrow, and can install the correct hardware files at that time. The current versions of the correctly-named configuration files were uploaded to the PTAGIS FTP server, and the mis-named versions have been deleted from the server. 11/13/2003 08:20 darren@r 01:RocketPortNoEOT,03:RocketPortNoEOT,0D:RocketPortNoEOT,20:RocketPortNoEO T,32:RocketPortNoEOT,34:RocketPortNoEOT: These alarms will be dealt with on Friday during a PTOC sight visit. We will be replacing PC1 on the DCP (Data Collection Platform). 11/11/2003 08:33 darren@r 01:RocketPortNoEOT,03:RocketPortNoEOT,10:RocketPortNoEOT,17:LowExcCurrent, 17:RocketPortNoEOT,20:RocketPortNoEOT,30:RocketPortNoEOT,32:RocketPortNoEO T: All the EOT alarms are actually on the same port. This board was replaced on Friday. I will have to investigate this problem on the next site visit or on wednesday when I am back in the office. I installed a new RPC and did not see any failures while I was on site. 11/07/2003 13:18 Darren There was another short time period that PC1 was out of data collection. The file BO303311.209 fills the gap between files BO303311.109 and .110. I had to reboot the PC for maintenance reasons. 11/07/2003 12:57 Darren A site GMC was performed. I also had to replace the second Rocketport card on PC1. Files BO303311.205 and .206 were sent from PC2 to cover the time PC1 was out of collection mode. I tested the port that was fialing and found it to be sound for now. We will be watching to see if the port issues come back. We are working with Comtrol to find an answer to the port buffering issues. 11/03/2003 08:03 darren@r 01:RocketPortNoEOT,10:RocketPortNoEOT,15:ReaderReset,30:InputSyncDetect,30 :InputSyncLost,32:ReaderReset: The alarms for the RP No EoT will be dealt with on the next site visit. The other alarms were caused by random reader resets. This problem has and will continue to be investigated byt PTOC personnel. 10/31/2003 08:10 darren@r 01:RocketPortNoEOT: This problem is being investigated by PTOC personnel in the lab. We are working with comtrol to try and find the cause and possibly fix this situation. 10/27/2003 10:44 darren@r 03:RocketPortNoEOT,12:Overrun: PTOC personnel are looking into the RCP errors of the No EOT failures, although the error is being reported on coil 03 it is actually failing on Port 08 or coil 0B. The overrun condition could be caused by outside sources. Both will be addressed on the next site visit. 10/25/2003 09:18 alan@ruf 11:LowExcCurrent,11:Overrun: Alarm caused by PTOC personel during a GMC. 10/24/2003 13:11 Darren A site GMC was performed on these two sites. At BO3 I had to reposition and test the timer tag on Coil 34 (400khz) because it was not firing at all. I also checked the noise and tune on all transceivers, no problems found. I had to restart Multimon because of the no EOT's that have been seen, although we are getting alarms on different ports it is only one port that has this periodic problem and that is port 08 which is related to coil OB. I will be replacing the rocketport card on the next site visit. The file BO303297.204 was closed 1 minute and 18 seconds early to perform the restart of Multimon and in that time frame there were no pittag detections or timer tags fired. 10/24/2003 11:55 darren@r 10:RocketPortNoEOT,11:Overrun,32:RocketPortNoEOT: All alarms will cleared during site GMC today. 10/21/2003 08:34 darren@r 01:RocketPortNoEOT: This problem will be resolved on the next site visit. 10/20/2003 09:28 darren@r 03:RocketPortNoEOT,10:RocketPortNoEOT: PTOC personnel are aware of this problem and will be addressing it on the next site visit. 10/18/2003 08:26 darren@r 01:RocketPortNoEOT: PTOC personnel are aware of the "no EOT" alarm and are currently working on a solution. We will be implementing a solution on the next site visit. 10/14/2003 21:54 scottl@r 01:RocketPortNoEOT,30:LowExcCurrent,32:LowExcCurrent: The rocket port EOT message is being addessed with Comtrol, the manufacturer of the mux card. This is a problem PTOC is rersolving. 10/13/2003 14:10 Darren As a result of this weekends random "OBOB" firings. I replaced the timer tag and the reader card. The new tag codes for coil 34 are 0B0B020801, 0B0B02080E. I have added them to the ignor.tag file and sent that to Dave M. I could not transfer it over to the PUB FTP directory from BO3. We will watch for future failures. 10/12/2003 14:07 D._Chase After checking the 10:00 file I found that the timer tag or the controller is now firing random tag codes most of which are not in the database so we will see bunches of "fish" or orphan tags. PTOC personnel will probably be down on Monday to rectify this situation. I can't do anything from PCAnywhere this is 400Khz equipment. I will check again later to see if this continuing. 10/12/2003 09:48 Darren |1D 34 03/10/12 03:45:07 0B0B080107 Ignore| 50792 |1D 34 03/10/12 03:45:07 0B0B08010D Ignore| 50853 It appears that whatever happend at BO3 is now working. I could not tell if the timer tag went haywire or if the controller started putting out random codes. I will checkwhen the next file comes in but as of 10:00 everything appears to be working correctly. 10/12/2003 09:42 Darren This what I found in the raw file at 02:57 this morning. |1D 34 03/10/12 02:57:30 0B0808010D NOTFound| 8558 |1D 34 03/10/12 02:57:30 0B0B08010D Ignore| 8607 |1D 34 03/10/12 02:57:35 080B08010D NOTFound| 13576 |1D 34 03/10/12 02:57:35 0B0B08010D Ignore| 13686 |1D 34 03/10/12 02:57:38 0B0808010D NOTFound| 16371 |1D 34 03/10/12 02:57:38 0B0B08010D Ignore| 16408 |1D 34 03/10/12 02:57:38 0B0808010D NOTFound| 16677 |1D 34 03/10/12 02:57:38 0B0B08010D Ignore| 16701 |1C 28 03/10/12 02:58:15 0B0B04020B Ignore| 54988 |1C 28 03/10/12 02:58:16 0B0B040208 Ignore| 55096 |1D 34 03/10/12 02:59:18 0B0808010D NOTFound| 53389 |1D 34 03/10/12 02:59:18 0B0B08010D Ignore| 53487 I will try to PCA into site and possibly reboot this PC. I cannot explain why the ignor.tag file is showing this tag as ignore and not found. This also explains why there were 28 "fish" seen on coil 34 and not on 36 or 38. 10/12/2003 09:20 darren@r 01:RocketPortNoEOT,17:LowExcCurrent: PTOC personnel will be discussing the no EOT prtoblem on Monday. It appears to be a rocketport issue but there is the possibility that it coould be related to Multiimon. The low current alarm was caused by Ptoc personnelwhile doing site GMC. 10/10/2003 13:30 Darren A site GMC was performed. All transceivers were checked for tune and noise. No problems were found. 10/10/2003 12:00 Darren Site was visited for a GMC. I had to reboot PC1 for the "No EOT" alarms. The time gap was 1 minute 24 seconds, there no detections during the down time of PC1. There were no other problems found. 10/08/2003 08:11 darren@r 01:RocketPortNoEOT: This issue will be dealt with on the next site visit. We are trying to resolve some issues with comtrol about the rocketport cards. 10/01/2003 08:58 Dave Retrieved BO303273.105 to fill a 12 minute hole created by PTOC maintenance activities. 09/30/2003 13:46 Darren I cleared the no EOT alarm by rebooting PC1. The file BO303273.206 was sent in from PC2 as the file for filling the gap of time. PTOC staff will be watching for the no EOT alarm and may possibly have replace a rocketport card if needed. I check the 400 gear by rubbing sticks on the coils to ensure detections. No problems found. 09/30/2003 13:21 darren@r 01:RocketPortNoEOT,10:RocketPortNoEOT: The no EOT alarm turned out to actually be coil 0B that was causing the alarms. After a brief discussion with Scott L. we decided to try and reboot the PC first and see if that had any impact on the alarm. PC1 was rebooted and it did solve the EOT problem. I sent various commands to coil 0B without any kind of rocketport failure. We will watch for this alarm in the future and replace componenets as necessary. 09/29/2003 09:18 alan@ree 11:Overrun: This is an ongoing problem. Troy and I ruled out the motors that run the picketed gates nearby. PTOC will continue to investigate. 09/29/2003 08:38 alan@ree 02:LowExcCurrent,08:LowExcCurrent: These alarms were caused by PTOC personel during a site visit. 09/26/2003 12:41 Alan A GMC was performed 9/26/2003. All transceivers were tuned, no problems found. PC1 is within one second of atomic time and PC2 is 14 seconds slower. 09/26/2003 11:06 darren@r 03:RocketPortNoEOT: I checked the "raw" file for any indicators of the infamous parsed staus dump everytime the timer tag fires, which indicates that the rocketport card may need to be reseated, but did not see any such occurance. We will monitor for any future no eot alarms. 09/23/2003 08:41 Don_Warf A short power outage occurred around midnight PST last night that affected B2J and BO3. It did not last long enough to affect the PCs at either site. Dean B. said he would post an entry once the cause is known. 09/23/2003 08:12 dlwarf@r 01:ReaderReset,02:ReaderReset,03:ReaderReset,04:ReaderReset,05:ReaderReset ,06:ReaderReset,07:ReaderReset,08:ReaderReset,09:ReaderReset,0A:ReaderRese t,0B:ReaderReset,0C:ReaderReset,0D:ReaderReset,0E:ReaderReset,0F:ReaderRes et,10:ReaderReset,11:ReaderReset,12:ReaderReset,13:ReaderReset,14:ReaderRe set,15:ReaderReset,16:ReaderReset,17:ReaderReset,18:ReaderReset,20:InputSy ncDetect,20:ReaderReset,22:ReaderReset,30:InputSyncDetect,30:ReaderReset,3 2:ReaderReset: Power outage 09/22/2003 08:17 troy@ruf 01:ReaderReset,02:ReaderReset,03:ReaderReset,04:ReaderReset,05:ReaderReset ,06:ReaderReset,07:ReaderReset,08:ReaderReset,09:ReaderReset,0A:ReaderRese t,0B:ReaderReset,0C:ReaderReset,0D:ReaderReset,0E:ReaderReset,0F:ReaderRes et,10:ReaderReset,11:ReaderReset,12:ReaderReset,13:ReaderReset,14:ReaderRe set,15:ReaderReset,16:ReaderReset,17:ReaderReset,18:ReaderReset,20:InputSy ncDetect,20:ReaderReset,22:ReaderReset,30:InputSyncDetect,30:ReaderReset,3 2:ReaderReset: These alarms were most likely generated from a brief power outage. 09/19/2003 14:59 Dave David Griffith (U of I) contacted me this morning and requested that disable Signal by Code for all Yakama Coho (AC-76). At approximately 2:45 pm (PDT), I updated the map file to BO303262.map on both machines. This map file simply monitors the presence of AC-76 tags at the AFF; it does not issue an alert. I also restored the BO303238.DB database, removed last week, so we can monitor the presence of all Yakama Coho as they ascend the BO3 ladder. The clocks on the two PCs are within 1 second of each other and atomic time. 09/15/2003 09:23 darren@r 01:RocketPortNoEOT,15:Overrun,15:ReaderReset: Alarms will be addressed on the next site visit. 09/12/2003 16:00 Dave As requested by Steve Lee, I replaced the existing database file, BO303238.DB, with the previous version, BO303219.DB. This effectively removes the 24,763 AC-76 tags added on 8/26. Steve reports that U of I has finished radio-tagging fish in this group, and the alerts are no longer necessary. The clocks on the two BO3 PCs are within one second of each other and atomic time. 09/07/2003 08:32 alan@ree 15:Overrun: Acknowledged,PTOC personel will discuss a fix for this on Monday. 09/06/2003 12:07 alan@ruf 12:Overrun,15:Overrun: Acknowledged alarms. PTOC personel will discuss a game plan for fixing this problem on Monday. 09/06/2003 12:01 alan@ruf 01:ReaderReset,02:ReaderReset,03:ReaderReset,04:ReaderReset,05:ReaderReset ,06:ReaderReset,07:ReaderReset,08:ReaderReset,09:ReaderReset,0A:ReaderRese t,0B:ReaderReset,0C:LowExcCurrent,0C:ReaderReset,0D:ReaderReset,0E:ReaderR eset,0F:ReaderReset,10:ReaderReset,11:ReaderReset,12:ReaderReset,13:Reader Reset,14:ReaderReset,15:ReaderReset,16:ReaderReset,17:ReaderReset,18:Reade rReset,20:InputSyncDetect,20:ReaderReset,22:ReaderReset,30:InputSyncDetect ,30:ReaderReset,32:ReaderReset: Apparently, three power failures occurred last night, the longest being about three and a half minutes. I haven't been able to PCA into the site, but as of 9:00 this morning it was loading files. PTOC will continue to monitor. 09/02/2003 13:34 Darren The exciter for coils 24 and 26 was replaced. this mayhave been caused by the brief power disturbance over the weekend. I also adjust transceivers 11, 15, and 17 for noise and overrun's. We will monitor for future alarms. 09/02/2003 07:11 scott_li This needs to bo looked at on the next GMC BO3 AFF NORTH FLUME [400KHZ] 24 0B0B0E0408 0 BO3 AFF NORTH FLUME [400KHZ] 24 0B0B020E01 0 BO3 AFF NORTH FLUME [400KHZ] 24 0B0B080408 0 BO3 AFF NORTH FLUME [400KHZ] 24 0B0B0B020E 0 BO3 AFF NORTH FLUME [400KHZ] 26 0B0B04010D 0 BO3 AFF NORTH FLUME [400KHZ] 26 0B0B04010B 0 BO3 AFF NORTH FLUME [400KHZ] 28 0B0B04020B 0 BO3 AFF NORTH FLUME [400KHZ] 28 0B0B040208 0 09/02/2003 07:09 scott_li $01 Temperature: 38C Exciter power: 14.7V 03/09/01 23:04:30 $01 Exciter current: 4.3A Signal level: 66% 03/09/01 23:04:30 Probably why no timertag and no fish detected. Will address on the next GMC 09/01/2003 08:39 darren@r 01:ReaderReset,02:ReaderReset,03:ReaderReset,04:ReaderReset,05:ReaderReset ,06:ReaderReset,07:ReaderReset,08:ReaderReset,09:ReaderReset,0A:ReaderRese t,0B:ReaderReset,0C:ReaderReset,0D:ReaderReset,0E:ReaderReset,0F:ReaderRes et,10:ReaderReset,11:ReaderReset,12:ReaderReset,13:ReaderReset,14:ReaderRe set,15:LowExcCurrent,15:ReaderReset,16:ReaderReset,17:ReaderReset,18:Reade rReset,20:InputSyncDetect,20:ReaderReset,22:ReaderReset,30:InputSyncDetect ,30:ReaderReset,32:ReaderReset: It Appears there was a brief power disturbance. I will check to see if there was any time gap in the files if not then it was probably shorter than 10 or 15 minutes, that is about how long we get on the UPS in the pittag room. 08/31/2003 09:40 darren@r 11:Overrun,14:Overrun,15:LowExcCurrent: Alarms will be addressed on the next site visit. 08/30/2003 09:58 darren@r 11:Overrun,15:Overrun: These will be addressed on the next site visit. 08/29/2003 08:01 darren@r 11:Overrun: This alarm will be addressed on the next site visit. This transceiver has had chronic overrun problems. The overrun condition is an occasional occurance and may be caused by the lift gate for the ferl. We will try to test this theory. 08/28/2003 08:11 darren@r 15:Overrun,20:InputSyncDetect,20:InputSyncLost,22:ReaderReset: The alarm on coil 20 was generated by a random reader reset. The alarm on coil 15 will be addressed on the next site visit. We have been monitoring the overrun condition on this coil. We were informed by COE personnel at Bonneville yesterday that this ladder will not be de-watered this year so we will not be able to do any maintenance on the antennas or conduit. This may change but for now this is the case. 08/26/2003 18:08 Dave I updated the database to BO303238.DB. This version contains 24,763 additional AC-76 tags (YNCOHO) provided by Scott Prevatte of the Yakama Nation. These tags will trigger the 'Yellow Alert' when they appear at the AFF weir. The clocks on the BO3 PCs are within two seconds of each other and three seconds of atomic time. 08/26/2003 08:23 darren@r 11:Overrun: Although there were only two overrun alarms in this file PTOC personnel will be taking a good look at this transceiver and the surrounding area for potential ambient noise. 08/25/2003 08:28 darren@r 0B:ReaderReset,11:Overrun: The alarm on coil 11 is being investigated by PTOC personnel and will be addressed on the next site visit. There could some outside interference that is causing the overrun condition, but this will need to be tested when we are on site. The alarm on coil 0B appears to be the same phenomenon that we see on the juvenile transceivers. The transceiver did reset after the timer tag was fired, thirty seconds after, but this could be some buffering of data that caused the delay in time. We may try to test this in the lab with an adult transceiver to see if we can duplicate the scenario. 08/21/2003 10:20 darren@r 11:Overrun,20:InputSyncDetect,20:ReaderReset: Alarm on coil 20 was generated by a random reader reset. This is a juvenile transceiver problem that PTOC personnel is aware of. The alarms on coil 11 were inspected by PTOC personnel while performing site GMC yesterday but no direct cause could be located. The transceiver was tuned and checked for noise and no problems were found. We will continue to monitor for this failure and re- tune when necessary. 08/20/2003 15:01 troy@ree 15:ReaderReset,16:LowExcCurrent,16:ReaderReset: Alarms were generated by PTOC personel performing a site GMC. 08/18/2003 10:36 darren@r 12:Overrun: Alarm was acknowledged and will be investigated by PTOC personnel on next site visit. 08/08/2003 08:44 darren@r 0E:RocketPortNoEOT,15:Overrun: The alarm on coil 15 could be caused by broken conduit, we have had trouble with this antenna in the past with noise and overrun's. We think that there could possibly be some cable trouble as well so when the ladder is de-watered we will inspect for these failures. 08/07/2003 11:10 Dave I updated the SbyC map and database at BO3 with files BO303219.map and BO303219.db, respectively. This configuration includes new definitions for Yakama Nation coho (AC #76 - YNCOHO) and COE Kelts (AC #77 - CEKELT). Any of these fish detected in the Adult Lab will activate the 'yellow' alert. The PC clocks are with eight seconds of each other and atomic time. Toad rebooted in the midst of my pcA session with BO3-PC1. This has been a recurring problem this year, specific to Toad. As with prior occurrences, the local reboot had no affect on the status of the remote machine. 08/02/2003 10:06 alan@ruf 11:LowExcCurrent,11:Overrun,15:LowExcCurrent,15:ReaderReset,16:LowExcCurre nt,16:ReaderReset: These alarms were generated by PTOC personel during a GMC. 08/01/2003 14:08 Alan_Bro A GMC was performed 8/1/2003. All transceivers were tuned. Execessive noise was found on Coil 15. Two weeks ago this transceiver was meg at which time it showed bad. We attempted to tune the noise out. We then swapped cables with Coil 16 and the noise followed the Coil. The noise on Coil 15 has been reduced considerably from what it was when we first looked at it. We will continue to monitor this coil and take a closer look at it when the ladder is de-watered. No other problems were noted. 08/01/2003 10:57 darren@r 13:Overrun: Alarm is acknowledged and will be investigated by PTOC personnel today during site GMC. 07/29/2003 12:26 darren@r 0F:ReaderReset,13:Overrun,15:TestTagFailure: Alarms acknowledged and site will be adjsuted on Friday during the next site visit. 07/25/2003 08:15 scott_li Coil 15 is still reporting an excessive amount of " Ecessive Noise" alarms. Not sure whats going, but will address on the next GMC sometime late next week. 07/22/2003 08:08 darren@r 13:Overrun: There were a total of 2 overruns in this file but the noise and current on this transceiver look fine. PTOC personnel will investigate this condition on next site visit. 07/21/2003 08:42 scottl@r 01:ReaderReset,13:Overrun,15:LowExcCurrent,15:ReaderReset,17:LowExcCurrent : All alarms other than the Overrun on coil 13 were generated by PTOC during GMC. Interesting that the "Raw" data file indicates that coil 15 has had numerous errors, example: $15 PROBLEM: Excessive noise level 03/07/21 03:22:07 $15 PROBLEM: Excessive noise level 03/07/21 03:22:19 TASS is not picking up these errors... 07/21/2003 08:35 darren@r 01:ReaderReset,13:Overrun,15:LowExcCurrent,15:ReaderReset,17:LowExcCurrent : The alarms on 7-16-03 were generated by PTOC personnel while performing site GMC. The alarm on 7-20-03was an "overrun" condition and could have been caused by either the Power supply or some external noise. 07/18/2003 11:58 Dave Updated BO3 db to BO303193.db. This version includes yellow alerts for ISO tags associated with fish previously radio-tagged in 2001 and 2002; and red alerts for 400 kHz tags associated with similar groups of previously-tagged fish. 07/17/2003 15:45 darren@r 15:Overrun: Alarms were cleared yesterday but TASS is not clearing. 07/15/2003 15:43 Dave I updated the db file to BO303196.DB. This version contains 3590 new AC75 codes, and 14 'conversions' from AC74 to AC75. The clocks on the PCs are within two seconds of each other and eight seconds of atomic time. 07/14/2003 10:46 darren@r 15:Overrun: This alarm will be addressed on the next site visit. I cannot seee anything from the status that would indicate excessive noise or overrun conditions. 07/10/2003 08:24 darren@r 15:LowExcCurrent: I PCA'd into site and changed the current alarm for coil 15 to 2800. The current had dropped to 3100. PTOC personnel will check into the reasons for the current drop on the next site visit. 07/09/2003 08:11 scottl@r 20:InputSyncDetect,20:InputSyncLost,22:ReaderReset: This problem is not of concern. 07/03/2003 07:58 darren@r 08:LowExcCurrent,17:LowExcCurrent: 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/29/2003 08:02 darren@r 11:Overrun: This transceiver will be addressed on the next site visit. 06/26/2003 14:57 darren@r 15:LowExcCurrent: I PCA'd into site and changed the alarm threshold to 3100mA. When I was onsite trying to figure out what was causing the "overrun" conditions I retuned the transceiver and did not reset the alarm threshold. 06/25/2003 15:12 troy@ruf 11:BadExcFreq,11:BadOscFreq,11:LowExcCurrent,15:LowExcCurrent,16:Overrun,1 7:LowExcCurrent,30:InputSyncDetect,30:ReaderReset: These alarms are being cleared in order to monitor the effectiveness of maintenance performed during a site GMC on 06/23/03 and 06/24/03 06/25/2003 08:53 Darren_C Site was visited yesterday for a GMC. Coils 15 and 16 were checked for the "overrun" conditions that keep appearing on the TASS panel. I went through the tune and checked for read distance. I could not find any direct transceiver cause so I investigated the conduit to see if there was any broken conduit. I could not see if the conduit was broke below the water line but it looked as if the strapping had pulled away from the wall. We will addressing this with the COE personnel for the winter work schedule. We will be inspecting and suggesting what if any additional strapping needs to be added. There is also some work being performed underneath the visitors center on the Washington shore, removal of tanks and pipes the have been de-commissioned, it appears that welding and cutting torches being used. They will be doing this until Friday. 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/19/2003 11:57 Alan At 11:30 I discovered a failed hard drive on the Sun SPARCstation 5 in the pittag room. After speaking with Willy Kelly, I powered it down at 11:40. 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 07:03 darren@r 03:LowExcCurrent,11:LowExcCurrent,11:Overrun,17:LowExcCurrent,17:ReaderRes et,32:TestTagFailure: All alarms on 6-5-03 were caused by PTOC personnel while performing site GMC. The test tag failure on coil 32 will be checked in the raw files, I was unable to see what was the direct cause through the given file provided. 06/06/2003 08:14 Alan A GMC was performed 6/5/2003. Transcievers were tuned, no problems found. 06/05/2003 11:22 darren@r 12:Overrun: This alarm will be addressed today during the 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/03/2003 08:50 darren@r 0A:LowExcCurrent,0E:ReaderReset,0F:LowExcCurrent,12:Overrun,17:LowExcCurre nt: All alarms generated on 5/29 were created by PTOC personnel performing site GMC's. The ReaderReset alarm is unusual to say the least. I think this may be the first random reader reset on an adult transceiver. We will monitor this site for further reader resets. 05/29/2003 12:59 Darren 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/29/2003 10:56 darren@r 0A:LowExcCurrent,12:Overrun,13:Overrun,15:LowExcCurrent: All transceivers will be checked during the site GMC today. The 2 current alarms are due to the threshold and the current being equal. 05/27/2003 10:58 darren@r 0A:LowExcCurrent,12:Overrun: Both transceivers will be adressed on next site visit. Coil 0A will be checked for de-tuning to see if the original current can be achieved. 05/22/2003 08:07 darren@r 0A:LowExcCurrent,0F:LowExcCurrent,0F:Overrun,12:Overrun,17:LowExcCurrent,1 7:ReaderReset: Alarms were generated by PTOC personnel while performing site GMC. 05/21/2003 12:42 darren@r 03:Overrun: This site will be checked and retuned if necessary. I will perform a GMC today. 05/18/2003 08:51 darren@r 03:Overrun: This condition will be rectified on the next site visit. 05/15/2003 09:50 darren@r 03:LowExcCurrent,03:Overrun,03:ReaderReset,03:TestTagFailure,04:LowExcCurr ent,0A:LowExcCurrent,0F:ReaderReset,0F:TestTagFailure,15:LowExcCurrent,15: Overrun,15:ReaderReset,15:TestTagFailure,17:ReaderReset,17:TestTagFailure, 18:LowExcCurrent: Alarms were generated by PTOC personnel while performing GMC's 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:28 dlwarf@r 0A:LowExcCurrent,10:LowExcCurrent: Site will be visited today. 05/01/2003 13:41 Dave Horrendous session with pcA attempting to update the database. Multiple dropped connections, WinCmd hung on PC1 during an FTP download, etc. Local Win2K machine crashed, with the helpful message: "Driver_IRQL_NOT_LESS_OR_EQUAL: Address BFED1C2B base at BFEC8000, DateStamp 3ab8beaa - NDIS.sys". Fortunately, Darren was on site, and assisted in killing and restarting WinCmd on PC1, and completing the FTP download, after which I could re-establish a pcA connection to PC1. Finally updated database on both machines to BO303121.DB, containing ~230k additional yellow and red action codes for U of I. Darren noticed "EOT" messages on PC2 diagnostic of the RocketPort card seating issue, and reseated both cards in PC2. 04/25/2003 16:36 Dave I initiated SbyC at BO3 at ~4:00 pm PDT today. I instantiated three Action Codes (AC-71, AC-72, and AC-73) for U of I. SbyC means "Signal by Code" at this site, as there are audible and visual alerts when target fish are detected at the weirs in the Adult Lab. Fish are manually, rather than automatically, diverted into the facility trap. The action code lists had a number of problems that delayed implementation. These included duplicate tag codes within the AC-73 list, and bad tag codes (invalid or illegal code masks) in both the AC-72 and AC-73 lists. In the instantiated database, AC-71 (UI-RT) has 3,000 tag codes; AC-73 (UI-CHR) has 539,504 tags. Both these groups activate the "red" alerts. AC-72 (UI-CHY) has 817,420 tags; this group activates the "yellow" alerts. 04/25/2003 08:01 darren@r 02:LowExcCurrent,02:ReaderReset,14:LowExcCurrent,17:LowExcCurrent: These alarms were generated by PTOC personnel during a site GMC. 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/22/2003 10:55 darren@r 02:Overrun,14:LowExcCurrent: Alarms will be checked while performing routine GMC on site. 04/19/2003 07:43 darren@r 14:LowExcCurrent: The current and the threshold are equal. We will adjust the threshold to eliminate the alarm and then check the transceiver on next GMC. 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:43 darren@r 14:LowExcCurrent: I checked the raw file and found no direct reason for this alarm. The current is at 3.9A and the threshold is set at 3.8A. I will watch for the current dipping below the threshold. 04/16/2003 12:55 scottl@r 02:Overrun,14:LowExcCurrent: Erros not a concern at this time. 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/07/2003 09:11 Dave Synchronized file and PTTP settings to adjust to DST. 03/24/2003 15:40 Carter_S CEA configuration for bo3 set up. bwl was deleted. 03/14/2003 11:07 Scott_Li Reviewed entire site status, things of concern listed below. A site visit is scheduled for the first of next week, 3/17 to correct these problems. Report run on 14-Mar-2003 00:49:16) BO3 AFF NORTH FLUME (400KHZ) 24 0B0B0B020E 0 $11 PROBLEM: Excessive noise level 03/03/14 03:53:39 $11 PROBLEM: Excessive noise level 03/03/14 03:54:17 $11 PROBLEM: Excessive noise level 03/03/14 03:54:19 $11 PROBLEM: Excessive noise level 03/03/14 03:54:26 $11 PROBLEM: Excessive noise level 03/03/14 03:54:34 $11 PROBLEM: Excessive noise level 03/03/14 03:54:36 $0E PROBLEM: Excessive noise level 03/03/14 04:34:59 $0E PROBLEM: Excessive noise level 03/03/14 04:35:25 $0E PROBLEM: Excessive noise level 03/03/14 04:35:32 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 12:43 Darren_C I PCA'd into site to find out why there had been no file submission since 3-6-03 at 12:00. The collection platform was collecting Data and files were being generated correctly. I checked the history and found that at 12:00 on the 6th PTTP hung waiting for an acknowledgement of file transfer. The light on PTTP was yellow so I clicked the "Start Auto" button and submitted nine (9) files. The next scheduled upload will be in 3 hrs. 02/26/2003 13:55 Darren The site was visited today for a general maintenance check. The "status" and "noise" report delays on the transceivers were changed to match the DCP SOP (Data Collection Platform SOP) along with the file generation and upload frequency. The transceivers are now set with the following parameters: File generation and upload: Timer Tag= 60 min. Files generated a day= 8 Status Report= 60 min. Number of uploads per day= 8 Noise Report= 0 min.(off) delay before upload= 120 seconds. The light and horn were also tested to ensure the operations were correct. 02/19/2003 16:17 Scott_Li PCA'd to sites and issued a DRS command to each transceiver in order to ensure no catastrophic failures have occurred. Will continue to do this periodically until the TASS panel is updated to reflect the integration of B2A and BWL. 01/23/2003 13:58 Dave In order to accommodate 17 new 400 kHz test tag sticks added to the base Multimon database file, I instructed Darren to create a new db file, BO3- gen2.db. This file is now active on BO3-PC1 and BO3-PC2, and has been archived to the 'multimon/Site_Configurations/BO3' directory on the public FTP site. 01/23/2003 13:53 Dave I added 17 more 400 kHz tag codes were added to the base AC-254.db Multimon database file used at these sites. 01/17/2003 18:07 Dave Enabled file checking. 01/17/2003 17:32 Dave PTAGIS staff were notified yesterday (Jan. 16) that the Bonneville Washington shore ladder will water up tomorrow (Jan. 18) am. In preparation for that event, PTAGIS staff traveled to the Bonneville Washington shore ladder PIT tag site (BO3) today, and performed the following configuration/verification procedures: 1) Enabled all transceivers, flushed their buffers, and verified their communication with the centralized computer platform. 2) Identified a bad RocketPort address for coil #15 on the PC2 board at port 10; coil #15 was moved to port 1F on both boards. This change was recorded in a revised BO3-gen.map file, which was then distributed to both PC1 and PC2 and uploaded to the PTAGIS public FTP site. 3) Modified the PTTP file uploading process to direct the data files from the 'testing' to the 'production' port on the PTAGIS file server. In addition, PTAGIS staff remotely synchronized the BO3-PC1 and PC2 clocks within two seconds of each other. As of 3:30 pm today, Jan. 17, the BO3 interrogation site is collecting live data and submitting those data to the PTAGIS database, in preparation for activation of the Washington shore ladder tomorrow morning. 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/08/2003 17:00 Darren The 400 Khz equipment was inadvertantly left on after the site was tested for communications upon the completion of B2A and BWL combination. The equipment will be turned off on 1-8-03 and will not be turned back on until the ladder is watered back up. 01/01/2003 12:07 Dave Initialized new event log for 2003. 2002 event log has been archived. ####End of Event Log for BO3###