Site Type

Site Name

JO2 - John Day North Fish Ladder

The interrogation site at the John Day Dam north fish ladder consists of eight antennas installed in two weir walls of the fish ladder. Each weir has two orifice antennas and two over flow antennas. The antennas were installed February 2017 without dedicated communication and synchronization lines. Only the upstream weir antennas were active for the first year. During that time PIT tag detections were stored to the transceiver buffers and then submitted to PTAGIS as passive recaptures. The site became fully operational and began automated data submissions of interrogation data on February 14, 2018.

Operated by:

PSMFC

First year:

2017

Last year:

2018

RKM:

347

Site Contacts

Steward

Nicole Tancreto
ntancreto@psmfc.org
(503) 595-3100

POC

Don Warf
dlwarf@psmfc.org
(509) 735-2773

Map

Photo Gallery

"JO2 Configuration 100"

JO2 Configuration 100 Download Image

Operational Dates

Year	Start Date	End Date	Notes
2017			Construction and installation of antennas was completed before all necessary communication and wiring was installed. Antennas on one weir wall were run and collected detections to transceiver buffers which were downloaded approximately weekly. These detections were submitted as Passive Recaptures from site JDALD2.
2018	2/14/2018		Automated data submissions started Feb 14. Prior to this one weir wall was collecting detections to transceiver buffers, which were downloaded weekly and submitted as Passive Recaptures.

Current and Historic Site Configurations

Select Configuration Number

Config Seq: 100

Start Date: 2/27/2017

End Date:

Antenna Group Name	Antenna ID
WEIR 247	01
WEIR 247	02
WEIR 247	03
WEIR 247	04
WEIR 246	05
WEIR 246	06
WEIR 246	07
WEIR 246	08

Event Logs

