Apex code - Sanity check

[LobsterOfJustice]

Can anyone tell me why my ATO outlet has switched itself from AUTO to OFF twice in the past month? My understanding is this is only possible from the "when" command, but according to my program the that line should never actually trigger. I had included it in the event I accidentally manually switched the outlet to ON - which is what I figured happened the first time. But now it has switched itself to OFF a second time, so something is up.

OSC 000:00/000:45/004:15 Then ON
If SumpLo CLOSED Then OFF
If SumpHi CLOSED Then OFF
If Power EB832_2 Off 000 Then OFF
When On > 001:00 Then OFF

 

[link81]

why are you running your ATO off an OSC command?
don't you want to run it based off your switches?
in mine, i have a low switch that turns on the ATO, and it shuts off after the lower switch has satisfied.

i'm not 100% sure its the best way, but it works on mine, and minimizes the on/off cycles of the pump.

Fallback OFF
Set OFF
If ATOLow OPEN Then ON
If ATOHig CLOSED Then OFF
Defer 005:00 Then ON
Defer 001:00 Then OFF

 

[rkpetersen]

OSC command is a valid way to use an ATO. Especially if you're dosing kalkwasser.
You're correct, the When On statement should not be triggering with that code.
Could be a firmware issue. I'd go to the Modules page and do a firmware update on the FMM, even if it says the current version is OK.

 

[link81]

OSC command is a valid way to use an ATO. Especially if you're dosing kalkwasser.

interesting. Don't you have to modify the command then whenever evap rate changes?
Maybe not as big a deal for people with conditioned houses year round?

 

[LobsterOfJustice]

interesting. Don't you have to modify the command then whenever evap rate changes?
Maybe not as big a deal for people with conditioned houses year round?

The OSC duration represents the most I would possibly evaporate, plus some overage. Then I have two float switches which override the OSC command and if the water level reaches either of these two switches the ATO will remain off. This is a safer way of doing ATO compared to activating the ATO based on switches which are prone to fail.

 

[LobsterOfJustice]

OSC command is a valid way to use an ATO. Especially if you're dosing kalkwasser.
You're correct, the When On statement should not be triggering with that code.
Could be a firmware issue. I'd go to the Modules page and do a firmware update on the FMM, even if it says the current version is OK.

Thanks for the confirmation. For clarity, this is not running through an ATK/FMM. This is just a peristaltic pump plugged into a EB8 outlet and two floats plugged into breakout box. But I will go through and update all modules and make sure base unit is also up to date.

 

[link81]

oooohhhhh! ;Bookworm

i see now. the OSC command basically gives the ATO a "window" that it's allowed to run. good idea. i like that quite a bit. i'll be switching mine over i think.

 

[LobsterOfJustice]

oooohhhhh! ;Bookworm

i see now. the OSC command basically gives the ATO a "window" that it's allowed to run. good idea. i like that quite a bit. i'll be switching mine over i think.

Well whatever you do, apparently don’t add a “when” command. ATO turned itself off a few days into vacation, came back to a dead gem tang.

 

[rkpetersen]

Well whatever you do, apparently don’t add a “when” command. ATO turned itself off a few days into vacation, came back to a dead gem tang.

To avoid this, you can keep an eye on your tank's outlets and probe parameters via the phone app while on vacation.
Also, add "If Error ATOName Then ON" to your base_email notifier outlet. Whenever the When On line triggers, the Apex sees that as an error and sends an alert.