EVENT LOG FOR SITE MC1 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/30/2005 08:50 darren@r 01:TestTagFailure: There was no direct cause for this alarm. PSMFC will investigate on the next site visit. 12/15/2005 08:10 troy@ruf 01:TestTagFailure: Noted 12/05/2005 08:26 Alan_Bro A GMC was performed 12/2/2005. All transceivers were tuned. Transceiver 09 was replaced. The clocks on both PCs were set to within one second of atomic time, no problems found. 12/03/2005 11:33 dlwarf@r 09:BadExcFreq,0A:LowExcCurrent: Alarms caused during yesterday's GMC. 12/01/2005 08:39 scottl@r 09:BadExcFreq,09:TestTagFailure: Tranciever will be replaced on the next site visit 11/30/2005 08:50 scottl@r 01:TestTagFailure,09:BadExcFreq,09:TestTagFailure: Transceiver 09 needs to be replaced. This was to happen on the previous GMC but the replacement transceiver had a damaged analog pcb. Both issues will be addressed on the next GMC. 11/28/2005 10:37 darren@r 09:BadExcFreq,09:TestTagFailure: This transceiver will be addressed on the next site visit. 11/27/2005 08:07 troy@ree 09:BadExcFreq: This transciever is slated to be replaced and will be on the next site visit. 11/22/2005 08:33 troy@ree 01:TestTagFailure: Noted. 11/21/2005 08:04 troy@ree 01:TestTagFailure: Noted 11/18/2005 08:26 scottl@r 01:TestTagFailure,09:BadExcFreq,09:TestTagFailure: During the last site visit, It was noticed that the lighting in the counting window closet where the transcievers reside had self ballasting light bulbs that are know to be a source of interference detected by the transceivers, Will address this issue with Brad Eby and post labels indicating"incandecent bulbs only " The interference caused by the bulbs was noticed to be around 10-12 percent. Will replace transceiver 09 on the next site visit. 11/17/2005 08:25 alan@ree 01:TestTagFailure,09:BadExcFreq,09:BadOscFreq,09:TestTagFailure,0A:TestTag Failure: These alarms were generated by PTAGIS Field Operations personnel during a site visit. 11/16/2005 16:06 scott XCVR 09 is sending analog comms failure. The spare transciever that was going to be installed was physically damaged in a bad way. Will monitor 09 and address when necessary. 11/16/2005 15:45 scott Performed GMC, all transcievers were re-tuned and calibrated as necessary. Reseated the virtual timertag PCB on 0C and along with the drive connector. This seemed to fix the TT functionality, retuned unit and appears to be functioning properly, will monitor for future occurances. 11/16/2005 08:25 scottl@r 01:TestTagFailure,09:BadExcFreq,09:TestTagFailure: This problem will be addressed to day. 11/14/2005 09:35 alan@ree 09:BadExcFreq,09:TestTagFailure: Alarms have been noted by PSMFC and will be addressed on the next site visit. 11/13/2005 09:27 darren@r 09:BadExcFreq,09:TestTagFailure: Alarms have been noted by PSMFC and will be addressed on the next site visit. 11/12/2005 07:35 darren@r 09:BadExcFreq,09:TestTagFailure: Transceiver will be repaired or replaced on the next site visit. 11/11/2005 08:17 darren@r 01:TestTagFailure,09:BadExcFreq,09:TestTagFailure: The transceiver on antenna 09 has been noted by PSMFC and will be addressed on the next site visit. The problem however may be underwater. The status report does not indicate any deviation in the tuning of the transceiver. If the problem is underwater PSMFC will only be able to inspect the antenna when the ladder is de-watered. 11/08/2005 08:04 darren@r 09:BadExcFreq,09:TestTagFailure: This transceiver will be inspected on the next site visit and will be repaired or replaced, there is the possibility that something is either in the ladder or the conduit that holds the antenna cable has broken away from the face of the weir. Although PSMFC does not yet know the de-watering schedule for this facility it will probably be de-watered somtime in January and at that time PSMFC can inspect the antenna and conduit for any breakage. 11/07/2005 08:54 troy@ree 09:BadExcFreq,09:TestTagFailure: This transceiver will be addressed on the next site visit. 11/06/2005 09:21 darren@r 09:BadExcFreq,09:TestTagFailure: This transceiver will repaired or replaced on the next site visit. 11/05/2005 11:31 scottl@r 09:BadExcFreq,09:TestTagFailure: Will respond on the next GMC 11/04/2005 08:09 scottl@r 09:BadExcFreq,09:TestTagFailure: Will address on the next site visit. 11/03/2005 08:28 scottl@r 09:BadExcFreq,09:TestTagFailure: Will address on the next site visit 11/02/2005 08:04 scottl@r 09:BadExcFreq,09:TestTagFailure: Will address on the next site visit 11/01/2005 08:25 scottl@r 09:TestTagFailure: Will address on the next site visit. 11/01/2005 08:13 Alan_Bro Manually pushed MC105304.D1 to PTAGIS via PCA. 10/31/2005 09:05 scottl@r 01:TestTagFailure,09:BadExcFreq,09:TestTagFailure: The transceiver more than likely is failing but could also be loose conduits or failing antenna.Problem will be corrected on the next site visit or at least diagnosed. Will try resetting the transceiver to clear the error for the time being. 10/31/2005 08:51 Scott_Li Manually PCA'd into each of the multimon sites and stopped and started the MM application due to the daylight savings time Phenom. 10/28/2005 08:13 scottl@r 09:BadExcFreq,09:TestTagFailure: This will be addressed on the next site visit. 10/27/2005 08:35 darren@r 09:BadExcFreq,09:TestTagFailure: This transceiver will be investigate on the next site visit. We will repair or replace as necessary. 10/24/2005 08:04 troy@ruf 09:BadExcFreq,09:TestTagFailure: These alarms will be addressed on the next site visit. 10/23/2005 09:01 troy@ruf 01:TestTagFailure,09:BadExcFreq,09:TestTagFailure: These alarms will be addressed on the next site visit. 10/22/2005 08:47 troy@ruf 09:BadExcFreq,09:TestTagFailure: Noted 10/21/2005 08:24 scottl@r 0F:LowExcCurrent: Problem will be addressed on the next site visit. 10/19/2005 14:19 scottl All transcievers were checked for tune and calibrated as necessary. MCJ platform clocks were within 13 seconds of each other. A side note, the transceiver enclosures at MC2 are being used as pigeon roosts and are becoming extremely filthy with droppings. Will suggest that the enclosures be washed down and spike strips or some other effective avian deterant be installed on top of the enclosures to prevent this. No other problems to report. 10/19/2005 08:09 troy@ruf 09:BadExcFreq: This alarm will addressed on the next site visit. 10/18/2005 08:21 troy@ruf 01:TestTagFailure,09:BadExcFreq,09:TestTagFailure: These alarms will be addressed on the next site visit. 10/17/2005 08:50 troy@ruf 01:TestTagFailure: Noted 10/17/2005 08:50 troy@ruf 09:BadExcFreq,09:TestTagFailure: This transceiver may be in need of tuning. It is firing it's TT and reading pittags. 10/15/2005 10:32 darren@r 01:TestTagFailure: Alarm will be addressed on the next site visit. 10/14/2005 16:17 darren@r 01:TestTagFailure,09:BadExcFreq,09:TestTagFailure: Alarms will be addressed on the next site visit. 10/14/2005 08:23 darren@r 01:TestTagFailure,09:BadOscFreq: PSMFC will monitor the alarms on transceiver 09 and repair or replace as necessary. The alarm on transceiver 01 has no direct cause. 10/13/2005 08:19 darren@r 01:TestTagFailure,09:BadExcFreq,09:TestTagFailure: PSMFC is monitoring the alarms on transceiver 09. The test tag failure may be do to tuning but the "BadExcFreq" alarm could be caused by a power supply issue. We will continue to monitor this transceiver and repair or replace as necessary. 10/12/2005 08:08 darren@r 09:BadExcFreq: Alarm will be investigated on the next site visit. 10/11/2005 08:10 darren@r 01:TestTagFailure,09:BadExcFreq,09:TestTagFailure: The alarm for the "badExcFreq" on transceiver 09 is being picked out of the staus report as an alarm. I will erase the alarm from the memeory and see if the problem persists. 10/09/2005 10:59 alan@ruf 09:BadExcFreq,09:TestTagFailure: This transceiver is reading PIT Tags and timer tags with high efficiency. PTAGIS Field Operations will investigate on the next site visit. 10/08/2005 10:35 alan@ruf 09:BadExcFreq,09:TestTagFailure: This transceiver is reading PIT Tags and timer tags with high efficiency. PTAGIS Field Operations will investigate on the next site visit. 10/07/2005 08:20 alan@ruf 09:BadExcFreq,09:TestTagFailure: This transceiver is reading PIT Tags and timer tags with high efficiency. PTAGIS Field Operations will investigate on the next site visit. 10/06/2005 08:18 alan@ruf 01:TestTagFailure,09:BadExcFreq,09:TestTagFailure: These transceivers are reading PIT Tags and timer tags with high efficiency. PTAGIS Field Operations will continue to monitor. 10/03/2005 08:16 alan@ruf 09:BadExcFreq: This transceiver is reading PIT Tags and timer tags and appears to be in tune. PTAGIS Field Operations will investigate on the next site visit. 09/29/2005 08:12 scottl@r 01:TestTagFailure,09:BadOscFreq: Problems noted. 09/22/2005 08:02 scottl@r 01:TestTagFailure: Noted 09/21/2005 08:12 scottl@r 01:TestTagFailure: Noted 09/08/2005 08:36 alan@ruf 01:TestTagFailure: No apparent reason for this alarm. PTAGIS Field Operations will continue to monitor. 08/30/2005 08:25 darren@r 0C:LowExcCurrent: Alarms will investigated on the next site visit. 08/23/2005 16:02 Alan_Bro A GMC was performed 8/23/2005. All transceivers were checked and tuned as necessary, no problems found. 08/15/2005 13:12 Troy A site GMC was performed 08/15/05. All transceivers were checked for tune and no problems were found. It was verified that the collection platform is still collecting data and files are waiting to be submitted once the network problem is resolved. Inspected the counting window room and all is dry and clean now. It didn't appear to have reached the transceivers in anyway. Inspected the antenna's and no damage is visible. The system is still reading tags. 08/15/2005 08:47 Scott_Li PTAGIS personnel traveling to the site to verify data is being collected and to check on the flooding situation in the counting window. 08/14/2005 11:39 troy I was able to contact Kent Blevins at GRJ who confirmed that their server was down. He verified that PC1 and PC2 were up and collecting data. I was unable to conact anyone at the adult trap. I then contacted Solt Monitoring Personnel at MCJ. It was stated that the Power House has trouble with their internet service earlier this morning and reboot all their machines. It was verified that PC1 and PC2 were collecting data. I will check later today to see if the internet connectivity problem has been resolved. PSMFC will be on sight first thing 8/15/05 if not today. 08/14/2005 10:20 Troy The following problems with remote sites were detected; mcj: Last data submission was received on Sun Aug 14 0:03:04 PST 2005 gra: Last data submission was received on Sun Aug 14 0:02:29 PST 2005 mc2: Last data submission was received on Sun Aug 14 0:02:36 PST 2005 grj: Last data submission was received on Sun Aug 14 0:02:18 PST 2005 mc1: Last data submission was received on Sun Aug 14 0:02:42 PST 2005 Please check this out. The tardiness of these files is being looked into. 08/14/2005 09:39 troy@ruf 01:LowExcCurrent,01:TestTagFailure: These alarms were most likely due to the flooding that occured as a result of the wind storm that came through on the night of 8/12/05. PSMFC will be on site 8/15/05 to ensure everything is working correctly. 08/13/2005 09:08 Troy Brad Eby called to report that the dust storm that occured on the night of 8/12/05 caused debri to back up in the ladder which in turn caused water to enter the fish counting window on the Oregon side. He reported that there was approximately 3 inches of water on the floor in the counting window room and asked that we check our counting window readers. The readers were checked through the web site and are working and reading well. 08/06/2005 10:38 alan@ruf 0F:HighTemp: Noted. 08/04/2005 12:09 Alan_Bro The platform was rebooted to re-establish PCA connectivity. The clocks were set to within one second of atomic time. File MC105216.F2 was manually submitted to fill the gap during PC1's downtime. 08/03/2005 15:01 Alan_Bro A GMC was performed 8/3/2005. All transceivers were tuned, no problems found. 08/03/2005 08:41 alan@ruf 0C:LowExcCurrent: This will be addressed on a site visit later today. 08/01/2005 09:24 alan@ruf 0C:LowExcCurrent: Alarm will be addressed on the next site visit. 07/30/2005 07:45 darren@r 0C:LowExcCurrent: I will address this alarm via PCA. I will adjust the threshold level. 07/29/2005 08:57 darren@r 07:TestTagFailure: Alarm will be addressed on the next site visit. 07/28/2005 08:07 darren@r 01:TestTagFailure,07:TestTagFailure,0C:LowExcCurrent: Alarms will be addressed on the next site visit. 07/24/2005 11:02 scottl@r 0C:LowExcCurrent: 0C:LowExcCurrent: Noted 07/24/2005 11:02 scottl@r 0C:LowExcCurrent: Noted 07/22/2005 13:37 Alan_Bro A GMC was performed 7/22/2005. All transceivers were tuned. The clocks on both PCs were adjusted 00:03:28 ahead and are now within one second of atomic time. No other problems found. 07/18/2005 11:01 Scott_Li The following problems with remote sites were detected; mcj: Last data submission was received on Mon Jul 18 6:03:28 PST 2005 gra: Last data submission was received on Mon Jul 18 6:03:48 PST 2005 mc2: Last data submission was received on Mon Jul 18 6:02:51 PST 2005 grj: Last data submission was received on Mon Jul 18 6:03:08 PST 2005 mc1: Last data submission was received on Mon Jul 18 6:05:35 PST 2005 Per Walla Walla district IS, a DS3 at MCI is down. The problem has been reported to MCI and they are working to correct the situation. As of now, it's unclear as to when the data services will be restored. Will follow up and post information as it becomes available. 07/13/2005 08:58 troy@ruf 0C:HighTemp: Noted 07/11/2005 08:09 darren@r 06:TestTagFailure: Alarm will be investigated today. 07/05/2005 13:28 Darren A site GMC was performed today (7-5-05). All transceivers were checked for tuning, noise, and detectability. No problems were found. Both PC's have Minimon running in a full screen upon departure. 06/25/2005 15:04 Darren I have not heard from anyone at WW district to confirm the completion time for the server replacement. I will post more when I have a confirmation. 06/25/2005 08:54 Darren I have tried to PCA into the sites but I am unable to get through. I suspect there is a problem in the district network and will wait to see if the sites load this afternoon, if not I will try to verify the problem with Pete Peterson. 06/23/2005 13:00 Troy A site GMC was performed 06/23/05. All transcievers were checked for tune and readability, no problems were found. The hit rate was checked on OF and the VTT pot adjusted to obtain 100% 06/20/2005 09:10 darren@r 07:TestTagFailure: Alarm will be investigated this week during site maintenance. 06/16/2005 17:11 Dave We did not receive data files from any of the COE Walla Walla sites at 4:00 PM this afternoon. I could not pcA into any of these sites at 4:20 PM. However, I was able to pcA in 4:55 PM, and manually pushed the single outstanding data file at each site to the PTAGIS file server. All appears to be OK now. 06/08/2005 08:08 scottl@r 0F:LowExcCurrent,0F:Overrun: Not of concern at this time 06/07/2005 14:01 Alan_Bro A GMC was performed 6/7/2005. All transceivers were tuned. The exciter voltage was increased slightly on transceiver 0F to achieve 300mA current above the threshold. No other problems found. 06/03/2005 08:09 darren@r 0F:LowExcCurrent: No direct cause for this alarm. PSMFC will monitor for future alarms. 06/01/2005 14:16 Alan_Bro A GMC was performed 6/1/2005. All transceivers were tuned, no problems found. 05/27/2005 12:34 Darren A site GMC was performed today (5-27-05). All transceivers were checked for tuning, noise, and detectability. No problems were found. Both PC's have Minimon running in a full screen upon departure. 05/17/2005 13:07 Darren A site GMC was performed today (5-17-05). All transceivers were checked for tuning and noise. No problems were found. Both PC's have minimon running in a full screen upon departure. 05/12/2005 13:23 Alan_Bro A GMC was performed 5/12/2005. All transceivers were tuned. The PCs clocks were adjusted ahead 00:00:41 and are now within one second of atomic time. No problems found. 05/05/2005 08:33 alan@ruf 01:Overrun: This alarm was caused by PTAGIS Field Operations personnel during a site visit. 05/04/2005 15:44 Alan_Bro A GMC was performed 5/4/2005. All transceivers were tuned. The v5.0 transceiver firmware was verified. No problems found. 04/30/2005 09:09 troy@ruf 0F:LowExcCurrent: This alarm occured during a site GMC 04/29/2005 15:40 Alan_Bro A GMC was performed 4/29/2005. All transceivers were tuned. The clocks on both PCs were adjusted ahead 00:05:48 to get them within one second of atomic time. No problems found. 04/28/2005 09:07 darren@r 01:Overrun: Alarms will be addressed on the next site visit. 04/23/2005 08:04 darren@r 01:Overrun: PSMFC will address this issue on the next site visit. 04/16/2005 09:33 alan@ruf 05:LowExcCurrent: This alarm was generated by PTAGIS Field Operations personnel during a site visit 04/15/2005 11:58 Troy A site GMC was performed 04/15/05. All transceivers were checked for tune. The VTT hit rate for 07 and 08 was check. Both reported at 100%. Coil 06 was reporting excessive noise levels. I connected the antenna to transceiver 05 and the problem followed but not to the extent that transceiver 06 exhibited. I put coil 06 back on transceiver 06 and lowered the voltage. This helped with the noise spiking. I then dropped the exciter current alarm by 100 miliamps to compensate for lowing the voltage and current. The previous low current alarm was at 3200 and now is at 3100. The transceiver was running at 3.7amps and is now at 3.4amps. PSMFC will continue to monitor this coils performance. No other problems were found. 04/15/2005 08:27 troy@ruf 01:Overrun,07:TestTagFailure,08:TestTagFailure: These alarms will be addressed today. 04/05/2005 08:02 scottl@r 07:TestTagFailure,08:TestTagFailure: Alarms caused by excessive noise levels. Will monitor 04/04/2005 14:52 Scott_Li Performed GMC, all transceivers were checked and retuned as necessary. Antenna 0D and 0E have excessive noise levels. After further review, it appears that the problem is originating from the antenna and or the exciter cable conduit is vibrating. Another possability is that the connector at the antenna is wet. No other problems to report. 04/04/2005 08:58 alan@ruf 07:TestTagFailure,08:TestTagFailure: Transceiver 07 might be slightly out of tune but is reading PIT Tags. No apparent reason for the failure on transceiver 08. PTAGIS Field Operations will address these on the next site visit. 04/01/2005 08:04 darren@r 07:TestTagFailure: 07:TestTagFailure: No direct cause for the test tag to fail. We will monitor this antenna for future failures and adjust the transceiver as needed on the next site visit. 04/01/2005 08:04 darren@r 07:TestTagFailure: No direct cause for the test tag to fail. We will monitor this antenna for future failures and adjust the transceiver as needed on the next site visit. 03/28/2005 10:40 Scott_Li Manually pushed MC105087.C1 to ptagis, Error logged in the interrogation file during the 0900 hr upload attempt was, Error Transmitting PTTP Package: Operations Interrupted, Files Upload Process Failed. 03/15/2005 13:11 Troy A GMC was performed 03/15/05. All transceivers were checked for tune and no problems were found. 03/09/2005 09:04 alan@ree 03:LowExcCurrent: This alarm was generated during a GMC. 03/08/2005 16:34 Alan_Bro All transceivers were flashed with version 5.0 firmware 3-8-2005. A GMC was also performed, no problems found. 03/08/2005 08:07 troy@ree 07:TestTagFailure: This alarm will be adressed today 03/06/2005 10:38 alan@ruf 07:TestTagFailure,08:TestTagFailure: PTAGIS Field Operations will address this during a site visit this week. 03/05/2005 09:35 alan@ree 01:Overrun,07:TestTagFailure,08:TestTagFailure: These will be addressed during a GMC this week. 03/01/2005 11:48 dlwarf@r 04:LowExcCurrent,07:TestTagFailure,08:TestTagFailure,09:BadExcFreq,09:Test TagFailure: Alarms will be investigated during next week's GMC. 02/23/2005 09:20 darren@r 04:LowExcCurrent,07:TestTagFailure,08:TestTagFailure,09:BadExcFreq,09:Test TagFailure: PSMFC will be on site to tune all the transceivers and clear buffers for the upcoming season. I PCA'd into the site and reset the alarm threshold on antenna 04 and rest the alarm on antenna 09. This will help minimize the file sizes. 02/22/2005 09:16 Dave The Oregon shore ladder began watering-up from winter maintenance on Wednesday, Feb. 16, and reached normal in-ladder flow by mid-day on Thursday, Feb. 17. 02/21/2005 11:08 troy@ruf 04:LowExcCurrent,07:TestTagFailure,08:TestTagFailure,09:TestTagFailure: These alarms are the result of the ladder being de-watered. 02/20/2005 09:33 troy@ree 04:LowExcCurrent,07:TestTagFailure,08:TestTagFailure,09:BadExcFreq,09:Test TagFailure: Clearing TASS. These alarms caused by the ladder being de- watered. 02/19/2005 09:09 troy@ruf 04:LowExcCurrent,07:TestTagFailure,08:TestTagFailure,09:BadExcFreq,09:Test TagFailure,0D:LowExcCurrent: This ladder is still de-watered which is the cause of these alarms 02/13/2005 12:29 scottl@r 09:BadExcFreq: Problem will be investigated on the next site visit 02/12/2005 11:46 scottl@r 09:BadExcFreq: Not a concern at this time. 02/07/2005 08:25 darren@r 05:LowExcCurrent,09:BadExcFreq: Alarms will be cleared and the threshold level for antenna 05 will be adjusted to minimize the file size. 02/05/2005 07:13 darren@r 09:BadExcFreq: Alarm cleared by PSMFC personnel. Ladder is currently de- watered. 02/04/2005 16:07 darren@r 09:BadExcFreq: Alarm cleared. Ladder is de-watered until 2-10-05. 02/03/2005 08:12 darren@r 09:BadExcFreq,0A:LowExcCurrent: The current alarm thresholds were adjusted yesterday. The BadExcFreq alarm may be caused the fact that the ladder is de-watered all transceivers will be re-tuned once the ladder has watered back up. 02/02/2005 08:27 darren@r 09:BadExcFreq,0A:LowExcCurrent: Alarm threshold level on coil OA will be adjusted by PSMFC personnel. 01/31/2005 08:06 alan@ree 05:LowExcCurrent,08:LowExcCurrent,09:BadExcFreq,0A:LowExcCurrent: This ladder is currently de-watered. PTAGIS Field Operations will be onsite to correct this when the ladder waters back up. 01/28/2005 08:29 troy@ruf 02:LowExcCurrent,05:LowExcCurrent,08:LowExcCurrent: These alarms are the result of the ladder being de-watered. 01/25/2005 08:22 troy@ree 03:LowExcCurrent,04:LowExcCurrent,06:LowExcCurrent,08:LowExcCurrent,0A:Low ExcCurrent,0D:LowExcCurrent: PCA'ed into PC2 and adjusted the alarm threshold for 06. Will monitor the other antennas for further occurences. 01/24/2005 08:40 Troy The ladder was inspected 1/20/05. Pictures were taken and are available from PTAGIS Field Operations. The conduits were inspected and loose straps were reported to Brad Eby. Brad stated that his personnell will fix the reported straps and add strapping to the western most antenna conduits where they transition across the eastern most antennas. 01/24/2005 08:14 troy@ree 03:LowExcCurrent,04:LowExcCurrent,05:LowExcCurrent,06:LowExcCurrent,09:Bad OscFreq,09:TestTagFailure,0A:LowExcCurrent,0D:LowExcCurrent,0F:LowExcCurre nt: These alarms were generated during the de-watering. This ladder is de- watered and all transceivers were placed in standby on 1/20/05. 01/21/2005 11:29 Alan_Bro The Oregon Ladder was de-watered for winter maintenance at approximately 12:00 on January 18, 2005. 01/20/2005 13:54 Troy PC2 was re-booted as PCA had it locked up since 1/14/05. Everything seems to be normal now. Placed all transcievers into standby in order to perform a ladder inspection. 01/17/2005 09:51 troy@ruf 09:TestTagFailure: There is a problem below the water line. PSMFC will investigate when the ladder is de-watered. 01/15/2005 16:29 troy@ruf 0F:TestTagFailure,10:TestTagFailure: Both of these transceivers are experiencing excessive noise levels possibly due to cold temperatures. This ladder is scheduled to be de-water in a few days. PSMFC will check into this problem. 01/14/2005 08:22 darren@r 09:BadExcFreq,09:TestTagFailure: The bad exciter frequency alarm came from the status report. This can be removed by placing the reader into "standby" and then into read mode, this will clear the alarm, if it is not valid. The timer tag is firing but sporadically. The ladder is scheduled to be de-watered next week at which time PSMFC will do ladder inspections of all antennas and conduit. 01/14/2005 08:17 troy@ruf 09:BadExcFreq,09:TestTagFailure: The problem is below the water line. PSMFC will investigate when the ladder is de-watered. 01/13/2005 09:08 alan@ree 09:BadOscFreq,09:TestTagFailure: This antenna is having trouble below the water line. PTAGIS Field Operations will investigate further when the ladder is de-watered. 01/11/2005 08:05 alan@ruf 09:BadExcFreq,09:LowExcCurrent,09:TestTagFailure,0A:LowExcCurrent: These alarms were caused by PTAGIS Field Operations personnel during a site visit. 01/09/2005 10:08 alan@ree 09:BadExcFreq,09:TestTagFailure: No apparent reason for this alarm. PTAGIS Field Operations will investigate during a site visit on Monday. 01/08/2005 13:41 alan@ree 09:BadOscFreq,09:TestTagFailure: This will be addressed during a site visit Monday. ####End of Event Log for MC1###