EVENT LOG FOR SITE MC1 The first line of each entry contains a date/time stamp & who is reporting. The most recent entry is listed first. Date Time Who ---------- ----- -------- 12/29/2009 07:24 troy@bay 10:LowExcCurrent: This will be addressed on the next GMC. 12/29/2009 07:15 Troy Manually pushed the delinquent file. 12/28/2009 07:24 troy@bay 10:LowExcCurrent: This alarm will be addressed on the next site visit. If tuning doesn't raise the current then the current alarm threshold will be lowered. 12/24/2009 08:19 troy@bay 10:LowExcCurrent: Noted 12/15/2009 07:49 darren@b 10:LowExcCurrent: This system will be addressed during the next site visit. 12/14/2009 07:34 troy@bay 10:LowExcCurrent: This is most likely tune related and will be addressed on the next site visit. 12/12/2009 07:45 darren@b 0D:TestTagFailure: This system will be investigated during the next site visit. 12/11/2009 07:36 darren@b 04:TestTagFailure,0D:TestTagFailure: These sytems will be addressed during the next site visit. 12/10/2009 07:19 darren@b 0D:TestTagFailure,10:LowExcCurrent: These systems will be investigated during the next site visit. 12/09/2009 07:42 darren@b 0D:TestTagFailure: This system will be investigated during the next site visit. 12/07/2009 08:25 darren@b 10:LowExcCurrent: The alarm threshold level and the current level are equal. I will adjust the threshold to mitigate the alarms. The system will be investigated during the next site visit. 12/03/2009 07:08 alan@bay 01:LowExcCurrent,01:TestTagFailure,02:LowExcCurrent,02:Overrun,02:TestTagF ailure: These alarms were generated by PTAGIS Field Operations personnel during a site visit. 11/24/2009 07:01 scottl@b 01:LowExcCurrent,02:LowExcCurrent,02:Overrun: Alarms were addressed during the recent GMC, Clearing TASS 11/23/2009 14:08 scottl Performed site GMC, all transceivers were re tuned and calibrated as necessary. CW antenna 01 has elevated noise levels into the 20 to 30 percent. Swapped antenna cables in order to isolate were the issue lyes and the problem points away from the transceiver. Water levels through the antennas are higher than normal but the flow is very flat with little turbulence. Suggest that maybe the cap bank is having issues, cable?? and that this be further evaluated when the opportunity arises. 11/23/2009 10:18 Don_Warf DLW email test _____________________________________________ From: Don Warf Sent: Monday, November 23, 2009 9:26 AM To: 'pitevent@psmfc.org'; 'pitevent@ptagis.org' Subject: gra,grj,goj,rpj,lmj,ich,mcj,mc1,mc2,jdj,pro,esj,jcj,cfj,bcc,bo1,bo2,bo3,b2 j,rzf Email test 11/23/2009 09:39 Troy_Hum Email Test from Troy 11/10/2009 14:34 Troy Voltage to Neutral to Ground .108 VAC. The 'Building Wiring Fault' light on the back of the UPS's is NOT on. 10/22/2009 07:14 scottl@b 01:LowExcCurrent,01:Overrun,02:LowExcCurrent,02:Overrun: A GMC was performed yesterday, clearing TASS. 10/21/2009 11:20 Alan A GMC was performed 10-21-2009. All transceivers were checked and tuned as necessary. 01 is showing noise into the teens due to accumulations in the trash rack. Outstanding files on PC2 were archived. The clocks on both PCs are within one second of atomic time, no other problems found. 10/15/2009 13:50 Alan Eastern Oregon Telecom reports a problem with their equipment. The resultant connectivity issue is causing file uploads to fail. PTAGIS Field Operations will continue to monitor. 10/14/2009 13:46 alan@bay 02:LowExcCurrent,02:TestTagFailure: This will be addressed during the next site visit. 09/29/2009 14:33 scottl Performed site GMC, all transceivers were retuned and calibrated as necessary, no problems to report. 09/18/2009 13:58 scottl performed site GMC all transcievers were retuned and calibrated as necessary, no problems to report 09/18/2009 07:52 troy@bay 09:HighTemp,10:Overrun: 09's alarm common for this time of year. 10 has experience 1 overrun a day for the last week. This one occured at 14:57:20. 09/17/2009 07:47 troy@bay 10:Overrun: No known cause for this alam. Antenna still reading fish at a high efficiency. 09/16/2009 12:42 troy@bay 10:Overrun: Noted. 09/15/2009 07:45 troy@bay 10:LowExcCurrent,10:Overrun: The current was operating 100mA below the current alarm threshold. The current alarm threshold was lowered remotely. 09/14/2009 07:53 troy@bay 10:LowExcCurrent,10:Overrun: This transceiver may be in need of a tune as it's current level is bouncing between acceptable and low exciter current. PSMFC will monitor and may make adjustments to the low exciter current remotely. 09/05/2009 08:14 darren@b 10:Overrun: This alarm is being monitored and addressed. Several things have been tried to alleviate the "overrun" conditions. These conditions have not affected the overall efficiencies of the system. 09/04/2009 10:48 Don_Warf Manually pushed late file. 09/03/2009 07:12 darren@b 11:LowExcCurrent: Alarm was addressed yesterday during site GMC. 09/02/2009 15:17 scottl Performed site GMC, all transcievers were retuned and calibrated as necessary, no problems to report. Rest paramters on MC1 10 in order to correct overrun conditions but was unsuccessful. Slide gate air pressures are at 100 psi on both A and B gates, cycled gates and all is normal. 09/02/2009 14:31 scottl All PTAGIS data collection computers and utility pc's were reconfigured and put on the new wireless network that separates PTAGIS PC's from the USACE network. All equipment e.g., switches, converters etc.. that were used on the USACE network were left in place in the event that we needed to revert back to COE network for whatever reason. PCA sessions were tested at each site , in particular MCJ SBC PC's and seemed to perform well. More thorough testing will be done in the next few weeks. 09/02/2009 07:15 darren@b 0C:HighTemp,10:LowExcCurrent,10:Overrun,11:LowExcCurrent: These alarms will be addressed during the next site visit. 09/01/2009 07:10 darren@b 10:Overrun: Alarm will be addressed during the next site visit. 08/31/2009 07:55 darren@b 10:Overrun: This alarm will be addressed during the next site visit. 08/28/2009 07:47 troy@bay 10:Overrun: Noted 08/26/2009 08:06 troy@bay 10:Overrun: This will be looked into on the next site visit. 08/25/2009 08:12 troy@bay 10:Overrun: Unclear as to the cause of the overruns. This transceiver's reading efficiency is in line with the transcievers above and below it. PSMFC will continue to monitor. 08/21/2009 07:49 alan@bay 10:LowExcCurrent,10:Overrun: Alarm will be investigated during the next site visit. This transceiver is reading PIT tags and timer tags well. 08/20/2009 12:59 Darren A site GMC was performed today 8-20-09. All transceivers were checked and adjusted for tuning, noise, and detectability. No problems were discovered during this visit. I adjusted the Power Supply on transceiver 10 to try and eliminate the few "overrun" conditions that have been appearing in TASS. 08/20/2009 07:58 alan@bay 10:Overrun: This alarm will be investigated during a site visit today. 08/19/2009 07:55 alan@bay 10:Overrun: Alarm will be investigated during the next site visit. This transceiver is reading PIT tags and timer tags well. 08/18/2009 07:51 alan@bay 03:LowExcCurrent,08:LowExcCurrent,10:Overrun,11:LowExcCurrent: These alarms will be investigated during the next site visit. 08/13/2009 07:44 alan@bay 10:Overrun: Alarm will be investigated during the next site visit. This transceiver is reading PIT tags and timer tags well. 08/12/2009 07:55 alan@bay 10:Overrun: Alarm will be investigated during the next site visit. This transceiver is reading PIT tags and timer tags well. 08/11/2009 07:44 alan@bay 10:Overrun: Alarm will be investigated during the next site visit. This Transceiver is reading PIT tags well. 08/10/2009 07:45 alan@bay 10:Overrun: Alarm will be investigated during the next site visit. 08/08/2009 08:50 darren@b 10:Overrun: Alarm will be investigated during the next site visit. 08/06/2009 13:55 scottl Performed site GMC, all transceivers were retuned and calibrated as necessary, no problems to report. 08/04/2009 07:25 darren@b 10:Overrun: Alarm will be addressed during the next site GMC. 08/03/2009 08:14 alan@bay 10:Overrun: This will be investigated during a site visit this week. This transceiver is reading PIT tags well. 07/30/2009 10:10 troy@bay 10:Overrun: This will be investigated on the next site visit. 07/29/2009 08:33 troy@bay 10:Overrun: This alarm will be investigated on the next site visit. 07/26/2009 09:13 darren@b 10:Overrun: This alarm will be investigated on the next site visit. 07/25/2009 09:20 darren@b 10:Overrun: Alarm will be investigated on the next site visit. 07/23/2009 14:18 Alan A GMC was performed 7/23/2009. All transceivers were checked and tuned as necessary. The files on PC2 were archived. The clocks on both PCs were set to within one second of atomic time. No undocumented problems found. 07/23/2009 10:19 darren@b 0C:HighTemp,10:Overrun: The overrun alarms on antenna 10 will be investigated during today's site GMC. The high temp alarm is to be expected at this time of year. 07/16/2009 09:02 darren@b 02:LowExcCurrent,10:Overrun: The current alarm threshold on 02 was adjusted to 400mA below the actual current. There was not direct cause for the "overrun" alarms on antenna 18. PSMFC will monitor for future alarms on this antenna. 07/15/2009 11:07 scottl Performed site GMC, all transceivers were retuned and calibrated as necessary, no problems to report. 07/12/2009 09:24 troy@bay 10:Overrun: This will be investigated on the next site visit. 07/11/2009 09:52 troy@bay 10:Overrun: Noted 07/11/2009 09:51 troy@bay 0B:TestTagFailure: This transceiver has been turned off. Clearing TASS. 07/11/2009 09:50 troy@bay 02:LowExcCurrent: No obvious reason for this alarm. The reports don't show the current dropping.PSMFC will monitor. 07/10/2009 15:44 Troy Manually pushed the delinquent file. 07/10/2009 14:30 Troy A site GMC was performed 07/10/2009. All transceivers were checked for tune and adjustments made where needed. PC1 and PC2 were set to with in 1 second of atomic time and each other. The 'temp' directory was emptied on each computer. The following is the sync configuration: 03,04,05,06 No sync cables 08 to 07, 07 to 09, 09 to 0A. 0B(off) to 0C, 0C to OD, 0D to OE. 0F,10,11,12 No sync cables OB was turned off and it's exciter cable removed from the transceiver as there is a problem below the water line. The transceiver was only able to generate .6A and was not reading pit tags. No other problems to report. 07/10/2009 08:51 darren@b 0B:Overrun,0B:TestTagFailure: Alarms on a known problematic system. 07/09/2009 09:14 darren@b 09:LowTemp,0B:Overrun,0B:TestTagFailure: The alarm on 09 may be caused by a failing thermistor. PSMFC will monitor for future alarms. The alarms on 0B are on a known problematic system. 07/08/2009 08:13 darren@b 0B:TestTagFailure: Alarm on problematic system. 07/07/2009 08:21 darren@b 0B:TestTagFailure: Alarm on known problematic system. 07/07/2009 08:15 scottl@b 02:LowExcCurrent: Noted, will adjust on next scheduled site visit. 07/06/2009 10:05 alan@bay 0B:Overrun,0B:TestTagFailure: Clearing TASS on a known problematic system. 07/06/2009 10:05 alan@bay 02:LowExcCurrent: This transceiver is reading PIT tags well and appears in tune. The current was at 4.1A and threshold was set to 4000mA. The threshold was remotely lowered to 3800mA. This will be investigated during the next site visit. 07/05/2009 09:20 troy@bay 10:Overrun: PSMFC will investigate on next site visit. 07/05/2009 09:20 troy@bay 02:LowExcCurrent: It appears the current has dropped slightly. PSMFC will investigate on the next site visit. 07/04/2009 09:09 troy@bay 0B:Overrun,0B:TestTagFailure,10:Overrun: Clearing TASS on known problematic systems. 07/03/2009 08:38 troy@bay 0B:Overrun,0B:TestTagFailure,10:Overrun: These alarms will be investigated on the next GMC. 07/02/2009 08:57 alan@bay 0B:Overrun,0B:TestTagFailure: Clearing TASS on a known problematic system. 07/01/2009 11:49 Darren A site GMC was performed today 7-1-09. All transceivers were checked for tuning, noise, and detectability and adjusted as necessary. No problems were discovered during this visit. 06/28/2009 08:29 alan@bay 0B:Overrun,0B:TestTagFailure: Clearing TASS on a known problematic system. 06/28/2009 08:28 alan@bay 10:Overrun: No apparent reason for this alarm. PTAGIS Field Operations will continue to monitor. 06/27/2009 08:08 alan@bay 0B:Overrun,0B:TestTagFailure: Clearing TASS on a known problematic system. 06/26/2009 08:36 alan@bay 0B:Overrun,0B:TestTagFailure,0C:HighTemp: 0B - clearing TASS on a known problematic system. 0C - Hi temp noted. 06/25/2009 08:48 alan@bay 0B:Overrun,0B:TestTagFailure: Clearing TASS on a known problematic system. 06/24/2009 12:15 Darren A site GMC was performed today 6-24-09. All transceivers were checked for tuning, noise, and detectability and were adjusted as necessary. No problems were discovered during this visit. 06/24/2009 08:13 Scott_Li Manually pushed delinquent data file 09175.B , no apparent reason for the missed upload. 06/22/2009 09:09 alan@bay 0B:TestTagFailure: Clearing TASS on a known problematic system. 06/21/2009 08:45 darren@b 0B:TestTagFailure: This alarm is on a known problematic system. 06/20/2009 09:05 darren@b 0B:TestTagFailure: Alarm on problematic system. 06/19/2009 08:16 darren@b 0B:LowExcCurrent,0B:Overrun,0B:TestTagFailure: Alarm on known problematic system. 06/18/2009 12:50 Alan A GMC was performed 6/18/2009. All transceivers were checked and tuned as necessary. The files on PC2 were archived. The clocks on both PCs were set to within one second of atomic time. No undocumented problems found. 06/18/2009 08:10 darren@b 0B:Overrun,0B:TestTagFailure: Alarm on problematic system. 06/16/2009 08:00 darren@b 0B:Overrun,0B:TestTagFailure: Alarm occurred on a known problematic system. 06/15/2009 10:02 darren@b 0B:Overrun,0B:TestTagFailure: Alarms are on a known problematic system. 06/09/2009 15:14 Alan A GMC was performed 6/9/2009. All transceivers were checked and tuned as necessary. The files on PC2 were archived. The clocks on both PCs were set to within one second of atomic time. No undocumented problems found. 06/08/2009 08:13 darren@b 0B:TestTagFailure: These alarms are on a known problematic system. 06/07/2009 10:26 troy@bay 0B:TestTagFailure: Clearing TASS on a known problematic system. 06/06/2009 09:50 troy@bay 0B:Overrun,0B:TestTagFailure: Clearing TASS on a know problematic system. 06/02/2009 13:14 Darren A site GMC was performed today 6-2-09. All transceivers were checked for tuning, noise, and detectability. No problems were discovered during this visit. The corp fiber is all terminated with the only spare pair being the GRN/BRN. The CW is utilizing the Red/SLT fibers for their comms. 06/02/2009 08:32 troy@bay 0B:Overrun,0B:TestTagFailure,10:Overrun: These alarms will be investigated on the next site visit. 06/01/2009 08:21 troy@bay 0B:Overrun,0B:TestTagFailure,10:Overrun: These alarms will be addressed on the next site visit. 05/31/2009 09:41 alan@bay 0B:Overrun,0B:TestTagFailure,10:Overrun: These alarms will be investigated during the next site visit. 05/30/2009 11:02 alan@bay 0B:Overrun,0B:TestTagFailure: Clearing TASS on a known problematic system. 05/29/2009 08:46 alan@bay 0B:Overrun,0B:TestTagFailure: Clearing TASS on a known problematic system. 05/28/2009 09:10 alan@bay 0B:Overrun,0B:TestTagFailure: Clearing TASS on a known problematic system. 05/26/2009 13:20 Alan A GMC was performed 5/26/2009. All transceivers were checked and tuned as necessary. The files on PC2 were archived. The clocks on both PCs were set to within one second of atomic time. No undocumented problems found. 05/26/2009 09:36 alan@bay 0B:Overrun,0B:TestTagFailure: Clearing TASS on a known problematic system. 05/22/2009 08:42 darren@b 0B:TestTagFailure: Alarm on known problematic system. 05/19/2009 12:03 scottl Performed site GMC, all transceivers were retuned and calibrated as necessary, no problems to report. 05/19/2009 08:02 scottl@b 02:LowExcCurrent,0B:Overrun,0B:TestTagFailure: A GMC is scheduled for today, will make corrections as necessary. 05/18/2009 09:49 darren@b 0B:Overrun,0B:TestTagFailure: Alarm on problematic system. 05/17/2009 08:45 darren@b 0B:TestTagFailure,0C:LowTemp: The alarms on antenna 0B are a known problem system. The low temp on 0C will be checked during the next GMC. 05/16/2009 08:06 darren@b 0B:TestTagFailure,0C:TestTagFailure: Alarms on antenna 0B are on a known problematic system. The alarm on antenna 0C will be investigated during the next site visit. 05/15/2009 08:25 troy@bay 09:HighTemp,0B:LowExcCurrent,0B:TestTagFailure: High temp is un-common for this time of year. PSMFC will monitor. OB is a known problematic system. 05/13/2009 12:06 scottl Performed site GMC, all transceivers were tuned and calibrated as necessary. No problems to report. 05/12/2009 08:33 alan@bay 0B:TestTagFailure: Clearing TASS on a known problematic system. 05/11/2009 08:48 darren@b 0B:TestTagFailure: Alarm on problematic system. 05/10/2009 08:53 troy@bay 0B:TestTagFailure: Known problem, clearing TASS. 05/09/2009 09:42 troy@bay 0B:TestTagFailure: Known issue on problematic system, clearing TASS. 05/08/2009 09:14 troy@bay 0B:TestTagFailure: Clearing TASS on a known problematic system. 05/07/2009 09:52 alan@bay 0B:TestTagFailure: Clearing TASS on a known problematic system. 05/07/2009 09:51 alan@bay 11:LowExcCurrent: No apparent reason for this alarm. PTAGIS Field Operations will continue to monitor. 05/06/2009 11:59 Darren A site GMC was performed today 5-6-09. All transceivers were checked for tuning and noise. No problems were discovered during this visit. 05/06/2009 08:45 darren@b 0B:TestTagFailure: Alarm on problematic system. 05/04/2009 10:17 troy@bay 0B:TestTagFailure: Noted. 05/03/2009 08:24 darren@b 0B:TestTagFailure: Alarm on problematic system. 05/02/2009 08:44 darren@b 0B:TestTagFailure: Alarm on problematic system. 04/30/2009 07:44 darren@b 0B:TestTagFailure: Alarm on problematic system. 04/29/2009 08:07 darren@b 0B:TestTagFailure: Alarm on problematic system. 04/28/2009 08:22 darren@b 0B:LowExcCurrent,0B:TestTagFailure,0D:LowExcCurrent: Alarms on 0B are on a known problematic system. The alarm on 0D was generated during a site GMC. 04/27/2009 16:17 Alan The site bio reports that the USACE network is having issues. The platforms have been verified to be collecting data. No ETA was mentioned for communications resolution. 04/27/2009 13:42 scottl Perfroemd site GMC, all transcievers were retuned and calibrated as necessary, no unknown problems to report. FYI that the network connection to the outside world is not working. The internal connection to the COE router and all other PIT-tag rooms is OK, so the problem is on the WAN side of COE router. Alan is in the process of contacting the COE IT services in order to restore the connection. 04/27/2009 09:46 alan@bay 0B:TestTagFailure: Clearing TASS on a known problematic system. 04/26/2009 10:52 alan@bay 0B:TestTagFailure: Clearing TASS on a known problematic system. 04/25/2009 11:10 alan@bay 0B:TestTagFailure: Clearing TASS on a known problematic system. 04/24/2009 08:18 alan@bay 0B:TestTagFailure: Clearing TASS on a known problematic system. 04/23/2009 10:46 darren@b 02:TestTagFailure,0B:LowExcCurrent,0B:TestTagFailure: Alarms on 02 were addressed during a site GMC. Antenna 0B is a problematic system. 04/22/2009 13:40 Alan A GMC was performed 4/22/2009. All transceivers were checked and tuned as necessary. The files on PC2 were archived. The clocks on both PCs were set to within one second of atomic time. No undocumented problems found. 04/16/2009 13:12 Troy A site GMC was performed 04/16/2009. The water level at the counting window was ~6" higher than it was on the last GMC. I spoke with the site biologist about this and he stated that they are working to replace the outdated controls but does not know when this will be completed. While checking the site I noticed that the down stream antenna (02) was experiencing periodic noise spikes of 100%. I also noticed that the incandescent lights had been replaced with self ballasting florescent lights. I had all the lights shut off and this didn't help. I went up to the top of the antenna and I noticed the window gate was low enough that water was causing it to bang in it's guide channel. I raised the gate and wedge sticks in the gap to keep the gate from banging. This eliminated the noise spikes. The mysterious noise on the middle coils of the lower ladder was not present when I performed this GMC. No other problems to report. 04/13/2009 08:06 scottl@b 0B:TestTagFailure: Problem will be addressed on the next scheduled site GMC 04/12/2009 08:04 alan@bay 0B:TestTagFailure: Clearing TASS on a known problematic system. 04/11/2009 10:05 alan@bay 0B:TestTagFailure: Clearing TASS on a known problematic system. 04/10/2009 12:18 Troy A site GMC was performed 04/10/2009. All transceivers were checked for tune and adjustments made where needed. I noticed the water level was a little low in the counting window. Fish counting personnel stated that the automatic level control was broken and that operators were making adjustments when they could, usually every 3-4 hours. This may effect the performance of 01 and 02. There is still some noise on the middle eight transceivers which cannot be tuned out. The upper 4 and lower 4 antennas don't seem to be effected by whatever is causing the noise. 04/10/2009 09:11 alan@bay 02:TestTagFailure,0B:TestTagFailure: These alarms will be investigated today during a site visit. 04/09/2009 08:38 alan@bay 0B:TestTagFailure: Clearing TASS on a known problematic system. 04/08/2009 12:01 alan@bay 0B:TestTagFailure: Clearing TASS on a known problematic system. 04/07/2009 08:31 alan@bay 0B:TestTagFailure: Clearing TASS on a known problematic system. 04/06/2009 08:40 alan@bay 0B:TestTagFailure: Clearing TASS on a known problematic system. 04/05/2009 10:24 troy@bay 0B:TestTagFailure: Known problematic system, clearing TASS. 04/04/2009 10:09 troy@bay 0B:TestTagFailure: Known problematic system, clearing tass 04/02/2009 13:37 troy@bay 02:TestTagFailure,0B:TestTagFailure: noted 03/31/2009 08:23 troy@bay 0B:TestTagFailure: Noted 03/30/2009 08:35 troy@bay 0B:TestTagFailure: Noted 03/29/2009 09:43 darren@b 02:TestTagFailure,0B:TestTagFailure: Alarm on antenna 02 will be investigated during the next site visit. The alarm on antenna 0B is a documented issue. 03/28/2009 08:02 darren@b 0B:TestTagFailure: Alarm on Problematic system. 03/27/2009 23:34 darren@b 0B:TestTagFailure: Alarm noted on problematic system. 03/26/2009 10:45 alan@bay 0B:TestTagFailure: Clearing TASS on a known problematic system. 03/24/2009 09:13 troy@bay 0B:TestTagFailure: Known problematic system, clearing TASS. 03/19/2009 08:31 troy@bay 0B:TestTagFailure: Known problematic system, clearing TASS. 03/16/2009 08:05 scottl@b 0B:TestTagFailure: This antenna has known issues as previously documented 03/15/2009 09:05 troy@bay 0B:TestTagFailure: Known problematic system, clearing TASS. 03/14/2009 08:27 troy@bay 0B:TestTagFailure: Known problematic system, clearing TASS. 03/12/2009 08:30 troy@bay 0B:TestTagFailure: Known problem, clearing TASS. 03/10/2009 09:04 scottl Manually pushed delinquent data file. Purged the .temp directory, will monitor. 03/10/2009 08:12 troy@bay 0B:TestTagFailure: Known problematic system, clearing TASS. 03/09/2009 08:38 troy@bay 0B:TestTagFailure: This alarm will be addressed on the next site visit. 03/08/2009 08:17 alan@bay 0B:TestTagFailure: Clearing TASS on known problem antenna. 03/07/2009 06:47 alan@bay 0B:TestTagFailure: Clearing TASS on a known problematic system. 03/06/2009 11:27 alan@bay 0B:TestTagFailure: Clearing TASS on a known problematic antenna. 03/05/2009 11:58 alan@bay 05:BadExcFreq,05:LowExcCurrent: These alarms were generated by PTAGIS Field Operations personnel during a site visit. 03/05/2009 11:57 alan@bay 0B:TestTagFailure: Clearing TASS on a known problematic antenna. 03/05/2009 08:50 Scott_Li During the GMC on 34March09, it was found that the antenna 0B has little to no drive current. Further troubleshooting indicated that the antenna has failed in someway. The unit was left in operation and will further discuss what actions will be taken. 03/04/2009 15:57 scottl Performed site GMC, all transceivers were retuned and calibrated. No unknown problems to report. 03/04/2009 08:33 alan@bay 0B:TestTagFailure: This will be investigated today during a site visit. 03/03/2009 08:29 darren@b 0B:TestTagFailure: This alarm will be addressed during the next site visit. 03/01/2009 08:17 darren@b 03:LowExcCurrent,04:LowExcCurrent,0B:TestTagFailure,0C:LowExcCurrent,11:Lo wExcCurrent,11:TestTagFailure: It appears that the ladder watered-up yesterday around 10:00-11:00. I will post moree information and update the site operational page when more information is available. 02/07/2009 08:41 Troy Pushed MC109038.B1 to ptagis. 02/06/2009 13:23 Scott_Li Manually pushed data files, cleared the contents of the temp directory at BO1, no zip files were present. 02/03/2009 15:29 Alan The OS on both PCs has been changed to Vista Business. File MC109034.H2 was created on PC2 during PC1's downtime. No problems found. 02/02/2009 08:00 troy@bay 02:TestTagFailure,04:LowExcCurrent,0B:TestTagFailure: Site dewatered,clearing TASS. 01/27/2009 07:12 scottl@b 04:LowExcCurrent,0B:BadExcFreq,0B:BadOscFreq,0B:LowExcCurrent,0B:TestTagFa ilure: Will monitor and adjust when necessary. 01/24/2009 09:15 darren@b 03:TestTagFailure,04:TestTagFailure,06:TestTagFailure,08:TestTagFailure,09 :TestTagFailure,0A:TestTagFailure,0C:TestTagFailure,0D:TestTagFailure,0E:T estTagFailure,10:TestTagFailure,11:TestTagFailure,12:TestTagFailure: Site down. Clearing TASS. 01/23/2009 07:56 Alan During the platform upgrade, I inadvertently set the date on PC1 one day ahead. PC2 was set properly. Files MC109023.Q1, MC109023.R1, MC109023.S1, MC109024.A1 and MC109024.B1 are loaded in the database and have inaccurate date stamps. PC1's clock/calendar has been adjusted to within one second of atomic time. The data file that was being built at the time of this discovery has been archived and will not be submitted. The site is currently dewatered rendering any data gaps inconsequential. 01/22/2009 15:23 Alan New data collection computers (Dell Optiplex/XP Pro) have been deployed. The former MC2-PC1 has been converted to the new MC1-Util PC. The ladder is still dewatered. 01/21/2009 16:26 Alan The platform upgrade has not gone as smooth as hoped and is out of service at the moment. No files will be submitted until the platform can be brought back online (tomorrow). The site is currently dewatered. 01/17/2009 09:38 troy@bay 11:LowExcCurrent: Site down clearing TASS. 01/09/2009 07:19 darren@b 03:LowExcCurrent: Site down. Clearing TASS. 01/08/2009 08:10 Darren_C After seeing the posting by Scott I updated the site operational page to reflect the outage time for the ladder (10:00pdt 1-7-09). The ladder is scheduled to be reinstated on 2-28-09, but Brad stated that it may come back up early. Darren R. Chase PSMFC Office :(509) 735-2773 Ext. 3 Cell: (509) 539-6786 01/08/2009 07:39 Scott_Li Per Brad Eby, the ladder was completely dewatered at 1005 hrs on Jan 7th, 09. 01/08/2009 07:31 darren@b 03:LowExcCurrent,04:LowExcCurrent,08:LowExcCurrent,0A:LowExcCurrent,11:Low ExcCurrent,11:TestTagFailure: Site down. Clearing TASS. 01/07/2009 07:04 darren@b 03:LowExcCurrent,11:TestTagFailure: Site down. Clearing TASS. I will adjust the alarm threshold on 03 to avoid large files. 01/06/2009 14:59 Alan A GMC was performed 1/6/2008. All transceivers were checked and tuned as necessary. The clocks on both PCs (~5 min slow) were set to within one second of atomic time. Data files from 2008 were moved from the archive folder to the "Previous Years' Data\2008" folder on both PCs. During this visit it was discovered that PC1 will not recover after a power outage. PC2 has been set to create three-hour files and submit those files automatically. PC1 will be taken to Kennewick and diagnosed. The ladder is set to be dewatered tomorrow. No other problems found. 01/06/2009 10:14 Darren_C I was able to confirm that the ladder went to orifice flow on Sunday 1-4-09 and will remain in this state until possibly tomorrow 1-7-09. I will try to confirm that the ladder de-waters tomorrow. I have updated the Ladder Outage Calendar to reflect the ladder being de-watered on 1-7-09, but this is subject to change. Darren R. Chase PSMFC Office :(509) 735-2773 Ext. 3 Cell: (509) 539-6786 01/06/2009 07:13 darren@b 03:LowExcCurrent,04:LowExcCurrent,11:LowExcCurrent: Clearing TASS. 01/05/2009 07:39 darren@b 03:LowExcCurrent: Site Down. Clearing TASS. 01/01/2009 00:00 PTOC_Bot Annual log file initiation for MC1 #### End of Event Log for MC1 ###