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/2005 08:26 darren@r 11:ReaderReset: This alarm is a by product of the transceiver PSMFC and Digital Angel are aware of this phenomenon. The site will be inspected during the next site visit. 12/29/2005 08:07 troy@ruf 0C:ReaderReset: Possible Random Reader reset. PSMFC will continue to monitor for furture occurances 12/22/2005 07:45 darren@r 0A:ReaderReset: Alarm noted and will be inspected today by PSMFC personnel. 12/20/2005 08:09 alan@ruf 0E:LowExcCurrent: Clearing the TASS Panel. These alarms were generated prior to yesterday's threshold adjustment. 12/19/2005 10:16 alan@ruf 0E:LowExcCurrent: Adjusted alarm threshold to 3400mA via PCA. PTAGIS Field Operations will investigate at the next opportunity. 12/18/2005 09:02 darren@r 0E:LowExcCurrent: The alarm will be checked by PSMFC via PCA. The current threshold may need to be adjusted. 12/17/2005 08:35 darren@r 03:LowExcCurrent: The current threshold was adjusted by PSMFC. This is an old alarm. 12/16/2005 11:16 Alan_Bro With the help of on-site personnel, PC1 was re-booted at ~11:00 this morning reestablishing remote connectivity. No activity was observed on PC2 during PC1s downtime. 12/16/2005 08:40 Alan_Bro Manually pushed BO305350.102 to PTAGIS and adjusted the transceiver 03 alarm threshold to 3500mA via PCA. An error occurred with PCA at the completion of this operation. Site personnel have been contacted and a re-boot is forthcoming. 12/16/2005 08:13 darren@r 03:LowExcCurrent: The current alarm is only .1A below the actual current. The alarm level will be adjusted to avoid sending a substantial amount of alarms. PSMFC will address this alarm issue on the next site visit. 12/15/2005 15:39 darren@r 03:LowExcCurrent: No direct cause for this alarm. PSMFC will monitor for future alarms. 12/15/2005 08:07 troy@ruf 02:LowExcCurrent,03:LowExcCurrent,08:LowExcCurrent,0E:LowExcCurrent,15:Tes tTagFailure: These alarms are most likely due to tuning that was done during a GMC. If they persist PSMFC will lower the alarm threshold in the transcievers. 12/13/2005 13:48 Troy A site GMC was performed 12/13/05. All transcievers were checked for tune. No previously unknown problems were found. 15 and 17 most likely have a problem below the water. This ladder is not scheduled to be de- watered this year. 12/12/2005 08:10 darren@r 03:LowExcCurrent: Alarm will be addressed on the next site visit. 12/08/2005 16:57 Alan_Bro Responding to the lack of files from Bonneville, it was found that the CentreCom FH712SW has a noisy fan. While moving cables and equipment in the coms rack connectivity was restored, probably due an intermittent cable or perhaps the FH712SW itself. The tardy files were submitted manually from BO4 and BO3, the others were submitted via PCA. PTAGIS Field Operations will continue to monitor. 11/28/2005 10:32 darren@r 15:TestTagFailure: No direct cause for this alarm. PSMFC will investigate on the next site visit. 11/23/2005 08:54 troy@ree 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 are the result of power being turned off for COE maintenance. 11/09/2005 08:24 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,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: COE power outage. 10/31/2005 08:51 Scott_Li Manually PCA'd into each of the multimon sites and stopped and started the MM application due to the daylight savings time Phenom. 10/24/2005 13:28 Darren A site GMC was performed on both BO3 and BO4. No problems were found at BO3 all transceivers were checked for tuning and noise. At BO4 I adjusted the timer tag hit rate on transceivers 01 and 04. According to the timer tag report this morning the timer tag on 04 was not reading at 100%, when I arrived on site I found that the hit rate was only at 70% I tuned the capacitors and brought the hit rate back to 95-100%. I performed the same actions on antenna 01. Antennas 02 and 03 were checked and the hit rate was still above 95%. 10/24/2005 08:02 troy@ruf 15:TestTagFailure: This will be addresses today during a scheduled GMC 10/22/2005 08:38 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,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 are the result of a power outage. 10/21/2005 08:15 scottl@r 11:Overrun,15:TestTagFailure: Problems are not of concern at this time. 10/16/2005 07:33 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: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 outage. PSMFC will contact site personnel on Monday to confirm this outage as well as last night. 10/15/2005 06:33 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: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: It appears that there was another scheduled power outage at this facility. PSMFC will confirm this on Monday. 10/14/2005 16:13 darren@r 11:Overrun: No direct cause for this alarm. PSMFC was on site yesterday for site GMC's. We will continue to monitor for future alarms. 10/14/2005 08:10 darren@r 01:ReaderReset,02:ReaderReset,03:ReaderReset,04:ReaderReset,05:ReaderReset ,06:ReaderReset,07:ReaderReset,08:LowExcCurrent,08:ReaderReset,09:ReaderRe set,0A:ReaderReset,0B:ReaderReset,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,22:InputSyncDetect,22:ReaderReset,24:InputSyncDetect,24:ReaderReset ,26:InputSyncDetect,26:ReaderReset,28:ReaderReset,32:InputSyncDetect,32:Re aderReset,34:InputSyncDetect,34:ReaderReset,36:InputSyncDetect,36:ReaderRe set,38:ReaderReset: These alarms were generated by a power outage at this facility. 10/13/2005 20:00 Scott_Li GMC was performed, all transcievers were retuned and calibrated as necessary. No outstanding problems to report. 10/13/2005 08:09 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:Overrun,11:ReaderReset,12:ReaderReset,13:ReaderReset, 14:ReaderReset,15:Overrun,15:ReaderReset,15:TestTagFailure,16:ReaderReset, 17:ReaderReset,18:ReaderReset,22:InputSyncDetect,22:ReaderReset,24:InputSy ncDetect,24:ReaderReset,26:InputSyncDetect,26:ReaderReset,28:ReaderReset,3 2:InputSyncDetect,32:ReaderReset,34:InputSyncDetect,34:ReaderReset,36:Inpu tSyncDetect,36:ReaderReset,38:ReaderReset: Tammy Mackey notified PSMFC that there was a brief power outage at this site overnight. This was confirmed this morning and is the cause for these alarms. 10/12/2005 08:04 darren@r 11:Overrun: This alarm will be addressed on the next site visit. 09/23/2005 08:20 scottl@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,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: Obvious power glitch. COE informed us of scheduled outages at Bradford, but no mention of this site 09/21/2005 08:16 scottl@r 11:Overrun: Noted 09/09/2005 08:08 alan@ruf 17:LowExcCurrent: This alarm was generated by PTAGIS Field Operations personnel during a site visit. 09/08/2005 13:29 Scott_Li This site was checked for tuning and efficiencies. Transceiver 05 was retuned and checked for timer tag. No problems were found. 09/02/2005 11:08 darren@r 15:Overrun: Alarms will be addressed on the next site visit. 09/01/2005 08:06 darren@r 11:Overrun,34:InputSyncDetect,34:ReaderReset: The alarms on antenna 34 were generated by a random reader reset. The overrun conditions will be investigated on the next site visit. 08/30/2005 08:22 darren@r 10:ReaderReset,11:Overrun,15:TestTagFailure: Alarms will be investigated on the next site visit. 08/25/2005 14:49 Alan_Bro A GMC was performed 8/25/2005. All transceivers were checked and tuned as necessary. Transceivers 11-18 are exhibiting noise rolling from single digits to high teens, presumably caused by the HDX system. Transceiver 17 is exhibiting noise up to 50% more than likely due to the previously documented problems below the waterline. No other problems found. 08/19/2005 08:19 scottl@r 15:Overrun: Noted 08/18/2005 12:39 Dave Updated map and database files to BO305230.MAP and BO305230.DB, respectively. New configuration sets "Red Light" alert for 38,510 Wenatchee/Methow coho in Action Code #101. Reset PC clocks to within 1 second of each other and atomic time. 08/18/2005 07:06 scottl@r 15:Overrun: Noted. 08/16/2005 08:06 scottl@r 15:Overrun: This error is common for this antenna. Suspect leaking 08/12/2005 08:16 troy@ruf 15:TestTagFailure: This transceiver is known to have problems which are believed to be below the water line. PSMFC will monitor for futher occurences. 08/05/2005 14:53 Alan_Bro A GMC was performed 7/20/2005. All transceivers were tuned. Antennas 11, 15 and 17 are still noisy with 17 bouncing up to 80% noise at times. No other problems found. 08/03/2005 07:58 Darren I manually pushed file BO305215.102 to the server. This site is periodically stalling on file uploads. 08/02/2005 08:48 alan@ruf 03:Overrun: This transceiver might be drifting slightly out of tune. It is reading timer tags and PIT Tags. PTAGIS Field Operations will examine on a site visit later this week. 08/01/2005 09:21 alan@ruf 11:TestTagFailure: PTAGIS Field Operations will monitor for future occurances. 07/30/2005 07:40 darren@r 15:LowExcCurrent: This alarm was addressed yesterday at around 09:00. 07/29/2005 08:47 darren@r 15:LowExcCurrent: System will investigated on the next site visit. The alarm level will changed to try and minimize the file sizes. 07/27/2005 08:21 darren@r 03:Overrun: Alarm will be addressed on the next site visit. 07/26/2005 07:59 darren@r 18:ReaderReset: Alarm was generated by a random reader reset. 07/25/2005 08:06 darren@r 03:Overrun: This alarm will addressed on the next site visit. 07/24/2005 11:02 scottl@r 03:Overrun: Noted 07/21/2005 08:05 darren@r 0F:LowExcCurrent,11:LowExcCurrent,13:LowExcCurrent,17:LowExcCurrent: Alarms were generated by PSMFC personnel while performing a site GMC. 07/20/2005 16:15 Alan_Bro A GMC was performed 7/20/2005. All transceivers were tuned. "Underwater problem children" antennas 11, 15 and 17 are being especially noisy with 15 bouncing up to 100% noise at times. No other problems found. 07/20/2005 09:23 scottl@r 03:Overrun,11:LowExcCurrent: A site visit is scheduled for tomorrow for GMC 07/17/2005 08:01 darren@r 03:Overrun: Alarms will be investigated on the next site visit. 07/16/2005 08:08 darren@r 03:Overrun,11:LowExcCurrent: Alarms will be addressed on the next site visit. 07/15/2005 09:03 darren@r 03:Overrun,15:Overrun: Alarms will be addressed on the next site visit. 07/13/2005 16:27 darren@r 11:LowExcCurrent: Alarms will checked on the next site visit. 07/08/2005 09:41 troy@ruf 03:Overrun: This transceiver is experiencing noise in the mid teens. This will be addressed on the next GMC. 07/07/2005 08:15 troy@ruf 03:Overrun: PSMFC will monitor for future occurences. 07/06/2005 13:12 Alan_Bro A GMC was performed 7/6/2005. All transceivers were tuned, no problems found. 07/01/2005 14:38 Darren I PCA'd into the site and manually pushed file BO305182.104 to the server. 06/29/2005 08:39 alan@ruf 32:InputSyncDetect,32:InputSyncLost,36:InputSyncDetect,36:InputSyncLost,38 :ReaderReset: These alarms were generated by a random reader reset. PSMFC and Digital Angel are aware of the problem. 06/27/2005 08:14 alan@ruf 15:Overrun: This antenna is suspected to be leaking. PTAGIS Field Operations will optimize on the next site visit. 06/26/2005 08:49 darren@r 11:Overrun,15:LowExcCurrent: The alarms will be investigated on the next site visit. There seems to be a problem with antenna 15 the current dropped .5A in one hour. This antenna has become troublesome this year and is suspect to have leaked. PSMFC will try to maximize the efficiencies next visit. 06/24/2005 08:28 darren@r 36:InputSyncDetect,36:ReaderReset: Alarm was genrated by a random reader reset. PSMFC and Digital Angel are aware of this anomaly. It does not effect the transceivers ability to detect efficiently. 06/21/2005 08:21 darren@r 17:LowExcCurrent: Alarm was addressed on site visit. 06/20/2005 13:18 scottl All transceivers were tuned and recalibrated as necessary, transceivers 11 and 18 are in a chronic excessive noise condition due to suspected leaky antennas, no other problems to report. System clocks are within 6 seconds of each other 06/20/2005 08:44 darren@r 11:Overrun: Alarm will be investigated this week during site maintenance. 06/19/2005 11:22 dlwarf@r 15:TestTagFailure: Noted. 06/17/2005 08:25 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: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 what appears to be a brief(less than 4 minutes) power outage. 06/14/2005 09:11 scottl@r 36:InputSyncDetect,36:ReaderReset: Not of concern at this time 06/13/2005 08:28 darren@r 15:TestTagFailure: alarm will be investigated on the next site visit. 06/10/2005 14:10 Dave Updated database to BO305161.DB. This version contains 5984 additional tag codes for Action Code #82 (UI-FPC). PC clocks are within 2 seconds of each other and 16 seconds of atomic time. 06/10/2005 08:35 scottl@r 15:Overrun: This antenna is known to be consistently noisey due to bad antenna and or cable/connector. 06/09/2005 12:05 Troy A site GMC was performed 06/09/05. All transceivers were checked for tune and readability. 15 and 17 are still exhibiting problems and the problem is below the waterline. They were tuned as well as we possibly could under the circumstances. 11 is looking good at this time. PC1 is 13 seconds behind atomic time and 3 seconds behind PC2. Multimon is running in full screen mode on both PC's. 06/05/2005 09:44 troy@ruf 36:InputSyncDetect,36:ReaderReset: Random reader reset is a known issue. 06/05/2005 09:42 troy@ruf 15:Overrun: This will be addressed on the next site visit. 06/03/2005 16:46 Dave Updated database and map files to BO305154.DB and BO305154.MAP, respectively. The new configuration includes references for AC-83 (UI-NPT), with a "Yellow Alert" action within the AFF. The PC clocks were reset to within 1 second of each other and atomic time. 06/03/2005 07:59 darren@r 11:ReaderReset,12:ReaderReset,15:LowExcCurrent,15:ReaderReset,15:TestTagFa ilure,17:LowExcCurrent: Alarms were generated by PSMFC personnel while performing a site GMC. 06/02/2005 11:42 Troy A site GMC was performed 06/02/05. All transceivers were checked for tune and readability. 11 and 15 are still experiencing excessive noise. The problem is below the water line on both systems. I took the cable that is attached to antenna 11 and hooked it to transceiver 12 and the noise moved to transceiver 12. I did the same with antenna 12 and transceiver 11 was quiet. No other problems to report. 06/01/2005 08:15 darren@r 11:Overrun: Alarms will be addressed on the next site visit. 05/27/2005 08:48 alan@ruf 17:LowExcCurrent: This alarm was generated during a site visit by PTAGIS Field Operations. 05/27/2005 08:47 troy@ruf 17:LowExcCurrent: These alarms caused by PSMFC personnel performing at GMC. 05/26/2005 09:57 Darren A site GMC was performed today (5-26-05). All transceiver were checked for tuning, noise, and detectability. No problems were found. Both PC's have Multimon running in a full screen upon departure. 05/21/2005 08:30 alan@ruf 15:LowExcCurrent,15:TestTagFailure: These alarms were generated by PTAGIS Field Operatins personnel during a site visit. 05/21/2005 08:27 alan@ruf 10:ReaderReset: This alarm was generated by a random reader reset. PSMFC and Digital Angel are aware of this problem. 05/21/2005 08:23 alan@ruf 03:LowExcCurrent: This alarm was generated by PTAGIS Field Operatins personnel during a site visit. 05/18/2005 16:05 Darren A site GMC was performed today (5-18-05). All transceivers were checked for tuning, noise, and detectability. No problems were found. Both PC's have Multimon running in a full screen upon departure. 05/17/2005 11:13 Dave Updated database and map files to BO305137.DB and BO305137.MAP, respectively. The map file contains definitions for AC-81 and AC-82 (U of I target groups) and AC-251 (test tags used by U of I to test the SbyC system in the AFF). AC-81 and AC-82 are defined in all DUs, but AC-251 is defined only in the two SbyC DUs. The new database contains codes for AC-82 and AC-251; the codes for AC-81 were previously defined in BO305104.DB. The PC clocks were reset to within 1 second of each other and atomic time. 05/13/2005 08:54 alan@ruf 15:Overrun: This antenna has trouble below the waterline and this could be the cause of this alarm. This transceiver is reading timer tags and PIT Tags. 05/11/2005 08:08 troy@ruf 17:LowExcCurrent: This alarm occured during a site GMC. 05/11/2005 08:06 Troy A GMC was performed 5/10/05. All transceivers were checked for tune. 15 is still a problem and the problem is below the waterline. 05/05/2005 10:33 Troy A site GMC was performed 05/05/05. All transceivers were checked for tune and no problems were found. 05/03/2005 08:23 troy@ruf 05:ReaderReset: Possible Random reader reset. PSMFC will monitor for future occurences. 04/30/2005 09:06 troy@ruf 11:ReaderReset: Possible random reader reset. PSMFC will monitor for future occurances. 04/30/2005 09:05 troy@ree 01:LowExcCurrent,03:ReaderReset,09:LowExcCurrent: these alarms were caused by psmfc personnel while performing a GMC 04/28/2005 10:34 Troy A GMC was performed 04/28/05. All transceivers were checked for tune and no new problems were found. 11 and 15 will run quiet for a while and then spike in noise. This is a known problem. Both these problem antennas are reading tags. 04/28/2005 09:13 darren@r 11:Overrun,15:Overrun: PSMFC is on site today (4-28-05) for a site GMC and will address these alarms. 04/20/2005 16:28 alan@ruf 11:LowExcCurrent: This has been addressed. 04/20/2005 10:06 alan@ruf 11:LowExcCurrent: This transceiver/antenna is having troubles below the waterline. It is reading PIT Tags and timer tags. Via PCA I lowered the alarm threshold from 2300mA to 2000mA. PTAGIS Field Operations will continue to monitor. 04/16/2005 09:10 alan@ruf 15:Overrun: This antenna has been problematic and was experiencing noise at the time of this alarm. It has since quieted down. PTAGIS Field Operations will continue to monitor. 04/16/2005 09:06 alan@ruf 0F:ReaderReset: This alarm was caused by a random reader reset. PSMFC and Digital Angel are aware of the problem. 04/14/2005 16:33 Dave Reset FTP client in Windows Commander to locate the new Site_Configuration location under 'Software' rather than 'pub' on the PTAGIS FTP server. 04/14/2005 14:43 Dave Updated database to BO305104.DB. This version contains 38k+ tags for AC-81, the U of I study. This version of the database also includes 200 additional test tags, 100 each of AC-254 and AC-255; these are the new SGL tags added to the general database earlier today. I also updated the BO3-GEN.DB file on both PCs, and refreshed the WATCH.TAG file on PC2. The PC clocks are within 8 seconds of each other and 38 seconds of atomic time. 04/13/2005 10:59 Troy A site GMC was performed 04/13/05. All transceivers were checked for tune. Coils 11 and 15 are reporting excessive noise. This is a known issue and the problem is suspected to be below the water line. Attempts to tune out the noise were unsuccessful. Coil 17's TT was tested and the hit rate is at 100%. The noise is elevated on this coil as well which may be the cause of the occassional TT being missed. PSMFC will continue to monitor the problem coils. 04/13/2005 10:55 Troy A site GMC was performed 04/13/05. All transceivers were checked for tune. Coil's 11 and 15 are reporting excessive noise. These are known issues and the problem is suspected to be below the water line. Attempts to tune out the noise were un-successfull. Coil 17's TT was tested and the hit rate was at 100%. The noise is elevated on this coil as well which may be causing the TT to fail occassionally. PSMFC will continue to monitor the problem coils. 04/13/2005 09:24 Alan_Bro The pitevent stating the power outage scheduled for 4/12/2005 was intended for BO1. 04/12/2005 09:02 Don_Warf Tammy Mackey called to say that power would be off at BO3 for 2 to 4 days starting today. This is necessary for maintenance at the powerhouse. The COE has offered to power the Pittag room with a generator. There will be a 10 minute outage during the change-over. The exact time of the change-over is not known. We will be on-site tomorrow to monitor the situation. 04/12/2005 08:53 alan@ruf 16:ReaderReset: This alarm was generated by a random reader reset. PSMFC and Digital Angel are aware of the problem. Additionally, transceiver 11 has not been reading it's timer tag. Antenna 11 has a problem below the waterline creating noise. I PCA'd into the site and sucessfully fired the timer tag. PTAGIS Field Operations will continue to monitor. 04/11/2005 09:46 Alan_Bro Site Bio Tammy Mackey called to confirm the power outage at the AFF on 4/8/2005 around 11:00 AM. 04/09/2005 08:42 scottl@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:Overrun,11:ReaderReset,12:ReaderReset,13:ReaderReset, 14:ReaderReset,15:ReaderReset,16:ReaderReset,17:ReaderReset,18:ReaderReset ,22:InputSyncDetect,22:ReaderReset,24:InputSyncDetect,24:ReaderReset,26:In putSyncDetect,26:ReaderReset,28:ReaderReset,32:InputSyncDetect,32:ReaderRe set,34:InputSyncDetect,34:ReaderReset,36:InputSyncDetect,36:ReaderReset,38 :ReaderReset: Resets caused by brief power outage 04/03/2005 11:25 Dave I pcA'd in and stopped, and then immediately restarted, MultiMon, to adjust the file creation times on both PCs. These had been shifted forward an hour due to Daylight Savings Time. Stopping and restarting data collection will reset the creation times to 03:00, 06:00, 09:00, and 12:00. This is a documented phenomenon with the MultiMon software. I pushed the outstanding files from PC1 to the PTAGIS server. I did not adjust the PC clocks. 03/31/2005 08:45 Scott_Li An In/Pre-Season site visit was conducted by Dave and Scott in order to ensure that the interrogation platforms were set to their base configuration prior to the peak out-migration period. Most sites had already been reset but were revisited anyway in order to go over some the SByC activities and mild changes to the base configuration files. 03/27/2005 08:40 troy@ruf 15:Overrun: This transceiver has been a problem child. It is suspected that the problem lies below the water line. PSMFC will address this issue on the next site visit. 03/20/2005 09:47 alan@ruf 17:TestTagFailure: No apparent reason for this alarm. PTAGIS Field Operations will investigate on the next site visit. 03/19/2005 11:30 Alan_Bro Manually pushed BO305077.105 to PTAGIS via PCA. 03/18/2005 10:57 Alan_Bro Transceiver 11 has not fired a timer tag on it's own since midnight. The transceiver is in a high noise state due to a problem below the waterline. I PCA'd into PC2 and fired the timer tag successfully three out of three times. PTAGIS Field Operations will continue to monitor. 03/18/2005 07:53 darren@r 17:TestTagFailure: No direct cause for this alarm. PSMFC will investigate during the next site visit. 03/17/2005 08:16 darren@r 11:LowExcCurrent,11:Overrun,11:ReaderReset,12:LowExcCurrent,12:ReaderReset : Alarms were generated by PSMFC personnel while performing a site GMC. 03/16/2005 13:07 Alan_Bro A GMC was performed 3/16/2005. All transceivers were tuned. The problem child transceiver 11's sensitivity and EQ were adjusted. The sensitivity was adjusted six turns from max CCW and it is currently behaving well with signal levels in the low single digits. It reads PIT Tags at a 40% signal level. Multimon on PC1 was unresponsive to keyboard commands although it was collecting and submitting data. PC1 was rebooted and is back online. File BO305075.105 was manually archived because it had no closing time stamp due to Multimon not being able to be shut down properly. Files BO305075.205 (valid time stamps) and BO305075.206 (created during PC1 reboot) were submitted manually from PC2 to fill the gap. Both clocks are within one minute of atomic time. The v5.0 transceiver firmware upgrade was verified on all transceivers. No other problems found. 03/16/2005 08:42 darren@r 11:Overrun,15:TestTagFailure: PSMFC will be on-site today (3-16-05) for a GMC. 03/14/2005 07:59 darren@r 11:Overrun: This alarm will be investigated by PSMFC personnel on the next site visit. 03/13/2005 08:07 darren@r 11:Overrun: This alarm condition will be investigated on the next site visit. 03/05/2005 09:33 alan@ruf 15:LowExcCurrent: Clearing the TASS panel, this has been addressed. 03/04/2005 08:44 darren@r 15:LowExcCurrent: Alarm threshold will be adjusted to eleviate the file size. The threshold and level are equal thus causing large alarm amounts. 03/03/2005 09:45 troy@ree 11:LowExcCurrent,11:Overrun,11:ReaderReset,12:LowExcCurrent,12:ReaderReset ,18:ReaderReset,18:TestTagFailure,24:TestTagFailure,26:TestTagFailure,32:T estTagFailure: These alarms have been looked into. Transciever 11 has a problem below the water line. 03/02/2005 12:26 Alan_Bro The VTT for transceiver 18 was changed due to an intermittent switch on the VTT board. It will be sent to DA for repair. Transceiver 11 is in a high noise state. Swapping antennas with transceiver 12 shows that the problem is below the waterline. PTAGIS Field Operations will continue to monitor. 03/02/2005 09:14 scottl@r 24:TestTagFailure,26:TestTagFailure,32:TestTagFailure: Not sure why these TT are did not fire. They fire when prompted from PC1 or PC2 and when the transceiver is toggled from scan to standby and back to scan. 03/02/2005 08:49 scottl@r 08:LowExcCurrent,08:TestTagFailure,09:LowExcCurrent,0D:LowExcCurrent,11:Ov errun,11:ReaderReset,11:TestTagFailure,12:LowExcCurrent,12:ReaderReset: These alarms were caused by PSMFC personnel performing a GMC. 03/01/2005 12:38 Dave I re-enabled site-checking for BO3. 03/01/2005 12:31 scottl The Wa shore fish ladder watered up on Monday, Feb 28,05 at 11:15 am. The BO3 data collection computer was not sending data files at that time due to work being performed in the PIT-tag room for the BO4 site. Although data was not being submitted to PTAGIS, the data collection platform was collecting data from all transceivers in the BO3 ladder and the AFF. Transceivers are currently being tuned and calibrated. The PTTP uploaded was re-engaged at 12:30 pm 3/1/05 and files were sent to PTAGIS at that time.System clock are within 4 seconds from each other and lagging the atomic time time by 28 seconds. 02/24/2005 15:11 Alan_Bro All transceivers were flashed with version 5.0 firmware 2-24-2005. 02/18/2005 15:54 Dave Pre-season site visit. Archived previous year's data files on both PCs. Downloaded current generic db files from PTAGIS FTP server. No Internet connection available for BO3-PC1; copied updated db files from PC2 to PC1. Reset map and db files to site defaults on both PCs. Synchronized both clocks to within 1 second of atomic time. 01/31/2005 11:12 Dave The 2004 MultiMon operational configuration files have been archived on the PTAGIS FTP server at ftp://ftp.ptagis.org/multimon/Site_Configurations/2004-Config. begin:vcard fn:Dave Marvin n:Marvin;Dave org:Pacific States Marine Fisheries Commission;PIT Tag Information Systems adr;dom:;;205 SE Spokane Street, Suite 100;Portland;Oregon;97202 email;internet:Dave.Marvin@ptagis.org title:PTAGIS Systems Analyst tel;work:(503) 595-3100 tel;fax:(503) 595-3232 tel;cell:(503) 705-7849 x- mozilla-html:TRUE url:http://www.ptagis.org version:2.1 end:vcard 01/31/2005 09:36 Scott_Li E-Mail to T.Mackey at Bonneville regarding BO3 ladder repairs. During our antenna inspection this week in the Wa Shore Ladder, we had found several of the metal straps that fasten the electrical conduits to the weir walls were either loose or non existent. It's important that this is corrected in order to eliminate vibration of the conduits. The PIT-tag transceivers are very sensitive and the result of vibration is noise pick up by the transceivers. With that, I would like to make the request that new 2-Hole conduit straps replace the existing 1-Hole straps where required. If time permits, it would be advised that we have all the single hole straps replaced with 2 hole straps in order to avoid problems during the waterup periods. This would also be a time saver in the future, as we more than likely would not have to revisit the same situation year after year. This has been done at other projects and has proved to be worth the time and effort.. 01/31/2005 08:45 Scott_Li Request for repairs on BO3 ladder conduits _____ From: Scott Livingston [mailto:scottl@psmfc.org] Sent: Monday, January 31, 2005 8:35 AM To: 'tammy.m.mackey@nwp01.usace.army.mi' Cc: 'Don Warf' Subject: Wa Shore ladder repairs Hi Tammy.. During our antenna inspection this week in the Wa Shore Ladder, we had found several of the metal straps that fasten the electrical conduits to the weir walls were either loose or non existent. It's important that this is corrected in order to eliminate vibration of the conduits. The PIT-tag transceivers are very sensitive and the result of vibration is noise pick up by the transceivers. With that, I would like to make the request that new 2-Hole conduit straps replace the existing 1-Hole straps where required. If time permits, it would be advised that we have all the single hole straps replaced with 2 hole straps in order to avoid problems during the waterup periods. This would also be a time saver in the future, as we more than likely would not have to revisit the same situation year after year. This has been done at other projects and has proved to be worth the time and effort.. I will be on the project this Wednesday, 2/2 Ground hogs day! and can point out what needs to be done. Let me know how to further coordinate this effort.. Thanks Tammy.. Scott. 01/28/2005 12:36 Scott_Li An inspection of all the orifice antennas was conducted on 1/26/05. Several of the electrical conduit straps were identified as either being loose or missing. Also noted that the upstream face of some antennas has been degrading significantly. In some instances, pieces of the outer skin of the antenna had chipped off exposing the fiber matting underneath. Photographs of every antenna were taken at several different angles. Will send a request for repairs to the POC Tammy Mackey outlining what needs to be done prior to waterup of the ladder. ####End of Event Log for BO3###