Fuge light config.. what am I missing?

southerntnreefer · Nov 23, 2020

So I'm sure it's something stupid I'm missing, but what did I do wrong? At 2200 last night the fuge light did not come on. I had to manually put it on in fusion... Even tried a bit and then putting into auto and it turns off...

homer1475 · Nov 23, 2020

Whats your temp?

You apex logic says to not turn the light on, or turn it off if your temp is above 81.5

The switch has to be on AUTO to run through it's programming. Off is off, and On is on.

southerntnreefer · Nov 23, 2020

current temp is 78 on the dot. I want it to come on at 2200, and turn off at 10 am.

LiveWire · Nov 23, 2020

Do you have more than one temp probe?

Also If you click on the advanced tab what is the code?

southerntnreefer · Nov 23, 2020

LiveWire said:
Do you have more than one temp probe?

Also If you click on the advanced tab what is the code?

Just one temp probe currently.

homer1475 · Nov 23, 2020

In apex logic your light should turn on @ 22:00, and shut off at 10:01.

LiveWire · Nov 23, 2020

Yes like Homer Said. This is how mine in written

Fallback OFF
Set OFF
If Time 20:00 to 10:00 Then ON
If Time 10:01 to 19:59 Then OFF

homer1475 · Nov 23, 2020

With the "Set off" statement, you do not need the "off" coding.

The "set off" statement shuts the light off until the time statement comes into play.

LiveWire · Nov 23, 2020

So then I would think this would do it for you.

Fallback OFF
If Time 22:00 to 10:00 Then ON
If Time 10:01 to 21:59 Then OFF
If Tmp > 81.5 Then Off

Or

Fallback OFF
Set OFF
If Time 22:00 to 10:00 Then ON
If Tmp > 81.5 Then Off

homer1475 · Nov 23, 2020

If you want it to go off at exactly 10:00, then change the time statement to 09:59. The statement won't evaluate to "true" until the time 10:01.

This is just how apex logic is quantified.

southerntnreefer · Nov 23, 2020

homer1475 said:
If you want it to go off at exactly 10:00, then change the time statement to 09:59. The statement won't evaluate to "true" until the time 10:01.

This is just how apex logic is quantified.

Not exact but as long as it's that time frame were good

Hows this then?

homer1475 · Nov 23, 2020

Just for reference this is my T5 white setting:
Fallback ON
Set OFF
If Time 09:00 to 18:59 Then ON
If Tmp > 84.0 Then OFF

Notice the 18:59. that way might light shuts off exactly at 7pm. You do not need an "off" time statement as the "Set Off" shuts the light off.

Apex reads and evaluates codes starting from the top down. The last "true" statement is the one that gets evaluated.

So in my coding, the "set Off' is evaluated first, and the apex stops there if the "time" statement isn't evaluated as true. If the time is evaluated as true, then it skips the "Set Off" statement and evaluates the "time" statement. Now the next line, my temp statement. If the temp statement evaluates as true, it turns the light off, then if the temp statement evaluates as false, it reverts back to the time statement.

southerntnreefer · Nov 23, 2020

I changed it finally to this, kicked it back to auto and it's still on. Which is what I'd want. Until 10 cst.

homer1475 · Nov 23, 2020

I personally would delete the "MIN time" statement, but it should work just fine.

All the "MIN TIME" statement does is leave the light in it's current state for 1 minute after the programming has been evaluated.

Basically your light has to remain in the off state more a minimum of 1 minute before it will actually shut off.

southerntnreefer · Nov 23, 2020

homer1475 said:
I personally would delete the "MIN time" statement, but it should work just fine.

All the "MIN TIME" statement does is leave the light in it's current state for 1 minute after the programming has been evaluated.

Basically your light has to remain in the off state more a minimum of 1 minute before it will actually shut off.

And this is why im learning to just love the advanced tab for every outlet. One i can do what i actually want, that the GUI manages to mess up. I wasnt sure what that setting was and left it standard. Its to turn on at 2200, and off at 10 am now. That should be a good start.

homer1475 · Nov 23, 2020

You might want to change it to "Fallback off"

You do not want the light to run 24/7 if the eb loses communication with the brain.

homer1475 · Nov 23, 2020

I have never used the "basic" function of programming. I learned early on it's best to program them yourself in the "advanced" tab, if you understand the logic.

And you can program things the way you want them without having to adjust your programming to fit the predetermined setting by neptune. Some are useful and helpful, but most times it's just easier to use the "advanced" tab.

homer1475 · Nov 23, 2020

You could also add a PH statement in case your PH gets too high(unlikely, but it can happen).

If PH > 8.45 then off

southerntnreefer · Nov 23, 2020

homer1475 said:
You might want to change it to "Fallback off"

You do not want the light to run 24/7 if the eb loses communication with the brain.

Done!

homer1475 said:
I have never used the "basic" function of programming. I learned early on it's best to program them yourself in the "advanced" tab, if you understand the logic.

I do alot better actually than whatever they have in there for the " easy route" plus i wanted a ton of extra stuff. I have defers on quite a bit of equipment that draws water out of the sump, and the ato unit for power loss as well as other things just to allow the system to stabilize before anything else kicks on. I needed the advanced to do that as well.

Im done programming for a while. Next up will be in a few weeks when a breakout box and floats get here so i can add monitoring for my non apex integrated ATO, Skimmer kill switch as well as feed mode buttons etc.