Event Date	Comments	Error	User
03/13/2017 10:54 AM	On site to download buffers. Replaced lithium battery on 04?. Downloaded and erased buffers. Set time and verified unique mode was on and storing of timer tags was off.		rclark
03/14/2017 11:22 AM	Submitted two passive recapture files containing tags detected on the upstream weir wall from February 27-March 13. The recapture site for these records is JDALD2.		NTancreto@psmfc.org
03/24/2017 03:59 PM	Submitted two passive recapture files containing tags detected on the upstream weir wall from March 13-23. The recapture site for these records is JDALD2		NTancreto@psmfc.org
04/14/2017 03:59 PM	Submitted a passive recapture file containing tags detected on the upstream weir wall from March 23 - April 14. The recapture site for these records is JDALD2.		NTancreto@psmfc.org
04/24/2017 10:11 AM	Submitted a passive recapture file containing tags detected on the upstream weir wall from April 14 - 20. The recapture site for these records is JDALD2.		NTancreto@psmfc.org
05/17/2017 10:00 AM	Performed site GMC on 5/17/2017. All transceivers were checked for tune. 02 and 04 had high noise. Noise levels returned to normal after a full tune. Tested UPS operation. Downloaded buffers. There are no problems to report.		rclark
05/17/2017 04:00 PM	Submitted a passive recapture file containing tags detected on the upstream weir wall from April 20 - May 17. The recapture site for these records is JDALD2.		NTancreto@psmfc.org
05/24/2017 09:52 AM	Performed site GMC on 5/24/2017. All transceivers were checked for tune and detection. Downloaded transceiver buffers. There are no problems to report.		rclark
05/24/2017 05:00 PM	Submitted a passive recapture file containing tags detected on the upstream weir wall from May 17-24. The recapture site for these records is JDALD2.		NTancreto@psmfc.org
06/13/2017 10:00 AM	Submitted a passive recapture file containing tags detected on the upstream weir wall from May 24 - June 8. The recapture site for these records is JDALD2.		NTancreto@psmfc.org
06/14/2017 04:00 PM	Submitted a passive recapture file containing tags detected on the upstream weir wall from June 8-14. The recapture site for these records is JDALD2.		NTancreto@psmfc.org
07/06/2017 01:35 PM	Submitted a passive recapture file containing tags detected on the upstream weir wall from June 20 - July 5. The recapture site for these records is JDALD2.		NTancreto@psmfc.org
07/13/2017 09:58 AM	Submitted a passive recapture file containing tags detected on the upstream weir wall from July 5 - 12. The recapture site for these records is JDALD2.		NTancreto@psmfc.org
07/31/2017 12:03 PM	Submitted a passive recapture file containing tags detected on the upstream weir wall from July 12 - 18 and July 18 - 27. The recapture site for these records is JDALD2.		NTancreto@psmfc.org
08/02/2017 01:13 PM	Performed site GMC, no problems to report. Downloaded buffered data		scottl
08/03/2017 09:51 AM	Submitted a passive recapture file containing tags detected on the upstream weir wall from July 27 - Aug 2. The recapture site for these records is JDALD2.		NTancreto@psmfc.org
08/10/2017 08:51 AM	Submitted a passive recapture file containing tags detected on the upstream weir wall from Aug 2 - 9. The recapture site for these records is JDALD2.		NTancreto@psmfc.org
08/25/2017 08:09 AM	Submitted passive recapture files containing tags detected on the upstream weir wall from August 9 - 16 and 16 - 23. The recapture site for these records is JDALD2.		NTancreto@psmfc.org
08/30/2017 03:36 PM	Submitted passive recapture files containing tags detected on the upstream weir wall from August 23 - 30. The recapture site for these records is JDALD2.		NTancreto@psmfc.org
09/08/2017 08:21 AM	Submitted passive recapture files containing tags detected on the upstream weir wall from August 30 - Sep 6. The recapture site for these records is JDALD2.		NTancreto@psmfc.org
09/14/2017 11:09 AM	Submitted passive recapture files containing tags detected on the upstream weir wall from Sep 6 - 13. The recapture site for these records is JDALD2.		NTancreto@psmfc.org
10/03/2017 08:45 AM	Submitted passive recapture files containing tags detected on the upstream weir wall from Sep 13 - Oct 2. The recapture site for these records is JDALD1.		NTancreto@psmfc.org
10/12/2017 12:15 PM	Submitted passive recapture file containing tags detected on the upstream weir wall from Oct 2 - 11. The recapture site for these records is JDALD2.		NTancreto@psmfc.org
10/25/2017 03:18 PM	Submitted passive recapture file containing tags detected on the upstream weir wall from Oct 11 - 25. The recapture site for these records is JDALD2.		NTancreto@psmfc.org
11/14/2017 09:34 AM	Submitted passive recapture file containing tags detected on the upstream weir wall from Oct 25 - Nov 9. The recapture site for these records is JDALD2.		NTancreto@psmfc.org
11/29/2017 03:29 PM	Submitted passive recapture file containing tags detected on the upstream weir wall from Nov 9 - 29. The recapture site for these records is JDALD2		NTancreto@psmfc.org
12/05/2017 09:00 AM	JO2 down The ladder was de-watered.	Site Operation	dchase
01/04/2018 10:00 AM	JO2 up	Site Operation	Alan
02/15/2018 12:32 PM	File JO2-2018-046-P-010 had an invalid xml character. The offending character was removed, JO2-2018-046-X-010 was submitted. No detections were affected.		Alan
02/15/2018 01:45 PM	Automated data submission to PTAGIS was initiated on 2/14/2018 at ~14:30 pst. Transceiver buffers were checked for recapture detection and none was found. Buffers were then erased , platform is now collecting real-time data. No problems to report.		scottl
02/15/2018 02:51 PM	File JO2-2018-046-P-014 had invalid xml characters. The offending characters were removed, JO2-2018-046-X-014 was submitted. No detections were affected.		Alan
02/16/2018 09:22 AM	The timer tag for antenna 05 was not firing because the delay was set to 0. Delay was adjusted to 60 minutes and the timer tag is now firing on the hour.		dchase
03/01/2018 02:00 PM	Installed output cards to the platform UPS to send the data to SCADA for power failure. We have 2 UPS for the transformers and 2 UPS at the platform with relay cards. Between the 4 different power monitoring locations, we can tell if the UPS or circuit feeding the UPS is the problem or if all 4 are running on battery power, we know the site has a power failure. The cards will also tell us if the UPS needs a battery replacement or is in a faulted state.		Mleonard
03/05/2018 01:33 PM	File JO2-2018-064-P-013 had invalid xml characters. The offending characters were removed, JO2-2018-064-X-013 was submitted. No detections were affected. File JO2-2018-064-X-012 was created from secondary data to fill a data gap.		Alan
03/08/2018 01:03 PM	Files JO2-2018-066-P-001 & 010 had invalid xml characters. The offending characters were removed, JO2-2018-066-X-001 & 010 were submitted. No detections were affected.		Alan
03/12/2018 11:00 AM	Files JO2-2018-069-P-001, 006, 007, 010 & 015; JO2-2018-070-P-012, 017, 023; JO2-2018-071-P-002 had invalid xml characters. The offending characters were removed, JO2-2018-069-X-001, 006, 007, 010 & 015; JO2-2018-070-X-012, 017, 023; JO2-2018-071-X-002 were submitted. No detections were affected.		Alan
03/18/2018 10:00 AM	File JO2-2018-077-P-006 had invalid xml characters. The offending characters were removed, JO2-2018-077-X-006 was submitted. No detections were affected.		Alan
03/26/2018 03:12 PM	Files JO2-2018-081-P-018 and JO2-2018-084-P-021 had invalid xml characters. The offending characters were removed, JO2-2018-081-X-018 and JO2-2018-084-X-021 were submitted. No detections were affected.		Alan
03/31/2018 12:00 PM	Files JO2-2018-087-P-023, JO2-2018-090-P-009 & 011 had invalid xml characters. The offending characters were removed, JO2-2018-087-X-023, JO2-2018-090-X-009 & 011 were submitted. No detections were affected.		Alan
04/05/2018 10:42 AM	Checked all transceivers for tune and detection.		rclark
04/06/2018 08:00 PM	File JO2-2018-096-P-019 had an invalid xml character. The offending character was removed, JO2-2018-096-X-019 was submitted. No detections were affected.		Alan
04/09/2018 11:00 AM	File JO2-2018-099-P-009 had invalid xml characters. The offending characters were removed, JO2-2018-099-X-009 was submitted. No detections were affected.		Alan
04/18/2018 08:34 AM	File JO2-2018-107-P-016 had an invalid xml character. The offending character was removed, JO2-2018-107-X-016 was submitted. No detections were affected.		Alan
04/18/2018 10:18 AM	Checked all transceivers for tune and detection.		rclark
04/23/2018 07:27 AM	Files JO2-2018-111-P-009 and JO2-2018-113-P-005 had invalid xml characters. The offending characters were removed, JO2-2018-111-X-009 and JO2-2018-113-X-005 were submitted. No detections were affected.		Alan
04/23/2018 10:00 AM	Checked all transceivers for tune and detection. Cleared M4 alerts. Note: The Windows 7 on the utility PC needs to be activated and has no internet access.		rclark
04/28/2018 09:00 AM	File JO2-2018-118-P-007 had an invalid xml character. The offending character was removed, JO2-2018-118-X-007 was submitted. No detections were affected.		Alan
04/30/2018 03:14 PM	File JO2-2018-120-P-010 had an invalid xml character. The offending character was removed, JO2-2018-120-X-010 was submitted. No detections were affected.		Alan
05/02/2018 10:06 AM	Checked transceivers for tune and detection. PIT tag room door was once again closed and locked. No key available during this visit.		rclark
05/07/2018 09:41 AM	Files JO2-2018-124-P-002, 011, 022 & JO2-2018-125-P-022 had invalid xml characters. The offending characters were removed, JO2-2018-124-X-002, 011, 022 & JO2-2018-125-X-022 were submitted. No detections were affected.		Alan
05/08/2018 07:11 AM	File JO2-2018-127-P-019 had an invalid xml character. The offending character was removed, JO2-2018-127-X-019 was submitted. No detections were affected.		Alan
05/09/2018 10:26 AM	Checked transceivers for tune and detection.		rclark
05/15/2018 08:16 AM	File JO2-2018-131-P-019 had an invalid xml character. The offending character was removed, JO2-2018-131-X-019 was submitted. No detections were affected.		Alan
05/16/2018 10:03 AM	Checked transceivers for tune and detection.		rclark
05/17/2018 10:17 AM	Files JO2-2018-135-P-012 and JO2-2018-136-P-002 had invalid xml characters. The offending characters were removed, JO2-2018-135-X-012 and JO2-2018-136-X-002 were submitted. No detections were affected.		Alan
05/21/2018 10:16 AM	Files JO2-2018-137-P-023, JO2-2018-140-P-010, 011 and 017 had invalid xml characters. The offending characters were removed, JO2-2018-137-X-023, JO2-2018-140-X-010, 011 and 017 were submitted. No detections were affected.		Alan
05/21/2018 12:18 PM	On 5-19-2018 at ~1500, all eight transceivers began experiencing debilitating noise. The noise lasted until ~0900 5-21-2018, when all eight transceivers were remotely put into standby and then put back into scan. That proper operation was restored by toggling the scan status suggests a firmware problem. It appears the xcvr 03 was the first to go down and then took the others with it. PSMFC is onsite today investigating.		Alan
05/21/2018 01:47 PM	PSMFC was on site today to try and resolve the noise event that happened on 5-19 and was causing the poor efficiencies. They problem appears to have started during one the of the systems re-tuning processes. The synchronization between the systems has been removed and does not appear to have an adverse effects on any system individually. We will monitor this for the next few days and make any adjustments as necessary to maintain the high efficiencies that we are accustom.		dchase
05/24/2018 10:26 AM	Files JO2-2018-142-P-024, JO2-2018-143-P-017 and JO2-2018-144-P-001 had invalid xml characters. The offending characters were removed, JO2-2018-142-X-024, JO2-2018-143-X-017 and JO2-2018-144-X-001 were submitted. No detections were affected.		Alan
05/29/2018 08:51 AM	Files JO2-2018-144-P-019 & 020, JO2-2018-145-P-003 & 021, JO2-2018-146-P-015, JO2-2018-147-P-005 and JO2-2018-148-P-011 had invalid xml characters. The offending characters were removed, JO2-2018-144-X-019 & 020, JO2-2018-145-X-003 & 021, JO2-2018-146-X-015, JO2-2018-147-X-005 and JO2-2018-148-X-011 were submitted. No detections were affected.		Alan
06/04/2018 09:39 AM	Files JO2-2018-150-P-014, JO2-2018-150-P-017, JO2-2018-151-P-006, JO2-2018-151-P-010, JO2-2018-151-P-015, JO2-2018-153-P-005 and JO2-2018-154-P-016 had invalid xml characters. The offending characters were removed, JO2-2018-150-X-014, JO2-2018-150-X-017, JO2-2018-151-X-006, JO2-2018-151-X-010, JO2-2018-151-X-015, JO2-2018-153-X-005 and JO2-2018-154-X-016 were submitted. No detections were affected.		Alan
06/06/2018 08:37 AM	Files JO2-2018-156-P-007 and 018 had invalid xml characters. The offending characters were removed, JO2-2018-156-X-007 and 018 were submitted. No detections were affected.		Alan
06/11/2018 01:45 PM	Files JO2-2018-157-P-006, JO2-2018-158-P-007, 011, JO2-2018-160-P-014, 017, JO2-2018-161-P-002, 024 and JO2-2018-162-P-005 had invalid xml characters. The offending characters were removed, JO2-2018-157-X-006, JO2-2018-158-X-007, 011, JO2-2018-160-X-014, 017, JO2-2018-161-X-002, 024 and JO2-2018-162-X-005 were submitted. No detections were affected.		Alan
06/12/2018 10:09 AM	Checked transceivers for tune and detection.		rclark
06/13/2018 07:52 AM	File JO2-2018-163-P-017 had an invalid xml character. The offending character was removed, JO2-2018-163-X-017 was submitted. No detections were affected.		Alan
06/19/2018 10:43 AM	Checked transceivers for tune and detection. Turned exciter current up to 4.8A on all overflow transceivers.		rclark
06/26/2018 09:20 AM	File JO2-2018-175-P-017 had invalid xml characters. The offending characters were removed, JO2-2018-175-X-017 was submitted. No detections were affected.		Alan
06/26/2018 10:00 AM	For the period May 24th to June 21, 2018, there has been a slight decrease of .07 % in adult salmonid detections based on Dam to Dam comparisons. On May 24th, the combined detection efficiency for JO1 and JO2 was 99.2% and decreased to 98.5% on June 21st. As of June 26th, the efficiency is holding at 98.5%. Interesting enough, on May 24th, both JO1 and JO2 ladders raised the water levels an additional 4 inches, per passage criteria during the peak of the Shad runs. PTAGIS technicians went to both detection locations to evaluate what, if any adverse effects this additional 4inches had on the PIT tag antenna detection field. It was determined, through actual tag placement around the overflow antennas , the additional water level was not effecting read range and not a contributing factor in a decrease of reading efficiency. The decrease in efficiency seems to coincide with the peak of the Shad run passing over John Day dam. It is unknown whether the extremely high numbers of shad in the ladders are an attributing factor. There is some speculation the high shad numbers are causing the salmonids to jump over the PIt tag overflow antennas and not being detected, but daily PIT tag efficiency reports along with onsite analysis indicated a 100% detection rate for both JO1 and JO2, and is very unlikely. Another bit of speculation is the salmonids during high shad numbers maybe entering the navigation lockes and being released above the dam bypassing the fish ladders. This could explain why fish were seen at The Dalles and McNary, but not anywhere at John Day. A PTAGIS technician observed what looked to be thousands of shad in the locke and noticed the downstream locke gate in the up position. This raised questions about how many salmonids maybe intermingled with them. On another day, PTAGIS technicians did not observe any shad in the locke but the downstream gate was closed.		scottl
06/27/2018 11:59 AM	Checked transceivers for tune and detection.		rclark
06/28/2018 07:11 AM	File JO2-2018-178-P-012 had an invalid xml character. The offending character was removed, JO2-2018-178-X-012 was submitted. No detections were affected.		Alan
07/08/2018 11:00 AM	Files JO2-2018-185-P-002, 010 and JO2-2018-189-P-021 had invalid xml characters. The offending characters were removed, JO2-2018-185-X-002, 010 and JO2-2018-189-X-021 were submitted. No detections were affected.		Alan
07/16/2018 03:49 PM	File JO2-2018-196-P-003 had invalid xml characters. The offending characters were removed, JO2-2018-196-X-003 was submitted. No detections were affected.		Alan
07/23/2018 08:30 AM	File JO2-2018-203-P-020 had invalid xml characters. The offending characters were removed, JO2-2018-203-X-020 was submitted. No detections were affected.		Alan
07/26/2018 04:06 PM	Checked transceivers for tune and detection. Cleared M4 alerts.		rclark
07/30/2018 08:19 AM	File JO2-2018-209-P-003 had an invalid xml character. The offending character was removed, JO2-2018-209-X-003 was submitted. No detections were affected.		Alan
08/08/2018 11:18 AM	Checked transceivers for tune and detection. Cleared M4 alerts.		rclark
08/08/2018 02:11 PM	File JO2-2018-219-P-023 had an invalid xml character. The offending character was removed, JO2-2018-219-X-023 was submitted. No detections were affected.		Alan
08/09/2018 07:15 AM	File JO2-2018-220-P-017 had invalid xml characters. The offending characters were removed, JO2-2018-220-X-017 was submitted. No detections were affected.		Alan
08/13/2018 07:09 AM	File JO2-2018-223-P-011 had an invalid xml character. The offending character was removed, JO2-2018-223-X-011 was submitted. No detections were affected.		Alan
08/16/2018 12:23 PM	Files JO2-2018-225-P-024 and JO2-2018-227-P-014 had invalid xml characters. The offending characters were removed, JO2-2018-225-X-024 and JO2-2018-227-X-014 were submitted. No detections were affected.		Alan
09/04/2018 09:26 AM	File JO2-2018-245-P-015 had an invalid xml character. The offending character was removed, JO2-2018-245-X-015 was submitted. No detections were affected.		Alan
09/10/2018 12:54 PM	Checked transceivers for tune and detection.		rclark
09/11/2018 10:02 AM	Files JO2-2018-248-P-018 and JO2-2018-252-P-016 had invalid xml characters. The offending characters were removed, JO2-2018-248-X-018 and JO2-2018-252-X-016 were submitted. No detections were affected.		Alan
09/21/2018 08:54 AM	File JO2-2018-263-P-018 had an invalid xml character. The offending character was removed, JO2-2018-263-X-018 was submitted. No detections were affected.		Alan
09/24/2018 07:11 AM	File JO2-2018-266-P-006 had an invalid xml character. The offending character was removed, JO2-2018-266-X-006 was submitted. No detections were affected.		Alan
09/26/2018 07:28 AM	File JO2-2018-268-P-012 had an invalid xml character. The offending character was removed, JO2-2018-268-X-012 was submitted. No detections were affected.		Alan
10/01/2018 08:56 AM	File JO2-2018-273-P-012 had invalid xml characters. The offending characters were removed, JO2-2018-273-X-012 was submitted. No detections were affected.		Alan
10/09/2018 07:45 AM	Files JO2-2018-277-P-020, JO2-2018-278-P-006, 022, JO2-2018-280-P-008 and JO2-2018-281-P-004 had invalid xml characters. The offending characters were removed, JO2-2018-277-X-020, JO2-2018-278-X-006, 022, JO2-2018-280-X-008 and JO2-2018-281-X-004 were submitted. No detections were affected.		Alan
10/11/2018 07:33 AM	Files JO2-2018-283-P-022 and 023 had invalid xml characters. The offending characters were removed, JO2-2018-283-X-022 and 023 were submitted. No detections were affected.		Alan
10/15/2018 08:42 AM	Files JO2-2018-286-P-010 and 023 had invalid xml characters. The offending characters were removed, JO2-2018-286-X-010 and 023 were submitted. No detections were affected.		Alan
10/16/2018 07:40 AM	File JO2-2018-288-P-016 had an invalid xml character. The offending character was removed, JO2-2018-288-X-016 was submitted. No detections were affected.		Alan
10/24/2018 03:10 PM	Files JO2-2018-291-P-022, JO2-2018-293-P-017, JO2-2018-295-P-013, JO2-2018-296-P-009 and 016 had invalid xml characters. The offending characters were removed, JO2-2018-291-X-022, JO2-2018-293-X-017, JO2-2018-295-X-013, JO2-2018-296-X-009 and 016 were submitted. No detections were affected.		Alan
10/29/2018 09:08 AM	Files JO2-2018-298-P-016 and JO2-2018-301-P-015 had invalid xml characters. The offending characters were removed, JO2-2018-298-X-016 and JO2-2018-301-X-015 were submitted. No detections were affected.		Alan
10/31/2018 09:00 AM	File JO2-2018-303-P-009 had an invalid xml character. The offending character was removed, JO2-2018-303-X-009 was submitted. No detections were affected.		Alan
11/06/2018 02:10 PM	Files JO2-2018-304-P-015, JO2-2018-306-P-022, JO2-2018-308-P-009 and 012 had invalid xml characters. The offending characters were removed, JO2-2018-304-X-015, JO2-2018-306-X-022, JO2-2018-308-X-009 and 012 were submitted. No detections were affected.		Alan