EVENT LOG FOR SITE MC2 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/2003 11:37 troy Files MCJ03364.108-MCJ03365.103, MC103364.H-MC103365.C,and MC203364.H- MC203365.C were manually pushed due to the PTTP uploader not being able to connect to the Portland server. All settings in the PTTP uploader were check and appear to be correct. PTOC will monitor the 12pm upload to ensure that it is working correctly. 12/15/2003 13:20 Darren_C Troy was on site to set the upload process on PC1 to manual because we were unable to PCA into site from the office. Upon arrival he found PC1 with a windows exception error (the blue screen of death) and had to reboot the PC. We were able to obtain the files to fill the time gap from PC2 but we were unable to upload the files, it appears that there may be a problem with the Walla Walla district network. The PC was set to manual upload and the files were left in the data directory for future upload when the network is ready. 11/18/2003 15:00 Scott_Li PCA'd to the sites and verified that the PTTP loader was sucessfull in transfering files during the last upload interval. No problems to report. 11/18/2003 09:11 Scott_Li PCA's into each of the sites and manually pushed files to PTAGIS. The Minimon application was stopped then restarted in order to syncronize the PTTP loader and close the current files being built. This manual process will continue up until the problems with the firewall in Gladstone are corrected. 11/17/2003 11:07 Darren_C Site was checked for loading and file generation due to the firewall issues that we have been experiencing at Gladstone. The current file is: MC203321.D and there were no files to send. 11/17/2003 09:39 Darren_C Site was checked for loading and file generation due to the firewall issues that we have been experiencing at Gladstone. The current file is: MC203321.D and there were no files to send. 11/15/2003 14:26 Dave The ftp.pittag.org server failed at 11:15 AM. Coincident with this failure, interrogation site data files were not received at noon today. The FTP server was restored at 1:35 PM. Subsequently, I manually retrieved all outstanding files from the active interrogation sites maintained by PSMFC (BO1, BO2, BO3, MC1, MC2, IHA, and GRA). At BO3, PTTP-Uploader was observed to be in a suspended state. This was corrected. No problems were observed at the other sites polled. No data were lost at any site. 11/14/2003 14:28 Alan_Bro I PCA'd into these sites to assess the file loading of these sites. I found BO1 and MC2 in a normal state. BO2 and MC1 had not changed or uploaded files since yesterday. I stopped and restarted Minimon, verified that all data had been collected properly, and sent the files to PTAGIS. BO3 was manually sent by Darren as he was onsite. IHA and GRA were fixed by Scott this morning. We are continuing to monitor these sites as well as the inactive sites for proper file changes and uploads. 11/06/2003 15:41 Alan A GMC was performed 11-6-2003. All transceivers were tuned. No problems found. 10/25/2003 09:37 alan@ree 02:LowExcCurrent: No apparent cause for this alarm, PTOC will continue to monitor. 10/23/2003 12:38 Darren Asite gmc was performed on all adult transceivers. The noise levels and tuning was checked and no problems were found. 10/21/2003 09:16 darren@r 02:ExcessiveNoise,04:ExcessiveNoise: Noise levels and tune wil be checked on the next site visit. 10/20/2003 08:26 alan@ree 02:BadExcFreq: No apparent reason for this failure. We investigate further during a GMC this week. 10/13/2003 08:15 Scott_Li PCA'd into MC2PC1 and manually sent the data files that were missing from this mornings report. No explanation why the PTTP client did not sent at the 0600 interval. 10/12/2003 09:32 darren@r 02:BadOscFreq: PTOC personnel check this out on Thursday during site GMC and could not find any direct cause other than a minor glitch from transceiver 04. The two transceivers have a sync cable between them.We will investigate on the next site visit. 10/09/2003 16:24 Darren Site GMC's were performed. All transceivers were checked for tuning and noise. No Problems were found. 10/08/2003 08:23 darren@r 02:BadExcFreq: The badExcFreq alarm occurred after the timer tag was fired. I do not know what meaning this has but I will be on site thursday so I will check this out. 09/29/2003 09:06 alan@ruf 02:BadOscFreq: No apparent cause for this alarm. This coil is synchronized with Coil 04. PTOC will continue to monitor and investigate on the next site visit. 09/26/2003 08:50 Don_Warf Site did not send files this morning. PCAed in to verify data collection and manually sent files. 09/22/2003 12:42 scottl Gmc on both sites found no problems to report. All transceivers were checked for calibration. 09/08/2003 08:39 darren@r 02:BadExcFreq: There does not appear to be any direct cause for this alarm. PTOC personnel will check all conditions on the next site visit. 09/04/2003 15:36 PTOC_Bot A GMC was performed 9-4-2003. All transceivers were tuned, no problems found. 08/20/2003 11:17 Alan A GMC was performed 8/19/2003. All transcievers were tuned and checked for issues since the last visit. No problems found. 08/02/2003 11:02 alan@ruf 09:TestTagFailure: Unknown why this test tag failed one time. PTOC will continue to monitor. 07/31/2003 15:39 PTOC_Bot A GMC was performed 7/31/2003. All transcievers were tuned. 07/31/2003 08:38 alan@ruf 0F:LowExcCurrent,0F:Overrun,10:LowExcCurrent: I will look at these today during a GMC. 07/21/2003 08:28 scottl@r 02:BadOscFreq,10:LowExcCurrent: Alarms not of concern 07/17/2003 15:33 Alan FYI: During a GMC 6-26-2003 I installed sync cables between coils 02 & 04, 05 & 07, and 0E & 10 making three pairs of synchronized transceivers. This was found to be beneficial in reducing noise. The other transceiver pairs were not improved by being synchronized so they were left as is. 07/10/2003 08:11 alan@ree 02:BadOscFreq: The alarm was noted. There appears to be no reason. PTOC will investigate on the next site visit. 07/01/2003 16:17 scott_li Reinstalled the original analog pcb's that were modified with NPO style capacitors at MC1 and retuned. Swapped out all analog pcb's with the loaner pcb's at MC2 until the originals can be modified with the NPO style caps. Per Darren and Dan (DA) the lead time for this mod may be several months due the long lead time from the cap manufacturer. 06/27/2003 14:23 alan@ruf 02:LowExcCurrent,0B:BadOscFreq,0B:LowExcCurrent,0E:LowExcCurrent,0F:LowExc Current: These alarms were generated by PTOC personel during a site visit. 06/26/2003 15:06 darren@r 07:LowExcCurrent: Alarm was generated by PTOC personnel while performing a GMC. 06/25/2003 15:09 troy@ree 0C:TestTagFailure,0D:TestTagFailure,0E:TestTagFailure,0F:TestTagFailure: PTOC personel will be on site 06/26/03 to take a closer look at this. The test tag failures ceased after the readers were toggled from scan to standby and back to scan from a PCA session on 06/24/03. When the hit rate was test all but OF showed 100% but a single shot test failed every time for each transciever. These timer tags started failing 6/19/03 around 17:34. In this time period fish tags were still being read. 06/24/2003 08:36 Darren A site maintenance GMC was performed on 6/18/03. No problems found. 06/23/2003 13:39 Dave Uploaded MC203170.E9 and F9, containing excerpts from the MC2-PC2 versions of the MC203170.E and F files, to patch a 100-minute hole in data collection on MC2-PC1. 06/20/2003 08:27 scott_li The primary interrogation computers were reconfigured with new DNS I/P addresses yesterday afternoon in order to satisfy the latest COE firewall rules that were implemented on or around 6/17/03. Due to this reconfig, the primary computers had to be rebooted in order for the setting to take effect and therefore creating a gap in the data set. All efforts were made to minimize this gap and efforts will be made today to restore the missing records . 06/04/2003 08:39 Darren_C All sites were visited and GMC's were performed. All the analog boards that were replaced at MC1 were retuned and timer tag hit rates were checked. No problems found. 05/30/2003 22:11 darren@r 03:LowExcCurrent,04:LowExcCurrent,04:Overrun,05:LowExcCurrent,0F:LowExcCur rent: All alarms were generated by PTOC personnel while performing site GMC. 05/12/2003 22:50 D._Chase Today Site GMC's were performed. All transceivers were checked for tune. No problems were found. 05/07/2003 09:27 Scott_Li A GMC was performed on 5/7. Transceivers were checked for optimum tune, no significant problems to report. The PTTP interface on MC1-PC1 was reconfigured in order to Syncronize on the hour and the AboutTime NIST app. configuration was also checked for accuracy. No changes to this application were made. Suggestions about how to effectively use the AboutTime App. will be discussed within ithe PTOC group via e-mail. 05/01/2003 10:45 scottl@r 01:ExcessiveNoise,02:ExcessiveNoise,03:ExcessiveNoise,04:ExcessiveNoise,06 :ExcessiveNoise,08:ExcessiveNoise,0A:ExcessiveNoise,0B:ExcessiveNoise,0C:E xcessiveNoise,10:ExcessiveNoise: Clearing Tass in order to get a more recent account of noise events. Coil 02 and 04 is of concern. 04/30/2003 16:49 Alan I performed a GMC on these sites 4/29/2003. Transceivers were checked for tune and any major concerns that have been noted since the last visit. No problems were found. 04/24/2003 16:34 Alan I performed a GMC on these three sites today. Transceivers were checked for tune and any major concerns that have been noted since the last visit. I replaced the transceiver for coil 10 at MC1 to narrow down the possibilities for our noise problems there. PTOC will continue to monitor that coil. No problems were found. 04/17/2003 13:55 scottl A GMC was performed 4/16/03. no prblems to report. all xcvrs were checked for tune and optimized if nessesary. 04/17/2003 11:52 darren@r 09:TestTagFailure: This transceiver was addressed on yesterday's site visit. 04/16/2003 12:46 scottl@r 03:ExcessiveNoise,04:ExcessiveNoise,08:ExcessiveNoise,0C:ExcessiveNoise,0F :ExcessiveNoise,10:ExcessiveNoise: A site visit is scheduled for today. Will retune Coil 03,04 04/11/2003 07:58 Darren_C These sites were visited yesterday for general maintenance checks all transceivers were checked for tuning and the gates at the JFF were checked for timing. We changed all Adult transceivers timer tag delays to 61 minutes to try and avoid the timer tag and status report being sent at the same time. This may put a damper on some of the timer tag failures. If this works we will implement this on all adult transceivers. No problems were found. 04/06/2003 09:19 Darren_C The file MC203095.H that appears to be missing in the "load status" report is indeed in the "raw files" report. This is the third file that is being reported as missing but in fact has been received and loaded. 03/28/2003 12:53 darren@p 09:TestTagFailure: Site was visited today for a maintenance check. There were no problems discovered. This unit was in tune and no noise was seen. We will monitor for further alarms. 03/28/2003 12:50 Darren The site was visited for a maintenance check today. All transceivers were checked for tuning and adjusted if neccessary. No problems were discovered. 03/17/2003 09:37 alan@psm 09:TestTagFailure: ~09-5 03/15/03 03:50:30 ALARM PROBLEM: Test Tag Failed No apparent reason for failure. We will investigate during our next General Maintenance Check. 03/14/2003 11:15 Scott_Li Reviewed entire status of these sites and did not detect any significant events that warrants attention. 03/14/2003 09:20 darren@p 09:TestTagFailure,0A:TestTagFailure: There does not seem to be any apparent reason for the tag failure. We will check on the next site visit. 03/13/2003 09:00 darren@p 09:TestTagFailure,10:LowExcCurrent: The LowExcCurrent alarm on antenna 10 is valid in that the current has dropped .3A I will adjust the current alarm to avoid furhter alarms and will check the antenna on next visit. 03/07/2003 14:47 Dave I updated the ptagis3.test_tags table to associate each (previously- missing) coil_id value with each virtual timer tag at this site. This essentially enables the validation routines for the Timer Tag reports. 03/07/2003 09:04 darren@p 09:TestTagFailure: No apparent reason for failure. We will check on next scheduled site visit. 03/05/2003 09:03 darren@p 09:TestTagFailure: Alarm was checked. No immediate fialures noticed. Will monitor for future alarms. 02/27/2003 08:51 darren@p 09:TestTagFailure: Will investigate this problem on the next site visit. 02/14/2003 09:09 darren@p 09:TestTagFailure: Alarm has no significant failure. We will monitor for future failures. 02/10/2003 11:24 darren@p 03:LowExcCurrent,06:LowExcCurrent,06:TestTagFailure,07:LowExcCurrent,08:Ov errun,09:TestTagFailure,0A:BadExcFreq,0A:BadOscFreq,0A:LowExcCurrent,0B:Lo wExcCurrent,0F:LowExcCurrent,0F:Overrun,0F:TestTagFailure,10:TestTagFailur e: All alarms were generated by PSMFC personnel while performing site tuning for upcoming season. 02/10/2003 11:20 Darren_C On Friday 2-7-03 all transceivers were fine tuned and the buffers cleared for the upcoming 2003 season. The data collection platform was also tuned. The 2002 data was archived and only data from 2-3-03 on is being sent and archived, this was the actual water up date. While performing the fine tune a fiber was broken but it will be repaired today. 02/05/2003 10:44 darren@p 06:TestTagFailure,0E:TestTagFailure,10:TestTagFailure: This site was watered up on 2-3-03 at 09:30. The transceivers were placed back into "scan" mode on Tuesday 2-4-03 at about 10:30. This site will be fine tuned today. 02/04/2003 09:51 PTOC_Bot We were informed today by Brad Eby that this site was watered up at 10:30 yesterday morning. I PCA'd in to the site and returned readers to read from standby. The 2003 season began with file number MC203035.C. 01/23/2003 15:25 Dave Brad Eby informed us that the Washington Shore Ladder was dewatered the morning of January 6. The Corps plans to rewater on February 3. 01/07/2003 08:47 scottl@p 01:LowExcCurrent,03:LowExcCurrent,05:LowExcCurrent,06:LowExcCurrent,07:Low ExcCurrent,08:LowExcCurrent,08:Overrun,09:LowExcCurrent,09:TestTagFailure, 0A:LowExcCurrent,0B:LowExcCurrent,0C:LowExcCurrent,0D:LowExcCurrent,0E:Low ExcCurrent,10:LowExcCurrent: Event log has been updated. 01/07/2003 08:46 Scott_Li Changed current alarm thresholds from 3600 mA to 3300 mA. The transceivers need to be retuned . Will retune on the next site visit. All other alarms on the tass are not of immediate concern. Cleared tass panel. 01/03/2003 08:33 darren@p 09:TestTagFailure: Alarm may have been caused by the timer tag firing and the status report being sent by the transceiver. I tried to alter this time frame but it does not appear to have worked. 01/02/2003 11:17 darren@p 08:TestTagFailure,09:TestTagFailure: These alarms may be caused by the status report and the timer tag firing coinciding. I will PCA into the site to shift the time frame of the staus report being sent. 01/01/2003 12:19 Dave Initialized new event log for 2003. 2002 event log has been archived. ####End of Event Log for MC2###