EVENT LOG FOR SITE BO3 The first line of each entry contains a date/time stamp & who is reporting. The most recent entry is listed first. Date Time Who ---------- ----- -------- 12/31/2008 07:10 troy@bay 15:TestTagFailure: Known problem antenna. 12/30/2008 07:21 troy@bay 15:TestTagFailure: Noted 12/29/2008 07:55 alan@bay 15:TestTagFailure: Noted. Problems on this system have been documented. 12/28/2008 07:47 alan@bay 15:TestTagFailure: Noted. Problems on this system have been documented. 12/26/2008 10:01 alan@bay 15:TestTagFailure: Noted 12/25/2008 09:31 alan@bay 15:TestTagFailure: Noted. Clearing TASS on a known problematic system. 12/24/2008 07:40 alan@bay 15:TestTagFailure: Noted. Clearing TASS on a documented problem system. 12/23/2008 07:14 alan@bay 15:TestTagFailure: Noted. Clearing Tass on a known problematic system. 12/22/2008 07:43 alan@bay 0A:LowExcCurrent,15:TestTagFailure: The alarm on 0A was dealt with yesterday. Clearing Tass on known problem antenna 15. 12/21/2008 08:08 darren@b 0A:LowExcCurrent,15:TestTagFailure: I will adjust the current threshold for antenna 0A. The alarm on 15 is on a problematic system. 12/20/2008 08:54 darren@b 0A:LowExcCurrent,15:TestTagFailure: I will investigate the alarm on 0A but the alarm on 15 is on a problematic system. 12/19/2008 08:49 darren@b 15:TestTagFailure: Alarm on problematic system. 12/19/2008 08:48 darren@b 15:TestTagFailure: Alarm on problematic system. 12/18/2008 07:16 darren@b 15:TestTagFailure: alarm on problematic system. 12/17/2008 07:33 darren@b 0A:LowExcCurrent,15:TestTagFailure: The detection system 15 is a problematic system and these alarms have been well documented. The alarm on system 0A will be monitored for future alarms. 12/16/2008 08:05 darren@b 15:TestTagFailure: Alarm on problematic system. 12/16/2008 07:10 darren@b 15:TestTagFailure: Alarms will be addressed during the next site visit. 12/15/2008 07:34 darren@b 15:TestTagFailure: This alalrm will be addressed during the next site visit. 12/12/2008 07:19 troy@bay 15:TestTagFailure: Noted 12/10/2008 07:39 troy@bay 15:TestTagFailure: Known problem antenna, clearing TASS. 12/06/2008 09:30 troy@bay 15:TestTagFailure: Known problem antenna, clearing TASS. 12/04/2008 07:27 darren@b 15:TestTagFailure: Alarm on problematic system. 12/03/2008 07:20 darren@b 15:TestTagFailure: Alarm noted on problematic system. 11/30/2008 09:00 troy@bay 15:TestTagFailure: Noted 11/29/2008 08:34 troy@bay 15:TestTagFailure,18:TestTagFailure: Known problem antennas, clearing TASS. 11/27/2008 09:14 troy@bay 15:TestTagFailure: Known problem antenna, clearing TASS 11/26/2008 07:19 troy@bay 15:TestTagFailure: Noted 11/25/2008 07:48 Troy Manually pushed BO308330.101, .102. It appears there was a DSL issue that has now been resolved. 11/25/2008 07:29 troy@bay 15:TestTagFailure: Known problem antenna, clearing TASS. 11/24/2008 07:56 troy@bay 15:TestTagFailure: Known problem antenna, clearing TASS. 11/23/2008 07:09 alan@bay 15:TestTagFailure: Clearing TASS on known problematic system. 11/22/2008 06:52 alan@bay 15:TestTagFailure: Clearing TASS on known problematic system. 11/19/2008 07:34 alan@bay 15:TestTagFailure: Clearing TASS error on known problematic system. 11/17/2008 08:10 darren@b 15:TestTagFailure: Alarm on problematic system. 11/16/2008 07:21 alan@bay 15:TestTagFailure: Clearing TASS error on known problematic system. 11/15/2008 07:21 alan@bay 11:Overrun,15:TestTagFailure: Clearing TASS errors on known problematic systems. 11/14/2008 07:14 darren@b 15:TestTagFailure: Alarm on problematic system. 11/13/2008 07:30 darren@b 15:TestTagFailure: Alarm on a problematic system. 11/12/2008 15:27 scottl At a moments notice, Embarc the DSL provider informed us that they were switching over to some new equipment that would require us to reconfigure our network with the new addressing scheme. With help from Todd, this was finished at Nov 12th at 3:15 pst. The DSL modem was also upgraded to the new 655 model at absolutely no charge to PTAGIS. The password for the Sonic Wall box in the AFF network cabinet was changed to the PTAGIS remote universal PW. Hobbit reports GREEN for the entire site, no problems to report at this time. Will monitr the network while onsite to ensure the network remains stable. 11/12/2008 07:22 darren@b 15:TestTagFailure: Alarm generated on a problematic system. 11/11/2008 08:23 Darren The outstanding files were manually uploaded to PTAGIS via PCA. There was another zip file in the temp directory at GOJ which was not allowing the files to upload. 11/10/2008 07:55 darren@b 15:TestTagFailure: Alarm noted on problematic system. 11/09/2008 08:56 darren@b 15:TestTagFailure: Alarm noted on problematic system. 11/08/2008 07:42 darren@b 15:TestTagFailure: Alarm noted on problematic system. 11/06/2008 07:15 darren@b 15:TestTagFailure,18:TestTagFailure: These alarms will be addressed during the next site visit. The system on antenna 15 has been problematic for quite sometime. 11/05/2008 07:18 darren@b 15:TestTagFailure: Alarm has been noted on problematic system. 11/04/2008 07:13 darren@b 15:TestTagFailure: Alarm noted on problematic system. 11/03/2008 07:24 darren@b 15:TestTagFailure: Alarm noted on problematic system. 11/02/2008 10:19 scottl@b 15:TestTagFailure,18:TestTagFailure: Noted 11/01/2008 10:26 scottl@b 15:TestTagFailure: Noted 10/30/2008 07:39 troy@bay 15:TestTagFailure: Noted 10/29/2008 08:38 troy@bay 15:TestTagFailure: Known problem antenna, clearing TASS. 10/28/2008 07:35 darren@b 15:TestTagFailure: Alarm noted on well documented system. 10/27/2008 11:06 Alan Manually pushed BO308301.103 & GRJ08301.103 toPTAGIS via PCA. 10/26/2008 09:36 troy@bay 15:TestTagFailure: Known problem antenna, clearing TASS. 10/26/2008 09:21 Troy Noticed that the first file of the day was 1 hour shorter than normal, most likely due to the old DST dates. As a precaution, stopped and started MM on PC1 and PC2. Manually submitted BO3080300.104 and archived files on PC2. 10/25/2008 08:47 troy@bay 15:TestTagFailure: Known problem antenna, clearing TASS. 10/24/2008 08:34 troy@bay 15:TestTagFailure,18:TestTagFailure: Noted, clearing TASS. PSMFC will monitor. 10/23/2008 08:15 troy@bay 15:TestTagFailure: Known problem antenna, clearing TASS. 10/22/2008 07:46 darren@b 15:TestTagFailure: Alarm noted. 10/22/2008 07:24 darren@b 15:TestTagFailure: This alarm is on a well documented system. 10/21/2008 07:38 troy@bay 15:TestTagFailure: Known problem antenna, clearing TASS. 10/20/2008 08:03 troy@bay 0A:ReaderReset,15:TestTagFailure: No apparent reason for the reader reset. The Test tag failure of 15 is a common occurance. 10/18/2008 10:45 scottl@b 15:TestTagFailure: noted 10/17/2008 07:30 scottl@b 15:TestTagFailure,32:InputSyncDetect,32:ReaderReset: Noted 10/15/2008 07:16 scottl@b 15:TestTagFailure: Noted 10/14/2008 07:36 darren@b 15:TestTagFailure: This system will be addressed as much as possible today during a site visit. 10/13/2008 07:12 scottl@b 15:TestTagFailure: Problem is well noted for this antenna. 10/12/2008 08:04 darren@b 15:TestTagFailure: Alarm noted on degrading system. 10/11/2008 07:59 darren@b 15:TestTagFailure: Alarm noted. 10/09/2008 07:34 troy@bay 15:TestTagFailure: 15:TestTagFailure: Noted 10/09/2008 07:34 troy@bay 15:TestTagFailure: Noted 10/08/2008 09:08 troy@bay 15:TestTagFailure: Noted 10/07/2008 07:42 troy@bay 15:TestTagFailure: Well documented problem, clearing TASS. 10/06/2008 07:51 troy@bay 15:TestTagFailure: Known problem, clearing TASS. 10/05/2008 08:03 troy@bay 15:TestTagFailure: Noted,clearing TASS 10/04/2008 08:59 troy@bay 15:TestTagFailure: Noted 10/04/2008 08:49 Troy Manually pushed BO308278.102 to ptagis 10/03/2008 07:40 troy@bay 15:TestTagFailure: Noted 10/02/2008 07:42 troy@bay 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,15:TestTagFailure,16:ReaderReset,17:Re aderReset,18:ReaderReset,22:InputSyncDetect,22:ReaderReset,24:InputSyncDet ect,24:ReaderReset,26:InputSyncDetect,26:ReaderReset,28:ReaderReset,32:Inp utSyncDetect,32:ReaderReset,34:InputSyncDetect,34:ReaderReset,36:InputSync Detect,36:ReaderReset,38:ReaderReset: These alarms are the result of a scheduled power outage. 10/01/2008 15:12 Darren This message was sent to PSMFC to alert of us upcoming power switches. All, On Thursday, 2 October 2008 at approximately 0100 hours we will be performing Station Service Switching. The same equipment will be effected as is listed below. 1) Outfall Building 2) Intertie Lines #1 and #2 3) Bradford Island Service Building 4) Adult Fish Facility 5) Fish View Building 6) Visitors Observation Building 7) Pit Building @ A/B Branch If you have any questions please call the control room at ext. 2221. Thanks, Brenda 10/01/2008 07:41 troy@bay 15:TestTagFailure: Noted 09/30/2008 07:38 troy@bay 15:TestTagFailure: Noted 09/29/2008 16:21 troy@bay 15:TestTagFailure: Noted 09/29/2008 12:36 Scott_Li Per Jon Rerecich All, On Wednesday, 1 October 2008 in the early morning and again in the evening we will be performing Station Service Switching. There will be power outages to the following buildings and equipment: 1) Outfall Building 2) Intertie Lines #1 and #2 3) Bradford Island Service Building 4) Adult Fish Facility 5) Fish View Building 6) Visitors Observation Building 7) Pit Building @ A/B Branch If you have any questions please call the control room at ext. 2221. Thanks, Rob Witham 09/27/2008 11:43 alan@bay 15:Overrun,15:TestTagFailure,32:InputSyncDetect,32:InputSyncLost,36:InputS yncDetect,36:InputSyncLost,38:ReaderReset: The AFF alarms were caused by a random reader reset. The issues with transceiver 15 have been well documented. 09/25/2008 10:24 Alan Manually pushed BO308269.103 to PTAGIS via PCA. 09/25/2008 07:53 alan@bay 15:TestTagFailure: Noted 09/24/2008 07:44 alan@bay 15:TestTagFailure: Noted. 09/23/2008 07:49 alan@bay 15:TestTagFailure: Noted. Issues with this system have been well documented. 09/22/2008 07:46 alan@bay 15:TestTagFailure: Noted. 09/21/2008 07:52 darren@b 15:TestTagFailure: Alarm noted on well documented system. 09/20/2008 07:58 darren@b 15:TestTagFailure: Alarm has been noted. System has been well documented. 09/19/2008 07:40 darren@b 15:TestTagFailure,17:ReaderReset: Reader system 15 has been well documented. The alarm on 17 was generated by a random reader reset. 09/18/2008 14:27 Darren PSMFC is on site to do some cable management and may have had the network connection briefly disconnected at the time of the upload at 12:00. I manually pushed the missing files for all the sites up to PTAGIS. 09/18/2008 07:44 darren@b 15:TestTagFailure: Alarm noted. 09/18/2008 07:16 darren@b 15:TestTagFailure: Alarm has been noted. System is well documented. 09/17/2008 07:59 darren@b 15:TestTagFailure: Alarm has been noted. System has been well documented. 09/15/2008 15:08 Scott_Li The network renovation for the entire Bonneville data collection platforms has been completed. The following lists the changes and the replacement appliances that were installed. The old Black Box network cabinet was completely tore out and replaced with a new standup Black Box cabinet that will allow easier access and more room for expansion. All new appliances were installed that includes the replacement of the Watch Guard firewall with a new Sonic Wall firewall. A new managed 24 port Dell switch and new 24 port punch down panel. All the existing FO media converters were re-used along with the FO to copper phone converter. The DSL junction box was re-routed to a new, more convenient location. All cabling and connections have been labeled and are being documented. The next phase will consist of more labeling and documentation of the fiber optic runs from the AFF PIT room to all PIT tag rooms and junctions in between. 09/15/2008 07:21 darren@b 15:TestTagFailure: Alarm has been noted. System is well documented. 09/11/2008 11:24 scottl Performed site GMC, all transcievers were retuned and calibrated as necessary, no problems to report. 09/11/2008 11:24 sco9ttl Performed site GMC, all transcievers were retuned and calibrated as necessary, no problems to report. 09/11/2008 11:05 PTOC_Bot The network renovation for these sites has been completed. No outstanding issues exist. The SMP office has also been reconnected to the PSMFC DSL network. 09/11/2008 07:56 troy@bay 15:LowExcCurrent,15:TestTagFailure: This is a well documented problem antenna, clearing TASS 09/09/2008 09:17 Troy These sites data collection has been verified while the internet connection(s) is being reconfigured. 09/09/2008 07:10 darren@b 15:LowExcCurrent: Alarm noted. This system has benn well documented. 09/08/2008 13:38 Alan The network equipment is going to be upgraded starting today (9/8/2008) in the AFF PIT Tag room. Network connectivity for all Bonneville interrogation sites will be down for the duration of the work. The sites will continue to collect data as normal. The outstanding data files will be submitted after the upgrade is complete. The outage is expected to last no later than Thursday morning (9/11/2008). 09/07/2008 07:56 alan@bay 15:TestTagFailure: Noted 09/05/2008 11:10 alan@bay 15:TestTagFailure: Noted 09/05/2008 07:08 darren@b 15:TestTagFailure: Alarm noted. This system has been well documented. 09/04/2008 11:26 Alan The BO3 platform was updated with flat panel monitors and consolidated into a smaller Anthro cart on 9/3/2008. The utility computer was removed. The light box interface in the PIT Tag room was mounted to the wall. The clocks on both PCs were set to within one second of atomic time. Files BO308247.206 & .211 were uploaded from PC2 to fill the gaps during PC1's downtime. 09/04/2008 07:21 darren@b 01:LowExcCurrent,01:Overrun,01:ReaderReset,01:TestTagFailure,02:ReaderRese t,03:ReaderReset,03:RocketPortNoEOT,15:TestTagFailure: The alarms on antennas 01, 02, and 03 were generated by PSMFC personnel. The test tag failure on antenna 15 was investigated and adjusted to optimize this system. 09/03/2008 07:35 darren@b 15:TestTagFailure,18:TestTagFailure: These alarms will be investigated during the next site GMC. 09/02/2008 08:19 alan@bay 15:TestTagFailure,34:InputSyncDetect,34:ReaderReset: 15 is a known issue, 34 is a random reader reset. 08/30/2008 10:46 scottl@b 15:TestTagFailure: Noted 08/29/2008 08:28 alan@bay 15:TestTagFailure: Noted 08/27/2008 08:10 troy@bay 15:TestTagFailure: Known problem antenna, clearing TASS 08/26/2008 08:10 darren@b 01:ReaderReset,02:ReaderReset,03:ReaderReset,03:RocketPortNoEOT,04:ReaderR eset,05:ReaderReset,06:ReaderReset,07:ReaderReset,08:ReaderReset,09:Reader Reset,0A:ReaderReset,0B:ReaderReset,0C:ReaderReset,0D:ReaderReset,0E:Reade rReset,0F:ReaderReset,10:ReaderReset,11:BadExcFreq,11:BadOscFreq,11:LowExc Current,11:ReaderReset,12:ReaderReset,13:ReaderReset,14:ReaderReset,15:Low ExcCurrent,15:ReaderReset,15:TestTagFailure,16:ReaderReset,17:ReaderReset, 18:ReaderReset,22:InputSyncDetect,22:ReaderReset,24:InputSyncDetect,24:Rea derReset,26:InputSyncDetect,26:ReaderReset,28:ReaderReset,32:InputSyncDete ct,32:ReaderReset,34:InputSyncDetect,36:InputSyncDetect,36:ReaderReset,38: ReaderReset: Power outage due to COE switching. PSMFC will confirm with site personal. 08/23/2008 15:22 scottl@b 15:TestTagFailure: Noted 08/22/2008 08:12 darren@b 15:TestTagFailure: Alarm noted. 08/21/2008 08:15 darren@b 11:Overrun,15:TestTagFailure: alarms have been noted. 08/20/2008 09:13 Darren After the discovery at BO3 yesterday by Dave Marvin I PCA'd into the site this morning and found there were no rocketport EOT errors on PC2. We will try to check this situation as frequent as possible but it sounds like the PC needed to be re-booted. 08/20/2008 08:04 darren@b 11:TestTagFailure,15:TestTagFailure: Alarms have been noted. These two systems have been somewhat problematic over the past two seasons. PSMFC will adjust these systems to the best of their ability on the next site visit. 08/19/2008 17:38 Dave I pcA'd in to instantiate a new SxC map and database, but first I had a bit of an adventure with PC2. A couple of minutes into the session, before I really got started, the MultiMon display on BO3-PC2 went nuts. Unformatted text (clear ASCII) scrolled by faster than I could read. Then the display settled into a very rapid repeating cycle, toggling between "Backup PC Diverting" and "Primary PC Detected", and opening and closing data files faster than I could track. There was little or no activity on BO3-PC1 during this period. Finally, I took PC2 out of data collection mode, and then put it back in; this seemed to resolve the issue. At this point BO3-PC1 was on file BO308232.106 and BO3-PC2 was on file BO308232.263. I then noticed that I saw lots of EOT errors on PC2 that were not reported on PC1. I got on the phone to Kennewick and had a lovely conversation with Darren, who helped me trace the apparent problem to the RocketPort card for ports 17-32 on PC2. Darren advised a reboot, which I promised I would do as soon as I got the SxC configuration in place. When I looked at the BO3-PC2 data files, I discovered that file BO308225.205 was created August 12 at noon, but did not close until today (August 19) at 15:05, apparently when I pcA'd in. It looks like MultiMon's counters were all scrambled on BO3-PC2, so that it didn't know what day it was; after creating two one-minute files automagically, MultiMon created some 50+ one- or two-second files until I took it out of data collection. This was a good thing, as it gave MultiMon a fresh chance to look at the system clock (and calendar) and reset itself. I suspect if I had simply toggled the data file (Alt-F10), MultiMon would have continued to frantically generate files in an effort to get "caught up" to the current date and time. Once PC2 settled down, I installed a new map and database (BO308232.MAP and BO308232.DB, respectively) on both PCs. This configuration will trigger the "Red Light" response whenever a Yakama Nation target coho adult (AC-76) or coho jack (AC-77) is detected at the false weir. The clocks on the two PCs were reset to within one second of each other and atomic time. After completing the SxC configuration on both PCs, I rebooted BO3-PC2. Subsequent to the reboot, I did not immedidiately observe any EOT errors on PC2. 08/19/2008 08:05 darren@b 11:Overrun,15:TestTagFailure: These alarms have been noted. Both of these systems have weakened over the years and are becoming harder to drive. PSMFC will continue to monitor and make appropriate changes when on site for GMC's. 08/18/2008 08:30 darren@b 15:TestTagFailure: alarm noted. 08/16/2008 08:04 alan@bay 18:TestTagFailure: Noted. 08/15/2008 08:23 alan@bay 15:LowExcCurrent,15:TestTagFailure: Noted. This system's issues have been well documented. 08/13/2008 08:51 alan@bay 04:LowExcCurrent,06:LowExcCurrent,15:LowExcCurrent,18:TestTagFailure: These alarms were generated by PTAGIS Field Operations personnel during a site visit. 08/12/2008 13:35 scottl All transcevers were tuned and calibrated as necessary, no problems to report. PC clocks are within 1 second of each other and 1 second lagging atomic time. 08/12/2008 08:11 darren@b 15:LowExcCurrent: It appears that the ability to drive this antenna is becoming quite difficult. PSMFC is monitoring the ability of this system to efficiently detect PITtags and if necessary will shut the system down to avoid damage to the reader electronics. 08/11/2008 17:21 Dave I reset the PC clocks to within one second of each other and atomic time. I archived all outstanding data files on PC2. 08/11/2008 10:55 alan@bay 15:LowExcCurrent: Noted. This detection system's issues have been well documented. 08/08/2008 09:47 Darren The site had not loaded the .102 or .103 files but PSMFC was able to verify that the PC was alive and creating files. We were not able to gain remote access via PCA but we were able to ping the IP address. With the assistance of Dean Ballinger PSMFC was able to reboot PC1 while creating a patch file on PC2. The files from PC1 were sent in and the patch file BO308221.205 was created and sent in sequential order to PTAGIS. There were no PITtag detections during this process. PC1 is back in collection and creating the .105 file. 08/08/2008 08:29 darren@b 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,22:InputSy ncDetect,22:ReaderReset,24:InputSyncDetect,24:ReaderReset,26:InputSyncDete ct,26:ReaderReset,28:ReaderReset,32:InputSyncDetect,32:ReaderReset,34:Inpu tSyncDetect,34:ReaderReset,36:InputSyncDetect,36:ReaderReset,38:ReaderRese t: These alarms were generated by a power grid changeover by COE. 08/06/2008 09:47 darren@b 0B:ReaderReset: Alarm generated by a random reader reset. This is not an uncommon activity for this transceiver both Destron-Fearing and PSMFC are aware of this activity. 08/04/2008 08:07 darren@b 15:Overrun: Alarm noted. The alarms on this system have been well documented over the last two years. PSMFC has been trying to keep this system optimized despite the degradation of the antenna. 08/02/2008 08:24 troy@bay 11:TestTagFailure: Noted 07/26/2008 08:55 troy@bay 15:Overrun: Known problem antenna, clearing TASS. 07/25/2008 09:05 Alan Examination of BO308206.206 shows that no activity occurred during PC1's reboot on 7/24/2008. 07/25/2008 08:44 troy@bay 15:LowExcCurrent: This is a known problem antenna. The current alarm threshold was lowered from 1.5 A to 1.0 A in an effort to eliminate these alarms. The transceiver is currently running at 1.5 A. 07/24/2008 10:42 Alan In the course of recovering from internet connection issues, PC1 was rebooted at ~10:15 PDT (thanks Dean!). File BO308206.206 contains data created during the outage. When the exact time stamps are known, that file will be trimmed to fit the gap and then submitted to PTAGIS. 07/24/2008 08:39 troy@bay 15:LowExcCurrent: These alarms where generated during a site GMC. 07/23/2008 12:28 Troy A site GMC was performed 07/23/2008. All transceivers were checked for tune and adjustments made where needed. PC1 was 64 seconds behind atomic time and PC2 was 67 seconds behind atomic time. Both PC's were set to within 1 second of atomic time and each other. Patch file BO308205.206 was submitted after file BO308205.104 was manually pushed to ptagis. The rest of PC2's files were archived. No new problems to report. 15 is still 75% to 100% in noise due to a bad antenna. 07/23/2008 08:56 alan@bay 15:LowExcCurrent,15:Overrun: Noted. This system is well documented. 07/16/2008 07:50 darren@b 15:LowExcCurrent,15:Overrun: Alarms noted. This system has been well documented. 07/15/2008 08:19 alan@bay 15:LowExcCurrent: This will be investigated during the next site visit. 07/14/2008 08:11 darren@b 15:LowExcCurrent,15:Overrun,18:TestTagFailure: The current alarm threshold was adjusted to 1500mA to avoiud the low current alarms. All other alarms will be investigated during the next site visit. 07/13/2008 07:23 darren@b 06:TestTagFailure: Alarm will be investigated during the next site visit. 07/11/2008 08:19 darren@b 15:LowExcCurrent,15:Overrun: There is no direct cause for the Current alarms. The threshold is well below the actual measured level. This detection system has been well documented as being problematic. PSMFC will continue to monitor for future alarms and will maintain the system for optimum performance. 07/09/2008 08:13 darren@b 15:LowExcCurrent: Problematic system has been well documented. 07/08/2008 13:16 Alan A GMC was performed 7/8/2008. All transceivers were checked and tuned as necessary. Both PCs are 32 seconds behind atomic time. No problems found. 07/08/2008 08:07 darren@b 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,22:InputSy ncDetect,22:ReaderReset,24:InputSyncDetect,24:ReaderReset,26:InputSyncDete ct,26:ReaderReset,28:ReaderReset,32:InputSyncDetect,32:ReaderReset,34:Inpu tSyncDetect,34:ReaderReset,36:InputSyncDetect,36:ReaderReset,38:ReaderRese t: These alarms appear to be the result of a site power outage. PSMFC will try to confirm this with site personnel. 07/07/2008 08:16 darren@b 15:LowExcCurrent: These alarms will be addressed to the best of this systems ability during a site GMC tomorrow by PSMFC personnel. This detection system and it's problems have been well documented over the last few years. 07/06/2008 09:36 troy@bay 15:Overrun: Well documented problem antenna, clearing TASS. 07/05/2008 10:26 troy@bay 15:Overrun: Noted 07/04/2008 08:12 troy@bay 15:Overrun: Known problem, clearing TASS. 07/01/2008 08:51 troy@bay 15:Overrun: Noted 06/30/2008 08:34 troy@bay 15:LowExcCurrent,15:Overrun: Known problem antenna, clearing TASS. 06/25/2008 07:56 darren@b 15:Overrun,18:TestTagFailure: Alarm noted. These are problematic systems that are well documented. 06/24/2008 08:02 darren@b 15:LowExcCurrent,15:Overrun: This system has been well documented as a problem system. PSMFC is trying to maintain the detection ability of this system. 06/22/2008 07:40 alan@bay 15:LowExcCurrent: Noted 06/22/2008 07:39 alan@bay 0A:ReaderReset: This alarm was generated by a random reader reset. PSMFC and DF are aware of the problem. 06/21/2008 10:41 alan@bay 15:LowExcCurrent,15:Overrun: Noted 06/17/2008 14:22 scottl The switch over to the new ISP is complete. All internal DNS entries are now pointing to the new server. Did a diagnositc test upload on all computers without errors. B2J FF system is experiencing some noise in all transcievers that cannot be tuned out, especially 04. This phenom in the past has been associated with grounding but never been proven. BO4 also has intermittent and sometime persistent elevated noise levels that also cannot be tuned out. Will talk it over and get a game plan to correct the situations or atl east minimize the effects. 06/12/2008 12:36 Troy A site GMC was performed 06/12/2008. All transceivers were checked for tune and adjustments made where needed. PC1 is 20 seconds behind atomic time and PC2 is 17 seconds behind atomic time. Trapping and tagging in the AFF is still on going. No problems to report. 06/09/2008 08:16 troy@ree 15:LowExcCurrent: Known problem antenna. This will be looked into on the next site visit. 06/08/2008 08:57 alan@ree 15:Overrun: Noted 06/07/2008 08:00 alan@ree 15:Overrun: Noted 06/06/2008 08:46 alan@ree 15:Overrun: The alarms on this transceiver have been well documented. PSMFC will optimize this system to the best of it's ability during the next site visit. 06/04/2008 12:40 Alan A GMC was performed 6/4/2008. All transceivers were checked and tuned as necessary. Both PCs (PC1-00:01:41 slow, PC2-00:01:34 slow) were adjusted to within one second of atomic time. File BO308156.207 was uploaded from PC2 to fill the gap during PC1's downtime. No other problems found. 06/01/2008 07:09 darren@r 15:LowExcCurrent,15:Overrun: The alarms on this transceiver have been well documented. PSMFC will optimize this system to the best of it's ability during the next site visit. 05/30/2008 07:29 darren@r 15:Overrun: System is degrading. PSMFC is well aware of this system and it's attributes. 05/29/2008 13:25 Darren A site GMC was performed today (5-29-08). All transceivers were checked for tuning, noise and detection ability. No problems were discovered during this visit. 05/27/2008 08:58 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:BadExcFreq,11:BadOscFreq,11:LowExcCurrent,11:ReaderRe set,12:ReaderReset,13:ReaderReset,14:ReaderReset,15:Overrun,15:ReaderReset ,16:ReaderReset,17:ReaderReset,18:ReaderReset,22:InputSyncDetect,22:Reader Reset,24:InputSyncDetect,24:ReaderReset,26:InputSyncDetect,26:ReaderReset, 28:ReaderReset,32:InputSyncDetect,32:ReaderReset,34:InputSyncDetect,34:Rea derReset,36:InputSyncDetect,36:ReaderReset,38:ReaderReset: Clearing old alarms. 05/26/2008 10:29 scottl.o 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:BadExcFreq,11:BadOscFreq,11:LowExcCurrent,11:ReaderRe set,12:ReaderReset,13:ReaderReset,14:ReaderReset,15:Overrun,15:ReaderReset ,16:ReaderReset,17:ReaderReset,18:ReaderReset,22:InputSyncDetect,22:Reader Reset,24:InputSyncDetect,24:ReaderReset,26:InputSyncDetect,26:ReaderReset, 28:ReaderReset,32:InputSyncDetect,32:ReaderReset,34:InputSyncDetect,34:Rea derReset,36:InputSyncDetect,36:ReaderReset,38:ReaderReset: noted 05/25/2008 09:24 scottl.o 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:BadExcFreq,11:BadOscFreq,11:LowExcCurrent,11:ReaderRe set,12:ReaderReset,13:ReaderReset,14:ReaderReset,15:Overrun,15:ReaderReset ,16:ReaderReset,17:ReaderReset,18:ReaderReset,22:InputSyncDetect,22:Reader Reset,24:InputSyncDetect,24:ReaderReset,26:InputSyncDetect,26:ReaderReset, 28:ReaderReset,32:InputSyncDetect,32:ReaderReset,34:InputSyncDetect,34:Rea derReset,36:InputSyncDetect,36:ReaderReset,38:ReaderReset: Power outage 05/24/2008 09:50 scottl.o 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:BadExcFreq,11:BadOscFreq,11:LowExcCurrent,11:ReaderRe set,12:ReaderReset,13:ReaderReset,14:ReaderReset,15:Overrun,15:ReaderReset ,16:ReaderReset,17:ReaderReset,18:ReaderReset,22:InputSyncDetect,22:Reader Reset,24:InputSyncDetect,24:ReaderReset,26:InputSyncDetect,26:ReaderReset, 28:ReaderReset,32:InputSyncDetect,32:ReaderReset,34:InputSyncDetect,34:Rea derReset,36:InputSyncDetect,36:ReaderReset,38:ReaderReset: Power outage caused alarms 05/22/2008 07:56 darren.o 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:BadExcFreq,11:BadOscFreq,11:LowExcCurrent,11:ReaderRe set,12:ReaderReset,13:ReaderReset,14:ReaderReset,15:Overrun,15:ReaderReset ,16:ReaderReset,17:ReaderReset,18:ReaderReset,22:InputSyncDetect,22:Reader Reset,24:InputSyncDetect,24:ReaderReset,26:InputSyncDetect,26:ReaderReset, 28:ReaderReset,32:InputSyncDetect,32:ReaderReset,34:InputSyncDetect,34:Rea derReset,36:InputSyncDetect,36:ReaderReset,38:ReaderReset: These alarms were generated by a few brief power outages that were confirmed by site personnel. 05/21/2008 08:21 scottl.o 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:BadExcFreq,11:BadOscFreq,11:LowExcCurrent,11:ReaderRe set,12:ReaderReset,13:ReaderReset,14:ReaderReset,15:Overrun,15:ReaderReset ,16:ReaderReset,17:ReaderReset,18:ReaderReset,22:InputSyncDetect,22:Reader Reset,24:InputSyncDetect,24:ReaderReset,26:InputSyncDetect,26:ReaderReset, 28:ReaderReset,32:InputSyncDetect,32:ReaderReset,34:InputSyncDetect,34:Rea derReset,36:InputSyncDetect,36:ReaderReset,38:ReaderReset: Alarms caused by power outage 05/21/2008 08:00 scottl.o 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:BadExcFreq,11:BadOscFreq,11:LowExcCurrent,11:ReaderRe set,12:ReaderReset,13:ReaderReset,14:ReaderReset,15:Overrun,15:ReaderReset ,16:ReaderReset,17:ReaderReset,18:ReaderReset,22:InputSyncDetect,22:Reader Reset,24:InputSyncDetect,24:ReaderReset,26:InputSyncDetect,26:ReaderReset, 28:ReaderReset,32:InputSyncDetect,32:ReaderReset,34:InputSyncDetect,34:Rea derReset,36:InputSyncDetect,36:ReaderReset,38:ReaderReset: Power outage acknowledged 05/20/2008 13:13 scottl Performed scheduled GMC on 5-20-08, all transcievers were tuned and TT hits adjusted as necessary. PC clocks are within 11 seconds of each other and 1 min, 5 seconds behind atomic time. 05/17/2008 09:59 alan@ree 15:Overrun: Noted 05/15/2008 11:27 Troy confirmed that a tagging operation is happening at BO3. It appears that this has been happening since yesterday. Fish are being trapped via the swing gates and tagged and then released back to the ladder. 05/13/2008 13:27 Darren A GMC was performed today (5-13-08). All transceivers were checked for tuning, noise, and detection ability. No problems were discovered during this visit. 05/13/2008 08:09 Scott_Li Manually pushed outstanding data files 134.101 and .102 without any problems. Will monitor the upload service through out the day and take corrective action if necessary. Site GMC's are also being conducted today. 05/12/2008 08:40 alan@ruf 15:Overrun: Known problem antenna. Clearing TASS. 05/09/2008 08:35 troy@ruf 15:Overrun,32:InputSyncDetect,32:ReaderReset: These alarms will be investigated on the next GMC. 05/08/2008 08:22 troy@ruf 15:Overrun: Noted 05/06/2008 13:02 scottl Performed site GMC, all transicevers where checked for proper tune and TT hit rates as necessary. PC clocks are within 5 seconds of each other and lagging atomic time by 31 seconds.No problems to report. 05/05/2008 08:25 troy@ruf 15:Overrun: Known problem antenna. Clearing TASS. 05/03/2008 09:48 scottl@r 09:TestTagFailure: Noted 04/30/2008 13:04 Darren A site GMC was performed today (4-30-08). All transceivers were chekced for tuning, noise and detection ability. No problems were discovered during this visit. 04/30/2008 09:48 dlwarf@r 15:Overrun: Will be tuned today. 04/27/2008 08:34 darren@r 15:Overrun,18:TestTagFailure: alarms will be investigated during the next site GMC. 04/26/2008 07:50 darren@r 15:Overrun: Alarm noted on well documented troubled system. 04/24/2008 13:38 Alan A GMC was performed 4/24/2008. All transceivers were checked and tuned as necessary. Both PCs are three seconds behind atomic time. No problems found. 04/23/2008 13:30 Dave Stopped in to verify operations. Both PC monitors were on. Reset PC clocks to within one second of each other and atomic time. Archived data files on PC2. Turned monitors off. 04/23/2008 08:44 alan@ruf 32:InputSyncDetect,32:InputSyncLost,36:InputSyncDetect,36:InputSyncLost,38 :ReaderReset: Alarms were generated by a random reader reset. PSMFC and DF are aware of the problem. 04/20/2008 08:11 troy@ruf 15:Overrun: Known issue clearing TASS 04/19/2008 09:11 troy@ruf 15:Overrun: Known issue, clearing TASS. 04/18/2008 13:55 scottl Performed GMC, all transceivers were tuned and calibrated as necessary. No problems to report. 04/14/2008 16:24 Scott_Li The AFF was watered up today at 1530. CRITFC plans on sampling within the next couple days, maybe tomorrow 04/09/2008 12:49 Troy A site GMC was performed 04/09/2008. All transceivers were checked for tune and readablility. PC1 is 53 seconds behind atomic time and PC2 is 48 seconds behind atomic time. 04/08/2008 08:20 alan@ruf 15:Overrun: Alarm on a well documented detection system. 04/06/2008 10:11 Dave I pcA'd into both computers and stopped and restarted MultiMon to reset the collection schedule, which was advanced an hour when the DOS clocks attempted to "spring forward" into Daylight Savings Time. No detection time stamps or any other data were affected. 04/06/2008 08:07 darren@r 15:Overrun: Alarm on a well documented detection system. 04/04/2008 08:34 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,0E:TestTagFa ilure,0F:ReaderReset,10:ReaderReset,11:ReaderReset,12:ReaderReset,13:Reade rReset,14:ReaderReset,15:Overrun,15:ReaderReset,16:ReaderReset,17:ReaderRe set,18:ReaderReset,22:InputSyncDetect,22:InputSyncLost,22:ReaderReset,24:I nputSyncDetect,24:InputSyncLost,24:ReaderReset,26:InputSyncDetect,26:Input SyncLost,26:ReaderReset,28:ReaderReset,32:InputSyncDetect,32:InputSyncLost ,32:ReaderReset,34:InputSyncDetect,34:InputSyncLost,34:ReaderReset,36:Inpu tSyncDetect,36:InputSyncLost,36:ReaderReset,38:ReaderReset: Alarms were generated by PSMFC personnel while performing maintenance on the site. 04/03/2008 13:40 Alan A GMC was performed 4/3/2008. All transceivers were checked and tuned as necessary. All transceiver CPU Batteries were changed. Transceiver 15 had a broken switch on the timer tag board. It was replaced and the failed unit will be taken back to Kennewick for repair. PC1 is 39 seconds behind atomic time, PC2 is three seconds ahead of PC1. 03/31/2008 08:18 darren@r 06:ReaderReset,15:Overrun: Alarms on antenna 15 have been well documented and PSMFC is doing everything to maximize the detection ability of this system. The alarm on antenna 06 is an occassional reader reset generated by the transceiver. 03/25/2008 07:10 darren@r 02:ReaderReset: common problem. PSMFC is aware of this alarm. 03/24/2008 12:22 Alan A GMC was performed 3/24/2008. All transceivers were checked and tuned as necessary. Transceiver 01 was replaced. The failed unit exhibits SRAM failure symptoms. It will be taken back to Kennewick for repair. The clocks on both PCs are 15 seconds behind atomic time. No other problems found. 03/24/2008 08:03 darren@r 15:Overrun: Alarm noted. This system has been well documented over the last two seasons. 03/24/2008 07:28 darren@r 22:InputSyncDetect,22:InputSyncLost,26:InputSyncDetect,26:InputSyncLost,28 :ReaderReset: Alarms were generated by a random reader reset on transceiver 28. 03/23/2008 09:03 alan@ruf 15:LowExcCurrent,15:Overrun,15:TestTagFailure: This antenna has known issues underwater. 03/22/2008 09:58 alan@ruf 01:TestTagFailure,02:ReaderReset,03:ReaderReset,04:ReaderReset,05:ReaderRe set,06:ReaderReset,06:TestTagFailure,07:ReaderReset,08:ReaderReset,09:Read erReset,0A:ReaderReset,0B:ReaderReset,0C:ReaderReset,0D:ReaderReset,0E:Rea derReset,0E:TestTagFailure,0F:ReaderReset,10:ReaderReset,11:ReaderReset,12 :ReaderReset,12:TestTagFailure,13:ReaderReset,14:ReaderReset,15:LowExcCurr ent,15:ReaderReset,15:TestTagFailure,16:ReaderReset,17:ReaderReset,18:Read erReset,22:InputSyncDetect,22:ReaderReset,24:InputSyncDetect,24:ReaderRese t,26:InputSyncDetect,26:ReaderReset,28:ReaderReset,32:InputSyncDetect,32:R eaderReset,34:InputSyncDetect,34:ReaderReset,36:InputSyncDetect,36:ReaderR eset,38:ReaderReset: Alarms were caused by a power failure. 03/18/2008 07:57 alan@ruf 01:TestTagFailure,15:LowExcCurrent: These systems have documented problems. PTAGIS Field Operations will continue to monitor. 03/17/2008 08:01 alan@ruf 01:TestTagFailure,15:LowExcCurrent: These systems have documented issues. 03/16/2008 10:49 scottl@r 01:TestTagFailure: Noted 03/14/2008 11:12 scottl@r 11:Overrun,15:LowExcCurrent: Will adjust exciter current threshold to avoid errors with a known deficient antenna 03/13/2008 09:04 Dave I procedurally closed BO308072.106, which was apparently truncated during the replacement of the UPS on BO3-PC1 yesterday. This maintenance activity is also most likely responsible for the short (8-minute) interruption in detection activity between 13:09 and 13:17 on March 12. 03/13/2008 07:33 alan@ruf 15:LowExcCurrent,15:Overrun,15:TestTagFailure: Noted 03/12/2008 14:53 scottl Performed site GMC, all xcvrs were retuned and calibrated as necessary. BO3 PC clocks are within 36 sec. of each other and 13 sec. ahead of atomic time. UPS's were replaced with the new RS-1300s. 03/12/2008 07:50 alan@ruf 15:LowExcCurrent,15:Overrun,15:TestTagFailure: Noted 03/09/2008 08:22 troy@ruf 01:TestTagFailure,17:ReaderReset: Alarms noted, will monitor for future occurances. 03/08/2008 08:26 troy@ruf 15:Overrun: Noted. 03/07/2008 07:40 troy@ruf 01:TestTagFailure,15:Overrun,15:TestTagFailure: Known issues, clearing TASS. 03/06/2008 07:14 alan@ruf 01:TestTagFailure,15:Overrun: These antennas are known to have issues. 03/05/2008 07:28 troy@ruf 01:TestTagFailure,15:Overrun: These antenna's are known to have issues. 03/04/2008 07:54 troy@ruf 01:TestTagFailure: Noted 03/03/2008 10:56 Alan The platform was rebooted for maintenance issues. While Multimon was functioning properly on PC1, Windows explorer was locked up and could not be closed. In addition to the reboot, the clocks on both PCs were set to within one second of atomic time and data files from 2007 were moved to the previous years data folder\2007 on both PCs. File BO308063.206 was submitted from PC2 to cover the gap during PC1's downtime. File BO308060.108 was not submitted automatically (examination of the log file gives no clues). It was found in the archive folder and submitted manually. No other problems found. 03/03/2008 07:18 darren@r 01:TestTagFailure,22:InputSyncDetect,22:ReaderReset: Alarms will be addressed todya during a site GMC. 03/02/2008 08:06 darren@r 01:TestTagFailure,15:Overrun: The alrms on these two systems has been well documented.PSMFC will make the necessary adjustments on Monday to try and alleviate the alarms. 03/01/2008 07:39 darren@r 01:TestTagFailure: This alarm will be investigated on Monday during a site GMC. 02/28/2008 07:09 darren@r 01:TestTagFailure,0B:LowExcCurrent,15:Overrun: A site GMC was performed on Tuesday 2-26-08 by PSMFC personnel. 02/26/2008 13:22 Troy A site GMC was performed 02/26/2008. All transceivers were checked for tune and adjustments made where needed. 15 is un-tunable and the noise is in the high 90's. This is a known problem suspected to be below the water line. PC1 is 16 seconds behind atomic time and PC2 is 14 seconds behind atomic time. No other problems to report. 02/24/2008 08:58 troy@ruf 15:Overrun: A GMC is scheduled for this week. This alarm will be looked into then. 02/20/2008 07:12 troy@ruf 15:TestTagFailure: Noted 02/19/2008 09:42 Dave I reset the map and database files to BO3-GEN.MAP and BO3_GEN.DB, respectively. Cleared the counter files. Reset the clocks to within 1 second of each other and atomic time. 02/19/2008 07:20 troy@ruf 15:TestTagFailure: Noted 02/18/2008 07:23 alan@ruf 15:Overrun: Noted 02/14/2008 07:37 alan@ruf 15:Overrun: Noted 02/14/2008 07:36 alan@ruf 0E:LowExcCurrent: Clearing TASS - Alarm occurred before yesterday's actions. 02/13/2008 07:21 alan@ruf 15:Overrun: Noted 02/13/2008 07:21 alan@ruf 0E:LowExcCurrent: The transceiver appears to have slightly drifted out of tune. Both the alarm threshold and the operating current is 3.2A. I remotely lowered the threshold to 2.9A. This will be investigated during the next site visit. 02/11/2008 07:21 alan@ruf 15:Overrun: Noted 02/10/2008 08:52 darren@r 15:Overrun: Alarm noted. 02/09/2008 07:07 darren@r 15:Overrun: Alarm Noted. 02/05/2008 07:18 darren@r 15:Overrun: Alarm has been noted. 02/02/2008 12:18 scottl@r 07:ReaderReset,0E:LowExcCurrent,15:Overrun: Problems noted. 01/25/2008 07:36 alan@ruf 15:Overrun: Noted 01/24/2008 07:14 darren@r 15:Overrun: Alarm Noted. 01/23/2008 07:50 darren@r 15:Overrun: Problem has been noted. This system is well documented and PSMFC will address any issues during the next site visit. 01/22/2008 07:41 alan@ruf 15:TestTagFailure: Known problem, clearing TASS. 01/22/2008 07:40 alan@ruf 26:InputSyncDetect,26:ReaderReset: These alarms were generated by a random reader reset. PSMFC and DF are aware of the problem. 01/21/2008 09:31 troy@ruf 01:TestTagFailure: Noted 01/19/2008 09:19 troy@ruf 15:Overrun: Known issue, clearing TASS 01/18/2008 09:17 troy@ruf 15:Overrun: Noted 01/17/2008 10:40 Dave Jon Rericich (Corps) reported today that there was a partial, emergency dewatering of the BON Washington Shore ladder on Monday (Jan. 15) between 1800 and 2000h. 01/14/2008 07:26 troy@ruf 15:Overrun: Known problem, clearing TASS 01/11/2008 07:22 troy@ruf 15:Overrun: Known issue, clearing TASS. 01/11/2008 07:21 troy@ruf 0E:LowExcCurrent: The current is running at 3.4A and the alarm was set at 3400mA. The alarm was lowered to 3200mA. 01/10/2008 07:53 troy@ruf 0E:LowExcCurrent,15:Overrun: PSMFC will monitor for future alarms. The LowExcCurrent may be a result of de-tuning. 01/09/2008 07:44 alan@ruf 02:LowExcCurrent,06:LowExcCurrent,0D:LowExcCurrent,0E:LowExcCurrent,15:Low ExcCurrent,15:Overrun: These alarms were caused by PTAGIS Field Operations personnel during a site visit. 01/08/2008 11:56 Darren A site GMC was performed today 1-8-08. All transceivers were checked and adjusted for tuning, noise, and detection ability. No problems were found. 01/07/2008 12:08 troy@ruf 15:LowExcCurrent,15:Overrun: Noted 01/06/2008 08:35 darren@r 15:LowExcCurrent: This system has been well documented, the problem is below the water line. PSMFC will try re-tuning the system on the next site visit. 01/05/2008 08:20 darren@r 15:Overrun: Alarm will be addressed on the next site visit. 01/04/2008 08:44 darren@r 11:Overrun,15:LowExcCurrent,15:Overrun: The alarms on these systems has been well documented. The problem is below the water line and the ladder is not scheduled to down this season. 01/02/2008 08:12 troy@ruf 0E:LowExcCurrent,15:Overrun: The LowExcCurrent alarm may be a tuning issue. PSMFC will monitor and if the problem persists the alarm threshold will be lowered remotely. 01/01/2008 10:00 troy@ruf 15:Overrun,22:InputSyncDetect,22:InputSyncLost,26:InputSyncDetect,26:Input SyncLost,28:ReaderReset: These alarms may be Random Reader Resets. PSMFC will monitor for future occurances. 01/01/2008 00:00 PTOC_Bot Annual log file initiation for BO3 #### End of Event Log for BO3 ###