EVENT LOG FOR SITE BWL 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 ---------- ----- -------- ---------------------------------------------------- 01/07/2002 08:40 Carter_S BWL has been shut down since 12/11/01 due to technical concerns regarding the leaky antennas. The site will be brought back on-line after concensus of the APTOC. 12/30/2001 22:28 darren@p 2A:ExcessiveNoise,2A:TestTagFailure,2B:ExcessiveNoise,2B:TestTagFailure,3A :ExcessiveNoise,3A:TestTagFailure,3B:ExcessiveNoise,3B:TestTagFailure,4A:E xcessiveNoise,4A:TestTagFailure,4B:ExcessiveNoise,4B:TestTagFailure,5A:Tes tTagFailure,6A:ExcessiveNoise,6A:TestTagFailure,6B:ExcessiveNoise,6B:TestT agFailure,7A:ExcessiveNoise,7A:TestTagFailure,7B:ExcessiveNoise,8B:TestTag Failure,9A:ExcessiveNoise,9A:TestTagFailure,AA:TestTagFailure,AB:TestTagFa ilure,BA:TestTagFailure,BB:TestTagFailure,CA:TestTagFailure,CB:TestTagFail ure,DA:TestTagFailure,DB:ExcessiveNoise,DB:TestTagFailure: All the test tags were removed when coils 7B and DB were removed for testing. This site will be completly upgraded when the ladder is dewatered. 12/13/2001 13:51 Dave I identified four "missing" files from BWL in 2001: BWL01097.B, 089.E., 89.G, and 114.O. Of these four, I was able to locate and submit one from BWL-PC1: BWL01097.B. 12/13/2001 13:33 Dave At ~1:10pm today (12/13/01) I stopped MiniMon, transferred the outstanding data file, and then closed MiniMon on BWL-PC1. I also disabled polling for BWL data. I did NOT modify any actions on the BWL Multimon (PC2) machine. 12/12/2001 12:48 Don_Warf All transceivers were shut down at 12:50 yesterday due to technical concerns. They will remain down until further notice. 12/02/2001 17:56 darren@p 2B:ExcessiveNoise,3A:ExcessiveNoise,3A:TestTagFailure,3B:BadExcFreq,3B:Bad OscFreq,3B:ExcessiveNoise,3B:LowExcCurrent,3B:TestTagFailure,4A:ExcessiveN oise,4A:TestTagFailure,4B:TestTagFailure,5A:ExcessiveNoise,5A:TestTagFailu re,6A:ExcessiveNoise,6A:TestTagFailure,6B:ExcessiveNoise,6B:TestTagFailure ,7A:ExcessiveNoise,7A:TestTagFailure,7B:ExcessiveNoise,7B:TestTagFailure,8 A:ExcessiveNoise,8B:ExcessiveNoise,8B:TestTagFailure,9A:BadExcFreq,9A:BadO scFreq,9A:LowExcCurrent,9A:TestTagFailure,9B:BadExcFreq,9B:BadOscFreq,9B:L owExcCurrent,9B:TestTagFailure,AA:ExcessiveNoise,AA:TestTagFailure,AB:Test TagFailure,BA:TestTagFailure,CA:TestTagFailure,CB:ExcessiveNoise,CB:TestTa gFailure,DA:ExcessiveNoise,DA:TestTagFailure,DB:ExcessiveNoise,DB:TestTagF ailure: All alrms that were generated on 11-26-01 were caused by PTOC and NMFS personnel on site doing test. All test failure alarms are real and will be addressed on the next water-down period. Any other alarms will be looked at during the week of 12-3-01 at which time there will be personnel from PSMFC, NMFS, and Destron-fearing on site. 11/29/2001 15:07 Scott_Li The PTTP client has been restarted on these computers. 11/27/2001 09:08 Scott_Li The PTTP client has been disabled until Thursday , Nov. 29 01. 11/26/2001 08:07 darren@p 4B:TestTagFailure,6A:TestTagFailure,7A:TestTagFailure,BA:ExcessiveNoise,DB :ExcessiveNoise: The Timer tag failures have been occuring for some time and will be addressed during the Waterdown period for the Washington ladder. The excessive noise on coil DB has been apparent for a while and it is the opinion of Sean Casey that there may a Capacitor problem. This situation will also be addressed during Waterdown. 11/25/2001 17:45 darren@p 2A:ExcessiveNoise,2B:ExcessiveNoise,2B:TestTagFailure,3A:ExcessiveNoise,3A :TestTagFailure,3B:ExcessiveNoise,4A:ExcessiveNoise,4A:TestTagFailure,4B:E xcessiveNoise,4B:TestTagFailure,5A:ExcessiveNoise,5A:TestTagFailure,5B:Exc essiveNoise,5B:TestTagFailure,6A:ExcessiveNoise,6A:TestTagFailure,6B:Exces siveNoise,6B:TestTagFailure,7A:BadExcFreq,7A:BadOscFreq,7A:ExcessiveNoise, 7A:LowExcCurrent,7A:TestTagFailure,7B:ExcessiveNoise,7B:TestTagFailure,8A: ExcessiveNoise,8B:ExcessiveNoise,8B:LowExcCurrent,8B:TestTagFailure,9A:Exc essiveNoise,9A:LowExcCurrent,9A:TestTagFailure,9B:TestTagFailure,AA:Excess iveNoise,AA:TestTagFailure,AB:ExcessiveNoise,AB:TestTagFailure,BA:Excessiv eNoise,BA:TestTagFailure,CA:ExcessiveNoise,CA:TestTagFailure,CB:ExcessiveN oise,CB:TestTagFailure,DA:ExcessiveNoise,DA:TestTagFailure,DB:ExcessiveNoi se,DB:TestTagFailure: I believe most of these alarms were generated by PTOC personnel while they were performing tests on most of the coils. I don't know why these were not cleared when I posted to the event log yesterday. 11/19/2001 11:46 darren@p 2A:ExcessiveNoise,4B:TestTagFailure,6A:TestTagFailure,7A:TestTagFailure,9A :ExcessiveNoise,DB:ExcessiveNoise: The test tag failures are ligitimate. They will be reapired this upcoming de-watering time. The noise problems for 9A, and 2A will be look at today by PTOC personnel. Coil DB is a known noise problem and will also be addressed during the next de-watering work schedule. 11/16/2001 13:31 darren@p 2A:ExcessiveNoise,2B:ExcessiveNoise,3A:ExcessiveNoise,3B:ExcessiveNoise,4A :ExcessiveNoise,4B:ExcessiveNoise,4B:TestTagFailure,5A:ExcessiveNoise,5B:E xcessiveNoise,6A:TestTagFailure,6B:ExcessiveNoise,7A:ExcessiveNoise,7A:Low ExcCurrent,7A:TestTagFailure,7B:ExcessiveNoise,7B:LowExcCurrent,7B:TestTag Failure,8A:ExcessiveNoise,8B:ExcessiveNoise,9A:ExcessiveNoise,DA:Excessive Noise,DB:ExcessiveNoise: Most alarms were generated by NMFS personnel performing maintenance on transceivers. There appears to be some problems with coils 9A,7B,4B and 3A. PSMFC was contacted by Sean Casey from Destron-Fearing on 11-15-01 about potential failures on those coils. Bruce Johnassen from NMFS traveled to the site yesterday (11-15-01) and performed various tests and tuning on these coils but it appears that there may be problems with the antennas. Scott and I will travel to the site on Monday (11-19-01) to run some tests and collect our findings. 11/15/2001 09:38 darren@p 3A:ExcessiveNoise,4B:TestTagFailure,5A:ExcessiveNoise,6A:TestTagFailure,7A :TestTagFailure,7B:LowExcCurrent,9A:ExcessiveNoise,9A:TestTagFailure,DB:Ex cessiveNoise: The alarms are being monitored and will be addressed on the upcoming de-watering of the ladder. The excessive noise on coil 9A has been there all year, it is caused by the 13KV line that is directly underneath the coil. all other alrms are randomly being generated and will be addressed at the time mentioned above. 11/07/2001 08:28 darren@p 3A:ExcessiveNoise,4B:TestTagFailure,6A:TestTagFailure,7A:TestTagFailure,9A :ExcessiveNoise,9A:TestTagFailure,DB:ExcessiveNoise: We will monitor for further excessive noise failures. The timer tags have failed and will be fixed during in-water ladder work. 11/04/2001 16:54 ptagdev@ 2A:ExcessiveNoise,3A:ExcessiveNoise,4B:TestTagFailure,6A:TestTagFailure,7A :ExcessiveNoise,7A:TestTagFailure,9A:ExcessiveNoise,9A:TestTagFailure,DB:E xcessiveNoise: This is a test message. DPC 4nov01 10/29/2001 14:11 Dave Manually (re)transmitted BWL01301.H. Probably got dusted while in the PTTP queue due to the power outage on Sockeye this AM. 10/29/2001 08:10 darren@p 4B:TestTagFailure,6A:TestTagFailure,7A:TestTagFailure,7B:ExcessiveNoise,9A :ExcessiveNoise,DB:ExcessiveNoise: Test tag failures will be addressed during this winters in ladder work. The noise failures have been checked in the raw files it appears that some of the noise on coil DB could be due to a tag that is not quite in the feild. Coil 9A has always been noisy (high voltage line) and 7B is back to normal. 10/26/2001 08:16 darren@p 4B:TestTagFailure,6A:ExcessiveNoise,6A:TestTagFailure,7A:TestTagFailure,7B :ExcessiveNoise,9A:ExcessiveNoise,DB:ExcessiveNoise: Test tag failures are be cause the test tags have failed. We will address this issue during water-down. The excessive noise comes and goes. We will watch this site for on going noise alarms. 10/25/2001 08:26 darren@p 4B:TestTagFailure,6A:ExcessiveNoise,6A:TestTagFailure,7A:TestTagFailure,7B :ExcessiveNoise,DB:ExcessiveNoise: The test tag failures are legitimate. We will be putting in the Virtual Timer Tag boards at water- down. The excessive noise seems to come and go. I am not seeing any pittag's in or around the coil when the noise is jumping. This does not mean that the Tag is not close to the feild. We will watch these noise levels and check for tags that may or may not pass through the feild around the same time frame. 10/24/2001 08:48 Dave I logged into BWL PC1 just after 4:30pm PST yesterday and discovered that MiniMon was not loaded. Just a blank desktop, folks. I started the program and put it into active data collection mode. This morning I see (from the reports) that there's a hole in data collection from 0828 - 1636 yesterday, for a total of 8:08. Anybody got any ideas? 10/24/2001 08:07 darren@p 4B:TestTagFailure,6A:TestTagFailure,7A:TestTagFailure,7B:ExcessiveNoise,9A :ExcessiveNoise,DB:ExcessiveNoise: Once again the alarms for the Test tag failures are valid the tags have failed. We are unable to do anything about them unitl the ladder is de-watered. We will also be installing Virtual Timer tag bds at that time. The excessive noise alarms will come and go I am not sure where the levels are set. We may want to raise the levels if they are to low. 10/22/2001 08:13 darren@p 4A:ExcessiveNoise,4B:TestTagFailure,6A:TestTagFailure,7A:TestTagFailure,7B :ExcessiveNoise,9A:ExcessiveNoise,DB:ExcessiveNoise: The Test tag failures are caused by the fact that the timer tags have failed. This will be addressed during the next waterdown period. The excessive noise alarms are being caused when the when the noise peaks above the threshold. I do not know what the threshold is set to but it may need to be changed. 10/19/2001 06:34 darren@p 2A:ExcessiveNoise,2B:ExcessiveNoise,3A:ExcessiveNoise,3B:ExcessiveNoise,4A :ExcessiveNoise,4A:TestTagFailure,4B:ExcessiveNoise,4B:TestTagFailure,5A:E xcessiveNoise,5B:ExcessiveNoise,6A:TestTagFailure,6B:ExcessiveNoise,7A:Exc essiveNoise,7A:TestTagFailure,7B:ExcessiveNoise,8A:ExcessiveNoise,9A:Exces siveNoise,AA:ExcessiveNoise,AB:ExcessiveNoise,BA:ExcessiveNoise,BB:Excessi veNoise,CA:ExcessiveNoise,CA:TestTagFailure,CB:ExcessiveNoise,DB:Excessive Noise,DB:TestTagFailure: The excessive noise alarm may be seen quite frequently. The test tags have failed but nothing can be done until waterdown. We will be retrofitting all transceivers with virtual timer tag boards at that time. 10/18/2001 07:53 darren@p 4A:TestTagFailure,4B:TestTagFailure,6A:TestTagFailure,7A:TestTagFailure: Test tags have failed. We can't do anything until waterdown. I believe we will be attaching virtual timer tag boards at that time. 10/17/2001 17:24 Dave Transferred all queued files, and changed upload mode from manual to auto. 10/15/2001 08:56 Dave Switched MiniMon to Manual Upload mode in preparation for server maintenance. 10/09/2001 15:56 Darren_C I PC'Ad into site at 3:30 this afternoon and the files had been sent. I tried to view the logging data but there is to much information coming across the screen with the noise reports being reported every 2 minutes. I guess that the internet must have shaken itself loose. I will check in the morning to make sure it is still loading. 10/09/2001 08:56 Darren_C I checked this morning and found that B2J and B2A had loaded. I PC'Ad into BWL but the connection is just like it was yesterday (choppy). I talked with Todd K. and he is going to check out the connection and then put a trace route to found out where the latency is. I will try to send files after I talk to Todd. 10/08/2001 16:32 Darren_C I have been trying to get B2J to send files for about 1.5hrs. I get so far in the process and then PTTP appears to hang. The connection is acting very choppy. B2A has finally sent its files but after viewing the history of PTTP it appears that it to was trying to send its files but was unsuccessful until about 3p.m. BWL I am having trouble getting into I will call Todd K. in the morning and find out if we are having router problems or what is going on. 09/18/2001 12:15 scottl NMFS requested that PTOC look at wier 54n, antenna 4B due to a decline in Hits per fish . Electrically, the transceiver is functional and working well. Read range is seems to be exceptional with relationship to it's adjacent coil 4A. The amperage on 4B was adjusted from 3.8 mils, to 4.1 with the door open. Peak noise, FDX-B and average noise was well within reason. One interesting point is that the Testtag for coil 4b is not functioning at all. Appears to be completely dead. This could be related to the deficiency in hits per fish for some reason.. Not sure, the only way to tell would be look at the history on 4B and determine when the testag failed then look at when the coil hit rate started to die off. Could be some relationship. Will inform NMFS with what we have found. 09/11/2001 16:22 Scott_Li Synched system clock to the nist.gov clock. Did not change the current file in Minimon, will wait for the next scheduled file change and let minimon at that time sync to the new setting. 09/10/2001 15:45 Dave Per Carter's request, I pcA'd into BWL-PC1 to find out why MiniMon was usually 3-6 lates in posting data to PTAGIS. Thanks to John's astute observations, we changed the upload interval from four to three hours, coincident with the file changes. I also changed the upload delay from 15 seconds to two minutes. File operations and uploads should sync-up at midnight tonight, and remain in sync from that point forward. The clock on PC1 is 4:40 slow. I also logged into BWL-PC2 (running Multimon) to check its clock. That machine is running 2:10 fast. The total discrepancy between machines is 6:50, which is way outside our 0:30 standard, but since the machines are on different platforms the standard may not apply(?). I'll leave it to the Kennewick staff to synchronize the clocks. BTW, when I logged into PC2, there was a Windows Explorer session open, and MM was running in a window. I did not alter the configuration. 05/14/2001 12:10 Scott_Li Talked with Sandy D about the large number of files that were being submitted to Ptagis in the testdata directory.. She had no clear answer as to how all these files were generated.. On day 131, 74 individual files were created.. hmmm?? Scott will monitor the BWL load on a daily basis and take appropriate action to ensure only a minimum number of files accumulate in PC2data directory...Multimon is configured to create 8 files per day. 05/14/2001 09:03 Scott_Li Noticed that files being submitted to the testdata directory from the bwl-pc2(Multimon PC) were not being archive therefore, being resubmitted to ptagis.. remote accessed the computer and manually archived over 200 files. The upload process was successfull subsequent to manual archive... 04/25/2001 09:58 Scott_Li BWL-PC1 was upgraded to minimon ver 1.0.78 on 4/24/01. Looking at the reports this morning it was noticed that the site had not submitted data files since yesterday at 16:42. PCa into the computer to find that the current file being built was 114.p ~3,233 Mg in size. Talking with John, it looks as if the upgrade was somewhat unsuccessfull , something to do with the system registries were not cleaned out.. Will monitor site until the next site visit when we will de-install and re-install Minimon to ensure a clean installation. Everything looks back on track as we re-initialized a few settings and restarted the application. 04/20/2001 11:53 Scott_Li Looks as if the BWX computer is still resubmitting previously sent data files. This will corrected on 4/25 during the normal weekly site visit.. 04/13/2001 13:27 scott BWL-PC2 (Alias BWX) was configured for the I/P network and is sending the BWX data files 4 times per day to the TESTDATA directory. 03/16/2001 09:09 Dave Initial configuration of Bonneville Washington Ladder site log. ####End of Event Log for BWL###