EVENT LOG FOR SITE BO4 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/26/2006 07:10 scottl@r 02:TestTagFailure,04:TestTagFailure: Alarms not an issue at this time. 12/20/2006 07:18 darren@r 01:TestTagFailure,04:TestTagFailure: The ladder is currently out of service until 2-1-07. 12/14/2006 07:15 Scott_Li Correction to the last PIT event, the ladder is dewatered. Issues with the transceivers will be corrected when ladder is watered back up. 12/14/2006 07:13 scottl@r 01:TestTagFailure: Problem noted, will correct on the next site visit 12/13/2006 07:28 darren@r 01:LowExcCurrent,01:TestTagFailure,03:TestTagFailure,04:LowExcCurrent,04:O verrun: These alarms were cleared yesterday. The ladder was de-watered on Monday at around 08:00. The analog boards on the FS1001 A-B transceivers were modified by Digital Angel for the "overrun" conditions. The boards were removed at 08:30 and were replaced at 12:25. 12/12/2006 12:03 Dave I updated the Obs_Site_Dates table to reflect the termination of fish passage activity in the Washington Shore ladder. I changed the distribution list for site-checking notifications to ptoc_ken only in etc/sites. 12/12/2006 11:10 Darren The ladder was de-watered yesterday at around 08:00. PSMFC and Digital angel are on site to modify the analog boards for all the FS1001A-B transceivers. 12/12/2006 08:35 Dave The Corps reports that the Washington Shore Ladder went to orifice flow at 0945 on 09 December. 12/12/2006 07:13 troy@ree 01:LowExcCurrent,01:Overrun,02:LowExcCurrent,02:Overrun,03:Overrun,03:Test TagFailure,04:LowExcCurrent,04:Overrun,04:TestTagFailure: These alarms are most likely the result of the ladder de-watering.PSMFC personnel are on site with DA to correct the overrun problem. These other alarms will be looked into as well. 12/06/2006 07:33 darren@r 01:Overrun,02:Overrun,02:TestTagFailure,03:Overrun,03:TestTagFailure,04:Ov errun: Alarms were addressed yesterday during a site GMC. 12/05/2006 13:00 Alan A GMC was performed 12/5/2006. All transceivers were tuned. The parameters had been reset to flash defaults on transceiver 01. The current calibration, alarm threshold, report delay and unique setting were restored. No other problems found. 12/05/2006 07:18 darren@r 02:Overrun,02:TestTagFailure,03:Overrun,03:TestTagFailure: Alarms will be addressed today during a site GMC. 12/04/2006 07:30 darren@r 02:Overrun,02:TestTagFailure,03:Overrun,03:TestTagFailure: Alarms will be addressed during the next site visit. 12/03/2006 10:10 troy@ree 01:Overrun,02:Overrun,02:TestTagFailure,03:Overrun,03:TestTagFailure: These alarms will be addressed on the next site visit. 12/02/2006 11:01 troy@ree 01:Overrun,02:Overrun,02:TestTagFailure,03:TestTagFailure,04:Overrun,04:Te stTagFailure: These alarms will be addressed on the next site visit. 12/01/2006 07:43 troy@ree 01:Overrun,02:Overrun,02:TestTagFailure,03:Overrun,03:TestTagFailure,04:Ov errun,04:TestTagFailure: These will be looked into on the next site visit. 11/30/2006 10:15 troy@ree 01:Overrun,02:Overrun,02:TestTagFailure,03:Overrun,03:TestTagFailure: These alarms will be addressed on the next site visit. 11/30/2006 10:04 dlwarf@r 01:Overrun,02:Overrun,02:TestTagFailure,03:Overrun,03:TestTagFailure: Noted. 11/29/2006 07:26 troy@ree 01:Overrun,02:Overrun,02:TestTagFailure,03:Overrun,03:TestTagFailure,04:Ov errun: These alarms will be addressed on the next site visit. 11/28/2006 07:34 darren@r 01:Overrun,02:Overrun,02:TestTagFailure,04:Overrun: Site will be addressed during the next site visit. The "overrun" conditions are being addressed by Digital Angel and a modification will be performed during the week of 12-11-06 by Digital Angel. 11/27/2006 07:24 alan@ree 02:TestTagFailure,03:Overrun,04:Overrun,04:TestTagFailure: Alarms will be addressed during the next week. PSMFC is working with Digital Angel on trying to correct this and other situations. 11/26/2006 09:52 alan@ree 02:TestTagFailure,03:Overrun,04:Overrun,04:TestTagFailure: Alarms will be addressed during the next week. PSMFC is working with Digital Angel on trying to correct this and other situations. 11/25/2006 10:27 alan@ree 04:TestTagFailure: Alarms will be addressed during the next week. PSMFC is working with Digital Angel on trying to correct this and other situations. 11/23/2006 07:00 alan@ree 04:TestTagFailure: Alarms will be addressed during the next week. PSMFC is working with Digital Angel on trying to correct this and other situations. 11/20/2006 08:16 alan@ree 04:TestTagFailure: This transceiver might have detuned slightly. PTAGIS Field Operations will continue to monitor. 11/19/2006 08:33 darren@r 01:TestTagFailure: Alarm has been noted. PSMFC is monitoring to guage changes that were made to the panel heaters. 11/16/2006 18:09 scottl@r 02:LowExcCurrent,02:Overrun,02:TestTagFailure,03:Overrun,03:TestTagFailure ,04:Overrun: System was retuned and calibrated, panel heaters adjusted to 80 degrees f. 11/16/2006 07:39 darren@r 02:Overrun,03:Overrun,03:TestTagFailure,04:Overrun: Alarms will be addressed during a site GMC on Friday. 11/16/2006 07:36 darren@r 01:Overrun,01:TestTagFailure,02:Overrun,02:TestTagFailure,03:Overrun,03:Te stTagFailure,04:Overrun,04:TestTagFailure: Alarms will be addressed on Friday durign a site GMC. 11/15/2006 07:13 darren@r 01:Overrun,01:TestTagFailure,02:Overrun,02:TestTagFailure,03:Overrun,03:Te stTagFailure,04:Overrun: These alarms will be addressed on the next site visit. 11/14/2006 07:35 darren@r 02:Overrun,02:TestTagFailure,03:Overrun,03:TestTagFailure,04:Overrun,04:Te stTagFailure: Alarms will be addressed on the next site visit. The "overrun" conditions are being addressed by Digital Angel. 11/13/2006 07:27 darren@r 02:Overrun,02:TestTagFailure,03:Overrun,03:TestTagFailure,04:TestTagFailur e: These detection systems will be addressed on the next site visit. Digital Angel is working on addressing the "overrun" conditions that we are currently running into with the A-B type transceivers. 11/11/2006 10:42 scottl@r 02:Overrun,03:Overrun,03:TestTagFailure,04:TestTagFailure: Errors will be adressed on the next site visit. Will respond asap if problems persist to a point where data collection is severely compromised 11/10/2006 09:04 scottl@r 02:Overrun,02:TestTagFailure,03:Overrun,03:TestTagFailure: Errors will be corrected during the next site visit 11/09/2006 07:21 darren@r 02:Overrun,02:TestTagFailure,03:Overrun,03:TestTagFailure,04:Overrun,04:Te stTagFailure: These alarms will be cleared for future monitoring. The site was visited on Tuesday 11-7-06. The overrun condition is being addressed by Digital Angel. 11/03/2006 07:51 alan@ruf 01:TestTagFailure: Noted 11/02/2006 08:56 Alan A GMC was performed 11/1/2006. All transceivers were checked and tuned as necessary. In an effort to find the optimum operating point for the panel heaters, panel heaters 02 and 03 were lowered from 75F to 70F. Panel heater 01 was set from 75F to 70F and panel heater 04 was set from 75F to 71F which were the temperatures reported by the transceivers at the time of tuning. Endurance manager shows that the FTV and co-servers are running perfectly. The co-server2 device manager is showing a caution mark in the "Endurance Virtual Network Provider (MtcVnP) #2". With the exception of the caution signal, the system is performing flawlessly and will be troubleshot further when time allows. No other problems found. 11/02/2006 07:28 alan@ruf 01:Overrun,02:Overrun,02:TestTagFailure,03:BadOscFreq,03:Overrun,03:TestTa gFailure,04:Overrun,04:TestTagFailure: These alarms were generated by PTAGIS Field Operations personnel during a site visit. 10/31/2006 07:46 alan@ruf 01:TestTagFailure,02:Overrun,02:TestTagFailure,03:Overrun,03:TestTagFailur e,04:Overrun,04:TestTagFailure: These alarms will be investigated during a site visit this week. 10/30/2006 07:36 alan@ruf 01:TestTagFailure,03:TestTagFailure,04:Overrun,04:TestTagFailure: These alarms will be addressed on the next site visit. 10/29/2006 09:07 troy@ruf 04:TestTagFailure: These alarms will be addressed on the next site visit. 10/28/2006 08:15 troy@ruf 04:TestTagFailure: These alarms will be looked into next week during a scheduled GMC. 10/27/2006 08:45 troy@ruf 01:TestTagFailure,03:TestTagFailure,04:TestTagFailure: These alarms will be addressed on the next site visit. 10/26/2006 07:27 troy@ruf 01:TestTagFailure,04:TestTagFailure: These alarms will be addressed on the next site visit. 10/25/2006 08:08 Alan_Bro This is being reposted as the original posting yesterday didn't make it to the event logs: All primary data collection computers auto upload functions were re-engaged at 12:43 PST. Delinquent files were not manually pushed to PTAGIS. The uploader will submit files in the next 3 hrs. 10/25/2006 07:28 troy@ruf 04:TestTagFailure: This will be addressed on the next site visit. 10/24/2006 09:45 Alan_Bro Automated file loading has been disabled. 10/20/2006 07:12 scottl@r 03:Overrun: Noted 10/18/2006 16:28 Darren_C A site GMC was performed today (10-18-06). All the transceivers were checked for tuning and noise. The panel heaters that were installed yesterday were set for 75 degrees Fahrenheit and the noise reporting was turned on at an interval of every 10 minutes. PSMFC will monitoring the noise as well as the temperature that is reported by the transceiver with every status report to determine what the effects the panel heaters are having on the systems. Darren R. Chase PSMFC Systems Engineer (509) 735-2773 ext.3 darren@psmfc.org 10/18/2006 10:33 Alan_Bro Sites have been verified online. Will monitor for 13:00 load. 10/18/2006 10:21 Darren Yesterday (10-17-06) PSMFC installed panel heaters inside of the hoffman enclosures. This was done to try and eliminate the detuning of these transceivers do to what PSMFC believes to be temerature related drifting of the electronics. The doors of the transceivers were left open to help circulate the air through the transceivers. PSMFC will be monitoring the noise levels to help determine how effective this approach will be. 10/18/2006 07:19 alan@ruf 01:Overrun,01:TestTagFailure,02:TestTagFailure,03:Overrun,03:TestTagFailur e,04:TestTagFailure: These alarms will be addressed this week by PSMFC personnel. 10/17/2006 07:59 alan@ruf 01:Overrun,02:TestTagFailure,03:Overrun,03:TestTagFailure,04:TestTagFailur e: These alarms will be addressed this week by PSMFC personnel. 10/16/2006 10:20 Scott_Li Per Dean Ballinger and Sprint, there is a main break in the phone line at North Bonneville and Sprint is currently performing repairs. No estimation on when the repairs will be completed. Will post information when available. 10/16/2006 08:02 Scott_Li Called Sprint and placed trouble ticket on the DSL line. Ticket # 1325900 marked as urgent. To check status of ticket, call 877. 677.7596. All indications are the problem is the phone line coming into the facility. Called Dean B at the SMP office to check on Modem status. Will post more info as become available. 10/16/2006 07:47 darren@r 01:TestTagFailure,03:TestTagFailure,04:TestTagFailure: These alarms will be addressed this week by PSMFC personnel. 10/16/2006 07:37 Scott_Li Big Brother reports the Gateway for this site is down. Called Sprint and they confirmed that the DSL modem for Bonn cannot be seen on the network indicating the modem is either dead or needs rebooted or the copper line for the DSL connection is the problem. Called the telephone number associated with the DSL connection and get a fast busy signal. No confirmation as of yet to what the problem is. Will post more information as it becomes available. 10/15/2006 08:00 darren@r 01:TestTagFailure,03:TestTagFailure: These alarms will be addressed on the next site visit. 10/14/2006 08:30 darren@r 03:TestTagFailure: Alarms will be addressed on the next site visit. 10/12/2006 12:48 scottl Responded to the LAN outage for all Bonneville sites including the SMP facility. Isolated problem to a faulty network switch in AFF network cabinet. Moved all patch cables from this switch to an alternate network switch to repair the problem. Web access was restored at ~ 11:30 am PST. 10/12/2006 08:31 Scott_Li Big Brother reports all Bonneville data collection computers are unreachable. The gateway for this site is accessible, in the process of troubleshooting the problem. More soon. 10/12/2006 07:12 scottl@r 03:TestTagFailure: Noted 10/11/2006 07:32 darren@r 03:TestTagFailure: Alarms will addressed on Monday while PSMFC personnel are on site. 10/10/2006 07:18 darren@r 03:TestTagFailure: Alarms will be addressed on the next site visit. 10/09/2006 07:30 scottl@r 03:TestTagFailure: Noted and not an issue at this time. 10/08/2006 10:55 troy@ruf 03:TestTagFailure: This will be addressed on the next site visit. 10/07/2006 09:20 troy@ruf 03:TestTagFailure: This will be addressed on the next site visit. 10/06/2006 08:37 Dave The Corps of Engineers notified us that they opened the Cascades Island exit, picket leads, and lamprey barrier on October 5. They also installed the bulklhead at the North end of the Upstream Migrant Tunnel (UMT). Fish ascending the Cascades Island ladder now exit the ladder directly above the spillway, rather than crossing over the second powerhouse to the junction with the Washington Shore ladder. PIT-tagged fish detected at the Cascades Island ladder entrance (BO2) do not have the opportunity to be detected above the Washington Shore ladder junction at BO4. This condition will continue until both the Cascades Island and Washington Shore ladders are dewatered for scheduled maintenance this winter. 10/06/2006 07:47 troy@ruf 03:Overrun,03:TestTagFailure: These alarms will be addressed on the next site visit. 10/05/2006 07:25 troy@ruf 03:TestTagFailure: Noted 10/04/2006 16:20 troy@ruf 03:TestTagFailure: Noted. 10/01/2006 07:53 alan@ruf 01:TestTagFailure,04:TestTagFailure: Noted 09/30/2006 08:49 alan@ruf 04:TestTagFailure: This transceiver is reading PIT Tags with high efficiency. PTAGIS Field Operations will investigate on the next site visit. 09/28/2006 07:27 scottl@r 04:TestTagFailure: Problem has been Noted 09/26/2006 08:23 alan@ruf 04:TestTagFailure: No apparent reason for this alarm. The TT fired simultaneously with a status dump. 09/25/2006 16:17 Dave I created and posted a recapture file (DPM06260.BO4) to identify the 11 tags recorded to the transceivers, but not reported to MiniMon, due to the communication fault at BO4 on Sept 17-18. I also created and posted a recapture file (DPM06265.BO4) to identify the single tag not reported to MiniMon on Sept 22, due to a similar communication failure. Both of these recapture files were patterned after the DPM06176.BO4 file I generated to handle the communication fault on June 25-27. 09/23/2006 11:04 troy@ruf 04:TestTagFailure: This will be addressed on the next site visit. 09/22/2006 13:05 Scott_Li The device master drivers and firmware has been upgraded for the reasons described in the previous posting. As an additional pre-emptive measure, and to circumvent the loss of communications to the transceivers, the DM's were put on UPS power (Hmmm). The described measures should cover most scenarios during the power outages and minimize the risk of the resent occurrences. 09/22/2006 08:31 Scott_Li Another power outage occurred last night at the facility at 02:26:28 PST, power back on at 02:32.28 PST for duration of 6 min 5 sec. Unfortunately, the device masters serial ports did not resynchronize with the BO4 server platform and comms to the transceivers were lost for 4 hrs 9 mins. Manual intervention via remote access shook loose the problem and Minimon and transceivers regained connectivity at 6:48:25 PST. PTAGIS personnel are in transit to site in order to upgrade the Device Master Firmware to version 5.16 and bootloader version 2.04. This upgrade is required in order to be compatable with the 7.23 version of the DM hardware driver. After this has been completed, the DM will NOT try to load the drivers from the server platform, but rather keep the drivers resident within the DM therefore circumventing this problem in the future. This sequence of performing this upgrade is very specific and could not be accomplished via remote access. Data collection will be interrupted while this upgrade is taking place. After all activities are complete, Buffers for the 4 transceivers will be dumped and files will be submitted to PTAGIS. Will coordinate with data analyst regarding the submission of the files containing the buffered data. 09/22/2006 07:20 troy@ruf 01:TestTagFailure,03:TestTagFailure,04:TestTagFailure: Tuning will is required on 01 and 04. This will be done on the next site visit. 09/21/2006 08:21 troy@ruf 01:TestTagFailure,04:TestTagFailure: These transceivers are still reading fish but are in need of tuning. These will be addressed on the next site visit. 09/20/2006 07:41 troy@ruf 01:TestTagFailure,04:TestTagFailure: These alarms will be addressed on the next site visit. These two transceivers are reading fish but at a lower efficiency than 02 and 03. 09/18/2006 16:03 Alan_Bro Communications between the platform and the transceivers was lost from 00:32:23 PST on 9/17/2006 to 13:34:10 PST on 9/18/2006 for unknown reasons. The Device Masters were power cycled. Both co-servers and the fTv were rebooted. After communications were re-established, the buffers were downloaded into file BO406261.I1. This buffered data will be used to mitigate the gap. Files BO406261.D1, BO406261.E1, BO406261.F1, BO406261.G1, BO406261.H1 and BO406261.I1 were uploaded manually from the fTv. PTAGIS Field Operations is working to determine the cause of the failure. 09/18/2006 07:21 Alan_Bro Manually pushed BO406261.B1 to PTAGIS via remote access. 09/17/2006 11:33 scottl@r 01:TestTagFailure,02:TestTagFailure,03:TestTagFailure,04:Overrun,04:TestTa gFailure: Detection efficiencies for the site are way down, antenna 04 transceiver appears to be almost inoperable. Issues with site will be addressed tomorrow in the AM. The site did not load the .c file at the 0900 load cycle, will verify system in operating. 09/16/2006 08:12 alan@ruf 01:TestTagFailure,02:TestTagFailure,03:TestTagFailure,04:Overrun,04:TestTa gFailure: Site to be tuned on Monday. 09/15/2006 09:14 dlwarf@r 01:TestTagFailure,02:TestTagFailure,03:TestTagFailure,04:Overrun,04:TestTa gFailure: Site to be turned next week. 09/07/2006 13:16 Darren A site GMC was performed today (9-7-06). All the transceivers were checked for tuning, noise, and detection ability. No problems were found. The locker was stocked and the new site maps were installed. 09/04/2006 08:03 alan@ruf 01:TestTagFailure: No apparent reason for this alarm. PTAGIS Field Operations will investigate during a site visit this week. 08/29/2006 07:43 alan@ruf 03:TestTagFailure: This alarm could be due to a PIT Tag near the antenna during the test tag occurrence. 08/23/2006 12:57 Darren A site GMC was performed today (8-23-06). All the transceivers were checked for tuning, noise, and detection ability. No problems were found. The PC clocks are within 30 seconds of atomic time and 10 seconds of each other. 08/21/2006 07:40 darren@r 02:TestTagFailure: Failure could have been caused by the effects of a PITtag that was near the feild but not into the field. 08/18/2006 11:32 dlwarf@r 01:LowExcCurrent,01:Overrun,01:TestTagFailure,04:BadOscFreq,04:TestTagFail ure: Reseting alarms after GMC. 08/17/2006 13:30 Darren A site GMC was performed today (8-17-06). All the transceivers were checked for tuning, noise, and detection ability. The transceivers were retuned if necessary. No problems were found. 08/16/2006 07:02 scottl@r 01:TestTagFailure: A GMC is scheduled for tomorrow, 8/17 to correct minor problems 08/13/2006 08:39 alan@ree 01:TestTagFailure: This transceiver will be tuned Thursday. It is reading PIT Tags with high efficiency. 08/12/2006 10:14 alan@ree 01:TestTagFailure: This transceiver will be tuned Thursday. It is reading PIT Tags with high efficiency. 08/11/2006 08:14 dlwarf@r 01:TestTagFailure: Site to be tuned on Thursday. 08/08/2006 07:57 alan@ree 03:TestTagFailure: No apparent reason for this alarm. This transceiver appears to be in tune and is reading PIT Tags with high efficiency. PTAGIS Field Operations will continue to monitor. 08/05/2006 18:52 troy@ree 01:TestTagFailure: This will be addressed on the next site visit. 08/04/2006 08:29 dlwarf@r 01:TestTagFailure: Noted. Site is running at high efficiency. 08/03/2006 13:47 Darren A site GMC was performed today (8-3-06). All transceivers were checked for tuning, noise, and detection ability. No problems were found. 07/27/2006 07:28 troy@ree 03:TestTagFailure: This transceiver may have drifted in tune or missed it's VTT due to fish traffic. It will be looked into on the next site visit. It is currently reading with high effciencies 07/26/2006 10:30 troy@ruf 03:TestTagFailure: Noted 07/25/2006 10:13 troy@ruf 02:TestTagFailure,03:TestTagFailure: These will be looked into on the next site visit. Most likely the tuning has drifted. These antenna's are still reading PITTAGs 07/25/2006 09:05 troy@ruf 01:LowExcCurrent: The current alarm threshold was remotely lowered from 6100 to 5800. 07/24/2006 08:03 scottl@r 01:LowExcCurrent,02:TestTagFailure,03:TestTagFailure: Will recalibrate system on the next site visit. 07/20/2006 09:37 Alan_Bro The seven-minute data gap on 6/12/2006 was caused during routine platform maintenance. 07/20/2006 07:36 darren@r 01:TestTagFailure: Detection system will be addressed on the next site visit. 07/19/2006 08:46 darren@r 01:TestTagFailure,02:TestTagFailure: Alarms have been addressed. 07/18/2006 08:55 Darren The automated upload process has been re-established. The previous file were manually submitted by PSMFC personnel. 07/17/2006 15:10 Alan_Bro The auto upload process was disengaged until further notice due to the scheduled outage of the central database. The sites will not upload files until possibly Monday the 17th or 18th or when the central database resumes normal operations.. 07/17/2006 15:09 PTOC_Bot The auto upload process was disengaged until further notice due to the scheduled outage of the central database. The sites will not upload files until possibly Monday the 17th or 18th or when the central database resumes normal operations.. 07/14/2006 09:06 alan@ruf 02:TestTagFailure,04:TestTagFailure: These transceivers are reading PIT Tags well. PTAGIS Field Operations will investigate on the next site visit. 07/13/2006 07:49 alan@ruf 02:TestTagFailure: This transceiver is reading PIT Tags well. PTAGIS Field Operations will investigate on the next site visit. 07/12/2006 09:25 darren@r 02:TestTagFailure: Site will be visited today (7-12-06) to investigate this alarm. 07/11/2006 07:13 scottl@r 02:BadOscFreq,02:LowExcCurrent,02:TestTagFailure: System will be retuned either today or tomorrow. 07/10/2006 13:42 Alan A GMC was performed 7/10/2006. All transceivers were tuned. The clock on the FTV was set to within one second of atomic time. No other problems found. 07/10/2006 08:15 alan@ruf 04:TestTagFailure: This will be addressed today during a site visit 07/09/2006 11:23 troy@ruf 04:TestTagFailure: Noted. This antenna is reading at high efficiencies. 07/06/2006 07:44 scottl@r 02:LowExcCurrent: Alarms were generated during the GMC, not an issue 07/05/2006 13:30 Troy A site GMC was performed today (07/05/06). All transcievers were checked for tune and adjustments made where needed. The VE was raised as the current had dropped ~600mA's from 5700 to 5100. PSMFC will monitor for future current drops. No other problems found. 07/05/2006 07:16 scottl@r 02:LowExcCurrent: Will be addressed on the next site visit. 07/04/2006 08:29 darren@r 02:LowExcCurrent: The current alarm level will be adjusted this week while PSMFC is on site. 07/03/2006 07:52 darren@r 02:LowExcCurrent: The exciter current and the alarm level are close to each other. The level will be adjusted via PC anywhere. 07/02/2006 08:47 darren@r 02:LowExcCurrent,04:TestTagFailure: Alarms will be addressed on the next site visit. 06/28/2006 12:56 Troy A Site GMC was performed (06/28/06) All transceivers were checked for tune and adjustments made where needed. The buffers were downloaded due to a Device Master problem earlier in the week (see previous pitevent). The file was verified to have * before the buffered data then was submitted. Dave Marvin then grabbed the file. It was verified that current data was coming into the current file and the buffers were erased at the transciever at approximately 12:30 PDT. The buffered data was dumped into BO406179.E1. No other problems to report. 06/28/2006 07:18 darren@r 01:TestTagFailure,02:LowExcCurrent,04:TestTagFailure: Site will be visited today during a site GMC. 06/27/2006 09:41 Scott_Li While reviewing the CEA report, noticed that BO4 was not displayed in the report. This was odd knowing that the site should have seen at least 1 fish in the last 24 hrs. Remotely accessed the data collection platform in order to verify communications to the transceivers. The device status in Minimon indicated that the ports were open and active but was not receiving any data from the transceivers. Tried sending commands to the transceivers but got no response back. Stopped and restarted the Minimon application in an attempt re-establish communications and Minimon responded back with " Cannot Open Ports, Ports appear to be locked or used by another application" . The Port Vision utility indicated that the Device masters were online without errors. Reset DM's , still no comms to the transceivers. Restarted the entire Endurance platform, Still no comms. Manually forced a re-booted to the DMs, started the Minimon application and comms to the transceivers was restored. Will investigated why and how this happen and make necessary corrections, will also consult with the manufacturer Comtrol regarding this. The comms outage was from 02:44:36 6/25 until 06:48:15 6/27/06. The buffered data from the transceivers will be downloaded tomorrow, will coordinate with Dave M. when this takes place. 06/26/2006 06:56 Scott_Li E-Mail from Tammy.. On 24 and/or 25 June- operators will be doing switching in the evening. There will be a loss of power to the AFF, possibly the PIT tag equipment. Operators will restart the raw water booster pump. On 26 June- please see the attached clearance and email. Orifice lights, lamprey PIT tag equipment, fishway diffuser valves may all experience a loss of power. This is expected to begin at 1300 and end approximately 8 hours later. 06/25/2006 11:45 Scott_Li Site did not load at the scheduled intervals, with Darrens help due to my VPN client not responding verified data collection and Darren pushed files to PTAGIS. 06/22/2006 16:01 Alan_Bro The transceivers have all been verified as operating with "unique off" in preparation for the FDX lamprey test. 06/22/2006 07:14 scottl@r 01:TestTagFailure,04:BadOscFreq,04:Overrun,04:TestTagFailure: Problems were corrected yesterday during the GMC 06/21/2006 13:33 Alan A GMC was performed 6/21/2006. All transceivers were checked and tuned as necessary. The clock on the fTv is within 10 seconds of atomic time. No problems found. 06/20/2006 07:23 darren@r 03:TestTagFailure,04:TestTagFailure: Alarms will be addressed on the next site visit. 06/17/2006 10:27 troy@ree 03:TestTagFailure: This alarm will be addressed on the next site visit. 06/13/2006 11:58 scottl@r 01:LowExcCurrent,01:TestTagFailure,02:LowExcCurrent,02:TestTagFailure,03:L owExcCurrent,03:TestTagFailure: Alarms are generated by GMC 06/13/2006 08:25 scottl Upgraded the Device master RTS drivers to ver. 2.15.0.0. Interuption of PIT detections was minimal. Restarted endurance configuration on server, Upgrade completed. 06/12/2006 07:20 Scott_Li Antenna 01 is in chronic overrun condition. Unit will be repaired today. Will inform DA that the unit has failed and will send back to DA for failure analysis and repair. 06/12/2006 07:19 scottl@r 01:Overrun: Unit will be repaired to day. 06/11/2006 09:09 alan@ree 01:Overrun: This transceiver has a suspected bad analog board. It will hopefully be replaced this week. 06/10/2006 09:14 alan@ree 02:TestTagFailure: This transceiver might have drifted slightly out of tune. PTAGIS Field Operations will continue to monitor. 06/07/2006 08:11 alan@ree 01:LowExcCurrent: These alarms were caused by PTAGIS Field Operations personnel during a site visit. 06/05/2006 07:56 Scott_Li Transciever 01 is not detecting fish at this time. Sent DA the status and noise information for evaluation. PTAGIS personnel will be on-site tomorrow and repair the problem. In the mean time , DA has been made aware of the situation as the newly installed analog pcb's are still being evaluated. 05/31/2006 13:47 Alan A GMC was performed 5/31/2006. All transceivers were checked and tuned as necessary. The clock on the Ftv was set to within one second of atomic time. No other problems found. 05/31/2006 13:36 Scott_Li Responding to Problem with Remote Data Sites message, manually pushed files via PCA to PTAGIS with no problems. The BO4 log file indicates the recent attempt to auto upload failed due to " Error transmitting PTTP package" Auto upload failed. Looks as if this problem was just a hick-up at the right time, or wrong time. 05/31/2006 07:31 darren@r 04:Overrun: alarm was generated by PSMFC personnel. The site was checked for tuning. 05/30/2006 12:58 Scott_Li Retuned antennas 01,02,04. Hit rates and detection efficiencies were below normal, should see noticible improvement. Will monitor transceivers for drift in tuning. 05/30/2006 07:58 darren@r 03:TestTagFailure,04:TestTagFailure: Alarms have been noted and will be addressed during the next scheduled site GMC. 05/29/2006 11:25 scottl@r 02:TestTagFailure,04:TestTagFailure: Noted 05/28/2006 11:02 scottl@r 02:TestTagFailure,03:TestTagFailure,04:TestTagFailure: Transceivers may be drifting out of tune causing the TT failures.Detection efficiencies are alittle inconsistent but acceptable for the time being. 05/27/2006 11:14 scottl@r 04:TestTagFailure: Noted, Not of concern at this time. 05/26/2006 08:36 darren@r 04:TestTagFailure: Alarm will be addressed on the next site visit. 05/25/2006 07:34 scottl@r 04:TestTagFailure: Timertag hit rate was adjusted. 05/24/2006 09:33 Scott_Li Per Troy, retuned and calibrated transceiver 04 and adjusted Timer Tag hit rate to 100 percent. It appears that this transceiver drifted out of tune over night. Will monitor situation and report to DA if the problem with this transceiver continues. 05/24/2006 09:25 Scott_Li Event posting is for work done on May 23rd, 06. Replaced the analog pcb's in readers 01,02,04 with the latest revision from Digital Angel. These pcb's are considered to be the final production units. The analog pcb in reader 03 will be replaced when received from DA. Will continue to monitor the site and performance of the new boards to ensure good stability and detection efficiencies. 05/24/2006 07:15 scottl@r 01:LowExcCurrent,01:Overrun,02:LowExcCurrent,04:LowExcCurrent,04:TestTagFa ilure: Alarms were generated during the replacement of the analog PCB's. Will monitor 04 for future timer tag failures. 05/20/2006 09:34 troy@ruf 03:TestTagFailure: Noted 05/19/2006 07:34 Alan_Bro A GMC was performed 5/18/2006. All transceivers were tuned, no problems found. 05/19/2006 07:26 troy@ruf 01:TestTagFailure,03:TestTagFailure,04:TestTagFailure: Noted 05/18/2006 07:18 scottl@r 01:TestTagFailure,02:TestTagFailure,03:TestTagFailure,04:TestTagFailure: Problems will be corrected today during the GMC. 05/17/2006 07:52 troy@ruf 01:TestTagFailure,03:TestTagFailure,04:TestTagFailure: These alarms will be investigated on the next GMC. 05/16/2006 08:14 troy@ruf 01:TestTagFailure,02:TestTagFailure,04:TestTagFailure: These alarms will be addressed on the next site visit. 05/15/2006 07:13 darren@r 04:Overrun,04:TestTagFailure: Alarms will be addressed on the next site visit. 05/14/2006 10:14 alan@ruf 04:Overrun: PTAGIS Field Operations will investigate on the next site visit. 05/13/2006 11:29 alan@ruf 03:TestTagFailure,04:TestTagFailure: Noted 05/12/2006 08:48 Alan_Bro A GMC was performed 5/11/2006. All transceivers were tuned, no problems found. 05/12/2006 07:50 alan@ruf 04:Overrun: This alarm was generated by PTAGIS Field Operations personnel during a site visit. 05/11/2006 07:19 darren@r 04:TestTagFailure: This system will be checked today during a site GMC. 05/10/2006 07:21 darren@r 04:TestTagFailure: Alarm will be addressed tomorrow during site GMC's. 05/06/2006 08:49 darren@r 02:TestTagFailure,04:TestTagFailure: Alarms will be investigated on the next site visit. 04/29/2006 12:11 scottl@r 01:TestTagFailure: noted 04/28/2006 08:16 Alan_Bro A GMC was performed 4/27/2006. All transceivers were tuned. The clock on the fTv (which had drifted ahead about five minutes) was set to within one second of atomic time. No other problems found. 04/27/2006 09:55 scottl@r 01:TestTagFailure,04:TestTagFailure: A GMC will be performed today and correct the Timer Tag issues 04/26/2006 09:40 darren@r 01:TestTagFailure,04:TestTagFailure: Alarms will be addressed on the next site visit. 04/25/2006 08:16 darren@r 01:TestTagFailure,02:TestTagFailure,04:TestTagFailure: Problems will be addressed on the next site visit. 04/24/2006 08:30 darren@r 01:TestTagFailure,04:TestTagFailure: Alarms will be investigated by PSMFC personnel on the next site visit. 04/23/2006 10:17 dlwarf@r 04:TestTagFailure: Noted. 04/20/2006 08:14 alan@ruf 01:TestTagFailure,04:TestTagFailure: Noted 04/15/2006 09:18 troy@ruf 04:TestTagFailure: Noted 04/11/2006 08:03 darren@r 04:TestTagFailure: A site GMC will be performed this week. This transceiver will be addressed at that time. 04/10/2006 08:16 darren@r 04:TestTagFailure: Site will have a GMC this week, this alarm will be addressed at that time. 04/08/2006 09:17 alan@ruf 04:TestTagFailure: Alarm will be investigated on the next site visit. 04/06/2006 17:08 Scott_Li Forgot to mention that data collection and communications was restored at 3:26 PST 6APR06, 04/06/2006 17:06 Scott_Li Responded to the situation that the data collection platform was running extremely slow and remote commands could not be sent to the transceivers via the Minimon interface. Confirmed that the no data was being collected and the connectivity to the transceivers was lost. Prior to killing any processes in an attempt to understand why the applications on the FTv were slow to respond, referred to the system event viewer for errors, monitored CPU usage, Paging and memory usage on FTv interface, etc... all was normal or as expected All indications as to why this was happening point to the NISlink driver that supports the serial I/O to the multiplexers. Restarted the Ftv interface and reset the serial MUX's and comms were restored. I am aware that the current NISlink driver should be upgraded to the latest version. There are known problems with the version we are currently using. Will schedule this this upgrade ASAP to help avoid this issue from happening in the future. Will also consult with the data analyst and download buffered information from the transceivers and upload the file to PTAGIS as soon as tomorrow morning. Also, retuned transcievers today to improve timer tag consistency and fish detection. Will monitor situation.. 04/06/2006 09:16 alan@ruf 04:TestTagFailure: This alarm will be investigated at the next opportunity. 04/06/2006 09:03 Alan_Bro Manually pushed BO406096.B1 to PTAGIS via remote connection. 04/05/2006 08:52 alan@ruf 04:TestTagFailure: This alarm will be investigated on the next site visit. 04/04/2006 09:38 alan@ruf 04:TestTagFailure: This will be investigated during a site visit today. 04/01/2006 08:52 darren@r 02:TestTagFailure: This alarm will be addressed on the next site visit. 03/29/2006 08:57 darren@r 01:TestTagFailure,02:TestTagFailure,04:TestTagFailure: Site will be visited this week for site GMC. 03/28/2006 08:15 darren@r 02:TestTagFailure,04:TestTagFailure: The transceivers will be addressed on the next site visit. 03/24/2006 08:06 scottl@r 02:TestTagFailure,04:TestTagFailure: Will correct on the next visit. 03/23/2006 08:40 darren@r 02:TestTagFailure: This alarm will be addressed by PSMFC personnel sometime today. Personnel will be on site for the installation of the B2CC antenna. 03/22/2006 08:57 darren@r 02:TestTagFailure: This alarm will be addressed today (3-22-06) by PSMFC personnel. 03/21/2006 11:42 scottl@r 02:TestTagFailure,04:TestTagFailure: Timertag failures will be corrected this afternoon 03/20/2006 15:03 scottl Corrected the problem with the DSL service this morning. Problem was a poor connection at the demark. Verified that data services for all bonn sites was restored and also to the SMP office. Removed all the party lines from the DSL POT line in order to avoid any potential interuption in service. The BO4 server was restarted at 2:56 pm 3/20 in order to resyncronize co servers and Ftv and to flush the socket connections. Some hidden process was still running effecting the remote access capabilites to Ftv,CS1 and 2. 03/19/2006 10:46 Don_Warf Site is not responding. It will be investigated during a site visit on Monday. 03/19/2006 10:21 dlwarf@r 02:TestTagFailure: GMC to be performed on Monday. 03/18/2006 11:55 Don_Warf We are currently dealing with DSL problems. The modem has been rebooted and has re-established connectivity. 03/16/2006 09:58 scottl@r 02:TestTagFailure: GMC will be performed today 3/16 03/15/2006 15:26 scott The DSL data services were briefly interrupted around 10:00 AM this morning for reconfiguration and phone line consolidation purposes. Telephone service at BO1,2,3,4 all share a common party line therefore eliminating 2 unique analog lines. FYI.. The Copper to Fiber converter at BO2 is not working and a long term problem at BO1 is still being investigated. Trouble ticket was submitted to the COE with regards to these two problems.PSMFC will help facilitate repairs if necessary but replacement od the devices are the COE responsibility. As of 3:21 pm, it appears data services are up and running. 03/07/2006 10:23 Troy A GMC was performed 3/7/2006. The VTT was turned on for each transciever and the hit rate was observed. 01 was at 100% 02 was in the mid 90's. The tuning cap was tweeked to bring it up to 99%. No other adjustments were made. 03 was at 100% 04 was in the mid to low 90's. When the cover was removed to adjusted the recieve pot the hit rated dropped to single digits. The tuning cap and recieve pot were adjusted to bring the hit rate up as high as possible and the VTT voltage pot was adjusted to obtain 100%. No other problems were found. 03/07/2006 08:24 darren@r 04:TestTagFailure: PSMFC personnel will investigate this alarm today during a site GMC. 03/06/2006 08:09 troy@ruf 04:TestTagFailure: This TT failure will be addressed on the next site visit. 03/05/2006 06:58 alan@ruf 04:TestTagFailure: This will be addressed on the next site visit. 03/04/2006 12:35 alan@ruf 04:TestTagFailure: No apparent reason for this failure. PTAGIS Field Operations will continue to monitor. 03/03/2006 09:29 alan@ruf 04:TestTagFailure: Site being tuned. 03/02/2006 11:16 dlwarf@r 04:TestTagFailure: Site being tuned. 03/01/2006 15:39 Scott_Li Performed GMC and recalibrated transcievers to achieve the highest timer tag hit rate possible. 02/24/2006 08:31 troy@ruf 02:LowExcCurrent,02:TestTagFailure,03:Overrun: These alarms are most likely due to board changes being performed by DA. PSMFC will monitor for future occurances. 02/22/2006 14:39 Scott_Li Transcievers 01 and 02 were taken off line today at ~ 1230 pm for modifications to the mother board. Unclear as to how long they will be offline but will post more information as becomes available. Modifications to transceivers 03 and 04 will follow 01 and 02. 02/20/2006 09:35 dlwarf@r 02:TestTagFailure: To be addressed during tomorrows upgrades. 02/15/2006 08:37 troy@ruf 01:TestTagFailure: This will be addressed on the next site visit. 02/13/2006 08:27 scottl@r 01:TestTagFailure,04:TestTagFailure: Not of concern at this time. 02/10/2006 08:31 alan@ruf 01:TestTagFailure: No apparent reason for this for this failure, this transceiver has been reading test tags well since. PTAGIS Field Operations will continue to monitor. 02/08/2006 08:18 darren@r 01:TestTagFailure: PSMFC will be on site tomorrow. If this problem persists we will correct it at that time. 02/03/2006 18:27 Troy None of these sites are 'green' in PCA. This site and another DSL site PRO are not responsive to PCA. PRO was visited this evening and internet connectivity is good. 01/30/2006 08:55 troy@ruf 04:TestTagFailure: Noted 01/26/2006 08:32 alan@ruf 01:TestTagFailure: No apparent reason for this alarm, the transceiver appears to be in tune and reading timer tags well since. PTAGIS Field Operations will continue to monitor. 01/23/2006 17:39 Dave I reviewed the unique tags downloaded from the transceiver buffers into BO406020.E1, and confirmed that all of the codes were already recorded in the ptagis3.obs_data table, or were timer/test tags registered in the ptagis3.test_tags table. 01/20/2006 11:34 Scott_Li The data services for these sites were converted from the T-1 to DSL on 1/19/06 at 1600 hrs. A comprehensive function test was completed on all data collection computers. This included testing of the remote access PCA application to all sites. Will revise the site I/P address table on Monday 23rd, 06 to reflect the new adressing scheme. Buffers were dumped on the BO4 transcievers and the records are contained in file BO406020.E1. This was done due to recent outages incurred on the BO4 plaform. 01/12/2006 09:40 darren@r 01:TestTagFailure,02:TestTagFailure: Alarms will be addressed on the next sie visit. 01/12/2006 09:36 Alan_Bro More than likely two power events occurred between 00:00 and 03:00 1/12/2006. A message was left with site personnel requesting verification. Files BO406012.A9 and BO406012.B9 were created from .TMP files found in the data directory and submitted manually via remote access to help fill the gap. No further data exist to fill the remaining file gaps. 01/04/2006 08:25 scottl@r 04:TestTagFailure: Noted problem, will address on the next site visit 01/02/2006 12:13 Scott_Li Remoted into the FTv and found that Minimon would not connect to the device masters. Re-booted the endurance platform after several attempts to resolve the error. Devices are now connected and collecting data. It appears that 2 instances of Minimon were riunning at one time, hence the duplicate file submissions allthoug this has not been confirmed. Will dig into the problems that have occurred over the last week. Will continue to monitor for the rest of today. 01/01/2006 12:40 PTOC_Bot Annual log file initiation for BO4 #### End of Event Log for BO4 ###