EVENT LOG FOR SITE BO4 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/31/2005 09:41 Troy This site is loading what may appear to be duplicate files. The second file only has time stamps every 15 minutes. It is as if there are 2 versions of Minimon running but only one connnected to the device masters. I was unable to find another version of minimon running yesterday in my attempt to fix this problem. This problem will have to be addressed on 1/3/06. In the mean time PSMFC will continue to monitor and try and ensure that at least one of the files this site is submitting has valid data. 12/31/2005 09:28 troy@ruf 04:TestTagFailure: Noted. PSMFC will monitor for future failures 12/30/2005 10:08 Troy This site is still having issues. Rebooted the FTV and minimon failed to connect to the transcievers. Went through the disabling ports routine and rebooting twice before minimon work. PSMFC will continue to monitor for future problems and will be addressed on 1/3/06 12/29/2005 13:37 Troy In responding to a 'files not recieved' email concerning b04 it was found that all 4 devices (transcievers) were not connected. The Virtual Interface (VI) was rebooted and all but 03 connect. The VI was reboot again and no devices connected. A few more reboots of the VI were attempted but no go. Checked the device master through device manager and port monitor and all looked good. Port Monitor showed a framing error on DM port 2? Re-booted the servers and still no go. Went into device manager and disabled all 4 ports and re-booted the servers. Logged back in and re-enabled the 4 ports. Minmon connect! Pushed the several files that were created. This problem will be looked into more in depth next week. 3 fish were seen for this week so if problems occur over the weekend we will use the buffers to keep track. Approximately 1.5 hours of data was lost. 12/23/2005 09:27 Alan_Bro Apparently, a power event occurred in the PIT Tag room yesterday. We are working to verify what happened. BO405356.F9 was created from BO405356.F1.TMP and submitted manually from the platform via remote access. BO405356.I1.TMP contained no useful information. No further data exist to fill the nine, three and six minute file gaps on 12/22 2005. 12/21/2005 08:20 alan@ruf 02:TestTagFailure: This alarm will be addressed on the next site visit. 12/20/2005 08:10 alan@ruf 02:TestTagFailure,03:TestTagFailure: These alarms will be addressed on the next site visit. 12/19/2005 10:17 alan@ruf 02:TestTagFailure,03:TestTagFailure: These alarms will be addressed on the next site visit. 12/18/2005 09:04 darren@r 03:TestTagFailure: This alarm will be addressed on the next site visit. 12/17/2005 08:37 darren@r 03:TestTagFailure: Alarm will be addressed on the next site visit. 12/16/2005 08:15 darren@r 03:TestTagFailure: These alarms will addressed by PSMFC on the next saite visit. 12/15/2005 15:38 darren@r 03:TestTagFailure: No direct cause for this alarm. PSMFC will monitor for future alarms. 12/15/2005 08:08 troy@ruf 01:TestTagFailure,03:BadOscFreq,03:LowExcCurrent,03:Overrun,03:TestTagFail ure,04:TestTagFailure: These alarms are most likely due to a GMC that was perform. PSMF will monitor for future occurances. 12/13/2005 13:51 scottl Site was re-tuned on 12/12/05. Transceiver 03's timertag hit rate would not fire above 30 percent after extensive tuning. A standard ST tag was used in order to verify readability. 12/12/2005 08:12 darren@r 01:TestTagFailure,02:TestTagFailure,03:TestTagFailure,04:TestTagFailure: Alarms will be addressed on next site visit. 12/10/2005 10:54 scottl@r 01:TestTagFailure,02:TestTagFailure,03:TestTagFailure,04:TestTagFailure: Will be onsite next week to correct problems 12/08/2005 16:57 Alan_Bro Responding to the lack of files from Bonneville, it was found that the CentreCom FH712SW has a noisy fan. While moving cables and equipment in the coms rack connectivity was restored, probably due an intermittent cable or perhaps the FH712SW itself. The tardy files were submitted manually from BO4 and BO3, the others were submitted via PCA. PTAGIS Field Operations will continue to monitor. 12/06/2005 08:18 darren@r 01:TestTagFailure,02:TestTagFailure,03:TestTagFailure,04:TestTagFailure: Alarms will be addressed on the next site visit. 12/05/2005 08:17 scottl@r 01:TestTagFailure,02:TestTagFailure,03:TestTagFailure,04:TestTagFailure: System will tuned and calibrated on the next site visit. 12/03/2005 11:31 dlwarf@r 01:TestTagFailure,02:TestTagFailure,03:TestTagFailure,04:TestTagFailure: Site to be tuned on next week's GMC. 12/01/2005 08:38 scottl@r 01:TestTagFailure,02:TestTagFailure,03:TestTagFailure,04:TestTagFailure: Will address on the next site visit 11/30/2005 09:12 scottl@r 01:TestTagFailure,02:TestTagFailure,03:TestTagFailure,04:TestTagFailure: This site is in need of a tune up. Will recalibrate system on the next site visit. Transciever 04 noise levels are in the high 90's. 11/28/2005 10:34 darren@r 01:TestTagFailure,02:TestTagFailure,03:TestTagFailure,04:TestTagFailure: Site will be visited for a GMC in the near future. All alarms will be investigated at that time. 11/27/2005 08:06 troy@ree 01:TestTagFailure,02:TestTagFailure,03:TestTagFailure,04:TestTagFailure: Tuning should elimnate the TT failures. This will be addressed on the next site visit. 11/26/2005 10:28 troy@ree 01:TestTagFailure,02:TestTagFailure,03:TestTagFailure,04:TestTagFailure: These alarms will be addressed on the next site visit. 11/25/2005 10:07 troy@ree 01:TestTagFailure,02:TestTagFailure,03:TestTagFailure: Noted 11/24/2005 20:09 troy@ree 01:TestTagFailure,02:TestTagFailure,03:TestTagFailure,04:TestTagFailure: These transcievers will be tuned on the next site visit which should eliminate these alarms. 11/23/2005 09:59 Alan_Bro USACE Bio Tammy Mackey reports that routine maintenance caused power outages at 12:00 and 18:47 on 11/22/2005. This resulted in two file gaps. No data exists to fill the 00:07 gap at 12:00. File BO405326.H9 was manually created from BO405326.H1.TMP and manually submitted from the platform. No data exists to fill the 00:07 gap at 18:45. 11/23/2005 08:55 troy@ree 01:TestTagFailure,02:TestTagFailure,03:TestTagFailure,04:TestTagFailure: Noted 11/22/2005 08:32 troy@ree 01:TestTagFailure,02:TestTagFailure,03:TestTagFailure,04:TestTagFailure: These alarms will be addressed on the next site visit. 11/21/2005 08:03 troy@ree 01:TestTagFailure,02:TestTagFailure,03:TestTagFailure,04:TestTagFailure: These alarms will be addressed on the next site visit. 11/20/2005 10:03 alan@ree 01:TestTagFailure,02:TestTagFailure,03:TestTagFailure,04:TestTagFailure: These alarms will be addressed on the next site visit. 11/19/2005 09:48 alan@ree 01:TestTagFailure,02:TestTagFailure,03:TestTagFailure,04:TestTagFailure: These alarms will be addressed on the next site visit. 11/17/2005 08:33 Alan_Bro The last pitevent should have read: These alarms will be addressed on the next site visit. 11/17/2005 08:30 alan@ree 01:TestTagFailure,02:TestTagFailure,03:TestTagFailure,04:TestTagFailure: These alarms will be generated on the next site visit. 11/16/2005 08:01 scottl@r 01:TestTagFailure,02:TestTagFailure,03:TestTagFailure,04:TestTagFailure: Site will be tuned and calibrated on 11/16 or 11/17/05 11/15/2005 16:31 Alan_Bro File BO405311.C9 was created from a BO405311.C1.TMP file found on the FTV and submitted manually from the platform. There is no data to fill the seven-minute gap on 11/7/2005. BO405313.A1.TMP existed but had no data fill the seven-minute gap on 11/9/2005. 11/14/2005 09:34 alan@ree 01:TestTagFailure,02:TestTagFailure,03:TestTagFailure,04:TestTagFailure: These alarms have been noted by PSMFC and will be taken care of on the next site visit. 11/13/2005 09:25 darren@r 01:TestTagFailure,02:TestTagFailure,03:TestTagFailure,04:TestTagFailure: These alarms have been noted by PSMFC and will be taken care of on the next site visit. 11/12/2005 07:30 darren@r 01:TestTagFailure,02:TestTagFailure,03:TestTagFailure,04:TestTagFailure: PSMFC will be on site next week for a site GMC. Transceivers will be adjusted at that time. Although the timer tags are not firing the detection efficiencies are acceptable. 11/11/2005 08:11 darren@r 01:TestTagFailure,02:TestTagFailure,03:TestTagFailure,04:TestTagFailure: This site will be visited next week for a site GMC. PSMFC will make the necessary adjustments at this time. 11/09/2005 08:26 dlwarf@r 01:TestTagFailure,02:TestTagFailure,03:TestTagFailure,04:TestTagFailure: Site will be fulled tuned next week. 11/08/2005 08:05 darren@r 01:TestTagFailure,02:TestTagFailure,03:TestTagFailure,04:TestTagFailure: PSMFC is aware of these alarms and will be on site to perform a site GMC and retune the transceivers soon. These alarms will be addressed at that time. 11/07/2005 11:18 Troy Manually pushed 3 files that failed to load. Unsure as to why they didn't load. Thank you Nadia for you experties on logging into the server. 11/07/2005 08:52 troy@ree 01:TestTagFailure,02:TestTagFailure,03:TestTagFailure,04:TestTagFailure: These alarms will be addressed on the next site visit. 11/06/2005 09:14 darren@r 01:TestTagFailure,02:TestTagFailure,03:TestTagFailure,04:TestTagFailure: These transceivers will be checked for tuning and noise on the next site visit. 11/05/2005 11:30 scottl@r 01:TestTagFailure,02:TestTagFailure,03:TestTagFailure,04:TestTagFailure: although still operational, the system could use a good tune up.. 11/04/2005 08:08 scottl@r 01:TestTagFailure,02:TestTagFailure,03:TestTagFailure,04:TestTagFailure: Site needs tuned and hit rates need adjusted. Will respond when available. 11/03/2005 08:25 scottl@r 01:TestTagFailure,02:TestTagFailure,03:TestTagFailure,04:TestTagFailure: TT hit rates will be adjusted on the next site visit. 11/02/2005 08:02 scottl@r 01:TestTagFailure,02:TestTagFailure,03:TestTagFailure,04:TestTagFailure: Will address on the next site visit. 11/01/2005 08:08 scottl@r 01:TestTagFailure,04:TestTagFailure: Timertags will be re-calibrated on the next site visit. 10/31/2005 08:58 scottl@r 01:TestTagFailure,02:TestTagFailure,03:TestTagFailure,04:TestTagFailure: The testtag hit rates appear to need re-calibrated.Will respond when situation warrants attention 10/28/2005 08:15 scottl@r 01:TestTagFailure,02:TestTagFailure,04:TestTagFailure: Will monitor transceiver detection efficiency. Units will be retuned when becomes necessary. Very few fish are transiting the ladder at this time. 10/27/2005 08:32 darren@r 01:TestTagFailure,02:Overrun,02:TestTagFailure,03:TestTagFailure,04:TestTa gFailure: These transceivers will be checked on the next site visit. A GMC was recently performed and there did not appear to be any distinct problems during the visit. We will investigate these alarms on the next site visit. 10/26/2005 09:32 Alan_Bro A power outage occurred 10/21/2005 causing the platform to terminate Minimon unexpectedly. BO405294.C9 was created from the .TMP file and submitted manually via remote access. No data exists to fill the seven minute file gap. 10/26/2005 08:28 Alan_Bro Manually pushed BO405299.B1 to PTAGIS via remote access. 10/24/2005 13:28 Darren A site GMC was performed on both BO3 and BO4. No problems were found at BO3 all transceivers were checked for tuning and noise. At BO4 I adjusted the timer tag hit rate on transceivers 01 and 04. According to the timer tag report this morning the timer tag on 04 was not reading at 100%, when I arrived on site I found that the hit rate was only at 70% I tuned the capacitors and brought the hit rate back to 95-100%. I performed the same actions on antenna 01. Antennas 02 and 03 were checked and the hit rate was still above 95%. 10/24/2005 08:03 troy@ruf 04:TestTagFailure: This alarm will be addressed today during a scheduled GMC. 10/23/2005 08:59 troy@ruf 04:TestTagFailure: This is a ongoing problem and will require tuning to fix. This will be addressed on the next site visit. 10/22/2005 08:38 troy@ruf 01:TestTagFailure,04:TestTagFailure: These alarms will be addressed on the next site visit. 10/21/2005 08:16 scottl@r 04:TestTagFailure: Antenna may need tuned in the near future. Timer Tag hit rate is dropping 10/19/2005 08:02 troy@ruf 01:TestTagFailure,03:TestTagFailure,04:TestTagFailure: These alarms will be addressed on the next site visit. 10/18/2005 11:51 Alan_Bro More than likely, power outages occurred around midnight 10/14 and 10/15, 2005. We are awaiting confirmation on this from the USACE. Files BO405287.H9 and BO405288.H9 were created from TMP files found on the FTV and submitted manually from the platform. There is no data to fill the six-minute gap on 10/14/2005 or the eleven-minute gap on 10/15/2005. 10/18/2005 08:15 troy@ruf 02:Overrun,04:TestTagFailure: These alarms will be addressed on the next site visit. 10/17/2005 08:44 troy@ruf 03:LowTemp: This will be looked into on the next site visit. 10/16/2005 07:38 darren@r 04:TestTagFailure: PSMFC will address this alarm on the next site visit. This site is missing two files BO405288.H1 and BO405289.H1 which are probably on the server but as .temp files. These files will be fixed and submitted tomorrow. 10/16/2005 07:31 Darren It appears that there was another power outage around 23:50 last evening and it outlasted the UPS's on the server. The file BO405289.H1 is probably a temp file and will need to be altered befor being submitted. PSMFC will contact site personnel on Monday and confirm all the power outages. We will alter the temp files for files BO405288.H1 and BO405289.H1 and submit them to PTAGIS. 10/15/2005 10:44 Darren It appears that the power outage that occured last evening has caused a gap in the files. The file .H1 is probably a temp file that will have to be altered and submitted. I will attempt to PCA into the server and verify this as a fact and then submit the altered file. 10/15/2005 06:34 darren@r 04:TestTagFailure: Alarm has been noted and will be addressed on the next site visit. 10/14/2005 09:40 Alan_Bro Due to USACE planned power outages on 10/12/2005 and 10/13/2005, data collection was interrupted. The power outages exceeded the UPS battery life on the collection platform. BO405285.H9 and BO405286.H9 were created from TMP files found on the FTV and submitted manually from the platform. There is no data to fill the four-minute gap on 10/12/2005 or the six-minute gap on 10/13/2005. 10/14/2005 08:11 darren@r 01:BadOscFreq,01:TestTagFailure,02:TestTagFailure,04:TestTagFailure: Alarms were generated by PSMFC personnel while performing a site GMC. 10/13/2005 20:00 Scott_Li GMC was performed, all transcievers were retuned and calibrated as necessary. No outstanding problems to report. 10/13/2005 08:11 darren@r 01:TestTagFailure,02:TestTagFailure,04:TestTagFailure: Alarms will be addressed on the next visit by PSMFC. 10/12/2005 08:05 darren@r 01:TestTagFailure,02:TestTagFailure,04:TestTagFailure: PSMFC is aware of and have investigated these alarms. They will be addressed on the next site visit. 10/11/2005 08:30 Scott_Li Turned the timer tags on to check the hit rate, transceivers 01, 02 was at ~2-10 percent. The low hit rate accounts for the high numbers of missing timer tags in the report and directly reflects the detection efficiency of adult fish. The site will be monitored and retuned when appropriate. More than likely, this will happen next week when O&M personnel are performing GMCs. 10/11/2005 08:07 darren@r 01:TestTagFailure,02:TestTagFailure,04:TestTagFailure: Alarms will be addressed on the next site visit. PSMFC in conjunction with Digital Angel are in the process of testing analog boards in 2 of the 4 transceivers we will be montioring efficiencies and making adjustments as needed. 10/09/2005 11:04 alan@ruf 01:TestTagFailure,02:TestTagFailure,04:TestTagFailure: Noted again. 10/09/2005 10:57 alan@ruf 01:TestTagFailure,02:TestTagFailure,04:TestTagFailure: Noted. 10/08/2005 10:33 alan@ruf 01:TestTagFailure,04:TestTagFailure: Noted 10/07/2005 15:48 Scott_Li Transceivers 01 and 02 were retuned due to low efficiencies. This was done on 10/6 at ~10:45 am 10/07/2005 08:07 alan@ruf 01:TestTagFailure,02:TestTagFailure,04:TestTagFailure: Noted 10/06/2005 08:09 alan@ruf 01:TestTagFailure,02:TestTagFailure,04:TestTagFailure: Noted 10/03/2005 08:09 alan@ruf 01:TestTagFailure,02:TestTagFailure,04:TestTagFailure: This site is detecting PIT Tags with good efficiency. PTAGIS Field Operations will continue to monitor. 10/02/2005 13:56 scottl@r 01:TestTagFailure,02:TestTagFailure,04:TestTagFailure: Will monitor 09/30/2005 08:02 scottl@r 01:TestTagFailure: Not of concern at this time 09/29/2005 08:12 scottl@r 01:TestTagFailure,02:TestTagFailure,04:Overrun,04:TestTagFailure: Overruns on 04 do not appear to hindering the detection of tags, will monitor. 09/26/2005 08:03 darren@r 01:TestTagFailure,04:Overrun: These alarms will be investigated on the next site visit. The test tag failure alarm is being generated by the status report. 09/25/2005 11:24 dlwarf@r 01:TestTagFailure,02:TestTagFailure,04:Overrun,04:TestTagFailure: To be investigated on Monday. 09/24/2005 14:48 Dave I noticed that the FILE CLOSE for BO405265.F9 reported "15:03", even though Alan had specified "15:39". I added a return after that last line, and reposted the file. PTAGIS now correctly reports a FILE CLOSE value of "15:39" for BO405265.F9. I guess this means that any FILE CLOSE statement manually added to a file must terminate with a return character. 09/24/2005 10:52 Don_Warf A 43 minute file gap was created on Friday at 15:03 to 15:46. This will be investigated on Monday. 09/24/2005 10:29 dlwarf@r 04:Overrun: Overruns noted. 09/23/2005 10:35 Alan_Bro Apparently a power failure occurred between 15:00 and 15:39 PST 9/22/2005, we are awaiting confirmation from site personnel. BO405265.F1.tmp was manually appended with a closing time stamp, renamed BO405265.F9 and manually submitted to PTAGIS. No data exists to fill the seven minute gap on 9/22/2005 from 15:39 to 15:46. 09/23/2005 08:21 scottl@r 01:TestTagFailure,04:TestTagFailure: Noted 09/22/2005 08:03 scottl@r 02:Overrun,04:Overrun: Noted 09/21/2005 08:16 scottl@r 01:TestTagFailure,03:TestTagFailure,04:TestTagFailure: ~01-35 09/21/05 00:18:23 INFO FDXB Peak: 100 % Noise levels at certain times are excessive and could be the main reason for the periodic test tag failure 09/20/2005 08:05 scottl@r 03:TestTagFailure: Not of concern at this time. 09/19/2005 08:28 scottl@r 01:TestTagFailure,04:Overrun: The errors have been noted 09/18/2005 09:21 troy@ruf 01:TestTagFailure,04:TestTagFailure: These TT failures will be addressed on the next site visit. 09/16/2005 08:25 troy@ruf 03:TestTagFailure,04:TestTagFailure: These will be addressed on the next site visit. 09/15/2005 08:23 troy@ruf 02:Overrun,03:TestTagFailure,04:TestTagFailure: These alarms will be addressed on the next site visit. 09/14/2005 08:29 troy@ruf 01:TestTagFailure,02:Overrun,03:TestTagFailure,04:TestTagFailure: These transceivers were swapped around early on 09/13/05 which may have caused some of these alarms. The others may be due to tuning or high fish traffic. PSMFC will monitor for future occurances. 09/13/2005 12:39 Darren At 7 a.m. this morning PSMFC began the swap of transceivers 01 and 03 and 02 and 04. This was done to place the site back to it's original configuration. The transceiver swap was comleted at 09:00 as the NMFS fish test was getting under way. The transceivers were tuned using the Digital Angel procedure. The transceivers were swapped back after they had been swapped on 9-8-05 because PSMFC had noticed that efficiencies had slipped to levels that were not acceptable. PSMFC will monitor for future failures and correct as neccessary. 09/12/2005 08:12 darren@r 01:TestTagFailure: PSMFC will address any problems with these detectors on the next site visit. 09/09/2005 08:08 alan@ruf 03:LowExcCurrent: This alarm was generated by PTAGIS Field Operations personnel during a site visit. 09/08/2005 13:27 Scott_Li Transcievers positions were swapped as previously discussed. Transceiver 01 and 03 were swapped and 02 and 04 were swapped. All units were retuned with the procedure outlined by Digital Angel. Will run this experiment for a minimum of 1 month, then re-evaluate the performance of the system. The change out occurred at 11:45 pst. 09/08/2005 08:30 alan@ruf 02:Overrun,04:Overrun,04:TestTagFailure: These alarms will be addressed on a site visit today. 09/06/2005 08:07 alan@ruf 02:Overrun: This alarm will be addressed on the next site visit. 09/03/2005 07:48 darren@r 04:Overrun: This alarm will be addressed on the next site visit. 09/02/2005 11:09 darren@r 02:Overrun,04:Overrun,04:TestTagFailure: These alarms will be addressed on the next site visit. 09/01/2005 08:07 darren@r 02:Overrun: Alarms will be investigated on the next site visit. 08/30/2005 08:24 darren@r 02:Overrun,04:Overrun,04:TestTagFailure: Alarms will be investigated on the next site visit. 08/26/2005 08:07 scottl@r 02:Overrun: The transceivers will be swapped around as stated in a previous entry and retuned possably next week 8/29. 08/25/2005 14:37 Alan_Bro A GMC was performed 8/25/2005. All tranceivers were tuned, no problems found. 08/25/2005 07:55 scottl@r 02:Overrun,04:Overrun: Noted 08/23/2005 08:02 scottl@r 02:Overrun: Noted 08/21/2005 11:50 dlwarf@r 02:Overrun,03:Overrun: Overruns noted. Site will be visited this week. 08/20/2005 10:16 scottl@r 02:Overrun: Noted. 08/19/2005 08:12 scottl@r 02:Overrun,03:Overrun,04:Overrun: A GMC is scheduled for next week. 08/18/2005 07:06 scottl@r 04:Overrun: Noted 08/17/2005 08:01 scottl@r 02:Overrun: Not of concern at this time 08/16/2005 08:05 scottl@r 02:Overrun,03:Overrun,04:TestTagFailure: Problems not of concern at this time, system is under evaluation by DA and PSMFC. 08/14/2005 09:41 troy@ruf 02:Overrun,04:TestTagFailure: These alarms will be investigated on the next site visit. 08/13/2005 08:58 troy@ruf 02:Overrun: Noted 08/12/2005 08:19 troy@ruf 04:Overrun: Noted. 08/10/2005 08:19 troy@ruf 02:Overrun: This will be addressed on the next site visit. 08/09/2005 08:12 troy@ruf 02:Overrun: This will be addressed on the next site visit. 08/08/2005 08:19 troy@ruf 04:TestTagFailure: No readily apparent cause for this failure. PSMFC will monitor for future occurrences 08/07/2005 11:27 alan@ruf 02:Overrun,03:Overrun: Noted. 08/06/2005 10:37 alan@ruf 01:LowExcCurrent,02:Overrun,03:Overrun,04:LowExcCurrent: Noted. 08/05/2005 14:59 Alan_Bro A GMC was performed 8/5/2005. All transceivers were tuned. Analog ground was lifted from digital ground on the analog board in transceiver 01 in an effort to diagnose the instability at this site. No other problems found. 08/05/2005 09:00 darren@r 01:TestTagFailure,02:Overrun,03:Overrun,04:LowExcCurrent,04:TestTagFailure : PSMFC will be on site today for a site GMC and these alarms will be addressed today. 08/04/2005 12:06 alan@ruf 01:TestTagFailure,02:Overrun,04:LowExcCurrent,04:TestTagFailure: Alarms noted. This site will be visited tomorrow. 08/03/2005 08:25 alan@ruf 01:TestTagFailure,04:LowExcCurrent: Alarms will be addressed on a site visit this week. 08/02/2005 08:49 alan@ruf 02:Overrun,04:LowExcCurrent,04:TestTagFailure: Alarms will be addressed on the next site visit. 08/01/2005 09:23 alan@ruf 01:TestTagFailure,02:Overrun,03:Overrun,04:LowExcCurrent,04:TestTagFailure : Alarms will be addressed on the next site visit. 07/31/2005 07:40 darren@r 01:TestTagFailure,02:Overrun,03:Overrun,04:LowExcCurrent,04:TestTagFailure : Alarms will be addressed on the next site visit. 07/30/2005 07:41 darren@r 01:TestTagFailure,02:Overrun,03:Overrun,04:LowExcCurrent,04:TestTagFailure : Alarms will be addressed on the next site visit. 07/29/2005 08:54 darren@r 01:TestTagFailure,02:Overrun,04:LowExcCurrent,04:TestTagFailure: Alarms will be addressed on the next site visit. 07/28/2005 08:01 darren@r 02:Overrun,04:LowExcCurrent,04:TestTagFailure: Alarms will be investigated on the next site visit. Digital Angel was recently on site and replaced the analog boards on transceivers 01 and 02. This site is being monitored for performance. 07/27/2005 08:25 darren@r 01:TestTagFailure,02:Overrun,04:LowExcCurrent,04:TestTagFailure: Alarms will be addressed on the next site visit. 07/26/2005 08:22 darren@r 01:TestTagFailure,03:Overrun,04:LowExcCurrent,04:TestTagFailure: Alarms will be addressed on the next site visit. 07/25/2005 08:09 darren@r 01:TestTagFailure,02:Overrun,03:Overrun: Alarms will be addressed on the next site visit. 07/24/2005 11:01 scottl@r 01:TestTagFailure,03:Overrun,04:LowExcCurrent: Current alarm for 04 will be adjusted on Monday. 07/22/2005 15:15 Scott_Li Monitoring the noise reports for the recently installed analog pcb's installed in transceivers 01 and 02 indicates that the PEAK and FDXB levels are at 90 to 100 percent. Average signal levels are very low, ~ 1-5 percent. The detection efficiencies are somewhat acceptable but not where we would like to see them. Will monitor the situation over the weekend and schedule a trip to the site next week if necessary. Also, will consult with DA on the situation and ask for recommendations if required. Theres a question whether the status information gathered by transceivers is correct. 07/22/2005 09:23 Scott_Li The analog pcb's in transceivers 01 and 02 were replaced yesterday by Digital Angel and PSMFC. The 2 boards have different modifications and will evaluated on an individual basis to see which board performs the best. As of now, there are 3 different style boards, the original Rev 1 , Rev 1A and Rev 1B. Also, the Capacitor bank in antenna 03 was replaced. DA recommended this in an attempt to improve performance. A more formal document outlining the sequence of events and timelines will be drafted and posted to the Bonneville Wa Shore forum. 07/21/2005 16:26 darren@r 01:LowExcCurrent,01:Overrun,02:LowExcCurrent,03:LowExcCurrent,03:TestTagFa ilure,04:LowExcCurrent,04:Overrun,04:TestTagFailure: These alarms may have been caused by PSMFC personnel while replacing and retuning the analog boards in the transceivers. 07/21/2005 08:08 darren@r 01:LowExcCurrent,01:Overrun,01:TestTagFailure,02:TestTagFailure,03:LowExcC urrent,03:TestTagFailure,04:Overrun,04:TestTagFailure: PSMFC personnel will be on site today assisting Digital Angel with the analog board replacement on these transceiver. 07/20/2005 09:21 scottl@r 01:LowExcCurrent,01:Overrun,01:TestTagFailure,02:TestTagFailure,03:LowExcC urrent,03:TestTagFailure,04:Overrun,04:TestTagFailure: A site visit is scheduled for tomorrow for re-tuning and board replacement. 07/19/2005 08:17 scottl@r 01:LowExcCurrent,01:Overrun,01:TestTagFailure,02:TestTagFailure,03:LowExcC urrent,03:Overrun,03:TestTagFailure,04:Overrun,04:TestTagFailure: A site visit is scheduled for Thursday, 21st for retuning and analog pcb replacement on 2 of the transcievers. 07/18/2005 08:06 scottl@r 01:LowExcCurrent,01:Overrun,01:TestTagFailure,02:TestTagFailure,03:LowExcC urrent,03:Overrun,03:TestTagFailure,04:Overrun,04:TestTagFailure: PTOC personnel will be on-site Thursday of this week for GMC and retuning of the transceivers. 07/17/2005 08:03 darren@r 01:Overrun,03:LowExcCurrent,03:Overrun,03:TestTagFailure,04:Overrun: Alarms will be investigated on the next site visit. 07/16/2005 08:09 darren@r 01:Overrun,01:TestTagFailure,03:LowExcCurrent,03:TestTagFailure,04:Overrun ,04:TestTagFailure: Alarms will be addressed on the next site visit. 07/15/2005 16:23 Alan_Bro Manually pushed BO405196.E1 to PTAGIS. 07/15/2005 09:04 darren@r 01:Overrun,01:TestTagFailure,03:LowExcCurrent,03:Overrun,03:TestTagFailure ,04:Overrun,04:TestTagFailure: Alarms will be addressed on the next site visit. 07/14/2005 08:06 darren@r 01:Overrun,03:Overrun,03:TestTagFailure,04:Overrun: Alarms will be investigated on the next site visit. 07/13/2005 09:01 troy@ruf 01:Overrun,03:Overrun,03:TestTagFailure,04:Overrun: These alarms are a common 'feature' of these transceivers. PSMFC and Digital Angel are working on addressing this issue. 07/12/2005 08:02 darren@r 01:Overrun,03:Overrun,03:TestTagFailure,04:Overrun,04:TestTagFailure: Alarms will be addressed on the next site visit. 07/11/2005 08:03 darren@r 01:Overrun,03:TestTagFailure: Alarms will be investigated on the next site visit. 07/10/2005 10:45 troy@ruf 01:Overrun,03:Overrun,03:TestTagFailure,04:Overrun,04:TestTagFailure: These alarms will be addressed on the next site visit. 07/09/2005 08:49 troy@ruf 01:Overrun,03:Overrun: Noted 07/08/2005 09:44 troy@ruf 01:Overrun,01:TestTagFailure,03:Overrun,03:TestTagFailure,04:Overrun: Alarms noted. These will be addressed on the next GMC. 07/07/2005 08:14 troy@ruf 01:Overrun,02:BadOscFreq,02:LowExcCurrent,03:TestTagFailure,04:Overrun,04: TestTagFailure: This site was tuned 07/06/05. PSMFC will watch for future alarms. 07/06/2005 13:16 Alan_Bro A GMC was performed 7/6/2005. All transceivers were tuned, no problems found. 07/06/2005 08:01 scottl@r 01:LowExcCurrent,01:Overrun,01:TestTagFailure,03:Overrun,04:Overrun,04:Tes tTagFailure: Transceivers will be retuned today. 07/05/2005 08:16 troy@ruf 01:Overrun,01:TestTagFailure,03:Overrun,03:TestTagFailure,04:Overrun: Noted. These will be addressed on the next GMC. 07/05/2005 08:14 Alan_Bro Manually pushed BO405186.A1 to PTAGIS. 07/04/2005 10:34 alan@ruf 01:Overrun,01:TestTagFailure,03:Overrun,03:TestTagFailure,04:Overrun,04:Te stTagFailure: These alarms will be addressed during a GMC this week. 07/03/2005 10:36 alan@ruf 01:Overrun,01:TestTagFailure,03:Overrun,04:Overrun,04:TestTagFailure: These will be addressed during a site visit next week. 07/02/2005 10:47 alan@ruf 01:Overrun,01:TestTagFailure,03:Overrun,04:Overrun,04:TestTagFailure: These will be investigated during a site visit next week. 07/01/2005 09:02 alan@ruf 01:Overrun,01:TestTagFailure,03:Overrun,04:Overrun,04:TestTagFailure: Noted. These will be investigated during a site visit next week. 06/30/2005 08:14 scottl@r 01:Overrun,01:TestTagFailure,03:Overrun,04:Overrun,04:TestTagFailure: Errors are being addressed 06/29/2005 08:12 scottl@r 03:Overrun: Overruns do not appear to be hindering PIT detection. Scanned raw data file for interference but none detected 06/28/2005 08:26 scottl@r 01:Overrun,03:Overrun: Transceivers will be retuned on the next site visit. 06/28/2005 08:22 alan@ruf 01:Overrun,03:Overrun: These transceivers will be retuned on the next site visit. 06/27/2005 08:02 scottl@r 01:Overrun,01:TestTagFailure,03:Overrun: Transceiver 01 will re-tuned on the next site visit. Efficiencies have dropped considerably 06/26/2005 08:51 darren@r 01:Overrun,01:TestTagFailure,03:Overrun,04:Overrun: The transceivers will be adjusted on the next site visit. 06/25/2005 08:38 darren@r 01:Overrun,01:TestTagFailure,03:Overrun,04:Overrun: Alarms will addressed on the next site visit. 06/24/2005 08:47 scottl@r 01:Overrun,01:TestTagFailure,03:Overrun,04:Overrun: Overruns due not appear to be hindering detection efficiencies. Will continue to monitor situation. 06/21/2005 15:24 Dave I created a patch file to bridge the existing 11:27:00 gap in detection data on June 16-17 between BO405167.H1 and BO405168.A1. My process documentation is self-contained within the new BO405167.XX9 file. 06/21/2005 08:22 darren@r 01:Overrun,03:LowExcCurrent,04:Overrun: Alarms were addressed during site visit. 06/20/2005 08:50 darren@r 01:Overrun,03:Overrun,04:Overrun: Alarms will be investigated today during a site GMC. 06/19/2005 11:23 dlwarf@r 01:Overrun,04:Overrun: Site to be tuned tomorrow. 06/19/2005 11:23 dlwarf@r 01:Overrun,04:Overrun: Site to be tuned tomorrow. 06/17/2005 09:31 Scott_Li A power outage occurred at 21:45:13 according to the last time stamp in the .h1.tmp file. Best guess is that the outage lasted ~3 ˝ minutes. Unfortunately, the system event tracker in the 2003 server O/S reported the outage at re-boot and was asking for acknowledgement by user. Remotely accessed the platform and cleared the error and data collection resumed. In order to circumvent this in the future, “disabled” the “system event viewer” option so that this situation will not happen again. This problem was duplicated and corrected in the Kennewick lab prior to making the change on the production BO4 platform. Changed the attributes from hidden to read only on file BO4167.h1.tmp, and removed the .tmp extension. The file will be uploaded on the next interval. Data collection stopped at 21:43:13, 6/16 and resumed at 07:12:12, 6/17 PST. PTOC will be on-site early next week and can dump the buffers from the transceivers. Will consult with the data analyst prior to site visit. 06/17/2005 08:39 darren@r 01:Overrun: These alarms will be addressed on the next site visit. 06/17/2005 08:08 Alan_Bro I'm investigating the whereabouts of the tardy files. 06/17/2005 08:07 Scott_Li BO4 has not sent files since 0900 hrs on 6/16 and is being addressed. This is due to a power outage 06/16/2005 08:01 darren@r 01:Overrun,04:Overrun: Alarms will be addressed on the next site visit. 06/15/2005 08:08 darren@r 01:Overrun: Alarm will be addressed on the next site visit. 06/14/2005 16:21 Dave I created a patch file to bridge the existing 2:04:00 gap in detection data on June 9 between BO405160.D1 and BO405160.E1. My process documentation is self-contained within the new BO405160.XX9 file. 06/14/2005 09:10 scottl@r 01:Overrun,03:TestTagFailure,04:Overrun,04:TestTagFailure: Problems noted, not of concern at this time 06/13/2005 12:44 Scott_Li Downloaded buffered data from transceivers 01,02,03,04. Contents of buffers are contained in file BO405164.E1. The file is 1.883 k in size and verified that the buffered data has the asterisk at the start of each record. 06/13/2005 08:30 darren@r 01:Overrun,04:Overrun: Alarms will be investigated on the next site visit. 06/12/2005 10:52 scottl@r 04:TestTagFailure: Noted 06/10/2005 08:32 scottl@r 03:Overrun,04:Overrun: Some of the Overruns are most likely caused by fish hanging around the entrance of the PIT-tag antennas. Raw data file indicate an exceptional amount of "Hits per Fish" on all 4 of the antennas. Also may explain the lower overall detection efficienies over the last 24 hrs. General maintenance on the transceivers may also be a partial cause. 06/10/2005 08:17 Alan_Bro The platform was inadvertently taken out of data collection on 06/09/05 creating a 02:04:00 file gap. 06/09/2005 13:15 Alan_Bro A GMC was performed on 6/9/2005. All transceivers were tuned. The virtual server clock was adjusted back 00:01:51 so as to be within 1 second of atomic time. No other problems found. 06/09/2005 09:02 scottl@r 01:Overrun,04:Overrun,04:TestTagFailure: Site will be visited today for tuning of the transceivers. 06/08/2005 08:24 scottl@r 01:Overrun,04:TestTagFailure: Overruns on 01 are not excessive and TT failure on 04 is not of concern. Site will be tuned up on thursday of this week 06/07/2005 08:33 Scott_Li Antenna 03 efficiencies have dropped off , looks as is the receiver could use a tune up.. Will address on the next visit scheduled for later this week. The RAW data files indicate only about a 1 percent phase shift over a 4 degree C temperature swing in the last 12 hrs. Noise levels did not appear to change dramatically. 06/05/2005 09:40 troy@ruf 01:Overrun,04:Overrun: These coils are still performing well dispite these overruns. 06/04/2005 09:35 troy@ruf 01:Overrun,04:Overrun,04:TestTagFailure: Overrun's will be addressed on the next site visit. Test tag failures will be watched. 06/02/2005 12:35 Troy All transceivers were checked for tune, no adjustments were made. The HOBO Temp was downloaded at 12:12 PDT. A new set of temperature points was launched at 12:14 PDT. No problems to report. 05/31/2005 08:10 darren@r 01:Overrun,04:Overrun: Alarms will be addressed on the next site visit. 05/29/2005 08:39 darren@r 01:Overrun,04:Overrun,04:TestTagFailure: Alarms will be addressed on the next aite visit. 05/28/2005 08:33 darren@r 01:Overrun,01:TestTagFailure,03:Overrun,04:Overrun,04:TestTagFailure: Alarms will be addressed on the next site visit. 05/26/2005 11:16 Troy A site GMC was performed 05/26/05. All transceivers were tuned. No problems were found. A temperature monitor was installed inside transceiver 03 and launched at 16:08 DST on 05/25/05. 05/26/2005 08:10 scottl@r 01:Overrun,01:TestTagFailure: No appearent reason for the overruns or the Testtag failure, tuning looks good,noise levels are acceptable. Timertag may need slight readjustment. 05/26/2005 08:08 scottl@r 04:Overrun,04:TestTagFailure: No appearent reason for the overruns or testtag failure, tuning looks good,noise levels are acceptable. 05/26/2005 08:05 scottl@r 03:Overrun: No appearent reason for the overruns, tuning looks good,noise levels are acceptable. 05/25/2005 08:13 scottl@r 01:TestTagFailure: Nop appearent reason for the TT not to fire. Noise levels are acceptable . Will monitor. 05/25/2005 08:02 scottl@r 01:Overrun,02:Overrun,03:Overrun,04:Overrun: Overruns are not excessive at this time and do not warrant retuning of the transcievers, will continue to monitor their performance and pass information to Digital Angel. 05/23/2005 08:32 darren@r 03:Overrun,04:Overrun: These alarms will be addressed on the next site visit, which is scheduled for Thursday (5-26-05). We will monitor for additional alarms. 05/22/2005 10:31 Alan_Bro The 52-minute gap between BO405140.C1 and BO405140.D1 was caused by the platform being inadvertently taken out of data collection during Marathon Server training. 05/22/2005 10:11 alan@ruf 04:Overrun: noted 05/21/2005 09:04 alan@ruf 03:Overrun,04:Overrun: Noted 05/17/2005 08:36 darren@r 01:Overrun,01:TestTagFailure,03:Overrun,03:TestTagFailure,04:Overrun,04:Te stTagFailure: Site will be visited tomorrow for a GMC. All transceivers will be checked for tuning and noise. 05/14/2005 08:39 scottl Efficiencies for antennas 01 and 03 are lower than expected.. 03 had slight problems when tuning Per Alex from DA. Will monitor and pass this info on to DA as part of an on going effort to stabilize the system. 05/14/2005 08:27 scottl@r 01:BadExcFreq,01:BadOscFreq,01:LowExcCurrent,01:Overrun,01:TestTagFailure, 02:Overrun,03:LowExcCurrent,03:Overrun,03:TestTagFailure,04:Overrun,04:Tes tTagFailure: This info will be passed on to DA.. If problems persist, they will be corrected on the next site visit. 05/09/2005 09:03 Alan_Bro Scott manually pushed BO405127.E1 to PTAGIS via remote login. No explanation as to why this gap was created. An examination of the log file shows only successful file transfers. PTAGIS Field Operations will continue to monitor. 05/08/2005 10:15 scottl@r 02:Overrun,03:Overrun: Problem noted 05/07/2005 08:57 scottl@r 01:BadExcFreq,01:BadOscFreq,01:LowExcCurrent,02:Overrun,03:BadExcFreq,03:B adOscFreq,03:LowExcCurrent,03:Overrun,04:Overrun: Transcievera will be fine tuned earl;y next week. 05/06/2005 09:42 Alan_Bro The 25:04:00 file gap starting on 4/7/2005 was due to a power event that exceeded the duration of the battery backup on the server. This caused a reboot when power was restored. At that time Minimon was not configured to auto-interrogate. This has since been configured properly. 05/05/2005 10:57 Troy A site GMC was performed 05/05/05. Transceivers 01 and 03 were replaced with new transceivers. The temperature in the pittag room was approximately 82 Deg F. The thermostat was changed and the alarm thresholds on the marathon platform were modified. The upper threshold was decreased from 75C to 32C and the lower threshold was decreased from 20C to 10C. 05/03/2005 08:24 troy@ruf 02:Overrun,04:Overrun: The new boards are scheduled to arrive sometime this week which will hopefully eliminate these alarms. 05/02/2005 09:01 Alan_Bro The 02:46:00 file gap shown in the interrogation site status report on 4/29/2005 is not actually a gap. BO405119.D1 and BO405119.F1 create the contiguous data set during that time. File BO405119.E1 is a one minute file that was created most likely by a second instance of Minimon being invoked during our BO4 Marathon interrogation platform growing pains. Correction to my pitevent of 4/29/2005: The manually submitted file was BO405116.E1 not BO405116.F1. 05/01/2005 09:28 troy@ree 02:Overrun,04:Overrun: noted 04/30/2005 09:07 troy@ruf 02:LowExcCurrent,02:Overrun,03:Overrun,03:TestTagFailure,04:Overrun: PSMFC should be receiving new analog boards for these transceivers in the near future. Meanwhile we will continue to monitor. 04/29/2005 10:26 Alan_Bro Remotely logged into the server at BO4 and manually submitted BO405116.F1. The three minute file gap between BO405119.C1 and BO405119.D1 is due to this activity. 04/28/2005 12:18 Dave I programmatically closed the truncated BO405112.D1 file. 04/28/2005 11:43 scottl In an effort to bring up efficiencies on antenna 02 to an acceptable level, the transceiver was changed out with the xcvr from 03. With no standard transceiver available, BO3 xcvr 01 (FS-1001a) was put into BO4 antenna 03. The thought here was that a standard adult transceiver may work with the smaller style antennas, hence the reason for the swap around. Antennas 03 and 04 are of the smaller style, 01 and 2 are of the larger style. The FS1001a transceiver in 03 tuned up well and had excellent read range at the receive coil in the unit, but the concern here is that the receiver on the analog pcb may not be sensitive enough to pick the tag code from the larger RF field. Bottom line is that we have no working spare xcvrs for the slot antennas. After monitoring the activity for better part of 1.5 hrs, it became apprearent that the FS-1001a wasn't detecting fish and had little chance of any success. Re-installed the best of the two bad transceivers in antenna 03 and will hope for the best. All efforts will be made by the PTAGIS O@M group to keep this system running the best we can with what we got. Also, with Nadia's assistance, a user account was setup on the BO4 platform for the Minimon application with Auto-Login involked. this means that now if the platform shuts down for whatever reason, The interrogation software will begin collecting data with human intervention. During this process, no interrogation data was being collected. BO405118.c was stopped at 08:30:11 pst and data collection resumed at 09:39:25 file BO405118.f 04/25/2005 08:13 Scott_Li Coil 02 efficiencies are due to a noisy transceiver. Will male another attempt in tuning this unit on the next site visit. 04/24/2005 08:04 darren@r 04:Overrun: This alarm will be addressed on the next site visit by PSMFC. 04/23/2005 08:03 darren@r 01:LowExcCurrent,02:LowExcCurrent,02:Overrun,03:Overrun: PSMFC was on site yesterday to address these issues. I believe that most of these alarms were generated by PSMFC personnel. I will clear the TASS panel and monitor for future alarms. 04/22/2005 20:41 scottl The file BO405112.d attributes were unlocked and the file was manually submitted to PTAGIS at 19:40 pst. 04/22/2005 15:27 scottl In addition to the last pitevent, during the testing of the UPS, file BO405112.d was truncated at 11:45:11 PST and file BO405112.e opened at 11:51:00 PST. The .D file can and will be recovered and sent to PTAGIS. The .tmp file does exist and the .tmp was removed from the file name. Problem is that the file attributes are set to hidden thereofore Minimon does not know that the file exists. Will correct this tonight from home and submit the file. 6 minutes and 11 seconds of data cannot be recovered. 04/22/2005 15:10 scottl During the GMC, transceiver for antenna 02 was in a constant overrun state. Further investigation found the screws that hold the mother board to the aluminum backpanel were all loose. In fact, none of the 8 screws were screwed in at all. Tightned all the backpanel screws and the overruns , for the time being were suppressed. Retuned transceiver and noise levels are at ~ 1-20 % Further inspection confirmed that all 4 transceives are missing the resistors in power supply filter circuit. This was suspected and probably accounts for the elevated noise levels and instability of the transceivers. Other activities included was testing the UPS functionality. It was suspected that the UPS was not switching to battery backup during a power outage but this was not the case and was verified to operating correctly. One note is that the UPS with a 2000 watt load will only run ~ 7 minutes at the most. Per APC, auxilliary batteries can be purchase and plugged into the UPS that will extend the up time on battery power to 35 minutes. Also installed the Dell console monitor and keyboard in order to free up space in the PIT room. It was planned to create a separate user account for Minimon during this visit but due to time constraints and being a Friday , I elected not to change the platform configuration. This activity has been re-scheduled until Thursday , 4/27 so that time is not an issue in case things runamuck. No other issues to report. 04/22/2005 08:22 darren@r 01:LowExcCurrent,02:Overrun,03:Overrun,04:Overrun: PSMFC will be on site today to investigate these alarms. 04/20/2005 15:13 Scott_Li Adjusted the current alarms on transceivers 01 and 02 down to 6000 mA to avoid false alarms. 04/20/2005 07:52 scottl@r 02:LowExcCurrent,02:Overrun,03:Overrun,04:Overrun: Alarms will be addressed on Friday 4/22 during the GMC 04/18/2005 08:07 scottl@r 01:LowExcCurrent,02:LowExcCurrent,02:Overrun,03:Overrun,04:Overrun,04:Test TagFailure: Adjusted the exciter current threshold on antenna 02 to 7 Amps to avoid constant alarm messages. The displays and readers will be tuned and calibrated this Friday, 4-22-05. 04/13/2005 11:34 Troy A site GMC was performed 04/13/05. All transceivers were checked for tune. Transceiver 02's display was lock. The transceiver was turned off and then on. All transceivers were in tune, all averaging a phase of 10 signal level of 0-2. 04/11/2005 09:46 Alan_Bro Site Bio Tammy Mackey called to confirm the power outage at the AFF on 4/8/2005 around 11:00 AM. 04/11/2005 08:08 scottl@r 02:LowExcCurrent,02:Overrun,03:Overrun,04:Overrun: Still waiting on boards from DA. to help resolve this problem. 04/08/2005 08:37 Don_Warf We are currently investigating why bo4 is not sending files. More information will be posted soon. 04/05/2005 08:07 scottl@r 02:Overrun,04:Overrun: Still waiting for the replacement analog pcb's from DA in order to help solve these overrun problems. These overruns may not be caused soley by the analog pcb's, but could be unknown broadcast interference. 04/04/2005 08:06 scottl@r 02:LowExcCurrent,02:Overrun,04:Overrun: Problem is not of concern at this time. 04/01/2005 08:09 scottl@r 02:Overrun,04:Overrun: Problem not a concern at this time. 03/31/2005 08:35 alan@ruf 02:LowExcCurrent,02:Overrun,04:Overrun: Failures noted. 03/29/2005 09:32 ptagdev@ 02:LowExcCurrent,02:Overrun,04:Overrun: Testing PostMessssageOnly following URL changes. Doug 03/28/2005 08:01 scottl@r 02:LowExcCurrent,04:Overrun,04:TestTagFailure: Failures noted.. 03/27/2005 08:41 troy@ruf 02:Overrun,04:Overrun: PSMFC is waiting on new analog boards that will hopefully eliminate these types of alarms. 03/26/2005 08:35 troy@ruf 02:Overrun,04:Overrun: These alarms will be addressed on the next site visit. 03/25/2005 08:05 scottl@r 01:LowExcCurrent,02:Overrun,03:TestTagFailure,04:LowExcCurrent,04:Overrun, 04:TestTagFailure: Errors were generated by PTAGIS during a GMC. The cause of the overruns are unknown at this time but will be investigated 03/24/2005 13:18 Scott_Li Re-tuned the slot antenna transceivers in an effort to correct the timer tag problems, specifically on antennas 03 and 04. As of this e-mail ALL 4 transceivers are detecting timer tags. A few observations regarding this issue. First, the exciter voltage pot is very sensitive. In that, it's much more particular about where it' needs to be set. This is well known with the standard FS-1001A's but they dont seem near as picky as the BO4 xcvs. Second, the recieve vari-cap also is very particular about it's positioning. Third, the micro pot under the can on the analog pcb act's and looks like an equilization adjustment as on the FS-1001A's. By balancing the tuning cap,recieve cap and the micro pot, I was able to get the TT's to fire consistently. Add a grain of salt to all this, time will tell how long the tune-up will last..Also configured the RAC port on BO4- CS1 and is enabled. 03/24/2005 11:45 scottl@r 03:TestTagFailure,04:TestTagFailure: Test tags are not firing due to issues with the transceiver analog pcb. Further investigation will be conducted today while on site for a GMC 03/23/2005 08:15 scottl@r 03:TestTagFailure,04:TestTagFailure: This problem is being reported to digital Angel but still have not response.The transceivers are in an overrun and excessive noise condition and cannot be retuned to eliminate the problems. 03/20/2005 09:51 alan@ruf 03:TestTagFailure,04:TestTagFailure: PSMFC will address all these alarms on the next site visit. PSMFC is still waiting for instruction from Digital Angel on fine tuning of the new analog boards in the transceivers. These boards are due to be replaced with new boards in a few weeks. We will make every attempt to rectify these alarms on the next site visit. 03/19/2005 08:24 alan@ruf 02:Overrun,03:TestTagFailure,04:TestTagFailure: PSMFC will address all these alarms on the next site visit. PSMFC is still waiting for instruction from Digital Angel on fine tuning of the new analog boards in the transceivers. These boards are due to be replaced with new boards in a few weeks. We will make every attempt to rectify these alarms on the next site visit. 03/18/2005 08:06 darren@r 02:Overrun,02:TestTagFailure,03:Overrun,03:TestTagFailure,04:LowExcCurrent ,04:Overrun,04:TestTagFailure: PSMFC will address all these alarms on the next site visit. PSMFC is still waiting for instruction from Digital Angel on fien tuning of the new analog boards in the transceivers. These boards are due to be replaced with new boards in a few weeks. We will make every attempt to rectify these alarms on the next site visit. 03/17/2005 16:21 Dave I added pdf and jpg documents to BO4's configuration on both the production and development platforms, and created records in the respective site_diagram tables. 03/17/2005 10:00 Scott_Li The BO4 platform I/P configuration that allows multiple paths into the system at the CS and RAC level was completed yesterday. After configuring and enabling the RAC port on CS-2, CS2 was restarted. After the restart, the system indicated that that it was "transitioning". This took quite some time to complete but was finally successful and all lights were green. Per the File Load Stats and Gaps report, there is a 1 hr 28 min. gap in the data set for 3/16 that I at this time cannot explain but will be attempting to in the next couple days. Obviously, Minimon was not actively collecting data during this period and is more than likely due to the reboot of CS2. I will be working with John, Nadia and Todd in order to setup the development platform in Portland to simulate exactly the BO4 platform configuration so that questions can be answered without using the production platform. 03/16/2005 08:45 darren@r 02:Overrun,03:Overrun,03:TestTagFailure,04:Overrun,04:TestTagFailure: PSMFC will be on-site today (3-16-05) for a site GMC. 03/14/2005 15:48 Scott_Li Transceivers will be retuned tomorrow 3/15 in order to prevent Overrun messages. As we know, retuning the tranaceivers is only temporary at best. A temperature data logger will be installed in the enclosure for antenna 02. The data taken may add fuel to the idea that the analog pcb's in these units are extremely sensitive to temperature changes. 03/14/2005 15:26 Scott_Li This is only a test. 03/12/2005 07:55 darren@r 02:LowExcCurrent,02:Overrun,03:LowExcCurrent,03:Overrun,03:TestTagFailure, 04:LowExcCurrent,04:TestTagFailure: Alarms will be investigated on the next site visit. This site is still being adjusted to the enviroment to obtain the optimal detection efficiencies. PSMFC is keeping a close watch on performance and efficiencies. 03/10/2005 08:27 Scott_Li test 03/10/2005 08:12 Don_Warf TEST 03/10/2005 07:49 alan@ruf 02:Overrun,03:Overrun,04:Overrun: These alarms will be addressed during a site visit this week. 03/09/2005 09:30 ptagdev@ 02:Overrun,02:TestTagFailure,03:Overrun,04:Overrun: Testing AcknowledgeAndPost. Doug 03/09/2005 09:24 ptagdev@ 02:Overrun,02:TestTagFailure,03:Overrun,04:Overrun: Testing AcknowledgeAndPost. Doug 03/09/2005 09:01 alan@ree 02:Overrun,02:TestTagFailure,03:Overrun,04:Overrun: These alarms will be addressed during a site visit this week. 03/08/2005 16:49 ptagdev@ 02:Overrun,02:TestTagFailure,03:Overrun,04:Overrun: Testing TASS 'PostMessageOnly' for new site BO4. Doug 03/08/2005 08:19 Scott_Li Transceiver 02 was in an overrun condition for over 9 hrs yesterday afternoon from 12:30 to 9:30 pm. Attempts will be made to correct this problem on Thursday of this week, 3/10. 03/04/2005 08:32 Dave On March 2, I created a Timer Tag definitions file for BO4, and installed BO4 Timer Tag records to the ptagis.test_tags table. 03/04/2005 08:16 Scott_Li The below are snippets from the raw data file. Will continue to monitor the data files and look for a pattern as to when transceiver goes into an overrun. As of know and what we have seen so far is it appears that starting at ~ 1300 hrs some device turns on causing interference or the problem is temperature related. ~02-7 03/03/05 13:23:48 INFO PROBLEM: Overrun ~02-7 03/03/05 18:56:31 INFO PROBLEM: Overrun ~03-8 03/03/05 19:42:09 INFO PROBLEM: Overrun ~03-8 03/03/05 19:46:30 INFO PROBLEM: Overrun 03/02/2005 13:15 Scott_Li The Uploader client on the BO4 data collection computer was engaged at 1:05 pm on 3/2/05. The noise reports for all slot transceivers are set to 15 minute intervals for on going evaluation of the transceivers. The noise report will remain on for a period of ~ 1 week or until the evaluation is no longer needed. The first file submitted to PTAGIS from this new site is BO405061.L1. All previous files created were purged from the data directory due to garbled data in the file. Files were scanned to ensure no fish data existed.The file creation frequency is set for 24 files per day. This is due to an intermittent problem with the laptop rebooting for no apparent reason thus flushing the data file. The BO4 data collection computer is temporary until the new platform is installed early to late next week. 03/01/2005 16:10 Carter_S Site configuration is set up on PTAGIS server 3/1/2005. BO4 - Bonneville WA Ladder Slots --------------------------------------------------------------------- - Current Configuration -> Seq Nbr: 100 Main? N, Active? Y, Parallel_A_B? A, Poll? N Current Configuration: Seq Nbr 100 -> 28-Feb-05 To Present Comment: Initial vertical slot configuration. This system is up-stream of both BO2 and BO3. Monitors in Sort_Str sequence: Nbr 1 -> VERTICAL SLOT DETECTORS Mon_Ctgry_Str: RVR, Entry_Y_N? Y, Exit_Y_N? Y, Sort_Str: 1 (Coil,Controller): (01,01) (02,02) (03,03) (04,04) begin:vcard fn:Carter Stein n:Stein;Carter org:Pacific States Marine Fisheries Commission;PTAGIS and Columbia Basin Projects adr:Ste. 100;;205 SE Spokane St.;Portland;OR;97202-6413;USA email;internet:carters@psmfc.org title:Program Manager tel;work:503.595.3116 tel;fax:503.595.3232 tel;cell:503.709.6174 x-mozilla-html:TRUE url:http://test.ptagis.org/ptagis/ version:2.1 end:vcard 02/28/2005 13:52 PTOC_Bot TEST Message ####End of Event Log for BO4###