I’m hoping someone here can help me figure this out, because I’m stumped.
I have an ATK plus one extra optical sensor. All of them now seem to be misbehaving, even though they were working (or at least appeared to be working) before.
I put the extra optical sensor in my skimmer cup. At first it worked: it correctly reported Dry, then when the cup filled it changed to Wet. But after I emptied and cleaned the cup, the sensor is now exposed/dry yet still reports Wet. This is on my FMM, port 3.
My ATK sensors are currently submerged, but Apex says both are Dry. Earlier they seemed to work, but only when the wiring was reversed (wire 1 in port 2, wire 2 in port 1).
All optical sensors are clean, oriented properly, and plugged in securely.
So right now:
Skimmer sensor = stuck on Wet even though dry.
ATK sensors = stuck on Dry even though wet.
Literally nothing has changed in my setup between when it was working and now. Did all the sensors fail at once, or is something else going on (firmware bug maybe)?
At this point, the only Apex function I trust is the DOS doing AWC. Everything else has been frustrating. Any ideas or fixes?
I have an ATK plus one extra optical sensor. All of them now seem to be misbehaving, even though they were working (or at least appeared to be working) before.
I put the extra optical sensor in my skimmer cup. At first it worked: it correctly reported Dry, then when the cup filled it changed to Wet. But after I emptied and cleaned the cup, the sensor is now exposed/dry yet still reports Wet. This is on my FMM, port 3.
My ATK sensors are currently submerged, but Apex says both are Dry. Earlier they seemed to work, but only when the wiring was reversed (wire 1 in port 2, wire 2 in port 1).
All optical sensors are clean, oriented properly, and plugged in securely.
So right now:
Skimmer sensor = stuck on Wet even though dry.
ATK sensors = stuck on Dry even though wet.
Literally nothing has changed in my setup between when it was working and now. Did all the sensors fail at once, or is something else going on (firmware bug maybe)?
At this point, the only Apex function I trust is the DOS doing AWC. Everything else has been frustrating. Any ideas or fixes?
