EVENT LOG FOR SITE MCJ Most recent activity to be listed first. First line of each entry lists date, time & who is reporting. Subsequent lines of each entry aligned under Time column. Do not use tabs, only spaces. Date Time Who What ---------- ----- -------- ----------------------------------------------- 12/26/2000 09:41 darren@p 21:TestTagFailure,22:TestTagFailure,23:TestTagFailure,33:InputSyncDetect,3 3:ReaderReset,41:TestTagFailure,42:TestTagFailure,43:TestTagFailure,63:Inp utSyncDetect,63:ReaderReset,71:TestTagFailure,72:TestTagFailure,73:TestTag Failure,81:TestTagFailure,82:TestTagFailure,83:TestTagFailure,84:TestTagFa ilure,B1:TestTagFailure,B2:TestTagFailure,B3:TestTagFailure,B4:TestTagFail ure: Coils A3 and 63 failures are due to a random reader reset. The other failures are due to a test being performed by PTOC personnel and Destron- Fearing. 12/18/2000 08:07 darren@p 21:TestTagFailure,22:TestTagFailure,23:TestTagFailure,41:TestTagFailure,42 :TestTagFailure,43:TestTagFailure,71:TestTagFailure,72:TestTagFailure,73:T estTagFailure,81:TestTagFailure,82:TestTagFailure,83:TestTagFailure,84:Tes tTagFailure,91:ReaderReset,92:InputSyncDetect,92:InputSyncLost,B1:TestTagF ailure,B2:TestTagFailure,B3:TestTagFailure,B4:TestTagFailure: All alarms except for coils 91,92 are being monitored for a test. Coils 91,92 were caused by a random reader reset. This site will be monitored for such alarms. 12/12/2000 07:56 darren@p 21:TestTagFailure,22:TestTagFailure,23:TestTagFailure,41:TestTagFailure,42 :TestTagFailure,43:TestTagFailure,71:TestTagFailure,72:TestTagFailure,73:T estTagFailure,81:TestTagFailure,82:TestTagFailure,83:TestTagFailure,84:Tes tTagFailure,B1:TestTagFailure,B2:TestTagFailure,B3:TestTagFailure,B4:TestT agFailure: Test in progress. We will be monitoring the site for activity. 12/11/2000 08:06 darren@p 21:TestTagFailure,22:TestTagFailure,23:TestTagFailure,41:TestTagFailure,42 :TestTagFailure,43:TestTagFailure,71:TestTagFailure,72:TestTagFailure,73:T estTagFailure,81:TestTagFailure,82:TestTagFailure,83:TestTagFailure,84:Tes tTagFailure,B1:TestTagFailure,B2:TestTagFailure,B3:TestTagFailure,B4:TestT agFailure: Test in Progress. This will be ongoing for quite a while. 12/08/2000 16:24 darren@p 21:TestTagFailure,22:TestTagFailure,23:TestTagFailure,41:TestTagFailure,42 :TestTagFailure,43:TestTagFailure,71:TestTagFailure,72:TestTagFailure,73:T estTagFailure,81:TestTagFailure,82:TestTagFailure,83:TestTagFailure,84:Tes tTagFailure,B1:TestTagFailure,B2:TestTagFailure,B3:TestTagFailure,B4:TestT agFailure: These alarms are a result of the test firmware that was loaded as per Destron-Fearing. We will conducting a test for a few months so we should see these alarms everyday. 12/08/2000 08:25 Darren_C The "B" side transceivers have been reflashed with a new firmware (version 2.15). This version is a test to try and locate the reader reset problem. We will monitor this site for reader resets on all "B" side transceivers as well as transceivers 81,82,83,and84. 12/08/2000 08:13 darren@p 13:InputSyncDetect,13:InputSyncLost,21:ReaderReset,21:TestTagFailure,22:In putSyncDetect,22:ReaderReset,22:RocketPortNoEOT,22:TestTagFailure,23:Input SyncDetect,23:ReaderReset,23:TestTagFailure,41:ReaderReset,41:TestTagFailu re,42:InputSyncDetect,42:ReaderReset,42:TestTagFailure,43:InputSyncDetect, 43:ReaderReset,43:TestTagFailure,71:ReaderReset,71:TestTagFailure,72:Input SyncDetect,72:ReaderReset,72:TestTagFailure,73:InputSyncDetect,73:ReaderRe set,73:TestTagFailure,81:ReaderReset,81:TestTagFailure,82:InputSyncDetect, 82:ReaderReset,82:TestTagFailure,83:InputSyncLost,83:ReaderReset,83:TestTa gFailure,84:InputSyncDetect,84:InputSyncLost,84:ReaderReset,84:TestTagFail ure,93:InputSyncLost,A3:InputSyncDetect,A3:InputSyncLost,B1:ReaderReset,B1 :TestTagFailure,B2:InputSyncDetect,B2:ReaderReset,B2:TestTagFailure,B3:Inp utSyncLost,B3:LowExcCurrent,B3:ReaderReset,B3:TestTagFailure,B4:InputSyncD etect,B4:ReaderReset,B4:TestTagFailure: All alarms except A Raceway (coil 13) were generated by PTOC! personnel. site will be monitored for future reader resets on the "B" side. 12/06/2000 14:05 pittag@p 62:BadOscFreq,62:InputSyncDetect,62:InputSyncLost: carter saw this first 12/06/2000 08:50 pittag@p B1:TestTagFailure: Will monitor for future failures. 12/06/2000 08:48 pittag@p 61:ReaderReset,61:RocketPortNoEOT: Destron is working on the problem. 12/06/2000 08:47 pittag@p 61:ReaderReset,61:RocketPortNoEOT: Destron is working on the problem 12/01/2000 08:50 Don_Warf Brad Eby reported that MCJ shut down for the season on Wednesday the 29th at 11:30 am. He also reports that the site will have a 20 minute power outage on Monday the 4th. This should take place mid-morning. 12/01/2000 08:34 pittag@p 41:ReaderReset,42:InputSyncDetect,42:InputSyncLost: Alarms were generated by a random reader reset. This problem is being addressed by PTOC personnel and Destron-Fearing. 12/01/2000 08:34 pittag@p 41:ReaderReset,42:InputSyncDetect,42:InputSyncLost: Alarm was generated by a random reader reset. This problem is being addressed by PTOC personnel and Destron-Fearing. 11/06/2000 07:59 darren@p 62:InputSyncDetect,62:ReaderReset,81:ReaderReset,82:InputSyncDetect,82:Inp utSyncLost: Alarms were generated by a random reader reset. This problem is being addressed by PTOC personnel and Destron-Fearing. 11/02/2000 10:57 Dave I noted a +14-hour gap between data files at MCJ-PC1, between midnight and 2:40pm on 10/31. Noted that all five PC1 files for that date were submitted twice. FTP'ed into PC2 and retrieved MCJ00305.201-203. Modified 203 into 903, truncating the file at 14:36. Submitted all three files to PTAGIS. Hole is now backfilled. 10/31/2000 09:18 Scott_Li Verified the system clock setting on PC1 was set to PST 10/31/2000 09:06 Scott_Li Changed the number of files created per day on pc1 to 8 and the upload frequency to every three hrs. At this time xcvrs 51,52,11,21, sample room, B and A raceway respectively are set to status dump every 17 mins rather than the default of 240 min. I will be monitoring the system for upload consistancy on a daily basis and increasing the system activity periodically for continued evaluation of the PTTP client in a real world enviroment. 10/23/2000 09:16 scott_li PCAW'd into MCJPC1 via modem and I/P. Platform continues to be stable. 10/23/2000 08:18 darren@p 42:InputSyncDetect,42:ReaderReset: Alarm was generated by a random reader reset. This problem is being addressed by PTOC personnel and Destron- Fearing. 10/20/2000 08:00 darren@p 21:ReaderReset,22:InputSyncDetect,22:InputSyncLost: Alarms were generated by a random reader reset. This is being addressed by Destron- Fearing and PTOC personnel. 10/19/2000 15:43 scott_li tested both I/P and modem connection with PcAnywhere remote access program. All is well program is stable. 10/17/2000 08:35 scott_li Continued monitoring of the remote access feature was again successful. Modem and I/P was tested. 10/16/2000 16:02 scott_li Verified remote accessibility with PcAnyWhere via network and modem connection. Program is stable. 10/16/2000 09:13 darren@p 41:ReaderReset,42:InputSyncDetect,42:InputSyncLost,81:ReaderReset,82:Input SyncDetect,82:InputSyncLost,A3:InputSyncDetect: All alarms were generated by random reader resets. This problem is still being addressed by Destron-Fearing and PTOC personnel. 10/13/2000 09:11 scott_li Remote access to McNary is stable. PcAnywhere has not experienced any errors since the installation. Will continue to evaluate on a daily basis. 10/05/2000 14:29 Dave I backfilled missing data files between midnight and 10:59AM on 10/03/00. The original data file contents had already been incorporated into the PTAGIS3 database, but the data file wrappers were inadvertantly overwritten when pcAnywhere was enabled on PC1. I pulled the corresponding files from PC2. The net result of reapplying the data files is the duplication of detections of a single tag on the two sample-room coils. 10/03/2000 14:07 scott_li PcAnyWhere ver. 9.2 was deployed on MCJ-PC1 today. PTOC ran a battery of on-site testing to ensure the main functionality of the interrogation platform was not compromised. The test consisted of remote access via Modem PPP connection initiating ftp file transfer over I/P while stick tests where being conducted . Exiting the PCAW app and re-initiating connection repeatedly. We were very impressed with all the test results and behavior of this program working in conjunction with with the interrogation stack. We will continue to badger this application for sometime so that we can make a decision as whether to adopt PCAW as the standard remote access program. 10/02/2000 08:08 darren@p 42:InputSyncDetect,42:ReaderReset: This alarm was generated by a random reset. This problem is being addressed by PTOC personnel and Destron- Fearing. 09/27/2000 08:25 Darren_C The Nameplates for all the Monitors, Transceiver enclosures, and coil I.D.s were applied. I also checked the Flash version on coils 91, 92, and 93 because of the reader reset that was detected on Tuesday the 26th. The flash version was correct but I went ahead and reflashed these transceivers again to be sure. There were reports this morning of the resets caused by me and 2 others (coil 83,84). There did not seem to be a reader reset communicated but these coils displayed a loss of sync input. I will e-mail Sean Casey and let him know what we have seen on the river system. 09/27/2000 08:17 darren@p 83:InputSyncDetect,83:InputSyncLost,84:InputSyncDetect,84:InputSyncLost,91 :ReaderReset,91:TestTagFailure,92:InputSyncDetect,92:InputSyncLost,92:Read erReset,92:TestTagFailure,93:InputSyncDetect,93:InputSyncLost,93:ReaderRes et,93:TestTagFailure: The alarms on coils 91,92,and 93 were generated by PTOC personnell while reflashing the transceivers. The alarms on coils 83 and 84 were not generated by PTOC personnel. The upgrade may need to be addressed by Destron-Fearing to ensure that the Reader reset problem is solved before next season. 09/26/2000 08:57 scott_li Loaded PTTP ver 1.1.2 son the primary computer at ~ 1230pm Sept. 25th. This version allows user to enter a valid 3 digit site code therefore assuring the uniqueness of the data files through out the data load process.. 09/26/2000 08:43 darren@p 91:ReaderReset,92:InputSyncDetect,92:InputSyncLost: This alarm was generated by a reader reset on coil 91. This problem was to have been eliminated by the recent upgrade of the transceiver firmware. I will make sure that the upgrade was succesfully completed. 09/20/2000 12:24 Darren_C Visited Site because site had not downloaded files since yesterday (9-19-00) at about 21:00. Dave M. also reported that he could not get to PC2 through the SUN. When I arrived everything looked normal. PTTP reported that it had failed on it's last attempt to send files. I manually sent the files using PTTP and with Scott's help established that PC2 was reachable through the SUN. A General Maintenance Check was performed. 09/06/2000 07:56 darren@p 83:ReaderReset,84:InputSyncDetect,84:InputSyncLost: Reader reset was caused by PTOC personnel while replacing a Battery on coil 83. This does not constitute a random reader reset. 09/05/2000 15:22 scott_li General maintenance found no problems to report. Diversion efficiency was 100 percent for both A and B separator gates. All transceivers electrical parameters were checked with no problems to report. Replaced Battery due to Low Lithium message on coil 83, river1 exit. 09/05/2000 14:53 darren@p 83:LowLithium: Low Battery alarm was addressed by PTOC personnel on site visit today. 09/05/2000 08:07 darren@p 83:LowLithium: alarm has been acknowledged and will be attended to on the next site visit. 09/01/2000 10:06 dlwarf@p 83:LowLithium: Battery will be checked or replaced on the next visit. 08/30/2000 15:41 darren@p 11:ReaderReset,11:TestTagFailure,12:InputSyncDetect,12:InputSyncLost,12:Re aderReset,12:TestTagFailure,13:InputSyncDetect,13:InputSyncLost,13:ReaderR eset,13:TestTagFailure,21:ReaderReset,22:InputSyncDetect,22:InputSyncLost, 22:ReaderReset,23:InputSyncDetect,23:ReaderReset,31:ReaderReset,32:InputSy ncDetect,32:ReaderReset,32:TestTagFailure,33:InputSyncDetect,33:InputSyncL ost,33:ReaderReset,41:ReaderReset,41:TestTagFailure,42:InputSyncDetect,42: ReaderReset,43:InputSyncDetect,43:InputSyncLost,43:ReaderReset,51:ReaderRe set,52:InputSyncDetect,52:ReaderReset,52:TestTagFailure,61:ReaderReset,61: TestTagFailure,62:InputSyncDetect,62:ReaderReset,63:InputSyncDetect,63:Inp utSyncLost,63:ReaderReset,63:TestTagFailure,71:ReaderReset,72:InputSyncDet ect,72:InputSyncLost,72:ReaderReset,73:InputSyncDetect,73:InputSyncLost,73 :ReaderReset,73:TestTagFailure,81:ReaderReset,82:InputSyncDetect,82:Reader Reset,82:TestTagFailure,83:InputSyncDetect,83:InputSyncLost,83:ReaderReset ,83:TestTagFailure,84:InputSy! ncDetect,84:InputSyncLost,84:ReaderReset,91:ReaderReset,92:InputSyncDetect ,92:ReaderReset,92:TestTagFailure,93:InputSyncDetect,93:InputSyncLost,93:R eaderReset,93:TestTagFailure,A1:ReaderReset,A1:TestTagFailure,A2:InputSync Detect,A2:InputSyncLost,A2:ReaderReset,A3:InputSyncDetect,A3:InputSyncLost ,A3:ReaderReset,A3:TestTagFailure,A4:InputSyncDetect,A4:InputSyncLost,A4:R eaderReset,A4:RocketPortNoEOT,A4:TestTagFailure,B1:ReaderReset,B1:TestTagF ailure,B2:InputSyncDetect,B2:InputSyncLost,B2:ReaderReset,B2:TestTagFailur e,B3:InputSyncDetect,B3:InputSyncLost,B3:ReaderReset,B4:InputSyncDetect,B4 :InputSyncLost,B4:ReaderReset: All Reader resets were generated by PTOC personnel while flashing transceivers with a new version of firmware. This new version is 2.12hex and was put at this site to test and verify that it will take care of ther random Reader Resets that we have seen during the year. 08/29/2000 16:13 scott_li PTTP client was loaded on the windows PC today around 11:00 am. Laplink and PTTP do not want to work together. When Laplink is closed via remote I/P connection, A GPF is generated by PTTP in module tsicom.dll. John Tenny and Scott are looking into it for a possible solution. LapLink is not available at this time on PC1 at MCJ due to the above problem. 08/29/2000 16:12 Darren_C All Transceivers were flashed with an upgraded .hex version (2.12) today. This version has been put in place at McNary to see if it will eliminate the Reader Reset problems that we have been seeing sparatically crop up on the river. This site will be monitored for at least 1 month maybe even 2 months before we can say that the update actually did solve this problem. 08/29/2000 13:31 Dave Backfilled data collection hole with MCJ00231.104-105. 08/24/2000 07:59 darren@p 62:InputSyncDetect,62:ReaderReset: Alarm was generated by random reader reset. This problem is being addressed by PTOC personnel. 08/21/2000 14:15 Darren_C A general maintenance check was performed. Sticks were tested on the separator and diversion monitors with 100 0.000000e+00fficiency. All transceivers were checked for noise and current 08/18/2000 14:11 scott_li No data has been uploaded due to an apparent routing problem. A telnet session from gojsun to mcjsun was successful but could not ftp to ftp.psmfc from mcjsun. Todd also tried to ftp to mcjsun and could not. Pete Peterson or Darrell Maplethorp was not available for assistance. Called Portland district network operations center and they performed a traceroute to Mcnary and determined that there was a problem but would not elborate as to what. Trouble ticket for this call is # 157167. PTOC will manually retieve files if necessary. 08/13/2000 08:42 darren@p 81:ReaderReset,82:InputSyncDetect,82:InputSyncLost: The input sync lost on coil 82 is caused by the reader reset on coil 81. PSMFC and Destron- Fearing are currently working on solving this problem. 08/10/2000 09:52 Darren_C On Monday 8-7-00 the B separator slide gate was powered down by COE because of a broken flow gage valve at 07:30. The valve was repaired and system was returned to normal operation at 07:50 on Tuesday 8-8-00. Sticks were tested on the separator by PSMFC personnel with 100% efficiency. 08/08/2000 08:10 Darren_C A General maintenance check was performed on friday 8-4-00. All transceivers were checked for current and noise. Sticks were tested on the separators with 100 0.000000e+00fficiency. 08/08/2000 08:06 Don_Warf Site personnel sent this message yesterday: The diversion gate for the "B" side was turned off at 7:00 this morning. The tank is breaking. The flow gage for dropping the water is broken & the valve itself is broken. So they have no control over the tank at all. No estimate was given as to when the repairs would be made. All B side fish will be transported until repairs are made. 08/02/2000 07:50 darren@p A1:ReaderReset,A2:InputSyncDetect,A2:InputSyncLost: Reader reset on coil A1 caused the alarm on A2. The reader reset is being investigated by PTOC and Destron. 07/23/2000 07:30 darren@p 82:InputSyncDetect,82:InputSyncLost: Alarm generated by a reader rest on coil 81. 07/23/2000 07:29 darren@p 81:ReaderReset: alarm generated by random reader reset. This problem is being addressed by PSMFC and Destron-Fearing. 07/18/2000 07:57 darren@p 21:ReaderReset,22:InputSyncDetect,22:InputSyncLost: The redeader reset(coil 21) caused the loss of the sync input(coil 22). This problem is being addressed by PTOC and Destron-Fearing. 07/17/2000 08:13 scottl@p 21:ReaderReset: Problem is ongong and is being addressed. 07/16/2000 08:17 darren@p 82:InputSyncDetect,82:ReaderReset: Alarm caused by random reader reset. This problem is being addressed by PTOC personnel and Destron- Fearing. 07/08/2000 19:37 scottl@p B4:TestTagFailure: test tag failure was probably due to system activity at the time. |11 B3 00/07/07 06:31:36 3D9.0EEEEEE663 Ignore| 58330. test tag fired on the subsequent attempt. 07/08/2000 19:37 scottl@p B4:TestTagFailure: Test tag failed probably do to system activity.|11 B3 00/07/07 06:31:36 3D9.0EEEEEE663 Ignore| 58330. subsequent attempt was successful 07/08/2000 19:37 scottl@p B4:TestTagFailure: B4:TestTagFailure: Test tag failure was probably do to system activity.|17 B4 00/07/07 08:31:15 3D9.0EEEEEE2DE Ignore| 3544. subsequent attemt was sucessfull. 07/08/2000 19:37 scottl@p B4:TestTagFailure: Test tag failure was probably do to system activity.|17 B4 00/07/07 08:31:15 3D9.0EEEEEE2DE Ignore| 3544. subsequent attempt was sucessfull. 07/07/2000 08:29 darren@p 81:ReaderReset,82:InputSyncDetect,82:InputSyncLost: The reader reset on transceiver 81 is what caused the reader reset on transceiver 82. This problem is being addressed by Destron-Fearing. 07/01/2000 20:08 darren@p SLC500:CommsFailure: SLC CommsFailure has been noted and will be monitored for futher failures. This may be due to system activity. 06/27/2000 08:43 darren@p SLC500:CommsFailure: SLC500 CommsFailure has been noted. This could be due to system activity. I will monitor this failure for future problems. 06/26/2000 08:28 darren@p SLC500:CommsFailure: SLC CommsFailure has been noted. I will monitor this alarm. I will investigate today while I am at site. 06/21/2000 14:24 Darren_C Lori from McNary called me on 6-20-00 to inform me that the site had began collecting for transport on 6-20-00 at 11 a.m. not 7 a.m. that was previously mentioned in the event log. 06/21/2000 08:38 darren@p SLC500:CommsFailure: SLC500 CommsFailure noted. Will monitor for further failures.Could be due to system activity. 06/20/2000 08:24 Darren_C A General maintenance check was performed. No sticks were thrown because the site was sampling fish for marking. Paul Hoffarth informed me that the site will begin collecting for Transport today at 07:00. 06/18/2000 08:31 darren@p 81:ReaderReset,82:InputSyncDetect,82:InputSyncLost: The sync loss on coil 82 was generated by the Reader reset on coil 81 this problem is being looked into by Destron-Fearing. 06/12/2000 15:15 Darren_C A General Maintenance Check was performed. All Transceivers were checked for Noise and Current. Test sticks were thrown on the Separator coils. The efficiency was 100%. The site may begin collecting for transport as early as Wednesday 6-14-00. 06/09/2000 18:06 Dave Files MCJ00159.201 and MCJ00159.202 were submitted to PTAGIS as part of a data replacement packet following the loss of the primary data collection computer. The data in these two files were collected coincident with the data in MCJ00159.101 and MCJ00159.102, at least up to the point where MCJ00159.102 died. The incorporation of the data in these two files to the PTAGIS3 database resulted in fully redundant interrogation records from ~00:00-08:25 on 6/7/00. 06/09/2000 16:10 darren@p B1:TestTagFailure,B2:TestTagFailure,B3:TestTagFailure,SLC500:CommsFailure: These alarms were generated by PSMFC personnel while checking the slide gates for operation and timing. 06/09/2000 12:08 Darren_C The slide gates were checked for timing and workmanship. The air was turned on at 11:17 a.m. and left on as per Brad Eby. The facility is NOT collecting for transport as of yet. Fish will be flushed from tanks to the river via the river exit monitors. The site will notify us when they start collecting for transport. 06/08/2000 15:22 scott_li Data files 159.202 through 160.201 was submitted to intdata to fill in gaps. 06/08/2000 12:01 Darren_C On June 3, 2000 at about 18:23 a blockage was discovered in the River 1 exit and the fish from the B Separator were sent to the raceway. From 18:34 to 18:55 the A Separator was also sent to the raceway. At 18:55 the A separator was switched back to the River 2 exit. At 19:01 the B separator fish were routed through the Barge Boom until 21:34. From 21:34 to 0:04 on 6/4/00 both separators were going to the raceways. From 0:04 to 9:00 the A separator was routed through the River 2 exit and the B Separator was routed through the Barge Boom. From 9:00 until 10:55 both A and B Separators were routed to the raceways. From 10:55 until 23:59 on 6/5 the A Separator was routed to the River 2 exit and the B Separator was routed to the Barge Boom.Starting at 0:00:00 on 6/6 the Separators are routed to were they have been all year which is there perspective River exits ( A=River2 and B=River1). This is the reason we were accumulating fish on the raceways at different times. It appears that the blockage has been removed and the site is operating under normal circumstances. I will try and confirm this with Brad Eby. 06/08/2000 08:13 scott_li Pc1 stopped collecting data : $33 MESSAGE: Test Tag Found. 00/06/07 08:25:00 This was possibly due to myself testing LapLink with MiniMon Via I/P connection. Will retrieve file mcj00159.002 from pc2 and submit to intdata. SMP personnel rebooted computer. Data collection on pc1 has resumed. 06/07/2000 16:09 darren@p 11:ReaderReset,11:TestTagFailure,12:InputSyncDetect,12:InputSyncLost,13:In putSyncDetect,13:InputSyncLost: Alarms Were generated by PTOC personnel duing General Maintenance Checks on the facility. 06/07/2000 15:43 Darren_C A GMC was performed yesterday. All transceivers were checked for current and noise. 06/05/2000 08:37 Don_Warf A debris clog was reported over the weekend. Site personnel report that it happened at 18:23 on Saturday and is still not resolved. The B side fish are being sent out the barge loading line. The A side fish are not affected. I am waiting to hear from Brad Eby to get more details. 06/03/2000 13:02 dlwarf@p A2:TestTagFailure: Test tag failure noted. Will watch for further occurrances. 05/31/2000 11:19 scott_li MCJPC1 did not upload files due to an internal process causing a exception error. Had site smp personell reboot computer. Used remote access to manually send files. 05/29/2000 09:19 darren@p SLC500:CommsFailure: Comms failure has been noted. This may have been caused by an influx of information. We will monitor this site and watch for further alarms. 05/26/2000 09:03 scottl@p A1:ReaderReset,A2:InputSyncDetect,A2:ReaderReset,A3:InputSyncDetect,A3:Rea derReset,A3:TestTagFailure,A4:InputSyncDetect,A4:ReaderReset: A1:ReaderReset,A2:InputSyncDetect,A2:ReaderReset,A3:InputSyncDetect,A3:Rea derReset,A3:TestTagFailure,A4:InputSyncDetect,A4:ReaderReset: This was due to PTOC maintenence personnel. GMC was done , no stick on the Seperators was thrown. Gates are not being operated. 05/26/2000 09:03 scottl@p A1:ReaderReset,A2:InputSyncDetect,A2:ReaderReset,A3:InputSyncDetect,A3:Rea derReset,A3:TestTagFailure,A4:InputSyncDetect,A4:ReaderReset: This was due to PTOC maintenence personnel. GMC was done , no stick on the Seperators was thrown. Gates are not being operated. 05/24/2000 08:22 darren@p SLC500:CommsFailure: CommsFailure has been noted and will be monitored. 05/20/2000 08:51 scottl@p SLC500:CommsFailure: Problem acknowledged 05/13/2000 11:57 dlwarf@p 12:InputSyncDetect,12:ReaderReset: Reader reset noted. 05/11/2000 16:27 Don_Warf Visited site for a general maintenance check and found no problems. 05/10/2000 10:34 Darren_C On Tuesday May 2, 2000 I performed a GMC. I also changed the Status report times on some of the transceivers to try and avoid the interreporting of transceivers. We felt that this may have been causing the timer tags to fail occasionally. The Separators ( A&B ) were left at 240 minutes, the diversion, subsample, and the raceways were changed to 239 minutes, and the sample room and river exits were changed to 238 minutes. This has been evaluated and will be implemented river wide by 5-19-00. If there is a power outage it will have to be done again because the status times are not hard coded and will reset to 240 minutes. 05/06/2000 14:42 darren@p 22:InputSyncDetect,22:InputSyncLost: Both alarms caused by a reader reset on transceiver 21. 05/06/2000 14:41 darren@p 21:ReaderReset: Reader reset noted. This problem is still being addressed by Destron-Fearing. This also caused an alarm on coil 22. 05/03/2000 09:23 darren_c I was informed Tuesday May 2, 2000 from site Bio that on that day that they were diverting to the Barge offload from 7:50 a.m. to 8:10 a.m. and from 8:10 to 8:30 a.m. they were diverting to the raceway. Then after 8:30 they were sending fish back out through the river exits. 05/03/2000 08:31 darren_c Tuesday May 2, 2000 - I was alerted to a problem from the TASS panel that the transceiver on the A-Subsample (62) was not firing its timer tag. Upon further investigation the current was down to .3A. I inspected all the conections inside the sheild and the exciter cable for shorts but found none. I checked the exciter voltage (+VE) and found it to be 1.37V not 13.5V. I replaced transceiver and retuned the coil. The current was 1.9A and the noise was 3-4%. 05/03/2000 08:16 darren@p 61:ReaderReset,62:BadExcFreq,62:BadOscFreq,62:InputSyncDetect,62:InputSync Lost,62:LowExcCurrent,62:ReaderReset,62:TestTagFailure,63:InputSyncDetect, 63:InputSyncLost: These alarms were generated by PSMFC personel while replacing transceiver 62. 05/02/2000 10:15 dlwarf@p 13:InputSyncDetect,13:ReaderReset: Reader reset noted. 05/02/2000 08:13 darren@p 62:TestTagFailure: Test Tag failure noted. It will be checked out 5/2/2000. 04/28/2000 14:59 darren_c There was approxiamtely 300 fish that were seen between both A and B raceway on April 28, 2000. It was explained to scott and I that the fish were put in the raceway for about 8 hours on the 27th because there was the possibility of blockage in the river exit coils. These fish were released out the direct barge load line. There was no blockage and the fish are now being put through the river exit monitors. 04/28/2000 14:33 darren_c General site maintenance was performed on April 28, 2000. Coils A1, B1 were adjusted for noise all others were checked. 04/26/2000 08:49 dlwarf@p SLC500:CommsFailure: SLC comms failure noted. 04/26/2000 08:48 dlwarf@p 13:InputSyncDetect,13:ReaderReset: 13:InputSyncDetect,13:ReaderReset: Reader reset noted. 04/26/2000 08:48 dlwarf@p 13:InputSyncDetect,13:ReaderReset: Reader reset noted. 04/23/2000 09:47 dlwarf@p 42:InputSyncDetect,42:ReaderReset: Reader reset problem noted. 04/22/2000 09:48 dlwarf@p 43:InputSyncDetect,43:ReaderReset: Reader reset problem being tracked by Destron. 04/20/2000 15:52 darren_c Performed a site visit. Upgraded mailer.exe file to 3.0a and set the program options on laplink to show it only in the status bar versus the task bar. All transceivers were checked for noise and tune. 04/14/2000 08:13 darren@p 92:RocketPortNoEOT,93:RocketPortNoEOT: 92:RocketPortNoEOT,93:RocketPortNoEOT: The rocket port no EOT has been noted and we will watch for this occurrance over the weekend. It could be caused by the amount of information being sent to the computer at one time. 04/12/2000 09:03 darren_c April 5, 2000 Sean Casey and I ran a controlled stick test on all monitors and coils. There were no seen problems with the coils but there is one issue that may need to be addressed. The Flush water on the A Subsample positioning is right at the entrance to the monitor causing some difficult hydraulics. The stick test was run first through the separator and subsample and the results were poor for the subsample. Then the sticks were run right into the subsample and the results had a noticable improvement.We will keep an eye on the subsample and if need be this problem will be addressed. 04/11/2000 08:10 dlwarf@p 92:RocketPortNoEOT,93:RocketPortNoEOT: No EOT error will be checked on the next visit. 04/08/2000 12:07 davem Data collection on PC1 was suspended from approximately 2000h on 4/7/00 until 0930h on 4/8/00 (all times PST). The file MCJ00098.105 spanned the period 4/7/00 1900h - 4/8/00 0924h, but contained no live data after 2000h. I backfilled the collection hole from the data on PC2. I made a new file (MCJ00098.305) from MCJ00098.205 by clipping off data prior to 2000h. I submitted MCJ00099.201, containing data from midnight to 0600h on 4/8/00. And I created MCJ00099.302 from MCJ00099.202 by including only the data records prior to the restoration of data collection on PC1 at 9:30:01AM on 4/8/00. 03/31/2000 16:20 darren_c McNary Juvenile Facility watered up at 7:00 am today. PIT tag interrogation capabilities are enabled at water-up. 03/31/2000 10:21 Carter_S A1:ReaderReset,A2:InputSyncDetect,A2:InputSyncLost, A4:InputSyncDetect,A4:InputSyncLost: The sync loss was caused by the reader reset of coil A1. the reader reset is still being addressed by destron-fearing. 03/30/2000 08:47 dlwarf Random reader reset noted on coil 22. 03/27/2000 15:33 scottl Warnings have been acknoledged 03/27/2000 15:32 scottl The SLC comms failure problem has been fixed. The condition was due to an incorrect jumper setting on the serial line driver 03/24/2000 15:25 dlwarf No EOT on coil 84 noted. SLC comms failure noted. 03/24/2000 08:17 dlwarf SLC comms failure noted. Reader reset on coil 84 noted. No EOT errors noted. 03/16/2000 08:26 dlwarf SLC comms failure will be looked into today. 03/15/2000 08:31 dlwarf The SLC comms failure problem is being worked on. 02/16/2000 16:37 Carter_S Modifications were made to all transceivers to eliminate sync problems between transceivers. These modifications were made by Destron Fearing at the site on 2/15/00. 01/23/2000 12:05 Carter_S ISO configuration for McNary added to database. 01/21/2000 11:16 darren_c As of January 20, 2000 The transition from 400KHZ to ISO has been completed. 01/05/00 09:57 carters Initial log creation for MCJ ####End of Event Log for MCJ###