ATO program is this correct?

[110galreef]

OSC Code: PLEASE help me understand:
OSC xx:xx/yy:yy/zz:zz Then ON
....means off/on/off
Also the contoller starts each day new at 00:00 to figure it out..correct.

SO

[ATO_Allow]
OSC 000/20:00/160:00 Then ON
means basically that from:
00:00-00:20, 03:00-03:20, 06:00-06:20, 09:00-09:20, 12:00-12:20, 15:00-15:20, 18:00-18:20, 21:00-21:20, the outlet is ON

This is the code I have,
[ATO_Allow]
OSC 000/20:00/160:00 Then ON
If Time 10:00 to 22:00 Then OFF

00:00-00:20, 03:00-03:20, 06:00-06:20, 09:00-09:20, the outlet is ON.

Or does it calculate the time different due to this last stmt If Time.

I went down to look at my ATO this morning, and the ATO_Switch was calling for water (ON), yet it was 09:04 and wasn't adding water?


Here is the full code I ended up with:
[Sump_Low] Virtual Outlet
Set OFF
If Switch1 CLOSED Then ON {This float is CLOSED when DOWN} thus sump level too low, prevent pumps running dry

[ATO_Switch] Virtual Outlet
Set OFF
If Switch2 CLOSED Then ON {This float is CLOSED when DOWN} thus sump needs water
Defer 00:10 Then ON

[Sump_High]Virtual Outlet
Set OFF
If Switch3 OPEN Then ON{This float should be OPEN when UP} thus sump has too much water. Failsafe


[ATO_Allow] Virtual outlet to specify when to pump water. Allowed to pump for 20 mins every 3 hrs. But not between 10am-10pm
OSC 000/20:00/160:00 Then ON
If Time 10:00 to 22:00 Then OFF

[ATO] Physical outlet the ATO pump is plugged into
Fallback OFF
Set OFF
If Outlet ATO_Switch = ON Then ON
If Outlet ATO_Allow = OFF Then OFF
If Outlet Sump_High = ON Then OFF

set up email warning if sump level too LOW or too High

If Outlet Sump_Low = ON Then ON
If Outlet Sump_High = ON Then ON

 

[swearint]

Yes, you understand it correctly. No, the Time statement does not alter the OSC cycle, it just overrides it. So, even though the OSC at 12:10 would have the outlet ON, the Time command overrides and keeps it OFF.

I don't see anything wrong in the code. What is the status of [SumpHigh]?Verify that you have [ATO] set to Auto. Also, you should have enough data now to plot [ATO_Allow], [ATO], and the switches to verify the performance. Just to make sure, what firmware are you running?

Todd

 

[110galreef]

I believe it is 4.01. All outlets were on AUTO.

I will double check the code on switch 3 maybe I have it backwards in the actual code above. we originally talked POST 17

[SumpHigh]
Set OFF
If Switch3 CLOSED Then ON{This float should be CLOSED when UP}

which was backwards. Maybe I entered that by mistake and thus MY FAILSAFE is preventing water to the sump Like it thinks!

Hopefully thats it!

 

[swearint]

Yeah, you will need to upgrade the firmware to at least 4.04 in order to graph outlets. As for [SumpHigh], just look on the status page, if it is ON, there is your problem.

Todd

 

[110galreef]

i will check the version. The Apex was bought new in Oct, so it's only 7 mos old. Should have a pretty updated version, just not sure off top my head.

Last I looked, Sump_High, Sump_Low, were all OFF in the status section. So maybe just let the program run & see if it figures itself out and double check the code close for a simple mistake.

Thanks for all the help

 

[aquamanic]

If you think you have things backwards, just reach in the sump and manually move the float. See if that activates your ATO.

 

[110galreef]

just checked the status and all are on Auto:

ATO_Pump is OFF
ATO_Allow is OFF during the OFF times right now
Sump_High is OFF
Sump_Low is OFF
ATO_Switch is ON,


The code looks right.
So to test a little more... I can either Manually turn the ATO_Allow ON and given the status, should kick on the ATO correct.

Or I could also remove the If time stmt from ATO_Allow too and then it should kick on.

I will try this & see what happens.

 

[110galreef]

It is 15:16 on my apex right now, deleted the if time stmt, updated the outlets & refreshed the status a few times..... and not pumping water? but should be ON from 15:00-15:20.

Hmmm

 

[110galreef]

So i manually turned on ATO_Allow, and then the ATO_Pump turned on. So is there something wrong with my ATO_Allow code:

Fallback OFF
Set OFF
OSC 000:00/020:00/160:00 Then ON
If Time 10:00 to 22:00 Then OFF

 

[swearint]

You don't need Set OFF, the OSC handles both ON and OFF conditions. And you don't need Fallback with virtual outlets. With the Time command as written (10 am to 10pm), ATO_Allow should be OFF right now assuming your tank time is set correctly.

Todd

 

[110galreef]

You don't need Set OFF, the OSC handles both ON and OFF conditions. And you don't need Fallback with virtual outlets. With the Time command as written (10 am to 10pm), ATO_Allow should be OFF right now assuming your tank time is set correctly.

Todd

I know it should be OFF now, but this morning at 09:04 whne the ATO_Pump should have been ON it was OFF.

I will remove the SET & Fallback & see if it works tonight as it should.
Maybe those stmts are messing it up.

 

[swearint]

OK, go into the XML Outlet Report and observe the sequence of ATO_Allow state changes and verify that it is following the expected cycle.

Todd

 

[110galreef]

where do i check the version i have

 

[110galreef]

if in xml, then i have 4.03

 

[swearint]

From the web page: XML > XML Outlet

You should see a listing for today that shows each time an outlet changed state. Scroll through the listing and look for ATO_Allow and verify that it is changing as expected.

Todd

 

[110galreef]

I went in and looked.

ATO_Allow went ON at 2:00 & OFF at 2:20
ATO_Allow went ON at 05:00 & OFF at 05:20
ATO_Allow went on 08:00 & OFF at 08:20

the ATO_Pump came on like it should in those windows.

But why 2am, 5am, & 8am...
not
12am, 3am, 6am, 9am, etc....

 

[swearint]

Sounds like your clock is off by a hour. Check your time zone and DST settings.

Todd

 

[110galreef]

Well originally I had the time set manually and the DST set to automatic. And have time zone -5 set. I double checked the times were right & the time Zone is correct. OHIO.

I then set it to automatically set the time last night. Still shows correct times and still have -5 for the time zone. DST is still enabled.

ATO_Allow still came on at 2:00, 5:00, and 8:00 not 3, 6, & 9??

DST have something to do with it, but the TIME on the display, and computer interface all show correct.

Also when the time's changed here it compenstaed correctly.

 

[aquamanic]

What version of software do you have? Prior to 4.03_4A10 there was a bug where the DST flag wouldn't work if set via the web page - had to set it via the display module.

 

[110galreef]

looks like 4.03_6A10