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/23/2004 08:27 Troy_Hum The CAT5 cable for the platform was disconnected yesterday during preparation for the new slot antennas that will be install soon. This will be re-connected when construction is finished. 12/08/2004 12:35 Scott_Li All fiber optic cables for the Adult fish ladder transcievers have been disconnected at the FO patch in preparation for the replacement of a new 72 port unit. The Juvenile transcievers for the AFF antennas are not effected. The system will remain this way until further notice. For those reading this and who are not aware, the Bonneville Wa. shore fish ladder has been dewatered. 12/03/2004 08:28 alan@ree 22:InputSyncDetect,22:InputSyncLost,24:InputSyncLost,32:InputSyncDetect,32 :InputSyncLost,34:InputSyncLost: These alarms were created by PTAGIS Field Operations personel during a site visit. 12/02/2004 14:03 Alan_Bro All transceivers were powered down to avoid having them inadvertently placed into scan mode. 11/29/2004 08:55 Dave In response to the decommissioning of BO3 (in preparation for the installation of new slot antennas at the ladder exit), I've disabled site checking in etc/sites, changed the site status from "Green" to "Yellow" in obs_site_dates, added an explanation of the current activity to obs_site_dates, and appended a record to obs_site_interruptions. 11/29/2004 08:37 darren@r 32:InputSyncDetect,32:ReaderReset: Alarm generated by a random reader reset. 11/29/2004 08:24 Darren_C All transceivers were placed into "standby" at 08:23 this morning in preparation for the ladder de-watering. Tammy Mackey had requested that the transceivers be inactive so the ladder can be cleared of all fish during this process. PSMFC will be onsite during the installation of the new slot antennas at BO3. Darren R. Chase PSMFC Systems Engineer (509) 735-2773 ext.3 11/18/2004 08:20 alan@ruf 17:LowExcCurrent,18:LowExcCurrent: These alarms were generated by PTAGIS Field Operations personel during a site visit. 11/17/2004 13:23 scottl Performed GMC, all transcievers where retuned and calibrated. Noticed that at BO3 transcievers tune had drifted considerabley due to not having the NPO style caps on the analog boards. succesfully removed over 100 meat eating spiders from inside transceiver enclosure doors.. 11/14/2004 12:48 dlwarf@r 0E:ReaderReset: Reader reset problem. 11/11/2004 12:37 dlwarf@r 11:LowExcCurrent,11:Overrun: To be investigated on the next site visit. 11/10/2004 08:18 troy@ruf 11:LowExcCurrent,11:Overrun: This coil is still reading fish however it's tune has drifted possibly due to temperature swings. This will be addressed on the next site visit. 11/06/2004 10:45 troy@ruf 11:Overrun: This may be a tuning issue. PTOC Personnel will address this on the next site visit. 11/01/2004 11:03 Alan_Bro Multimon was stopped and restarted on both PCs in order to get the file creation schedules back on the normal schedule. 11/01/2004 09:10 darren@r 11:LowExcCurrent,11:Overrun: This detection system will be investigated and calibrated on the next site visit. 10/31/2004 09:41 alan@ruf 11:LowExcCurrent: This will be addressed on the next site visit. 10/30/2004 10:14 alan@ruf 11:LowExcCurrent,11:Overrun: This transceiver has gone into a high noise state. Ptagis field operations will investigate on the next site visit. 10/28/2004 08:16 alan@ruf 17:LowExcCurrent: This alarm was generated by PTAGIS Field Operations personel during a site visit. 10/27/2004 13:14 Alan_Bro A GMC was performed 10-27-2004. All transceivers were tuned. The doors were latched on transceivers 11 and 15 in an effort to reduce the number of overrun errors. No problems found. 10/26/2004 08:14 darren@r 11:LowExcCurrent: This alarm will be addressed by PSMFC personnel on the next site visit. 10/24/2004 08:29 darren@r 11:Overrun: This detection system will be addressed on the next site visit. 10/22/2004 08:00 darren@r 11:Overrun: this transceiver wil be addressed on the next site visit. 10/21/2004 08:06 darren@r 11:Overrun: This detection system will be serviced on the next site visit. 10/20/2004 09:03 darren@r 15:Overrun: PSMFC will check this alarm on the next site visit. The exciter report indicates that the tuning may have shifted now that the weather has become cooler. We will investigate the detection system on the next site visit. 10/20/2004 08:38 darren@r 11:Overrun: This system was checked on the last site visit and nothing was found to be out of adjsutment. The transceiver was retuned and the noise levels were acceptable. We will check the detection of this transceiver on the next site visit. 10/15/2004 08:13 alan@ruf 13:LowExcCurrent: This alarm was caused by PTAGIS Field Operations personnel during a site visit. 10/14/2004 09:16 alan@ruf 11:Overrun: This will be looked at today during a site visit. 10/14/2004 09:14 alan@ree 0B:ReaderReset: This FS1001A transceiver alarm was generated by a random reader reset. PSMFC and Digital Angel are aware of this problem. 10/13/2004 08:41 alan@ruf 11:Overrun: This antenna might have drifted out of tune but it is reading PIT Tags. PTAGIS Field Operations will investigate on the next site visit. 10/11/2004 08:51 alan@ree 11:Overrun,15:Overrun,15:TestTagFailure: Antenna 15 more than likely has problems below the water line, Antenna 11 might have drifted slightly out of tune. PTAGIS Field Operations will investigate on the next site visit. 09/29/2004 09:16 Dave I discovered last night that the Multimon log file directory was incorrectly named "C:\Multimon\Logs" on BO3-PC1. I renamed it to "C:\Multimon\Log" to match the path defined in the BO3-GEN.HW1 file. This is also consistent with the naming convention used with all other Multimon installations. Log files are now being generated in the correctly-named directory. 09/29/2004 08:14 darren@r 15:LowExcCurrent,24:LowExcCurrent,32:LowExcCurrent,32:TestTagFailure,34:Lo wExcCurrent: Alarms were generated by PSMFC personnel while performing site GMC. 09/28/2004 12:41 Alan_Bro A GMC was performed 9/28/2004. All transceivers were tuned. I adjusted the current threshold down to 2A on transceiver 15. The transceiver was showing sporadic noise but calmed down after extensive tuning. The timer tag on antenna 32 had indeed fallen out of the strap that held it in place. It was restored and the seven other timer tags were tightened. No other problems found. 09/28/2004 08:31 darren@r 15:LowExcCurrent,32:TestTagFailure: Both alarms have been acknowledged and will be addressed on the next site visit. 09/27/2004 08:05 alan@ruf 32:TestTagFailure: This timer tag will be addressed on the next site visit. The detection system is working with high efficiency. 09/26/2004 09:38 alan@ree 32:TestTagFailure: This timer tag will be addressed on the next site visit. The detection system is working with high efficiency. 09/25/2004 09:35 alan@ree 32:TestTagFailure: This timer tag will be addressed on the next site visit. The detection system is working with high efficiency. 09/24/2004 08:24 alan@ree 32:TestTagFailure: This timer tag will be addressed on the next site visit. The detection system is working with high efficiency. 09/23/2004 08:47 darren@r 32:TestTagFailure: This timer tag will be addressed on the next site visit. The detection system is working with high efficiency. 09/22/2004 09:59 alan@ruf 32:TestTagFailure: PTAGIS Field Operations will address this on the next site visit. 09/22/2004 09:57 Alan_Bro I think we have a problem with the timer tag on coil 32 at BO3, perhaps a failure or more likely the timer tag has come loose from the antenna. We will remedy this on the next site visit. It is reading PIT Tags. Investigating why the timer tag counts report doesn't show this failure I found the following: 3D9.0EEEEEE64A associated with coil 32 in the timer tag report is actually on coil 34 3D9.0EEEEEE6D2 associated with coil 22 in the timer tag report is actually on coil 24 Coils 38, 36, 34, 28, 26, and 24 are not represented in the timer tag report: http://www.ptoccentral.org/maint_op/timer_tags/counts/cf_count.04266.2 According to raw file BO304266.102, timer tag codes that appear for the particular coils are: 01 - Test aborted due to system activity 02 - 3E7.0000001D02 03 - 3E7.0000001D03 04 - 3E7.0000001D04 05 - 3E7.0000001D05 06 - 3E7.0000001D06 07 - 3E7.0000001D07 08 - 3E7.0000001D08 09 - 3E7.0000001D09 0A - 3E7.0000001D0A 0B - 3E7.0000001D0B 0C - 3E7.0000001D0C 0D - 3E7.0000001D0D 0E - 3E7.0000001D0E 0F - 3E7.0000001D0F 10 - 3E7.0000001D10 11 - 3E7.0000001D11 12 - 3E7.0000001D12 13 - 3E7.0000001D13 14 - 3E7.0000001D14 15 - 3E7.0000001D15 16 - 3E7.0000001D16 17 - 3E7.0000001D17 18 - 3E7.0000001D18 22 - 3D9.0EEEEEE1F0 24 - 3D9.0EEEEEE6D2 26 - 3D9.0EEEEEE0DA 28 - 3D9.0EEEEEE55F 32 - Test Tag Failed 34 - 3D9.0EEEEEE64A 36 - 3D9.0EEEEEE685 38 - 3D9.0EEEEEE2E3 Looking at file BO304252.105, the timer tag code for coil 32 is/was 3D9.0EEEEEE1B8 How do we fix this? Alan Brower Engineering Technician Pacific States Marine Fisheries Commission alan_brower@psmfc.org 509-735-2773 x4 09/21/2004 08:20 alan@ree 32:TestTagFailure: This timer tag will be replaced on the next site visit. The transceiver is working with good detection efficiencies. 09/21/2004 08:06 alan@ree 06:ReaderReset: This is a random reader reset on an adult transceiver. PSMFC and Digital Angel are aware of this problem. 09/19/2004 08:22 darren@r 32:TestTagFailure: This timer tag will be replaced on the next site visit. The transceiver is working with good detection efficiencies. 09/18/2004 07:39 darren@r 32:TestTagFailure: This timer tag has either fallen off the flume or has failed. PSMFC will address this on the next site visit. The transceiver status report does not indicate any problems with the detectability. 09/17/2004 20:14 darren@r 32:TestTagFailure: It appears that the timer tag is not firing, it has either fallen off the flume or has failed. Either way PSMFC will fix or replace this timer tag on the next site visit. 09/16/2004 10:47 Darren A site GMC was performed today (9-16-04). All transceivers were checked for noise and tuning. No problems were found. 09/14/2004 09:27 Dave I updated the database to BO304258.DB. This version contains 300 additional codes for AC-81. The PC clocks, which were within 11 seconds of each other and 63 seconds of atomic time, were reset to within 1 second of atomic time. 09/11/2004 09:46 dlwarf@r 15:LowExcCurrent: To be investigated. 09/01/2004 13:28 Alan A GMC was performed 9/1/2004. All transceivers were tuned. The DDS switch was turned on and 10 Action Code 254 and 10 Action Code 255 sticks were thrown on the three way gate. All sticks were diverted correctly and the DDS switch was turned off. The following are the results of the stick test. A1 20 of 20 A2 20 of 20 A3 20 of 20 A4 20 of 20 E1 10 of 10 E2 10 of 10 F1 10 of 10 F2 10 of 10 No problems found. 09/01/2004 12:50 Alan A GMC was performed 9/1/2004. All transceivers were tuned, no problems found. 08/27/2004 08:07 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,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: Alarms caused by brief power outage. 08/23/2004 08:47 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 were caused by a power outage 08/20/2004 13:42 Darren A site GMC was performed today (8-20-04). All transceivers were checked for noise and tuning. No problems were found. 08/20/2004 09:01 Troy While responding to the messages that BO3 had not loaded it was found via PCA that the pttp client was not active on PC1. I started the pttp client and reviewed the files that had not been sent. The pttp client was terminated during the 1300 hour on August 19th. I checked the file load status (on Scott's suggestion) to ensure that duplicate files were not going to sent in and then manually pushed the files and left the pttp client running. 08/19/2004 14:56 Dave Updated the database to BO304232.DB. This version contains an additional 19,978 tag codes for Yakima River Coho. These were appended to the existing 950k+ "yellow light" records in AC-82 (UI-YLO: "OK to tag"). The PC clocks, which were within 25 seconds of each other and 150 seconds of atomic time, were reset to within one second of atomic time. 08/11/2004 08:46 Scott_Li The recent entry with regards to the timertag repair for antenna 01 was not at bo3 but rather bo1.,. 08/11/2004 08:12 Scott_Li The Timertag problem will be corrected later this week if not this afternoon. Antenna 01 is detecting pit tags. 07/29/2004 08:29 troy@ree 02:LowExcCurrent,08:LowExcCurrent,0C:LowExcCurrent,0F:LowExcCurrent,10:Low ExcCurrent,13:LowExcCurrent,16:LowExcCurrent,18:LowExcCurrent: These alarms were caused during a site GMC. 07/27/2004 09:52 Darren A site GMC was performed today (7-27-04). All transceivers were checked for noise and tuning. No problems were found. The transceivers were tuned for peak sensitivity and low noise for HDX vs. FDX test that PSMFC will be assisting Earl Prentice (NOAA) with today. 07/26/2004 08:14 alan@ruf 34:InputSyncDetect,34:ReaderReset: This alarm was generated by a random reader reset. PSMFC and Destron are aware of this problem. 07/19/2004 08:16 alan@ree 0F:ReaderReset: This alarm is a random reader reset on an adult transceiver. PSMFC and Destron are aware of this problem. 07/16/2004 08:12 alan@ree 17:LowExcCurrent: This alarm was generated by PTAGIS Kennewick personel during a site visit. 07/15/2004 13:09 Alan A GMC was performed 7/15/2004. All transceivers were tuned, no problems found. 07/09/2004 08:15 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 were caused by a power outage. 07/07/2004 08:10 darren@r 18:ReaderReset: This alarm is caused by a random reader reset. This problem is generally seen on the Juvenile system, but we do occasionally see it occur in the adult system. 07/06/2004 08:11 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,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: Alarms caused by a brief, < than 2 minute power outage. 07/02/2004 07:52 darren@r 11:LowExcCurrent,17:LowExcCurrent,32:LowExcCurrent,32:TestTagFailure,34:Lo wExcCurrent: All alarms were generated by PSMFC personnel while performing a site GMC. 07/01/2004 13:53 Darren A site GMC was performed today (7-1-04). All transceivers were checked for tuning and noise. the timer tag on coil 32 was re-attached and fired. All the timer tags in the AFF were tightened to prevent them from falling off. No other problems were found. 06/30/2004 08:23 darren@r 32:InputSyncDetect,32:InputSyncLost,32:TestTagFailure,36:InputSyncDetect,3 6:InputSyncLost,38:ReaderReset: It appears that the timer tag on coil 32 has fallen off the coil. The other alarms are caused by a random reader reset. I will address the timer tag problem tomorrow during a site GMC. 06/29/2004 09:04 alan@ree 32:TestTagFailure: There is indeed a problem with the test tag for this coil, although it does not show up in the timer tag reports (that will be addressed separately). This coil is reading fish currently with 100% efficiency. PTAGIS Kennewick will be on site Thursday and will investigate the problem then. 06/26/2004 08:14 darren@r 11:LowExcCurrent,26:TestTagFailure: The test tag failure was rectified during a site GMC yesterday (6-25-04). I will check on the low exciter current alarm via PC Anywhere. 06/25/2004 10:43 scott Reattached TimerTag to antenna on Coil 26, Hit rate at 100 %. Performed GMC,Checked tune and recal'd as necessary. System clocks are with 5 seconds of each other. 06/25/2004 08:14 troy@ruf 26:TestTagFailure: This will be addressed during a site GMC today. 06/24/2004 08:14 darren@r 24:InputSyncDetect,24:ReaderReset,26:TestTagFailure: The alarm on coil 24 is due to a random reader reset. This is an ongoing phenomenon of the FS1001 (juvenile) transceiver. The test tag failure on coil 26 will be addressed tomorrow during the site GMC. The transceiver exciter report shows that the transceiver is in tune and reading efficiently. 06/22/2004 08:38 alan@ruf 26:TestTagFailure: This will be addressed by PTAGIS Kennewick this week. This coil appears to be in tune and is reading pittags with a high efficiency. 06/18/2004 17:00 Dave Updated database and map files to BO304170.DB and BO304170.MAP, respectively. The map file contains a new AC-101 "Red Light" diversion definition for COE Kelts (RWKELT). The database contains 629 codes for AC-101. The database was also reduced by 157,029 tags for AC-82, per Steve Lee. The PC clocks, which had been within 10 seconds of each other and 53 seconds of atomic time, are now both within 2 seconds of atomic time. 06/16/2004 12:40 Alan A GMC was performed 6/16/2004. All transceivers were tuned, no problems found. 06/08/2004 11:45 Troy A site GMC was performed today. All transceivers were checked for tune and no problems were found. 06/07/2004 11:45 Dave Updated database and map to BO304159.DB and BO304159.MAP, respectively, to include a RED LIGHT signal for 65 tag codes in the AC-92 group (UI-EST - Tagged fish released in the Col. estuary). PC clocks are with 5 seconds of each other and 26 seconds of atomic time. 06/06/2004 10:14 darren@r 0B:LowExcCurrent,11:LowExcCurrent: Alarms were generated by PSMFC personnel while performing site GMC. 06/04/2004 11:12 Troy A site GMC was performed today. All transceivers were checked for tune and no problems were found. 05/28/2004 17:32 Dave Updated map and database files to BO304149.MAP and BO304149.DB, respectively. The map file references four additional Action Codes (88-91), and the database contains approximately 900k additional tag codes. Installation of the database, which now contains almost 2.495M records, was complicated on BO3-PC1 because the Multimon PIF property settings on the Memory, Screen, and Misc tabs had been altered at some previous date. Specifically, the Memory settings had been changed from "Auto", and restricted to 16Mb of both EMS and XMS memory. All Multimon PIF properties on BO3-PC1 now match the standard properties already configured on BO3-PC2. During my diagnostics, I also altered the CONFIG.SYS file on BO3-PC1 to match that on BO3-PC2. Both PCs are functioning correctly, and support the ~2.5M records in BO304149.DB. The PC clocks, which had been within 5 seconds of each other and 183 seconds of atomic time, are now within 1 second of each other and atomic time. 05/28/2004 08:17 darren@r 17:LowExcCurrent,17:ReaderReset: Alarm was generated by PSMFC personnel while performing a site GMC. 05/27/2004 12:20 Darren A site GMC was performed. All transceivers were checked for noise and tuning. No problems were found. 05/20/2004 08:16 darren@r 03:LowExcCurrent,03:Overrun,04:LowExcCurrent,11:LowExcCurrent,15:LowExcCur rent,15:TestTagFailure,17:BadExcFreq,17:BadOscFreq,17:LowExcCurrent,17:Rea derReset,18:BadExcFreq,18:BadOscFreq,18:LowExcCurrent: Alarms were generated by PSMFC personnel during a site GMC. 05/19/2004 15:54 Scott_Li Performed GMC this afternoon, all transceivers were checked for tune and calibration. Coil 15 was reporting excessive noise alarms and overrun errors.. After retuning and calibration had failed to eliminate the noise, the antenna cable was swapped with the adjacent antenna, coil 16 and the noise was reduced to a steady 3-5 percent and stable.. It appears that the problems lye within the cable and or the connection at the antenna...Turned noise reports on for coil 15 and will evaluate further tomorrow... 05/15/2004 10:03 dlwarf@r 0E:LowExcCurrent,11:LowExcCurrent: Tuning generated errors. 05/14/2004 12:51 Alan A GMC was performed 5/14/2004. All transceivers were tuned. PC2 was taken out of data collection to reset it's clock. Both clocks are now within 1 second of each other and 30 seconds of atomic time. No problems found. 05/04/2004 09:06 darren@r 11:LowExcCurrent: alarm was generated by PSMFC personnel while performing routine maintenance. 05/04/2004 09:05 darren@r 17:LowExcCurrent: Alarm was generated by PSMFC personnel while performing routine maintenance. 05/03/2004 16:26 Darren the site was visited for a GMC. All transceivers were tuned and checked for noise. We removed the listening post (bx2). No problems were found. 05/01/2004 08:18 darren@r 32:InputSyncDetect,32:ReaderReset: Alarm was generated by arandom reader reset. 04/26/2004 14:22 Dave I updated the database and map file to BO304117.DB and BO304117.MAP, respectively. The new map file contains additional definitions for AC-86 (UI-IFG: IDFG Chinook acceptable for radio-tagging) and AC-87 (UI-STH: steelhead previously tagged by UI in 2002-2003). The database contains 22,517 tags for AC-86; detection of these tags will trigger the "Yellow" light. The database contains 1908 tags for AC-87; detection of these tags will trigger the "Red" light. The database was also updated with 874 new tags added to the AC-82 (UI-YLO) group. The PC clocks are within 7 seconds of each other and 48 seconds of atomic time. 04/26/2004 08:40 alan@ruf 15:Overrun: This transceiver reported some noise about the same time as the overrun. All other indications are that this transeiver is working properly. PTAGIS Kennewick will continue to monitor. 04/16/2004 08:06 alan@ruf 15:Overrun: Noise events were occurring at about the time of this alarm. We will check this out on the next site visit. 04/10/2004 07:54 alan@ruf 05:ReaderReset,15:Overrun: This alarm appears to be a random reader reset on an adult transceiver. PTAGIS Kennewick will continue to monitor. 04/06/2004 18:49 Dave I updated the Multimon database and map files to BO304097.DB and BO304097.MAP, respectively. These files have definitions for five new SbyC Action Codes, all related to the University of Idaho's research. I also updated the IGNOR.TAG file to include the coil IDs, and replaced the archaic BO3-GEN.DB file with the new standard STICKTAG.DB database file. The clocks on the PCs were reset within 2 seconds of each other and atomic time. 04/06/2004 08:49 troy A site GMC was performed. No problems were found. PC1 and PC2's Multimon applications were taken out of data collection and then restarted around 12:20 PST. 04/06/2004 08:45 darren@r 17:LowExcCurrent: Alarm was generated by PSMFC personnel while performing site GMC's. 04/05/2004 18:25 Dave I pcA'd into BO3-PC1, and verified that data file creation had been re- synchronized to 3-hour increments starting at midnight. Also discovered that files on PC1 were being archived into the PTTP Uploader archive directory, rather than Multimon's archive directory. I corrected this, and moved all recent archived files in Multimon's archive. I also enabled the checkbox in PTTP Uploader to synchronize uploads to the hour (and delay by 120 seconds, which was already selected). I was unable to pcA into BO3-PC2. 04/05/2004 08:17 darren@r 15:Overrun: This alarm will be addressed today during site GMC. 04/02/2004 09:01 darren@r 32:InputSyncDetect,32:ReaderReset: This transceiver will be addressed on Monday on the next site visit. 03/17/2004 08:45 alan@ruf 08:ReaderReset,09:LowExcCurrent,0C:ReaderReset: These alarms were caused by Kennewick PTAGIS personnel during a GMC. 03/15/2004 16:39 scott Correction to last Pitevent, the production UpLoader Version was NOT 1.1.5. but rather 1.1.6. 03/15/2004 16:00 scott These 3 site interrogation platforms were upgraded this afternoon to the the new production release Minimon 1.4.4 with exception of bo3 that recieved the new release UpLoader 1.1.5. The new file extention identifier option was also implimented on MiniMon platforms,i.e., primary pc identified as .X1 and the back up pc as .X2. The SOP that was written to back fill file gaps when PC's are taken offline was also tested and followed during this upgrade. 03/04/2004 09:04 darren@r 11:LowExcCurrent: This alarm was generated by PSMFC personnel performing a site GMC. The GMC was completed around 13:30 on Tuesday 3-2-04. 03/04/2004 08:59 darren@r 15:LowExcCurrent: The exciter reportindicates that the exciter current did drop to equal the current alarm threshold but has risen back up to 3.2A and should not trip this alarm. We will monitor for this alarm between site GMC visits. 03/04/2004 08:50 darren@r 14:LowExcCurrent: Transceiver was addressed on the site visitwhich occurred on the same day. There has not been any alarms since the site GMC. 02/28/2004 19:07 troy@ruf 0D:LowExcCurrent: This tranciever will be addressed on the next site visit. 02/21/2004 08:36 darren@r 0D:LowExcCurrent: This alarmed may have been caused by PTOC personnel while performing site GMC. I will monitor for future alarms. 02/20/2004 12:42 Alan A GMC was performed 2/20/2004. All transceivers were tuned. No problems found. 02/19/2004 08:10 darren@r 01:LowExcCurrent,01:ReaderReset: This transceiver was re-installed on 2- 13-04. It was retuned for the best reading capabilities possible. 02/13/2004 13:23 Scott_Li Antenna 01 was returned to service and tuned at ~12:30 pst. all other transceivers were checked for tune and are functioning. The light box that signals researchers that a pittag fish has been detected was also reconnected to the data collection platform and tested for functionality. 02/09/2004 12:30 scott_li Transceiver for antennae 01 was removed for use at a listening station for the Slot antennae project on Friday , Feb. 6th @ ~ 1100 am pst. The unit will be replaced on the next site visit possably scheduled for Thursday or Friday of this week. 02/07/2004 08:15 D._Chase Two (2) listening antenna's were installed at the serpentine weirs at the Washington ladder (BX2) and Bradford Island (BX1). We are noise testing for the upcoming slotted weir antenna's. We finished the installation and verified communications yesterday afternoon. 02/06/2004 11:38 Darren A site GMC was performed. All transceivers were checked for tune and noise. No problems were found. 02/06/2004 09:03 Dave The Cascade Islands and Washington Shore fish ladders were restored to full operation on January 20, after being taken to "orifice flow" on January 16. PIT tag detection operations were not suspended while the ladders were at orifice flow. Tammy Mackey informed me that fish already in the ladders on January 16 were expected to exit, but that "new" fish were not expected to enter the ladders until flows were restored on January 20. 01/19/2004 09:21 darren@r 03:LowExcCurrent: 03:LowExcCurrent: Parameters were changed at 10:51:37 to stop the current alarm alert. This site will have to be revisited for tuning when the operations return to normal. 01/19/2004 09:21 darren@r 03:LowExcCurrent: Parameters were changed at 10:51:37 to stop the current alarm alert. This site will have to be revisited for tuning when the operations return to normal. 01/18/2004 09:29 darren@r 03:LowExcCurrent: This alarm could be the results of the facilities operating status. I will PCA into the site and adjsut the current alarm level so the files will not be large. This site may have to visited to retune all ladders after the operations have been returned to normal. 01/17/2004 09:40 darren@r 03:LowExcCurrent,05:LowExcCurrent,05:TestTagFailure: This site is also in emergency operations as per COE personnel. 01/16/2004 15:33 Scott_Li Per Tammy Mackey Due to a reported oil slick upriver of Bonneville Dam, we have taken the following actions to prevent contamination of our fishways. All juvenile bypass systems remain out of service. The AFF is out of service. All adult fishways are going to orifice flow and all AWS valves are closed. Bays 1 and 18 are closed. PH1 ice and trash sluiceway is closed. Fishways will remain at orifice flow with the exit leads such that water will come from underwater rather than the surface. Since Bradford Island is going to orifice flow on Sunday, we will leave the ladder at orifice flow all weekend. Fisheries will come in on Saturday to check ladder conditions at Washington Shore/Cascades Island to determine whether or not it is safe to bring the ladder back to full operation. Please be patient. More details will follow as soon as possible. Thank you, Tammy 01/15/2004 08:17 darren@r 05:LowExcCurrent: Site and transceiver have since been tuned. The tuning was completed on 1-14-04. Site is ready for 2004 season. 01/14/2004 14:29 Darren Site is tuned and platform is ready for the 2004 season. 01/14/2004 11:39 Darren Both sites were watered up yesterday at roughly 16:00. PTOC personnel will be onsite to tune all transceivers for the upcoming 2004 season. 01/12/2004 16:03 Alan I moved all data files with a Julian date of 03365 and older to c:\multimon\2003 data on both PC1 and PC2. I also set the time on both PCs to within 1 second of atomic time. PC1 was out of data collection for about two minutes during this process, but no data was lost as there is no water in the facility at this time. 01/12/2004 14:35 Darren I was informed today (1-12-04)by Tammy Mackey that both site were not watered up, as was previously thought, last week due to the inclement weather. They are scheduled to be watered up tomorrow (1-13-04) PTOC personnel will be on site on Wednesday (1-14-04) to tune transcievers and setup the Data Collection Platform for the upcoming season. 01/12/2004 10:57 Carter_S New Configuration (110) added to remove 400kHz monitors. BO3 - Bonneville WA Shore Ladder/AFF --------------------------------------------------------------------- - Current Configuration -> Seq Nbr: 110 Main? Y, Active? Y, Parallel_A_B? A, Poll? N Current Configuration: Seq Nbr 110 -> 15-Dec-03 To Present Comment: Removed 400kHz monitors. Monitors in Sort_Str sequence: Nbr 1 -> WEIR 59 Mon_Ctgry_Str: LAD, Entry_Y_N? Y, Exit_Y_N? Y, Sort_Str: 1 (Coil,Controller): (01,01) (02,02) Nbr 10 -> WEIR 36 Mon_Ctgry_Str: LAD, Entry_Y_N? Y, Exit_Y_N? Y, Sort_Str: 10 (Coil,Controller): (13,13) (14,14) Nbr 11 -> WEIR 35 Mon_Ctgry_Str: LAD, Entry_Y_N? Y, Exit_Y_N? Y, Sort_Str: 11 (Coil,Controller): (15,15) (16,16) Nbr 12 -> WEIR 34 Mon_Ctgry_Str: LAD, Entry_Y_N? Y, Exit_Y_N? Y, Sort_Str: 12 (Coil,Controller): (17,17) (18,18) Nbr 13 -> AFF NORTH FLUME [ISO 134KHZ] Mon_Ctgry_Str: AFF, Entry_Y_N? Y, Exit_Y_N? Y, Sort_Str: 13 (Coil,Controller): (22,22) (24,18) (26,1D) (28,1C) Nbr 15 -> AFF SOUTH FLUME [ISO 134KHZ] Mon_Ctgry_Str: AFF, Entry_Y_N? Y, Exit_Y_N? Y, Sort_Str: 15 (Coil,Controller): (32,32) (34,1A) (36,1E) (38,10) Nbr 2 -> WEIR 58 Mon_Ctgry_Str: LAD, Entry_Y_N? Y, Exit_Y_N? Y, Sort_Str: 2 (Coil,Controller): (03,03) (04,04) Nbr 3 -> WEIR 57 Mon_Ctgry_Str: LAD, Entry_Y_N? Y, Exit_Y_N? Y, Sort_Str: 3 (Coil,Controller): (05,05) (06,06) Nbr 4 -> WEIR 56 Mon_Ctgry_Str: LAD, Entry_Y_N? Y, Exit_Y_N? Y, Sort_Str: 4 (Coil,Controller): (07,07) (08,08) Nbr 5 -> WEIR 55 Mon_Ctgry_Str: LAD, Entry_Y_N? Y, Exit_Y_N? Y, Sort_Str: 5 (Coil,Controller): (09,09) (0A,0A) Nbr 6 -> WEIR 54 Mon_Ctgry_Str: LAD, Entry_Y_N? Y, Exit_Y_N? Y, Sort_Str: 6 (Coil,Controller): (0B,0B) (0C,0C) Nbr 7 -> WEIR 53 Mon_Ctgry_Str: LAD, Entry_Y_N? Y, Exit_Y_N? Y, Sort_Str: 7 (Coil,Controller): (0D,0D) (0E,0E) Nbr 8 -> WEIR 52 Mon_Ctgry_Str: LAD, Entry_Y_N? Y, Exit_Y_N? Y, Sort_Str: 8 (Coil,Controller): (0F,0F) (10,10) Nbr 9 -> WEIR 37 Mon_Ctgry_Str: LAD, Entry_Y_N? Y, Exit_Y_N? Y, Sort_Str: 9 (Coil,Controller): (11,11) (12,12) 01/12/2004 09:24 Darren_C Both sites are reporting that there is problems with the firing of the timer tags. At BO2 (Cascade Island) we are seeing an abundance of noise because the transceivers have not been tuned since the ladder watered up either Thursday or Friday of last week. At BO3 (Washington Shore) there are only a few that have not fired because of the tuning of the transceivers, the timer tag report is showing quite a few timer tags that are no longer in service at this facility, all 400 Khz equipment has been removed and so should the subsequent timer tags. We will be on site at both places today to tune and check all transceivers and timer tags. 01/09/2004 08:32 darren@r 05:LowExcCurrent,0A:LowExcCurrent,15:LowExcCurrent: Site was due to have water on Monday the 5th, but due to inclement weather they postponed this activity until later this week. I have not been able to confirm this with Tammy Mackey. PTOC personnel will be on site 1-12-04 for tuning of all transceivers. 01/06/2004 08:20 darren@r 0A:LowExcCurrent,15:LowExcCurrent: Site is still currently not watered up. It is scheduled to be watered up on Wednesday or Thursday. I received an e-mail from Tammy Mackey stating this fact on Monday. 01/05/2004 08:21 darren@r 05:LowExcCurrent,0A:LowExcCurrent,15:LowExcCurrent: Site will have water in the ladder today. PSMFC personnel will be on site for tuning and getting the platform ready fro the upcoming 2004 season. 01/03/2004 11:40 dlwarf@r 04:LowExcCurrent,05:LowExcCurrent,05:TestTagFailure,06:LowExcCurrent,08:Lo wExcCurrent,0A:LowExcCurrent,0C:LowExcCurrent,11:LowExcCurrent,12:LowExcCu rrent,14:LowExcCurrent,15:LowExcCurrent,16:LowExcCurrent,18:LowExcCurrent: Site to be fine tuned on the next visit. 12/30/2003 22:56 Darren Both sites have had the transceivers powered on with no water in the ladder. The ladders are to be watered up on Jan. 5th. PTOC personnel will be on site shortly after to fine tune all transceivers and adjust the Data Collection Platforms for the upcoming 2004 season. 12/12/2003 10:04 darren@r 04:LowExcCurrent,05:LowExcCurrent,0A:LowExcCurrent: These transceiver were powered down at 08:39 on 12-10-03. The ladder has been inspected and all fixes have been turned over to COE personnel for rework. The ladder schedule has changed and it will not be watered up until 1-5-04, this is per Tammy Mackey. 12/11/2003 15:06 Scott_Li All 400 Khz PIT-tag equipment has been eliminated in the AFF and converted to the ISO 134.2 Khz. The nessesary revised config files were uploaded to the FTP server in the appropriate folder.The ladder is de-watered and will remain that way until Dec. 22 ,03. Data collection platform will remain collecting diagnostic information from the AFF coils even while the site is inactive. The ladder antennas will remain powered off until further notice. More on this conversion topic tomorrow. 12/10/2003 08:59 Darren On Monday 12-8-03 the ladder was taken to an oriface flow at 08:00. On 12-10-03 at 08:39 all transceivers to the ladder were turned off by request of the Bonneville COE personnel. The ladder is being de-watered and will be inspected by PSMFC PTOC staff today 12-10-03. 01/01/2004 12:07 Dave Initialized new event log for 2004. 2003 event log has been archived. ####End of Event Log for BO3###