Why am I getting this auto top off notification from apex
- Thread starter lubeck
- Start date
- Tagged users None
LOZReefer
Active Member
Send screenshot of what you have coded in the alarms output
Edit: No need, maybe. Can see the code there. You'll need to figure out which sensor Swx10_2 is. Either water is hitting it or it's malfunctioning. Based on that info, you need to decide if it should alarm if that sensor is covered and delete the code you have for that alarm if it's the sensor being covered is intended.
Essentially, if Swx10_2 is the lower sensor on the ATK, you should delete the alarm.
Edit: No need, maybe. Can see the code there. You'll need to figure out which sensor Swx10_2 is. Either water is hitting it or it's malfunctioning. Based on that info, you need to decide if it should alarm if that sensor is covered and delete the code you have for that alarm if it's the sensor being covered is intended.
Essentially, if Swx10_2 is the lower sensor on the ATK, you should delete the alarm.
Last edited:
LOZReefer
Active Member
Yeah, delete the bottom line.
Turbulent water in the sump is covering (closed) and uncovering (open) that sensor causing the alarm to trip.
Every time the ATK kicks off, it fills until that lower sensor is covered (closed) then turns off. No need for an alarm on that one.
Turbulent water in the sump is covering (closed) and uncovering (open) that sensor causing the alarm to trip.
Every time the ATK kicks off, it fills until that lower sensor is covered (closed) then turns off. No need for an alarm on that one.
LOZReefer
Active Member
If you wanted to, you could create a virtual output called like "Sump_Low" or something like that where if Swx10_2 is open for 60 minutes or so, then turn on the alarm. I can help you with that if you'd like
Last edited:
LOZReefer
Active Member
So the ATK only fills to the bottom sensor. The top sensor is just a backup in case the bottom one fails.
You would need to create a virtual output - I named mine "Sump_Low" and it's code looks like this:
Then in your alarms settings it looks like this.
You would need to create a virtual output - I named mine "Sump_Low" and it's code looks like this:
Then in your alarms settings it looks like this.
OP
OP
lubeck
Valuable Member
Do I put the first code in your images above where I deleted #7? Does the second image automatically happen?So the ATK only fills to the bottom sensor. The top sensor is just a backup in case the bottom one fails.
You would need to create a virtual output - I named mine "Sump_Low" and it's code looks like this:
Then in your alarms settings it looks like this.
I’m noticing the ATO is not going off and the sump is low. The pump still works because I can manually turn it on.
LOZReefer
Active Member
No, the first image is the Virtual Output. Might be worth looking for a video on youtube or just a google search on how to create one.
If your ATO is not filling then you might have deleted something in that output
If your ATO is not filling then you might have deleted something in that output
OP
OP
lubeck
Valuable Member
It’s odd. The only thing I deleted is #7 and since then I’ve heard it go off. Doesn’t make sense. What will the code you are suggesting actually do? If it doesn’t go off in an hour it will turn on?
LOZReefer
Active Member
Send pic of your EmailAlm_I5 code and your code for the ATK/ATO (not sure what you set the name as for this).
Might be worth enabling logging for the ATO as well and you can check the logs for when it turns on and off
Might be worth enabling logging for the ATO as well and you can check the logs for when it turns on and off
Last edited:
OP
OP
lubeck
Valuable Member
Yes. What I think happens is if the sump level changes quickly it doesn’t register and doesn’t go off. Once I got it back to the first sensor it started doing it automaticallyInteresting. This looks correct. Is the ATO set to Auto in the dashboard?
LOZReefer
Active Member
Turn on logging for the ATO. This will allow you to see how often and how long the ATO kicks on.
The ATO waits 1 hour between so that it doesn't put too many short cycles on the pump so don't expect it to keep the level perfectly stable. It will drop slightly below the sensor but if it's within that Min Time, it will not turn back on until the Min Time has passed. See below image of code applying it to wait 60 minutes, you can lower this to 30 minutes (030:00) if it's not keeping up with your evap. I personally wouldn't go lower than 30 minutes though.
Also worth noting, the When On setting says that when the ATO has been on for 5 minutes straight, turn off. I would be surprised if your ATO is actually running the full 5 minutes and still not keeping up with your evaporation rate. This is how it is supposed to look.
The ATO waits 1 hour between so that it doesn't put too many short cycles on the pump so don't expect it to keep the level perfectly stable. It will drop slightly below the sensor but if it's within that Min Time, it will not turn back on until the Min Time has passed. See below image of code applying it to wait 60 minutes, you can lower this to 30 minutes (030:00) if it's not keeping up with your evap. I personally wouldn't go lower than 30 minutes though.
Also worth noting, the When On setting says that when the ATO has been on for 5 minutes straight, turn off. I would be surprised if your ATO is actually running the full 5 minutes and still not keeping up with your evaporation rate. This is how it is supposed to look.
Last edited:
Similar threads
