Forum Replies Created
-
Posts
-
Looking at the app, many of the values in Options are seldom changed and don’t need a slider bar, IMO. There are quite a few values in the app that should only be changeable with a password, IMO. The need for a slider bars, in some instances, seems to me to be non existent. The need for entering precise values, and the need to protect those values from accidental or malicious changes, seems critical.
Realistically few end users are going to be interested in modifying Rays firmware. But it is easy to control open sprinkler externally. Using the program functionality in OS is probably the safe way, as OS is then responsible for valve closing.
While irrigation wouldn’t normally be run from a pressure tanks, I’m sure some drip systems are configured that way. A drip system could be run many times per day with a long station delay assuring adequate water pressure for other uses.
My previous post said “mechanically setting the rain flag”. I should have said “activating the rain sensor”: As in activating the rain sensor circuit as a system not ready indicator. Perhaps another way would be to programmatically alter the rain flag.
A station delay longer than four minutes would be useful for automatic fall blow-out too. I would like a longer than four minute delay to let the compressor recharge and then cool off before continuing to the next station. Not a big deal for me, of course. But I think dnnn needing a longer than four minute recharge period for his water supply.is not unique to him. A lot of people don’t have city water or a high volume well.
If the delay time becomes 16 bit, perhaps the slider for that value in the smartphone app could be made non-linear.
A thought for dnnn is to investigate mechanically setting the rain flag when the water system isn’t ready. Although I not sure how the scheduler responds to the rain flag turning on and off intraday.@Dan in CA wrote:
For controlling irrigation with soil moisture probes, multiple probes at different depths are generally used at each monitoring location. The frequency of irrigation is controlled by shallow probes and the duration of each irrigation is determined by deeper probes.
………
Shallow soil moisture is easy to accurately predict from an ET models. Variance over time from ideal will show up in the soil deeper in the rootzone. Also by just walking the lawn most people can tell if the top couple inches has dried out. So I believe that accurately measuring deeper moisture is more important than determining overall average moisture, especially when growing non-annuals (either ornamental or agricultural)
Testing soil probes for accuracy at determining when field capacity is achieved seems like an important early effort. Accurately flagging field capacity allows a reset of the ET model at 100%, zeroing out any drift in the model from reality. This may not be relevant to users with little rainfall, as I assume soils at field capacity are an infrequent occurrence.
Acclaim soil sensor install :https://www.youtube.com/watch?v=W4Wninln-uk
As a long term goal, perhaps accumulating user adjustments is worthwhile. Does a particular user choose more or less water than the model suggests? Do all user have a tendency towards altering irrigation towards more or less water?
