MoonLights() question
Posted: Wed Jan 02, 2013 2:50 pm
So, I see we have the MoonLights() function which is opposite the StandardLights.
We also have the ActinicOffset variable which works with the StandardLights by going on earlier than the Standard and staying on past the Standard by whatever ActinicOffset is set for.
So, my Actinic offset is set for 120 minutes.
11:08am - Actinic On
1:08pm - Standard On
9:49pm - Standard Off
11:49pm - Actinic Off
I'm already at 9 hours of Standard Lights, and 13 hours of Actinic.
My issue is that if I wanted to use the MoonLights() function to say, use my fuge light, then it would be on for 15 hours. So, can we either have a standard light function to be opposite the Actinics? or use the current MoonLight function but respect the ActinicOffset?
My goal is to have as much as possible based on the standard memory locations and the ease of use by just declaring the port by the basic function if possible.
We also have the ActinicOffset variable which works with the StandardLights by going on earlier than the Standard and staying on past the Standard by whatever ActinicOffset is set for.
So, my Actinic offset is set for 120 minutes.
11:08am - Actinic On
1:08pm - Standard On
9:49pm - Standard Off
11:49pm - Actinic Off
I'm already at 9 hours of Standard Lights, and 13 hours of Actinic.
My issue is that if I wanted to use the MoonLights() function to say, use my fuge light, then it would be on for 15 hours. So, can we either have a standard light function to be opposite the Actinics? or use the current MoonLight function but respect the ActinicOffset?
My goal is to have as much as possible based on the standard memory locations and the ease of use by just declaring the port by the basic function if possible.