EVENT LOG FOR SITE JDJ 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 ---------- ----- -------- ----------------------------------------------- 11/13/2001 09:27 Dave Shut down all computers at JDJ, after moving existing data files to their archive directories. 10/13/2001 17:13 darren@p 52:InputSyncDetect,52:ReaderReset: Alarm was generated by a random reader reset. This is being investigated by PTOC personnel and Destron-Fearing. 10/04/2001 16:10 Scott_Li Noticed that JDJ-PC1 had not reported since day 276.003. PCA'd into pc1 and could not make connection. PCA'd into JDJ-PC2 and got right in. PC2 did not indicate that it was diverting and controlling gates so my assumption is that PC1 is collecting data but for some reason the network connection is hosed up. Kinda a mute point beings that the facility is not in operation , but never the less will follow up on situation on 10/5 10/04/2001 09:49 Dave Haven't received data files from JDJ for 24 hours. Don't know why. Since the site is not in active collection, I've disabled the file-checking switch in the "sites" file. 09/17/2001 10:29 Dave The John Day Dam Smolt Monitoring Facility shut down for the season at 0700h (PDT) today, 9/17/01. The project is now in primary bypass and will remain so at least until the diversion screens are removed (likely in December). The SMF, and PIT tag detection operations, will resume in early April, 2002. 08/09/2001 11:19 dlwarf@p F1:ReaderReset,F2:InputSyncDetect,F2:InputSyncLost: F1:ReaderReset,F2:InputSyncDetect,F2:InputSyncLost: Ongoing problem. 07/12/2001 09:43 Darren_C A General Site maintenance check was performed. No problems were found. 07/09/2001 08:18 darren@p C4:InputSyncDetect,C4:ReaderReset: Alarm was generated by a random reader reset. This problem is being addressed by Destron-Fearing and PTOC personnel. 06/30/2001 22:32 darren@p C4:InputSyncDetect,C4:ReaderReset: alarm generated by a random reader reset. This is being addressed by PTOC personnel and Destron-Fearing 06/29/2001 22:50 Darren_C A general site maintenance check was performed. No problems were found. I also retrieved the data for Sandy on the Oregon ladder and Washington ladder. 06/07/2001 09:37 Scott_Li General maintenence check found no problems to report.. A router some where in the loop from JDJ to PTAGIS was down at the time of the site visit. A traceroute to psmfc stopped what I think to be a COE router out of Portland District. The connection has since been restored .. Stick test on the the two way and SByC leg was 100 percent successfull. 06/07/2001 14:35 Dave Scott asked me to post this up, as an apparent router problem prevents him from posting this directly from JDA. Ahem, "General maintenance inspection. Threw sticks. Everything checks out ok." That is all. 05/31/2001 07:49 Darren_C A General Site check was performed no problems found. 05/23/2001 15:13 Darren_C A site maintenance check was performed. No sticks were tested due to the amount of fish passing through the facility. The gate was checked for timing and no problems were found. 05/23/2001 08:23 Darren_C I was able to get into PC1 via dialup. I found that the PTTP uploader was not counting down to send the next file. The application was closed and reopened and then Files were sent manually and auto upload was checked to ensure that it was timing out to send files. 05/22/2001 11:12 Dave Having noticed, at 10 am (PST) today, that we had not received data from JDJ since 6 pm (PST) yesterday, I pcA'd into JDJ-PC1. Multimon was running and the data file was current. PTTP Uploader was also running, but it's status light was yellow. The last action noted was an upload at 15:06:04 on 5/21; the status message was "Waiting for host to acknowledge file transfer...". The time would have corresponded with the upload of jdj01141.105, so it's kind of curious that we had also received jdj01141.106. No matter. I manually PTTP'd all the queued files (jdj141.106-jdj142.103) to PTAGIS. After closing the manual upload window, I verified that PTTP was "ready" for further automated uploads by observing the green status light and the "idle" status message. 05/18/2001 14:01 Dave I updated the Multimon map file at JDJ with "jdj01138.map." Don Larsen asked that I replace the single 2-day sample scheduled for June 4-6 with a pair of 2-day samples on May 21-23 and May 27-29 (all samples start/stop at 10:00am PST). Don also asked that I increase the numbers of fish collected from 20 fish/AC/sample to 15 fish/AC/day (equivalent to a maximum of 30 fish/AC/sample). I accommodated Don's request by modifying DU #10 from the single sample date range (153-154) and AC seasonal maximums of 20 to the pair of date ranges (141-142 and 147-148) and AC daily maximums of 15. As long as I was at the site I checked the clocks on both machines; PC1 was within 5 minutes of "real" time (it is 2:55 fast), and PC2 is within 30 seconds of PC1 (it's 29 seconds slower than PC1). Since both parameters were within our tolerance standards, I did not adjust either clock. 05/18/2001 08:09 Darren_C Site maintenance check was performed. Few sticks were passed through the separator monitor due to high numbers of fish. The sample rate at the time was .67 at the time. No problems were found. PTOC labels were attached to computers. 05/18/2001 07:59 darren@p C4:InputSyncDetect,C4:ReaderReset: Alarm was generated by a random reader reset. This problem is being addressed by PTOC Personnel and Destron- Fearing. 05/11/2001 16:40 Dave I updated the Multimon map file with "jdj01131.map". This map has a new DU that specifically monitors the YIN ACs (91-94) at the separator; the previous map monitored all locations except the Separator, which only tracked the YIN codes when one of the YIN samples was active. The old map generated "BadAC" messages when a YIN AC was detected at the separator outside of an SbyC sample. This was not a problem logically, but I hope the new, explicit, messages will allow the SBCA reports to track and increment the YIN codes. While I was loading the map on both PC1 and PC2, I verified that the time stamps on the two machines were within 30 seconds of each other. 05/10/2001 14:45 scottl General maintenence check found no problems at all. Stick tested the diversion system at 100 percent efficiency on stick tag detections and gate diversion efficiency.. One note, time open on the three way gate is 1.2 seconds. seems alittle extreme. But if no one is squawking about incidental bycatch, then we should leave it at that time... 04/30/2001 19:33 Dave I encountered the same problem with Multimon's SbyC configuration that I found earlier in the day at GRJ. To wit: An SP7 definition with a duration of 23:59:59 terminates prematurely 348 minutes (5:48:00) after initialization. I addressed the problem in a similar fashion to my solution at GRJ. I replaced the SP7 definitions in map file jdj01114.map (three replicates of 45 hours) with three SP6 definitions. Each SP6 DU spans 48 hours (two days). The new map file is "jdj01120.map". I also had to edit the hardware files and set the counter reset value to "08:00". The new hardware files for JDJ-PC1 and JDJ-PC2 are "jdj01120.hw1" and jdj01120.hw2", respectively. As at GRJ, I locked up pcA when attempting to exit from a full-screen DOS box to the Windows desktop. As at GRJ, I was able to reboot the remote machine, and regain pcA communications. By reducing the DOS application to a window before terminating, I was able to maintain communications while terminating Multimon twice on each machine. At the end of each pcA session, I restored Multimon to full-screen. I'll standardize on this protocol when remotely terminating Multimon sessions, and record the success or failure of this approach. 04/29/2001 12:54 Darren Both sites were succesfully PC'aed into and both are collecting data and are sending files. Both have sent files Today 4-29-01. 04/26/2001 12:34 Scott_Li General maintenence check found no problems to report.. 04/25/2001 15:32 Dave I updated the Multimon db and map files to "jdj01114.db" and "jdj01114.map", respectively. The database and map contain the appropriate codes and actions for the collection of a subset of YINN fish over three separate 45-hour periods (late April, mid-May, and early June). Fish will be diverted into the East SbyC tank, beginning at 11:00am on April 30. In the process of submitting the "makeup" file from PC2, I configured PTTP-Uploader on that machine with a site code of "JD2". 04/20/2001 08:13 Darren_C A general maintenance check was performed. I also loaded a new database that included all 750 stick tag codes so sticks would be diverted. I ran all 36 sticks through the 2 way gate to ensure that they would be diverted. All 36 were diverted. I then ran 20 sticks across the separator. The results were 100 percent efficiency. 04/04/2001 14:34 darren@p C4:InputSyncDetect,C4:ReaderReset: Alarm was generated by a random reader reset. This problem is being addressed by PTOC personnel and Destron- Fearing. 04/04/2001 08:57 Scott_Li PCA into primary computer and looked at PTTP history to find out why it had not loaded for the last 1.5 day's. Indications were that the acknowledgement file was was not getting back to PTTP for some reason. Possably due to network latency. A manual load was successful , will monitor for reoccuring problem. From experience , the t-1 connection at the JDJ facility is extremely slow. 04/03/2001 08:18 Darren_C The program ABOUT TIME was removed from both PC1 and PC2 along with the Phone lines to both PC's. The systems were rebooted the time adjust was not noted until I was speaking with Dave Marvin while at B2J. He PC Anywhered into both machines and adjusted the time for PST. 03/30/2001 15:04 Darren On 3-29-01 all detection/diversion electronic equipment was tuned for current and noise. On 3-30-01 the timing of the gates was performed I will post the results of the stick test at a later date. 03/30/2001 06:04 darren@p 83:TestTagFailure,84:TestTagFailure,93:TestTagFailure,94:TestTagFailure,A4 :TestTagFailure,C3:TestTagFailure,C4:TestTagFailure,E2:TestTagFailure,F2:T estTagFailure: Alarms were generated by PTOC personnel while performing Pre Season Timing and Tuning of all Detection/Diversion electronics. 03/29/2001 16:30 Dave The JDA Juvenile Fish Facility (JFF) was watered up, and site operations switched from Primary Bypass to Secondary Bypass, at 4:30pm on Thursday, March 29, 2001. Sampling and PIT tag detection occur only when the JFF is in secondary bypass. This will be the normal mode of operation until October 31. 03/27/2001 12:47 dlwarf@p E2:InputSyncDetect,E2:ReaderReset: Alarm was generated by a random reader reset. This problem is being addressed by PTOC personnel and Destron-Fearing. 03/26/2001 07:40 darren@p A4:InputSyncDetect,A4:ReaderReset: Alarm was generated by a random reader reset. This problem is being addressed by PTOC personnel and Destron- Fearing. 03/22/2001 08:12 darren@p A3:InputSyncDetect,A3:ReaderReset: Alarm was generated by a random reader reset. This problem is being addressed by PTOC personell and Destron-Fearing. 03/09/2001 15:08 Scott_Li Generic Hardware config files for these sites have been uploaded to the PSMFC FTP server for archival. These files contain the new sample messaging enhancement and are the lastest revision and should be the last. 03/08/2001 18:01 Don_Warf Loaded modified PLC program to use messaging. 03/07/2001 08:36 darren@p 83:InputSyncDetect,83:ReaderReset: Alarm was caused by a random reader reset. This problem is being addressed by PTOC personnel and Destron- Fearing. 02/26/2001 13:46 darren@p E2:InputSyncDetect,E2:ReaderReset: Alarm was caused by a random reader reset. This is being addressed by PTOC personnel and Destron-Fearing. 02/22/2001 08:44 scottl@p E2:InputSyncDetect,E2:ReaderReset: This is an ongoing problem system wide and is being addressed by Destron Fearing. 02/22/2001 08:43 scottl@p 83:InputSyncDetect,83:ReaderReset: This is an ongoing problem system wide and is being addressed by Destron Fearing. 02/20/2001 09:41 darren@p A3:InputSyncDetect,A3:ReaderReset: Alarm was generated by random reader reset. 02/14/2001 08:55 darren@p 51:ReaderReset,52:InputSyncDetect,52:ReaderReset,53:InputSyncDetect,53:Rea derReset,54:InputSyncDetect,54:ReaderReset,81:ReaderReset,82:InputSyncDete ct,82:ReaderReset,83:InputSyncDetect,83:InputSyncLost,83:ReaderReset,84:In putSyncDetect,84:InputSyncLost,84:ReaderReset,91:ReaderReset,92:InputSyncD etect,92:ReaderReset,93:InputSyncDetect,93:InputSyncLost,93:ReaderReset,94 :InputSyncDetect,94:InputSyncLost,94:ReaderReset,A1:ReaderReset,A2:InputSy ncDetect,A2:ReaderReset,A3:InputSyncDetect,A3:ReaderReset,A4:InputSyncDete ct,A4:ReaderReset,C1:ReaderReset,C2:InputSyncDetect,C2:ReaderReset,C3:Inpu tSyncDetect,C3:InputSyncLost,C3:LowExcCurrent,C3:ReaderReset,C4:BadOscFreq ,C4:InputSyncDetect,C4:InputSyncLost,C4:ReaderReset,E1:ReaderReset,E2:Inpu tSyncDetect,E2:ReaderReset,F1:ReaderReset,F2:InputSyncDetect,F2:ReaderRese t: Alarms were generated by COE electricians throwing a breaker. This was verified through site personnel. 02/08/2001 09:17 darren@p 53:InputSyncDetect,53:ReaderReset,C4:InputSyncDetect,C4:ReaderReset: Alarms were generated by a random reader reset. This problem is currently under test at MCJ. The results are near completion. 02/05/2001 08:11 Darren_C On Friday 2-2-01 the old platform was decommissioned at about 11:30 a.m. The new platform was installed and communications were established. There appears to be a problem with PTTP mailer. We may need to reload PTTP but all other communications are working fine. 01/19/2001 08:08 darren@p 83:InputSyncDetect,83:ReaderReset: Alarm was caused by a random reader reset. A fix for this problem is currently being tested at McNary. 01/05/2001 18:00 Dave Manually created new event log for 2001. ####End of Event Log for JDJ###