EVENT LOG FOR SITE BO1 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/20/2007 08:07 Don_Warf The Bradford Is. ladder was dewatered on 12/17/07. DSM2 and the 2 mile pipe were dewatered on 12/19/07. Jon Rerecich Fisheries Biologist USACE Bonneville Lock and Dam 541-374-7984 jonathan.g.rerecich@usace.army.mil 12/17/2007 07:42 troy@ruf 01:TestTagFailure,0D:LowExcCurrent,15:TestTagFailure: This ladder is currently de-watered, clearing TASS. 12/16/2007 10:21 scottl Confirmed that A and B branches of the ladder has been reduced to orifice flow. The dewatering started on Friday 14th at 0900 hrs. Per the power house operator, the ladder will be completely detwatered on Monday 17th. The transcievers will remain in operation until further notice. 12/15/2007 10:56 Scott_Li See below. Note that the state of the transceivers for the A branch changed between 01:25:50 and 04:25:50 2007/12/15 04:25:50 | 34% 2007/12/15 01:25:50 | 2% 2007/12/14 22:25:49 | 2% 12/15/2007 10:46 scottl@r It appears something happen on the A-branch of the ladder . Noise levels are elevated and timer tags are intermittent along with a slight phase shift. It may be the case that the water level in the ladder has been reduced for some reason. Will try and contact someone at the COE and get more information if available. 12/15/2007 10:34 scottl@r 01:TestTagFailure,0D:LowExcCurrent: Errors Noted.What can be corrected will be on the next GMC 12/13/2007 07:06 scottl@r 01:TestTagFailure: Problem noted, not of concern at this time. 12/12/2007 07:07 scottl@r 01:TestTagFailure: Noted, will address on the next site visit. 12/08/2007 08:57 darren@r 01:TestTagFailure: alarm will be addressed on the next site visit. 12/05/2007 07:16 darren@r 02:TestTagFailure: Alarm will be investigated during the next site visit. 12/04/2007 07:08 darren@r 01:TestTagFailure: Alarm will be addressed during the next site visit. 12/03/2007 07:22 darren@r 01:TestTagFailure: Alarms will be addressed on the next site visit. 12/02/2007 08:45 alan@ree 01:TestTagFailure: This will be investigated on the next site visit. 12/02/2007 08:35 Alan Manually pushed BO107336.B1 to PTAGIS via PCA. 11/29/2007 07:38 alan@ree 03:TestTagFailure: This alarms was generated prior to yesterday's site visit. 11/28/2007 07:24 alan@ree 01:TestTagFailure: This will be addressed today during a site visit. 11/27/2007 07:29 alan@ree 01:TestTagFailure,02:TestTagFailure,03:TestTagFailure: These transceivers appear to have drifted slightly out of tune. This will be addressed on the next site visit. 11/26/2007 07:31 alan@ree 01:TestTagFailure,02:TestTagFailure,03:TestTagFailure: These alarms will be addressed on the next site visit. These transceivers are reading PIT Tags. 11/25/2007 10:58 alan@ree 01:TestTagFailure,02:TestTagFailure,03:TestTagFailure: This will be adressed on the next site visit. 11/24/2007 08:19 alan@ree 01:TestTagFailure: This will be investigated on the next site visit. 11/20/2007 07:48 alan@ree 02:TestTagFailure: Clearing the TASS panel, this alarm occurred prior to yesterday's site visit. 11/19/2007 13:39 Alan The slot transceivers were tuned 11/19/2007. No problems found. 11/15/2007 07:22 darren@r 02:TestTagFailure: The system will be investigated during the next site visit. 11/07/2007 07:11 darren@r 02:LowExcCurrent,02:TestTagFailure: Alarms were addressed yesterday during a site GMC. 11/06/2007 13:00 Troy A site GMC was performed 11/06/2007. All transceivers were checked for tune and adjustments made where needed. 11/04/2007 08:11 troy@ree 02:TestTagFailure: TT failures is usually a indication of a shift in tune. A GMC is scheduled for Tues. 11/03/2007 08:53 troy@ree 01:TestTagFailure,02:TestTagFailure,04:TestTagFailure: These alarms are most likely due to a shift in tune. A GMC is scheduled for next week. 11/02/2007 09:53 troy@ree 02:TestTagFailure,04:TestTagFailure: A GMC is scheduled for early next week. These alarms will be addressed at that time. 10/31/2007 07:54 troy@ree 02:TestTagFailure: This alarm will be addressed on the next site visit. 10/30/2007 07:42 troy@ree 02:TestTagFailure: This alarm will be addressed on the next site visit. 10/29/2007 08:00 troy@ree 02:TestTagFailure: These alarms will be addressed on the next site visit. 10/28/2007 09:25 alan@ree 02:TestTagFailure,04:TestTagFailure: Noted 10/27/2007 07:44 alan@ree 02:TestTagFailure,04:TestTagFailure: Noted 10/23/2007 12:50 scottl All transcievers TT hit rates were adjusted as necessary, no problems to report. 10/23/2007 07:38 alan@ree 02:TestTagFailure: No apparent reason for this alarm - it will be investigated during a site visit today. 10/22/2007 08:03 troy@ree 02:TestTagFailure,04:TestTagFailure: These alarms will be addressed during a GMC scheduled for tomorrow. 10/20/2007 10:33 scottl@r 02:TestTagFailure: Problem noted, will correct on the next site visit scheduled for Tuesday Oct 23rd. 10/09/2007 11:14 Alan A GMC was performed 10/9/2007. All transceivers were checked and tuned as necessary. Both clocks were set to within one second of atomic time, no problems found. 10/07/2007 08:53 alan@ree 03:TestTagFailure: Noted 10/06/2007 07:36 alan@ree 03:TestTagFailure: This will be investigated during a site visit next week. This transceiver is reading PIT Tags well. 10/03/2007 07:48 alan@ree 04:TestTagFailure: Noted. This transceiver is reading PIT Tags well. 10/01/2007 08:12 alan@ree 04:TestTagFailure: Noted 09/30/2007 08:30 troy@ree 01:TestTagFailure: Noted 09/28/2007 08:08 troy@ree 02:TestTagFailure,04:TestTagFailure: These alarms will be addressed on the next site visit. 09/27/2007 08:19 troy@ree 04:TestTagFailure: Noted. 09/26/2007 08:02 alan@ree 04:TestTagFailure: One time alarm - noted 09/25/2007 07:35 troy@ree 01:TestTagFailure,02:TestTagFailure,03:TestTagFailure,04:TestTagFailure: These alarms were addressed yesterday during a GMC. 09/24/2007 12:14 Darren A site GMC wasm performed today. The transceivers on antennas 01-04 were severly detuned when PSMFC personnel arrived. They were retuned as the other transceivers were checked for tuning, noise, and detection ability. No problems were found. 09/23/2007 11:59 scottl@r 01:TestTagFailure,02:TestTagFailure,04:TestTagFailure: Will be corrected on the next site GMC scheduled for tomorrow 09/22/2007 12:42 scottl@r 01:TestTagFailure,02:TestTagFailure: TT's will be corrected on the next site visit scheduled for Monday the 24th. 09/22/2007 12:41 scottl@r 01:TestTagFailure,02:TestTagFailure: TT's will be corrected on the next site visit scheduled for Monday the 24th. 09/21/2007 07:05 scottl@r 02:TestTagFailure: Noted 09/20/2007 07:02 scottl@r 01:TestTagFailure,02:TestTagFailure: Noted 09/19/2007 07:00 scottl@r 02:TestTagFailure: System will be retuned and TT's optimized during the next GMC. 09/16/2007 07:32 darren@r 0F:LowExcCurrent: The alarm level and the threshold are pretty close. It appears by the current that this system is becoming harder to drive above 2.0A. The threshold level will be adjusted via PCA. 09/15/2007 08:36 darren@r 0F:LowExcCurrent: This alarm will be investigated during the next site visit. 09/13/2007 07:34 troy@ree 0F:LowExcCurrent: PSMFC will monitor and adjust in the near future if needed. 09/11/2007 12:51 Troy A site GMC was performed 9-11-2007. All transceivers were checked for tune and adjustments made where needed. No problems to report. 09/08/2007 08:34 troy@ree 0F:LowExcCurrent: This alarm will be looked into on the next site visit. It is most likely due to a shift in the tuning. 08/30/2007 17:05 Alan_Bro Sprint confirms a DSL outage with a return of service estimated to "8 or 8:30 tonight" 08/30/2007 10:26 Scott_Li The DSL connection has been resolved by Embark. Remote access has been restored to all sites at this location. 08/30/2007 09:41 Scott_Li The DSL connection for all these sites is down. Called Embark (DSL Provider) and they have indicated that the entire Hood River area is experiencing an outage. The ETR according to them is 12:30 pm PST. Will monitor situation and follow up if necessary. 08/30/2007 08:08 darren@r 03:LowExcCurrent: I adjusted the alarm threshold to alleviate the alarm. 08/25/2007 08:10 alan@ree 0F:LowExcCurrent: This transceiver is reading PIT Tags and timer tags well. PTAGIS Field Operations will investigate on the next site visit. 08/17/2007 10:05 Alan A GMC was performed 8/17/2007. All transceivers were checked and tuned as necessary. Both clocks were set to within one second of atomic time, no problems found. 08/12/2007 10:20 scottl@r 01:TestTagFailure,0F:LowExcCurrent,24:TestTagFailure: Problems will be adressed on the next site visit 08/11/2007 08:12 scottl@r 0F:LowExcCurrent: Problem noted, not of concerna at this time, will monitor 08/10/2007 08:10 darren@r 0F:LowExcCurrent: PSMFC will adjust the current threshold via PCA. 08/07/2007 08:42 scottl@r 04:TestTagFailure: Problem noted and will monitor. 08/04/2007 09:50 troy@ruf 04:TestTagFailure: Noted 08/01/2007 08:30 troy@ruf 0D:LowExcCurrent,0E:LowExcCurrent,23:LowExcCurrent: PSMFC will monitor for future occurances and adjust the current alarm threshold if neccessary. 07/26/2007 07:47 darren@r 01:LowExcCurrent: Alarm was addressed yesterday via PCA. 07/25/2007 07:49 darren@r 01:LowExcCurrent: This will be addressed via PCA. 07/24/2007 08:29 darren@r 01:LowExcCurrent: This will be addressed through PCA. The threshold is equal to the displayed value. 07/23/2007 08:46 troy@ruf 01:LowExcCurrent,03:LowExcCurrent: These alarms will be monitored and remote adjustments made to the current alarm threshold made if they persist. 07/22/2007 12:06 scottl@r 01:LowExcCurrent,0F:LowExcCurrent: Will adjust the alarm threshold for VSD 01. Unit is detecting tags at high efficencies 07/20/2007 13:40 scottl Performed GMC on the slot antennas, transcievers were tuned and the timer tag hit rate was adjustd to achieve 100 percent. Unit 19 is in an excessive noise condition and cannot be tuned out. Unit is still functional irregardless of this condition. No other issues to report. 07/17/2007 08:04 scottl@r 03:TestTagFailure: Will correct the hit rate on the next GMC 07/16/2007 08:07 darren@r 02:TestTagFailure,03:TestTagFailure: These alarms will be investigated during the site GMC this week. 07/15/2007 10:22 troy@ruf 02:TestTagFailure,03:TestTagFailure,04:TestTagFailure: Noted, these alarms will be investigated on the next site visit. 07/14/2007 09:26 troy@ruf 02:TestTagFailure,03:TestTagFailure: These alarms will be addressed on the next site visit. 07/13/2007 08:13 darren@r 02:LowExcCurrent,02:TestTagFailure,03:TestTagFailure: The LowExcCurrent alarm was remedied yesterday by adjusting the threshold. The other alarm will be investigated during the next site visit. 07/12/2007 08:47 darren@r 02:LowExcCurrent,03:TestTagFailure: The alarm on antenna 02 was rectified by changing the alarm threshold to 300mA below the current. The alarm on 03 will be investigated during the next site visit. 07/11/2007 09:02 troy@ruf 02:LowExcCurrent: The tuning may have drifted below the current alarm threshold. PSMFC will adjust the current alarm threshold if needed but will monitor for now. 07/03/2007 21:58 darren@r 01:TestTagFailure,02:TestTagFailure,03:TestTagFailure,04:TestTagFailure: These alarms were generated by PSMFC personnel during a GMC. 07/03/2007 08:18 alan@ruf 02:TestTagFailure,03:TestTagFailure,04:TestTagFailure: These will be investigated today during a site visit. 07/02/2007 08:49 alan@ruf 02:TestTagFailure,03:TestTagFailure,04:TestTagFailure,0F:LowExcCurrent: These alarms will be investigated on a site visit tomorrow. 07/01/2007 07:37 Darren_C The files for the 9 hour gap were in the archive folder on PC1. It appears that the files were submitted and archived but did not reach the server for some reason. I manually pushed those files over this morning. 07/01/2007 05:31 darren@r 03:TestTagFailure,04:TestTagFailure: These failures will be addressed on the next site visit. The systems require some minor tuning. 06/30/2007 09:01 darren@r 02:TestTagFailure,03:TestTagFailure,04:TestTagFailure,0F:LowExcCurrent: These alarms will be addressed during the site GMC next week. 06/27/2007 09:04 troy@ruf 02:TestTagFailure: Noted 06/26/2007 08:40 scottl@r 02:TestTagFailure: Noted 06/26/2007 08:07 Alan Manually pushed BO107177.B1 to PTAGIS via PCA. 06/22/2007 07:50 darren@r 02:TestTagFailure,04:TestTagFailure: No direct cause for these alarms PSMFC will continue to monitor for failures. 06/20/2007 08:14 darren@r 01:LowExcCurrent: Alarms were generated by PSMFC personnel during a site GMC. 06/19/2007 12:12 Alan A GMC was performed 6/19/2007. All transceivers were checked and tuned as necessary. The clocks on both PCs were set to within one second of atomic time, no problems found. 06/12/2007 11:57 Darren A site GMC was performed today (6-12-06). All transceivers were checked for tuning, noise and detection ability. No problmes were found. 06/08/2007 08:00 darren@r 17:LowExcCurrent,18:LowExcCurrent,19:LowExcCurrent,19:Overrun: Alarms were generated by PSMFC personnel during a site GMC. 06/07/2007 12:21 Darren A site GMC was performed today (6-7-07). All transceivers were checked for tuning, noise, and detection ability. No problems were found. PC clocks are within 7 seconds of each other and 20 seconds of atomic time. 06/06/2007 08:10 troy@ruf 04:TestTagFailure: Noted, clearing TASS 06/05/2007 08:17 troy@ruf 01:TestTagFailure,03:LowExcCurrent,03:TestTagFailure,04:TestTagFailure: These alarms will be addressed on a GMC scheduled for later this week. 06/04/2007 08:40 alan@ruf 01:TestTagFailure,02:TestTagFailure,03:LowExcCurrent,03:TestTagFailure,04: TestTagFailure,0F:LowExcCurrent: These alarms will be addressed during a site visit this week. 06/03/2007 09:12 alan@ruf 03:TestTagFailure,04:TestTagFailure: These transceivers have drifted slightly out of tune but are still reading PIT Tags. This will be addressed during a site visit this week. 06/02/2007 09:38 alan@ruf 0F:LowExcCurrent: Noted 06/02/2007 09:36 alan@ruf 03:TestTagFailure: This transceiver might have drifted slightly out of tune but is reading PIT Tags well. PTAGIS Field Operations will continue to monitor. 06/02/2007 09:32 alan@ruf 01:LowExcCurrent: Clearing the TASS panel. The condition creating this alarm was addressed yesterday. 06/01/2007 08:59 troy@ruf 01:LowExcCurrent,03:LowExcCurrent: 01's current alarm threshold was remotely lowered from 6000 to 5900, the current is at 6100. 03's current alarm threshold was lowered from 6900 to 6700, the current is at 6900. No apparent cause for the dip in current on these trancievers. PSMFC will monitor. 06/01/2007 08:51 troy@ruf 0F:LowExcCurrent: The current dipped below the current alarm threshold last night around 10pm and looks to have stayed that way for ~2 hours and has since worked it's way back to the current it normally runs at. PSMFC will monitor for future occurances. 05/24/2007 07:53 darren@r 19:LowExcCurrent: This alarm may have been generated by PSMFC personnel while performing a site GMC. 05/23/2007 13:31 scottl Performed GMC, antenna 19 has periodic spiking and cannot be tuned out. Problem appears to be associated with cable and or antenna. All transceivers where tuned and calibrated as necessary. Hit rates on slot antennas were adjusted and all are at 100 percent. 05/22/2007 07:58 darren@r 0F:LowExcCurrent: The alarm threshold was lowered yesterday to alleviate this alarm. The system will be investigated on the next site visit. 05/21/2007 09:05 troy@ree 0F:LowExcCurrent: The current alarm threshold was lowered from 2100 to 1800 as the transciever was at 2100. PSMFC will investigate why the current has dropped on the next site visit. 05/20/2007 09:29 darren@r 0F:LowExcCurrent: This alarm is being generated because the alarm threshold and the level are equal. It will be addressed on Monday and investigated on the next site visit. 05/14/2007 08:42 troy@ree 17:LowExcCurrent: The current was right at the alarm threshold. The alarm threshold was lowered from 3000 to 2700 mA in order to reduce file size. PSMFC will investigate the current drop on the next site visit. 05/13/2007 09:14 alan@ree 17:LowExcCurrent: This will be investigated on the next site visit. This transceiver is reading PIT Tags well. 05/12/2007 07:57 alan@ree 17:LowExcCurrent: This transceiver could possibly have drifted out of tune, but is still reading PIT Tags. This will be investigated during a site visit next week. 05/10/2007 09:59 alan@ree 03:LowExcCurrent,04:LowExcCurrent: These alarms were generated by PTAGIS Field Operations personnel during a site visit. 05/09/2007 09:02 alan@ree 02:TestTagFailure,03:TestTagFailure,04:TestTagFailure,17:LowExcCurrent: These will be investigated today during a site visit. 05/08/2007 08:44 alan@ree 04:TestTagFailure: This will be investigated on the next site visit. 05/03/2007 08:02 darren@r 03:LowExcCurrent: This level was not adjusted yesterday as advertised. I will rectify this today. 05/02/2007 08:19 darren@r 01:LowExcCurrent,01:TestTagFailure,03:LowExcCurrent,03:TestTagFailure: All alarms with the exception of the LowExcCurrent alarm on antenna 03 were generated by PSMFC personnel while on site for maintenance. The Current threshold is equal to the level and will be adjusted to eliminate this alarm. 05/01/2007 10:02 Troy A GMC was performed 05/01/2007. All transcievers were checked for tune and adjusted where needed. The current has dropped on 01 so the current alarm threshold was lowered from 6300 to 6000. No explaination as to why the current dropped however the transciever did tune up and is reading tags. PC1 is 10 seconds behind atomic time and PC2 is 16 seconds behind atomic time. 04/30/2007 08:35 darren@r 01:TestTagFailure,03:LowExcCurrent,03:TestTagFailure: These alarms will be addressed on the next site visit. The Current alarm on system 03 is caused by the threshold being equal to value. The tune drifted on both systems and will be retuned during the visit. 04/29/2007 10:09 scottl@r 01:TestTagFailure,03:LowExcCurrent,03:TestTagFailure,04:TestTagFailure: problems will be a addressed on the next site visit. 04/28/2007 10:35 scottl@r 01:TestTagFailure,03:LowExcCurrent,03:TestTagFailure: Will correct errors o the next site visit, actual tag detections are not being effected. 04/27/2007 08:32 darren@r 01:TestTagFailure: It appears that the phase has shifted which would indicate that the tune has changed slightly. The transceiver will be addressed during the next site visit. 04/26/2007 08:00 scottl@r 01:TestTagFailure: Problem noted. 04/25/2007 08:02 scottl@r 01:TestTagFailure,04:TestTagFailure: Problem will be addressed on the next site visit. 04/24/2007 08:05 scottl@r 01:TestTagFailure: Will correct on the scheduled GMC 04/22/2007 10:07 troy@ree 01:TestTagFailure: Noted 04/19/2007 08:26 troy@ruf 04:TestTagFailure: noted 04/18/2007 09:01 troy@ruf 04:TestTagFailure: This will be looked into on the next site visit. 04/14/2007 07:57 alan@ruf 0D:LowExcCurrent,0E:LowExcCurrent,23:LowExcCurrent: These alarms were generated by PTAGIS Field Operations personnel during a site visit. 04/13/2007 15:13 Alan A GMC was performed 4/13/2007. All transceivers were checked and tuned as necessary. The clocks on both PCs were set to within one second of atomic time, no problems found. 04/11/2007 12:41 Alan Upon further review, no data exist to fill the 45 minute data gap on 3/10/2007. 04/11/2007 08:22 alan@ruf 01:TestTagFailure: PTAGIS Field Operations will investigate on the next site visit. 03/28/2007 13:26 scottl All transcievers were retuned and adjusted as necessary. Very little tuning was required, all TT hit rates are at 100 percent. 03/28/2007 07:35 darren@r 04:TestTagFailure: Alarms will be addressed by PSMFC personnel during a site GMC. 03/25/2007 09:49 troy@ree 01:TestTagFailure: This alarm will be addressed on the next site visit. 03/10/2007 20:28 Darren The 45 minute file gap appears to be caused by a power outage. I PCA'd into PC2 and the files are temp files for that time period. The power appears to have come on and off quickly to create two temp files. I will try to verify this with site personnel on Monday morning. 03/09/2007 08:08 darren@r 04:BadOscFreq,04:LowExcCurrent,04:Overrun: Alarms were generated by PSMFC during a site GMC visit. 03/08/2007 13:41 scottl All transceivers were checked for tune and calibration, no problems to report. 02/24/2007 08:12 alan@ree 04:TestTagFailure: This TT has been firing well since this one- time alarm. PTAGIS Field Operations will continue to monitor. 02/23/2007 13:42 scottl Tuned and calibrated all transcievers, erased buffers for start of season. No problems to report. 02/23/2007 07:29 troy@ree 17:Overrun: This alarm will be addressed today during a GMC. 02/03/2007 08:02 darren@r 04:TestTagFailure: 04:TestTagFailure: Alarm will be addressed on the next site visit. 02/03/2007 08:02 darren@r 04:TestTagFailure: Alarm will be addressed on the next site visit. 01/22/2007 08:06 Scott_Li This entry is for work done on Thursday, Jan 18th, 07. The firewall issues have been corrected but not resolved. Apparently, the configuration of the firebox in the AFF PIT room became corrupted in a way that did not allow incoming traffic and shutdown remote access and BB alerts. Todd K and I restored the configuration in the firewall and things started working correctly. At this time, there is no real good explanation for why this happen and how it was corrected. Todd I believe has a support thread started with Watch Guard in order to better understand these unknown phenomenons. 01/21/2007 07:15 alan@ree 04:TestTagFailure: Noted. PTAGIS Field Operations will continue to monitor. 01/17/2007 07:46 troy@ree 03:LowExcCurrent: This alarm is the result of a GMC. 01/16/2007 15:21 scottl Performed GMC, all transcievers were checked for tune and calibration. Slot antenna transcievers hit rate were all at 100 percent. No adjustmnent necessary, no problems to report. 01/16/2007 07:32 alan@ree 04:TestTagFailure: This transceiver may have drifted slightly out of tune. PTAGIS Field Operations will be on site and address this by Thursday. 01/15/2007 09:05 Darren These sites along with BCC are still being indicated as not connected to the Portland office but the files are being submitted on the scheduled intervals. It is possible that something has changed in Portland that is not this connection. I am also having trouble with my VPN service from home so I cannot verify the status of PC2. I will have to dig further when I am in the office on Tuesday. 01/13/2007 09:24 Darren I received a message from chum root indicating that the platforms at Bonneville are not able to be pinged by big brother. I have checked and found that the platforms are indeed sending files into PSMFC but I cannot find the source of the problem. I will continue to monitor this situation and report any changes in the status of big brother. 01/09/2007 07:22 darren@r 04:TestTagFailure: It appears that the system may have drifted slightly out of tune. PSMFC will be on site next week for ladder inspections and will address all tuning issues with BO1 at that time. 01/07/2007 12:04 scottl Antennas 03 and 04 may require tuning. Reports indicate no real problems but revciever circuits should be recalibrated to ensure optimal detection efficiencies. 01/04/2007 07:12 scottl@r 24:LowExcCurrent: Problem noted 01/03/2007 07:17 darren@r 24:LowExcCurrent: The alarm threshold was changed from 3100 to 2800mA. The current level and the threshold were equal. 01/02/2007 07:15 darren@r 24:LowExcCurrent: The alarm is equal to the threshold. The level will be adjusted to alleviate the alarm. 01/01/2007 09:38 troy@ree 24:LowExcCurrent: 24:LowExcCurrent: This alarm will be addressed on the next site visit. 01/01/2007 09:37 troy@ree 24:LowExcCurrent: This alarm will be addressed on the next site visit. 01/01/2007 00:00 PTOC_Bot Annual log file initiation for BO1 #### End of Event Log for BO1 ###