EVENT LOG FOR SITE RIA 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/20/2005 14:17 bturley@ Site visit on 12/20/05. I ran adaware and spybot antispyware programs on the two data computers to clean up the spyware on them. We think that unauthorized people were using the computers to get on the internet, and that has bogged the computers down and caused some of the problems sending files to ptagis. 12/16/2005 07:14 bturley@ The noise alarm thresholds were changed on all coils to 99%, except coil #03 on 12/14/05 @ 15:24:52. 12/16/2005 07:13 bturley@ 08:TestTagFailure: Test tag failed for unknown reason. We will check this out during a site visit next week. 12/15/2005 15:27 bturley@ Here are the dates for the adult ladder de-watering at Rock Island dam. The left ladder was dewatered on 12/5/05. The middle ladder will be dewatered on 12/27/05. The right ladder will be dewatered on 1/16/05. I was not given the dates when the ladders will be watered up. I will post that information when I get it. 12/12/2005 08:10 Dave I've removed "sitemaint@psmfc.org" from the ck_submit notification process for RIA, leaving the original "biomark_sitemaint" list intact. The default PTAGIS notification list, was added last Friday to aid in diagnosing an ongoing issue; notification to PTAGIS is no longer necessary. 12/09/2005 17:11 Dave I added PTAGIS to the distribution list in the RIA etc/site record for "ck_submit" failures, to diagnose the ongoing issue with extraneous entries in the RIA_Event SiteScape forum. 11/04/2005 09:08 bturley@ 09:TestTagFailure: Test tag failed. Noise report at the same time showed that noise peaked at 97%, possibly causing test tag failure??? 11/04/2005 09:04 bturley@ 08:TestTagFailure: Test tag failed for no apparent reason 10/25/2005 08:15 bturley@ 08:TestTagFailure: Test tag failed for unknown reason 09/20/2005 08:13 bturley@ 08:TestTagFailure: Test tag failure. Not sure what caused it to fail. 09/12/2005 15:44 bturley@ 08:TestTagFailure: Test tag failure. Not sure why it happened 09/09/2005 07:11 bturley@ 08:TestTagFailure: Test tag failure on 08. No indication as to why it happened 09/01/2005 13:33 bturley@ 06:HighTemp,09:HighTemp: High temp alarms caused by very hot temperatures outside. 09/01/2005 13:31 bturley@ 04:LowExcCurrent: We think a bad sync cable is causing this low current alarm. The coil itself appears to be in working order. The files show tags read from it. 08/23/2005 13:57 bturley@ 03:HighTemp,09:HighTemp,0A:HighTemp: More high temp alarms. Nothing we can do about this at this point. 08/23/2005 13:56 bturley@ 04:LowExcCurrent: Low exciter current caused by sync cable between 03 and 04. We will address this issue on the next site vist. 08/19/2005 08:01 bturley@ 09:HighTemp,0A:HighTemp,0C:HighTemp: More high temp alarms for 09, 0A and 0C. Due to high summer temps and where the transceivers are mounted, there's not much that can be done at this time. 08/19/2005 07:58 bturley@ 04:LowExcCurrent: Suspect the low exciter current alarm is caused by the sync cable. The transceiver appears to be working fine. 08/19/2005 07:54 bturley@ 08:TestTagFailure: Don't know why the test tag failed. This test tag seems to fail about once a week or so. 08/04/2005 15:06 bturley@ 04:LowExcCurrent: Suspect the low current alarm may be caused by bad sync cable connection with coil 03. The coil seems to be working well other than the occassional low current alarm. 08/03/2005 15:10 bturley@ 03:HighTemp,09:HighTemp,0A:HighTemp,0B:HighTemp,0C:HighTemp: Coils 03,09,0A,0B and 0C are experiencing high temperatures. Don't know what we can do with the hot days and where the transceivers are mounted. 08/03/2005 15:07 bturley@ 04:LowExcCurrent: Not sure what is causing the low exciter current. The coil is working well and the noise is low. Will continue to monitor closely. 07/27/2005 14:07 bturley@ 09:HighTemp,0A:HighTemp,0C:HighTemp: Coils 09 0A and 0C temperatures have reached 61C. These transceivers are difficult to keep cool due to their location on the dam. Will continue to monitor. 07/27/2005 14:03 bturley@ 04:LowExcCurrent: Not sure what caused the low exxiter current. Coil 04 may be interfering slightly with 03. The coil is reading well. Will continue to monitor. 07/25/2005 06:59 bturley@ 08:TestTagFailure: Test tag failed for no apparent reason. 06/30/2005 06:54 bturley@ 08:TestTagFailure: Don't know why the test tag failed. There was no reader activity at the time the tag fired. 06/28/2005 10:26 bturley@ 02:LowExcCurrent,03:LowExcCurrent,0A:LowExcCurrent: Low Exciter Current alarm was caused by Biomark personnel during routine maintenance. All transceivers were tuned on 6/21 and 6/22. 06/28/2005 10:25 bturley@ 08:TestTagFailure: Don't know why the test tag failure occurred. 06/17/2005 08:18 bturley@ 09:TestTagFailure: Transceiver sent a status report at the same time as the test tag. This may have resulted in the test tag failure. 06/17/2005 08:16 bturley@ 08:TestTagFailure: I'm not sure why the test tag failed. There was nothing in the data file indicating a problem 05/19/2005 12:43 acarson@ 09:TestTagFailure: Not sure why test tag failed. The reader sent a noise report at the same time, but I don't know if that is why the test tag failed. 05/19/2005 12:40 acarson@ 08:TestTagFailure: Not sure why test tag failed. The reader sent a noise report at the same time, but I'm not sure if this is why the test tag failed. 04/19/2005 09:57 acarson@ 08:TestTagFailure: Not sure why test tag failed. The reader did send a noise report at the same time, but I don't know if that is why it failed. 03/15/2005 13:33 acarson@ 01:ExcessiveNoise,02:ExcessiveNoise,03:ExcessiveNoise: All excessive noise levels due to ladders dewatering. I was able to get the dates of when the ladders have been dewatered and watered up but no exact times. From the noise reports I would say the left ladder was watered up for the last time on 3/14/05 at 13:45:00. The left fishway at Rock Island was dewatered on 13 December 2004 and watered back up on 6 January. The left fishway was dewatered again on 4 March and watered back up on 14 March. The middle fishway was dewatered on 13 December 2004 and watered back up on 15 December 2004. The middle fishway was dewatered again on 4 January and watered back up on 20 January. The right fishway was dewatered on 21 January and watered back up on 3 March. 03/15/2005 13:27 acarson@ 04:LowExcCurrent: The left fishway was dewatered again on 4 March and watered back up on 14 March. 03/15/2005 13:13 acarson@ 08:TestTagFailure: Looks as if the reader sent a DRS at the same time it fired the timer tag. Can't determine if this was the reason for the failure but antenna has been working properly since. 03/02/2005 15:43 acarson@ 01:ExcessiveNoise,02:ExcessiveNoise,03:ExcessiveNoise,04:ExcessiveNoise,05 :ExcessiveNoise,06:ExcessiveNoise,07:ExcessiveNoise,08:ExcessiveNoise: Tuned all coils (01-08) on both the left and center ladders. Placed coils 09-0C in "stby" while ladder is dewatered. 03/02/2005 15:35 acarson@ 05:TestTagFailure,06:LowExcCurrent,06:TestTagFailure,07:LowExcCurrent,07:T estTagFailure,08:TestTagFailure: Calibrated and flashed coils 05-08. Recorded initial data in antenna log book. 02/01/2005 08:15 ptagdev@ 01:ExcessiveNoise,02:ExcessiveNoise,03:ExcessiveNoise,04:ExcessiveNoise,05 :ExcessiveNoise,07:ExcessiveNoise,08:ExcessiveNoise: For weeks now, this site has been generating lots of Excessive Noise alarms, and posting lots of noise parameter data. Consequently, its TASS 'archive' file has grown to about 10x the size of a typical site's archive. Time required to load the huge archive into memory is causing TASS to fall behind in processing data for other sites. It would help if someone would 'acknowledge' these alarms and - if no one is paying attention anyway - turn off 'noise reporting' at this site to avoid further processing overhead. Thanks. Doug Clough ####End of Event Log for RIA###