Hi, the software has been mainly designed to manage time interval at minute level, not shorter than that. Actually the scheduler ignore the "seconds" information. Not saying that the system cannot work at faster scheduling, it was a decision taken to keep safety margins.
Hi, I would use this way to lit up a LED outside my controlbox that have to blink let say 3 sec ON and 3 sec off, just to see if the system is up-and running; is it possible to use this method or do you thing that too many events will be triggered? I read here somewhere that every time an event is triggered (both sensor reading or something similar) there is a lots of computational works so it's better not to have events too close each other... What would you suggest? Thankyou
Hi, the software has been mainly designed to manage time interval at minute level, not shorter than that. Actually the scheduler ignore the "seconds" information. Not saying that the system cannot work at faster scheduling, it was a decision taken to keep safety margins.
Hi, I would use this way to lit up a LED outside my controlbox that have to blink let say 3 sec ON and 3 sec off, just to see if the system is up-and running; is it possible to use this method or do you thing that too many events will be triggered? I read here somewhere that every time an event is triggered (both sensor reading or something similar) there is a lots of computational works so it's better not to have events too close each other... What would you suggest? Thankyou
In case you need only daytime operations, it is possible to set the bottom section of the page:
For example if you need the irrigation to happen only from 6am to 6pm, you can set the operational time START: 06:00, END: 18:00.
Yes you can use the automation and the timetrigger.
With reference to the below configuration you need to change two parameters:
Actuator values (END) = 60x5 = 300 sec
Pause between Activation = 60 min