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/13/2010 13:28 Troy A visual inspection from above was conducted of the de-watered ladder on the lower end. I was not able to get to a position that I could see the upper antennas. No obvious antenna damage was witnessed on the lower end, loose conduits could not be checked as they were not visiable from my vantage point. The DCP and pittag room was checked and no problems were found. 12/11/2010 06:27 Troy@bay 0F:ReaderReset,15:TestTagFailure: Possible random reader reset on 0F. 15 is a known problematic antenna. 12/07/2010 18:28 Dave Per the facility operators, the Washington Shore and Cascades Island fish ladders went to orifice flow on 01 December, and were dewatered to tailwater on 03 December. Per Darren's 12/06/10 event log entry for BO2, both ladders will remain Out of Service until the last week of February 2011. 12/06/2010 07:46 Troy@bay 02:LowExcCurrent,02:TestTagFailure,0D:LowExcCurrent,15:TestTagFailure: These alarms will be addressed on the next site visit. 12/01/2010 10:06 scottl@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,0F:TestTagFailure,10:ReaderReset,11:Overrun,11:ReaderReset,12:ReaderRes et,12:TestTagFailure,13:ReaderReset,14:ReaderReset,15:ReaderReset,15:TestT agFailure,16:ReaderReset,17:ReaderReset,18:ReaderReset,22:InputSyncDetect, 22:ReaderReset,24:InputSyncDetect,24:ReaderReset,26:InputSyncDetect,26:Rea derReset,28:ReaderReset,32:InputSyncDetect,32:ReaderReset,34:InputSyncDete ct,34:ReaderReset,36:InputSyncDetect,36:ReaderReset,38:ReaderReset: Obvious power outage has occurred 11/28/2010 09:05 darren@b 15:TestTagFailure: Alarm on known problematic system. 11/27/2010 09:15 darren@b 15:TestTagFailure: This alarm is on a known problematic system. 11/26/2010 08:44 darren@b 15:TestTagFailure: This alarm is on a known problematic system. 11/25/2010 07:47 darren@b 15:TestTagFailure: Alarm on known problematic system. 11/24/2010 07:01 darren@b 15:TestTagFailure: This alarm is on a known problematic system. 11/22/2010 08:06 darren@b 15:TestTagFailure: This alarm is on a known problematic system. 11/20/2010 08:40 Troy@bay 15:TestTagFailure: Known problematic antenna, clearing TASS. 11/18/2010 07:22 alan@bay 15:TestTagFailure: Clearing TASS on a known problematic system. 11/17/2010 07:23 darren@b 15:TestTagFailure: Alarm on known pr0oblematic system. 11/16/2010 07:45 Troy@bay 15:TestTagFailure: Alarm on a known problematica antenna. Clearing TASS. 11/15/2010 07:19 Troy@bay 15:TestTagFailure: Known problematic antenna. Clearing TASS. 11/14/2010 08:09 Darren These sites had trouble loading the first two files of the day today. I had trouble with the loading in some cases it took 5 tries to get the files to PTAGIS. 11/14/2010 08:00 darren@b 15:TestTagFailure: Alarm on known problematic system. 11/13/2010 08:16 darren@b 15:TestTagFailure: Alarm on known problematic system. 11/12/2010 08:31 darren@b 15:TestTagFailure: Alarm on known problematic system. 11/11/2010 07:08 darren@b 15:TestTagFailure: Alarm on known problematic system. 11/10/2010 07:25 alan@bay 15:TestTagFailure: Clearing TASS on a known problematic system. 11/09/2010 07:34 darren@b 15:TestTagFailure: Alarm on known problematic system. 11/08/2010 07:23 darren@b 15:TestTagFailure,22:InputSyncDetect,22:ReaderReset: Alarm on antenna 15 is on a known system. The other alarm on 22 was created by a reader reset. 11/07/2010 08:36 Alan With much effort I was able to push the outstanding files to PTAGIS. I suspect there is an issue of some sort in Sellwood. Data collection has been verified. PTAGIS Field Operations will continue to monitor. 11/07/2010 08:30 alan@bay 15:TestTagFailure: Clearing TASS on a known problematic system. 11/06/2010 06:52 alan@bay 15:TestTagFailure: Clearing TASS on a known problematic system. 11/03/2010 06:39 alan@bay 11:Overrun,15:TestTagFailure: These alarms will be addressed during the next site visit. 11/02/2010 11:28 Dave Stopped data collection on BO3-PC2. Reset PC clock. The clock on PC1 is now within 23 seconds of PC2 and atomic time. Restarted data collection on PC2; MultiMon now correctly tracks the time of day. Uploaded patch files from 8AM to ~11:10 from PC2; archived similar files on PC1. There is a short apparent gap in data collection from PC2 resulting from a 20 second data collection outage and the 2min+ clock adjustment; no tags or diagnostic data were recorded to PC1 during this outage on PC2. 11/02/2010 10:12 Scott_Li Jon R at the project assisted in rebooting the primary computer at ~ 10:10 am in lieu of the recent DST issues. Remote access was also restored. 11/02/2010 06:48 alan@bay 15:TestTagFailure: Clearing TASS on a known problematic system. 11/01/2010 13:15 Darren PSMFC is working with site personnel to restore remote access to PC1. The site personnel will not be available today but will be first thing in the morning. Once we have restored the remote access PSMFC can take care of the DST Phenom. 11/01/2010 06:54 alan@bay 15:TestTagFailure: Clearing TASS on a known problematic system. 11/01/2010 06:47 Scott_Li Due to the Daylight savings time issues on the Win 98 platforms, manually stopped and started Multimon on PC1 and 2 at these sites. Cannot access BO3-PC1 or JDJ-PC1 or BO3-PC1. Will call site SMP to see if we can get some assistance in correcting the access issues. 10/28/2010 06:51 darren@b 15:TestTagFailure: Alarm on known problematic system. 10/27/2010 06:29 darren@b 15:TestTagFailure: Alarm on known problematic system. 10/24/2010 06:38 alan@bay 15:TestTagFailure: Noted 10/23/2010 09:37 alan@bay 15:TestTagFailure: Noted 10/21/2010 06:33 Troy@bay 15:TestTagFailure: Noted 10/21/2010 06:32 Troy@bay 15:TestTagFailure: Noted 10/19/2010 06:35 alan@bay 15:TestTagFailure: Clearing TASS on a known problematic system. 10/18/2010 07:09 alan@bay 15:TestTagFailure: Noted 10/17/2010 07:51 Troy@bay 15:TestTagFailure: Known problematic antenna, clearing TASS. 10/16/2010 11:52 Troy@bay 11:Overrun,15:TestTagFailure: 15 is a known problematic antenna. PSMFC will investigate the overruns on 11 on the next site visit. 10/11/2010 07:55 Troy@bay 15:Overrun,15:TestTagFailure: Known problematic antenna, clearing TASS. 10/03/2010 07:33 darren@b 0A:ReaderReset,15:TestTagFailure: The alarm on antenna 15 is on a known problematic system. The alarm on 0A is due to a reader reset. 10/02/2010 07:42 darren@b 15:TestTagFailure: Alarm on known problematic system. 10/01/2010 07:32 darren@b 15:TestTagFailure: Alarm on known problematic system. 09/30/2010 08:03 darren@b 15:TestTagFailure: Alarm on a known problematic. 09/29/2010 07:34 darren@b 15:TestTagFailure: Alarm on known problematic system. 09/28/2010 07:33 darren@b 15:TestTagFailure: Alarm on a known problematic system. 09/27/2010 08:59 dlwarf@b 15:TestTagFailure: Noted. 09/26/2010 09:22 alan@bay 11:Overrun,15:TestTagFailure: Clearing TASS on known problematic systems. 09/25/2010 08:10 alan@bay 15:TestTagFailure: Clearing TASS on a known problematic system. 09/23/2010 07:42 alan@bay 15:TestTagFailure: Clearing TASS on a known problematic system. 09/22/2010 07:41 alan@bay 15:TestTagFailure: Clearing TASS on a known problematic system. 09/21/2010 08:29 alan@bay 15:TestTagFailure: Clearing TASS on a known problematic system. 09/20/2010 07:53 alan@bay 15:TestTagFailure: Clearing TASS on a known problematic system. 09/19/2010 09:03 Troy@bay 15:TestTagFailure: Known problematic antenna. Clearing TASS. 09/18/2010 07:51 Troy@bay 11:Overrun,15:TestTagFailure: 15 is a known problematic antenna. PSMFC will continue to monitor 11 for future overruns. 09/17/2010 07:44 Troy@bay 15:TestTagFailure: Noted 09/16/2010 07:49 Troy@bay 15:TestTagFailure: Noted 09/15/2010 07:32 Troy@bay 15:TestTagFailure: Noted 09/13/2010 08:07 Troy@bay 15:TestTagFailure: Known problematic antenna, clearing TASS. 09/12/2010 08:27 Darren The outstanding files were manually submitted for this site not BO1. 09/12/2010 08:15 darren@b 15:TestTagFailure: Alarm on known problematic system. 09/11/2010 08:04 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,0B:RocketPortNoEOT,0C:ReaderReset,0D:ReaderReset,0E:Reade rReset,0F:ReaderReset,10:ReaderReset,11:ReaderReset,12:ReaderReset,13:Read erReset,14:ReaderReset,15:ReaderReset,15:TestTagFailure,16:ReaderReset,17: ReaderReset,18:ReaderReset,22:InputSyncDetect,22:ReaderReset,24:InputSyncD etect,24:ReaderReset,26:InputSyncDetect,26:ReaderReset,28:ReaderReset,32:I nputSyncDetect,32:ReaderReset,34:InputSyncDetect,34:ReaderReset,36:InputSy ncDetect,36:ReaderReset,38:ReaderReset: These alarms were generated by a brief power outage. 09/09/2010 08:17 darren@b 0F:ReaderReset,15:TestTagFailure: Alarm on 0F caused by a reader reset. Antenna 15 is a known problematic system. 09/08/2010 08:16 darren@b 06:LowExcCurrent,15:TestTagFailure: Alarm on antenna 06 was addressed during yesterdays site GMC, the alarm on antenna 15 is on a known problematic system. 09/07/2010 11:54 Alan A GMC was performed 9/7/2010. All transceivers were checked and tuned as necessary. Outstanding files on PC2 were archived. The temp folders on both PCs were emptied. The clocks on both PCs were set to within one second of atomic time. No undocumented problems found. 09/03/2010 10:01 darren@b 15:TestTagFailure: Alarm on known problematic system. 09/01/2010 12:36 scottl All networking FO and copper converters and switches were replaced in lieu of the system wide network upgrades. The PSMFC network is now exclusively using black box products with the exception of the Sonicwall firewall and Dell managed switch in BO3. All Allied Telsyn products that were removed are being brought back to the Kennewick office for storage. Cleaned out the spiders webs underneath the level sensor in the transport flume at b2J. This was causing the level sensor to send false readings. 09/01/2010 08:28 alan@bay 15:TestTagFailure: Clearing TASS on a known problematic system. 08/31/2010 08:19 alan@bay 0C:ReaderReset,15:TestTagFailure: The alarm for 0C is a random reader reset and the TTF for 15 is due to a known problematic system. 08/29/2010 07:31 Troy@bay 15:TestTagFailure: Known problematic antenna, clearing TASS. 08/28/2010 08:30 Troy@bay 12:ReaderReset,15:TestTagFailure: The alarm for 12 is a possible Random Reader Reset and the TTF for 15 is due to a known problematic antenna below the water line. 08/26/2010 08:38 darren@b 15:TestTagFailure: Alarm on known problematic system. 08/24/2010 08:22 darren@b 11:Overrun,15:TestTagFailure: The alarms on antenna 15 are on a known problematic system. The overrun conditions on antenna 11 were brief. We will monitor and make the necessary adjustments if this continues. 08/23/2010 08:47 darren@b 15:TestTagFailure: Alarm on known problematic system. 08/22/2010 09:31 alan@bay 15:TestTagFailure,36:InputSyncDetect,36:ReaderReset: 15 is a known problematic system, 36 is a random reader reset. 08/21/2010 09:21 alan@bay 11:Overrun,15:TestTagFailure: Noted. 08/20/2010 08:30 alan@bay 15:TestTagFailure: Clearing TASS on a known problematic system. 08/19/2010 08:20 alan@bay 15:TestTagFailure: Clearing TASS on a known problematic system. 08/17/2010 08:59 darren@b 15:TestTagFailure: Alarm on known problematic system. 08/16/2010 09:29 alan@bay 15:TestTagFailure: Clearing TASS on a known problematic system. 08/12/2010 09:18 Troy@bay 15:TestTagFailure: Known problematic antenna, clearing TASS. 08/11/2010 08:20 darren@b 15:TestTagFailure: Alarm on known problematic system. 08/08/2010 07:49 darren@b 15:TestTagFailure: Alarm on known problematic system. 08/07/2010 07:58 darren@b 15:TestTagFailure: Alarm on known problematic system. 08/06/2010 08:31 darren@b 15:TestTagFailure: Alarm on known problematic system. 08/05/2010 13:01 Darren A site GMC was performed today (8-5-10). All transceivers were checked and adjusted for tuning, noise, and detectability. No problems were discovered during this visit. 08/05/2010 08:26 Troy@bay 15:TestTagFailure: Known problematic antenna. Clearing TASS. 08/04/2010 08:19 darren@b 15:TestTagFailure: Alarm on known problematic system. 08/03/2010 08:13 darren@b 15:TestTagFailure: Alarm on Known problematic system. 08/02/2010 08:50 darren@b 15:TestTagFailure: Alarm on known problematic system. 08/01/2010 08:17 Troy@bay 15:TestTagFailure: Known problematic antenna, clearing TASS 07/30/2010 11:11 Dave Updated map file to BO310211.MAP, disabling signal-by-code for the UofI's AC92 tags. Reset PC clocks to within one second of each other and atomic time. Archived all outstanding files on PC2. 07/30/2010 08:41 troy@bay 15:TestTagFailure: Knonwn problematic antenna, clearing TASS. 07/28/2010 08:35 troy@bay 15:TestTagFailure: Noted 07/27/2010 08:35 troy@bay 15:TestTagFailure: This is a known problematic antenna. Clearing TASS. 07/26/2010 08:46 troy@bay 15:TestTagFailure: Noted 07/25/2010 07:47 alan@bay 15:TestTagFailure: Noted 07/25/2010 07:38 Alan Manually pushed BO310206.102 to PTAGIS via PCA. 07/24/2010 09:02 alan@bay 15:TestTagFailure: Noted 07/23/2010 08:39 darren@b 02:ReaderReset,03:ReaderReset,03:RocketPortNoEOT,04:ReaderReset,05:ReaderR eset,06:ReaderReset,07:ReaderReset,08:ReaderReset,09:ReaderReset,0A:Reader Reset,0B:ReaderReset,0B:RocketPortNoEOT,0C:ReaderReset,0D:ReaderReset,0E:R eaderReset,0F:ReaderReset,10:ReaderReset,11:ReaderReset,12:ReaderReset,13: ReaderReset,14:ReaderReset,15:ReaderReset,15:TestTagFailure,16:ReaderReset ,17:ReaderReset,18:ReaderReset,22:InputSyncDetect,22:ReaderReset,24:InputS yncDetect,24:ReaderReset,26:InputSyncDetect,26:ReaderReset,28:ReaderReset, 32:InputSyncDetect,32:ReaderReset,34:InputSyncDetect,34:ReaderReset,36:Inp utSyncDetect,36:ReaderReset,38:ReaderReset: Power outage due to a scheduled switch over caused these alarms. 07/22/2010 13:06 Darren A new phone with speakerphone capabilities was installed. 07/22/2010 13:04 Darren A site GMC was performed today (7-22-10). All transceivers were checked and adjusted for tuning, noise, and detectability. The files on PC2 were archived and the clocks are within 20 seconds of each other and atomic time. No problems were discovered during this visit. 07/20/2010 08:24 alan@bay 15:TestTagFailure: Noted 07/19/2010 08:32 alan@bay 15:Overrun,15:TestTagFailure: Noted 07/19/2010 08:31 alan@bay 03:TestTagFailure: There was a PIT tag in the field coincidentally with the firing of the timer tag. 07/16/2010 08:11 scottl@b 01:ReaderReset,02:ReaderReset,03:ReaderReset,04:ReaderReset,05:ReaderReset ,06:ReaderReset,07:ReaderReset,08:ReaderReset,09:ReaderReset,0A:ReaderRese t,0B:ReaderReset,0B:RocketPortNoEOT,0C:ReaderReset,0D:ReaderReset,0E:Reade rReset,0F:ReaderReset,10:ReaderReset,11:ReaderReset,12:ReaderReset,13:Read erReset,14:ReaderReset,15:ReaderReset,15:TestTagFailure,16:ReaderReset,17: ReaderReset,18:ReaderReset,22:InputSyncDetect,22:ReaderReset,24:InputSyncD etect,24:ReaderReset,26:InputSyncDetect,26:ReaderReset,28:ReaderReset,32:I nputSyncDetect,32:ReaderReset,34:InputSyncDetect,34:ReaderReset,36:InputSy ncDetect,36:ReaderReset,38:ReaderReset: Error due to a power outage, appears that this outage was about 8 minutes 24 seconds. 07/12/2010 08:15 darren@b 15:TestTagFailure: Alarm on known problematic system. 07/11/2010 09:19 darren@b 15:TestTagFailure: Alarm is on a known problematic system. 07/10/2010 08:42 darren@b 15:TestTagFailure: Alarm on known problematic system. 07/09/2010 08:34 darren@b 05:ReaderReset,06:LowExcCurrent,06:ReaderReset,15:TestTagFailure: The alarms on antennas 05 and 06 were generated by PSMFC personnel during a site visit. The failures on 15 are on a known problematic system. 07/07/2010 13:25 Alan A GMC was performed 7-7-2010. All transceivers were checked and tuned as necessary. Transceivers 03, 04, 09 and 0D are showing noise into the low teens that does not appear to significantly affect performance. Transceiver 06 is showing noise into the mid 20's that cannot be tuned out. Swapping antenna cables with transceiver 05 shows that the noise is coming from antenna 06 (same results for either transceiver with either antenna). The fuses in transceiver 06 were scraped to remove some conformal coating. The wiring at the power distribution panel was verified as good. The current was increased and the hit rate was set to 100, but going from standby to scan rarely yields a successful timer tag read. Transceiver 01 is showing 100% noise. The mystery timer tag hits on 7-5-2010 were caused by me (remotely from PC2). All outstanding files on PC2 were archived. The clocks on both PCs (~00:01:15 slow) were set to within one second of atomic time. No other problems found. 07/07/2010 08:22 darren@b 15:TestTagFailure: Alarm on known problematic system. 07/06/2010 08:23 darren@b 15:TestTagFailure: This is a known problematic system. The current has dropped to .5A so the timer tag is probably not going to fire. 07/05/2010 07:59 alan@bay 15:TestTagFailure: Noted 07/04/2010 09:43 alan@bay 15:TestTagFailure: Noted 07/03/2010 09:49 alan@bay 15:TestTagFailure: Noted 07/02/2010 08:37 alan@bay 15:TestTagFailure: Noted 07/01/2010 12:51 Darren A site GmC was performed today (7-1-10). All transceivers were checked and adjusted for tuning, noise, and detectability. The noise has elevated on antenna 01 back to 100% but the upper 6 antennas have also increased into the teens with antenna 06 being the worst at 20%. The timer tag was adjusted to a 100% level. The PC clocks are with 20 seconds of atomic time and each other. No problems were discovered during this visit. 06/28/2010 09:43 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,0B:RocketPortNoEOT,0C:ReaderReset,0D:ReaderReset,0E:Reade rReset,0F:ReaderReset,10:ReaderReset,11:ReaderReset,12:ReaderReset,13:Read erReset,14:ReaderReset,15:ReaderReset,16:ReaderReset,17:ReaderReset,18:Rea derReset,22:InputSyncDetect,22:ReaderReset,24:InputSyncDetect,24:ReaderRes et,26:InputSyncDetect,26:ReaderReset,28:ReaderReset,32:InputSyncDetect,32: ReaderReset,34:InputSyncDetect,34:ReaderReset,36:InputSyncDetect,36:Reader Reset,38:ReaderReset: The alarms were generated by an unscheduled site wide power outage. 06/23/2010 12:55 Darren A site GMC was performed today (6-23-10). All transceivers were checked for tuning, noise, and detectability, adjustments were made when necessary. The files on PC2 were archived. No problems were discovered during this visit. 06/12/2010 08:44 darren@b 22:InputSyncDetect,22:InputSyncLost,26:InputSyncDetect,26:InputSyncLost,28 :ReaderReset: Alarms were generated by a random reader reset. 06/08/2010 16:18 Dave Updated database to BO310159.DB. Reset PC clocks to within one second of each other and atomic time. Archived all outstanding data files on PC2. 06/08/2010 12:12 Alan A GMC was performed 6-8-2010. All transceivers were checked and tuned as necessary. All outstanding files on PC2 were archived. Both PCs 31 seconds behind atomic time. No problems found. 06/06/2010 10:21 alan@bay 0B:ReaderReset,17:ReaderReset: These alarms are the result of a random reader reset. PSMFC and Destron Fearing are aware of the problem. 06/05/2010 08:47 alan@bay 34:InputSyncDetect,34:ReaderReset: These alarms are the result of a random reader reset. PSMFC and Destron Fearing are aware of the problem. 06/04/2010 08:15 scottl@b 09:Overrun: This was corrected during the site visit on 6/3/10 06/03/2010 13:07 scottl Re-tuned transceiver 09. Looking at the raw data, the transceiver was in an excessive noise level condition for a period of time. When arrived the unit was relatively quiet. After the re-tune, the hit rate is at 99 to 100 % and noise levels are at a minimum. No other problems to report. 05/26/2010 13:05 Alan A GMC was performed 5-26-2010. All transceivers were checked and tuned as necessary. All outstanding files on PC2 were archived. The clocks on both PCs (~00:01:00 slow) were set to within one second of atomic time. No problems found. 05/17/2010 13:14 scottl Tuned transceiver 11 due to timer tag misfires. Hit rate at 100 percent after tuning. No other problems to report. 05/13/2010 12:07 scottl Performed site GMC, all transceivers were re tuned and calibrated as necessary, no problems to report.PC1 clocks lags PC2 by 4 seconds. 05/04/2010 13:21 Dave Updated database to BO310124.DB, replacing the action code for seven from AC96 to AC97. Set manual upload mode to "Upload and Archive" in Uploader on PC1, and then exited and restarted Uploader to permanently register the correct mode. PC clocks are within two seconds of each other and atomic time. 05/03/2010 13:17 scottl All transceivers were re tuned and calibrated, no problems to report. PC clocks are exactly the same and lag atomic time by 1 second. 05/03/2010 12:22 Dave Updated database and map files to BO310123.DB and BO310123.MAP, respectively. This SxC version contains 629k "Yellow Light" tags codes for the UofI. Reset PC clocks to within one second of each other and atomic time. Corrected manual settings for Uploader from "Archive Only" on PC1. Archived all outstanding data files on PC2. 04/28/2010 08:42 troy@bay 0D:LowExcCurrent: The low current alarm threshold was reduced to 2900 mA. 04/27/2010 11:49 Dave Updated database to BO310113.DB, recasting 15 AC96 tag codes to AC97. Reset PC clocks to within 1 second of each other and atomic time. Corrected manual upload mode from "Archive Only" on PC1. Archived all outstanding files on PC2. 04/27/2010 11:09 Scott_Li Turned OFF noise reporting for all transceivers that were involved in monitoring noise levels during the Sea Lion Electrical Deterrence System (SLEDS) evaluation. The SLEDS system is being removed at this time, the study has been discontinued. 04/27/2010 08:56 troy@bay 0D:LowExcCurrent: It appears the current dropped below the low current threshold. PSMFC will continue to monitor and make adjustments if needed. 04/26/2010 13:03 scottl The ladder xcvrs Unique function has been turned back to OFF. 04/26/2010 12:31 scottl As requested, the "Unique" function on all of the BO3 ladder xcvrs only has been changed from OFF to ON.They will remain operating in this configuration until further notice. 04/24/2010 08:05 darren@b 09:ReaderReset: This alarm is not uncommon and PSMFC is aware that this can and will happen. 04/23/2010 16:30 Dave Updated database to BO310113.DB, with additional tags for AC96-97. PC clocks are within three seconds of each other and 17 seconds of atomic time. Archived all outstanding data files on PC2. Corrected default manual action for PTTP-Uploader on PC1 from "Archive Only" to "Upload and Archive". 04/20/2010 13:50 Dave Updated database to BO310110.DB, with new codes for AC97 and additional codes for AC96. PC clocks are within two seconds of each other and 10 seconds of atomic time. Corrected default status for manual file uploads from PC1. Archived all outstanding data files on PC2. 04/16/2010 10:41 Dave Updated SxC configuration map and db files to include AC96 (RUBTAG) with a "Red Light" action. Reset PC clocks to within one second of each other and atomic time. Archived all outstanding data files. Corrected default manual file upload action on PC1 from "archive only" to "upload and archive". 04/15/2010 08:21 darren@b 32:InputSyncDetect,32:ReaderReset: This alarm was generated by a random reader reset. 04/11/2010 10:37 scottl@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: Apparent brief power outage. 04/09/2010 08:54 troy@bay 15:Overrun: This alarm is on a system that occassionally has issues. PSMFC will monitor. 04/08/2010 08:35 troy@bay 11:Overrun,12:LowExcCurrent,12:TestTagFailure: These alarms were generated by PSMFC personnel during a site GMC. 04/07/2010 13:29 Darren A site GMC was performed today (4-7-10). All transceivers were checked for tuning, noise, and detectability. The detection system associated with antenna 11 was investigated for timer tag failures and driveability. A different transceiver was used to check the antenna system and I found that the problem follows the antenna. When the system power is adjusted the noise floor increases for a period of time until the capacitors can stabilize. I can increase the power but again the noise floor elevates. The current was at 2.2A when I began testing and I was able to increase it to 2.9A, I adjusted the timer tag to read 100%. The system appears to have a decent read range when testing in the transceiver and no hesitation reading PIT tags. The original transceiver was left in use because the problem is pointing to antenna system that could be failing. The PC clocks were more than 1 minute from atomic time and 30 seconds from each other. The clocks were adjusted, during the timegap on PC1 there was no data collected on PC2, to within 1 second of each other and atomic time. 04/02/2010 13:52 Darren A site GMC was performed today (4-2-10). All transceivers were checked for tuning, noise and detectability. The pc clocks are within 10 seconds of each other and atomic time. No problems were discovered during this visit. 03/23/2010 15:04 Darren This message was received from Jonathan Rerecich today. The AFF was watered up at about 1600 yesterday, 3/22. 03/15/2010 08:15 darren@b 05:LowExcCurrent: The current threshold is equal to the actual current causing the occasional alarm. The threshold will be adjusted via a PCA session until the system can be checked for optimization and tuning. 03/14/2010 11:49 alan@bay 05:LowExcCurrent: The threshold was remotely lowered 300mA to 2400mA. 03/10/2010 07:25 alan@bay 02:LowExcCurrent: Clearing TASS, this was addressed yesterday. 03/09/2010 07:50 alan@bay 02:LowExcCurrent: This transceiver appears to be in tune and is reading timer tags and PIT tags well. The current alarm threshold was remotely lowered to 2900mA (300mA below the operating current). 03/03/2010 07:28 darren@b 02:LowExcCurrent: The current and the alarm threshold are equal causing the alarms. The threshold will be adjusted to avoid this condition. 02/18/2010 14:15 Alan "SOP Multimon Annual Reset" was performed on the data collection platform. The platform is functioning properly with the exception that PC1 would run scandisk on a warm boot but not a cold boot. Scandisk was disabled via software. We will continue to investigate this issue. Transceiver 0B was replaced due to timer tag issues. 02/16/2010 07:35 darren@b 17:ReaderReset: Alarm noted. This site will be visited this week for a site GMC. 02/11/2010 07:26 scottl@b 0B:ReaderReset: noted 02/10/2010 12:41 scottl Check on transceiver 0B, noise very low, checked fuse holders and all looked good. No signs of arching whatsoever, fuses real tight in holders. Did notice that the TT hit rate was intermittent. Turned TT on and off via the switch on the VTT and checked the connections on the plug for the pickup coil. VTT is now working. Will monitor. 02/02/2010 08:06 alan@bay 0C:ReaderReset: This alarm is the result of a random reader reset. PSMFC and Destron Fearing are aware of the problem. 01/22/2010 08:03 Scott_Li Appears that something is happening to the transceiver on a repetitive basis, speculate that possibly the fuse holder maybe arching or outside interference of some sort. Will further investigate on the next site visit. 01/19/2010 12:17 Darren A site GMC was performed today (1-19-10). All transceivers were checked for tuning, noise, and detectability. The transceivers on antennas 0B and 12 (BO3) were out of tune and were adjusted for optimization. No other problems were discovered during this visit. 01/16/2010 07:21 alan@bay 32:InputSyncDetect,32:ReaderReset: These alarms are the result of a random reader reset. PSMFC and Destron Fearing are aware of the problem. 01/08/2010 08:29 troy@bay 0B:TestTagFailure,15:TestTagFailure: Noted 01/04/2010 07:25 troy@bay 0B:TestTagFailure,15:TestTagFailure: 15 is a known problematic system, 0B will be investigated on the next GMC. 01/01/2010 00:00 PTOC_Bot Annual log file initiation for BO3 #### End of Event Log for BO3 ###