Aquatroll WTE OWC // UP logger

[bpbond]

Moving this here from email so it doesn't get lost.

@robertapeixoto said

If you have a chance, could you check the OWC UP logger program to make sure the wetland transitional edge is being read correctly? I think it may be linked to Table A, since the data is showing as NaN in LoggerNet.
I just wanted to check whether I might need to go out there for another reason because of these NaN values.

and then @roylrich said

I fixed this and pushed new code to turn on table A. We need to make sure that this table is correctly identified for Ben and SP if anything changed. It is running on address 7 but is at OWC-TR site. I currently have Able B on still but can turn off if not needed.

Correction-
OWC-Upland runs AQ on address 8, Table B
OWC-W runs AQ on address 7 Table A.
This was a relic of original departure from standard. I have corrected both programs. At only OWC are these swapped. The
Program update without version change attached. Already pushed.

[robertapeixoto]

I am confused here. Please, help me make sure we have everything correct to link it to the pipeline..

I have updated the metadata in 10-10-2015 to correct the tables from where the data was coming in each zone/plot as bellow:

-OWC-UP = Table B -> it receives the aquatroll from the WTE (name updated in the metadata too) because we don't have any troll in the UP. It was receiving data on Table C before 10/10/2025

-OWC-TR = Table B -> NO changes

-OWC-W = Table C -> it was table A before 10/10/2025

@roylrich you corrected the UP and W yesterday, but changed the TR from Table B to A. Are we keeping TR on Table A from now one?? I am ok with that, just confirming so I can update the metadata for Ben and Steph P.

From today on logger net:
Transition on Table A

Upland on Table B

Wetland on Table C

[bpbond]

I'm glad to know that I'm not the only one who is confused!

[roylrich]

Howdy folks-
This is why nothing should ever be special. The table that the AQ600 goes to is assigned by SDI12 address in the program. If the AQ600, address 7 goes to A, 8 goes to B, and 9 goes to C. But OWC has been rebellious since it was 1st made, and the AQ600's were installed out of order from the start of time.
For me to get this to work, without writing special code in the new program just for OWC, I needed to switch the tables to the standard order to get it to work in the program. In the old code, OWC had a specific code to fix this mistake and correct for the addressing mistake.

My preference would be just to keep it on the tables that code has on now, but I can make it however you want. If you want the tables to be back to how they were originally, then I can do code change again. Let me know. I thought this was simplest but obviously I confused the situation more.
Roy

[robertapeixoto]

OMG! I just sent you an email about it. I will call you - easy.

[robertapeixoto]

Just got off the phone with Roy and Evan. Everyone agrees we are done making changes to this program and Tables A, B, and C. Let’s finalize this one last time to keep everything consistent and avoid non-uniform changes.
OWC has a special configuration at the AquaTROLL installation point, but the program will now follow the same pattern as all COMPASS synoptic sites.
The upland logger is located at the highest elevation, but it is connected to the AquaTROLL at the wetland transitional edge (WTE). We do not have an upland AquaTROLL installed in the field. Therefore, even though the WTE is at a mid elevation, its addressing and table assignment will follow the upland configuration (based on which logger it is connected to).
From now on:
OWC – UP – PB 323 - addressing 7 – Table A
Note: Equipment is installed at the WTE, and there is no upland AquaTROLL.
OWC – TR – PB 322 - addressing 8 – Table B
OWC – W – PB 321 - addressing 9 – Table C
I will update the metadata one more time for Steph P and Ben.