Do you have a predict issue of zones not being shown when they are not either manual control or disabled?
Announcement
Collapse
No announcement yet.
New user, several questions
Collapse
X
-
Originally posted by Michael McSharry View PostDo you have a predict issue of zones not being shown when they are not either manual control or disabled?
A few minutes later after R5 starts, same thing...
At present I have all Areas scheduled for fixed days/times to start. I'm slowly figuring out that the PI may prefer to run on a more automated basis (ET calcs, etc.) and perhaps these pages aren't able to display the data correctly with start date/time constraints. I may eventually move to ET calcs but for now I'm more comfortable with scheduling.-Wade
Comment
-
This is probably just a slightly different manifestation of the same issue in the previous post. These images were both take a few moments ago.
Area 1 is scheduled to start at 7:00pm today. Inhibit device correctly reports this.
But the run list doesn't show the Area 1 zones scheduled today at all. I'm confident they'll run, as they did this morning, but I can report back later to confirm if you'd like.
-Wade
Comment
-
When I looked this morning at run list I see A4 zones scheduled for their first run cycle today. I also noticed that R11 and R15 are programmed with 0 auto times. I will investigate further if the 0 causes any issues. I will also try some other scenarios to try to replicate your observations in the run list. If I do not have success then I will add debug to the prediction logic so a trace can be obtained from your system.
Comment
-
I did find an issue that was caused by javascript for the popup in rainfall device that was used to assess if predicted time will be affected by the current day's rainfall. I also added detail in the debug for prediction in general. After we confirm the prediction is working as expected then this debug should be pared down so the file does not get too big too fast.
The update will be at http://mcsSprinklers.com/mcsSprinkle...20_0_4_HS3.zip. The only file needed is MCSSPRINKLERS_2009.dll to replace the existing one in your HS folder. If want version to be updated to 2.20.0.4 in HS display then also replace HSPI_MCSSPRINKLERSP.exe.
Internet has been problematic today and upload just does not want to happen right now. I will try a little later. This often happens when Google, Apple, or Microsoft push updates that consume all my meager bandwidth.
Comment
-
Thank you Michael. I've copied over both the .dll and .exe.
On restart, the run list populated with the Area 4 zones scheduled to run and immediately began watering. Local time was 6:57, but the area was scheduled to start at 8:15pm. Once the first zone (R12) was done watering, it remained at top of the run list, showing a start time in the past (12am today).
Here's the run log showing R12 ran for 3 minutes.
Before I finished typing the post, the next zone finished. Here's the run list after R13 turned off.
-Wade
Comment
-
Originally posted by Michael McSharry View PostIt is hard to establish a starting state following a restart. There are many reasons that a restart occurs, such as a power outage, so wait until tomorrow when everythings gets a midnight restart. This can nearly be simulated with a Zone Satus Stop All, Restart button bushes.
I have a couple other questions, but I'll start new threads for them to make tracking simpler (for me at least).
Thanks.-Wade
Comment
Comment