Forum Replies Created
-
AuthorPosts
-
Rogers WateringParticipantThanks again @Ray, this looks like it works as you described. It also look like I was overthinking the schedule. I can just run 1 program and have it start all four stations at the same time. The sequential logic queues them up one by one with the station delay in between each pair. This is probably better than I was hoping for 🙂
Attachments:
Rogers WateringParticipantI am using “Hardware Version: 3.2 – DC”, so it sounds like I am good to go.
Thanks!
Rogers WateringParticipantThanks for the suggestion @Ray. Is it safe to basically short out the four station outputs or would I need to add a diode or something to each to make it safe? I’m being a bit cautious now as I was careless and already destroyed one of the stations 🙁
i.e. Station 1 Station 2 Station 3 Station 4 | | | | | | | | Diode Diode Diode Diode <-- See None 1 below. | | | | | | | | +-------------+------+------+-------------+ | | Valve | | Common
Note 1: Would diodes or something ever be needed here to protect the station outputs from one another?
If this solution is electronically safe, it sounds like a super simple fix. I assume that serial runs would queue up in the order received and so I could set up the timing as follows for example?
- Station 1 @ Sunrise – 40 Min
- Station 2 @ Sunrise – 39 Min
- Station 3 @ Sunrise – 38 Min
- Station 4 @ Sunrise – 37 Min
This change in approach may also fix what seems like it could potentially be a bug I have with my current config where the first run has a differing water duration from the three subsequent repeats. I did notice that the Zimmerman Last Update time fell in between the first and second run, so maybe that is is the reason rather than a bug.
-
AuthorPosts