PredictNextWaterTime Error?

[duhl]

First off, a quick question: Could the calculated strategy be used to start a zone multiple times in a single day?

Now on to the problem at hand...

I'm receiving the following error in the homeseer log every time I view the ControlSystems.asp page:

mcsControlSystems PredictNextWaterTime with Progress 14 Subscript out of range.

All of my start time estimates are the current time and for some reason my zones will not auto-start. And yes, they are enabled and work correctly with "days of week" strategy.

I've tried clearing out the mcsTemperature database (manually deleting all the tables) and having the controls re-create the tables, but still have the same error. Maybe something in the config files?

My Config:
homeseer 1.6.119
mcsTemperature 4.6.0
mcsControlSystems 1.5.2
temp05 with relay05

I can send you my database if needed, but here are the Log Entries:
9/4/2003 3:15:19 AM~!~mcsControlSystems~!~PredictNextWaterTime with Progress 14 Subscript out of range
9/4/2003 3:15:35 AM~!~mcsControlSystems Debug~!~TurnOn=True, TurnOff=False, Override=False
9/4/2003 3:15:35 AM~!~mcsControlSystems Debug~!~Computed ET=1.688501E-02,es=2.274408, d=0.141274, Rn=0, g=0.0672315, light=0, RH=90, Temp=67.2, U=3.576
9/4/2003 3:15:35 AM~!~mcsControlSystems Debug~!~Computed ET=0.5516121,es=2.274408, d=0.141274, Rn=4.221804, g=0.0672315, light=151.0722, RH=90, Temp=67.2, U=3.576
9/4/2003 3:15:35 AM~!~mcsControlSystems Debug~!~Computed ET=0.1230714,es=2.274408, d=0.141274, Rn=0.838368, g=0.0672315, light=30, RH=90, Temp=67.2, U=3.576
9/4/2003 3:15:35 AM~!~mcsControlSystems Debug~!~Computed ET=0.1230714,es=2.274408, d=0.141274, Rn=0.838368, g=0.0672315, light=30, RH=90, Temp=67.2, U=3.576
9/4/2003 3:15:36 AM~!~mcsControlSystems Debug~!~Computed ET=0.1230714,es=2.274408, d=0.141274, Rn=0.838368, g=0.0672315, light=30, RH=90, Temp=67.2, U=3.576
9/4/2003 3:15:36 AM~!~mcsControlSystems Debug~!~Computed ET=1.688501E-02,es=2.274408, d=0.141274, Rn=0, g=0.0672315, light=0, RH=90, Temp=67.2, U=3.576
9/4/2003 3:15:36 AM~!~mcsControlSystems Debug~!~Computed ET=0.5516121,es=2.274408, d=0.141274, Rn=4.221804, g=0.0672315, light=151.0722, RH=90, Temp=67.2, U=3.576
9/4/2003 3:15:36 AM~!~mcsControlSystems Debug~!~Future: Rain=0.4, ET=0.2306615

[Michael McSharry]

Sorry I missed your post a few days ago.

The subscript error is comming for a section of the code that applies to the "Calculated" control strategy which seems to be different that your intention of day-of-week.

My best hope of isolating the problem is with your ini file. Dont know if I need them all, but the database and mcsTemperature.ini ,mcsControlSystems.ini , and mcsForecast.ini are all used.

There was some discussion on changing the control resolution from 24 hours to 12 hours to allow AM and PM watering. Is this your desire for multiple times within a day?

[duhl]

First off, let me say mcsTemperature is an awesome add-in, and mcsControlSystems looks like the most promising add-in I need. What language are you writing mcsControlSystems in? Any chance of getting the source code?

Let me answer the multiple water schedules next. I would actually like to be able to use the calculated schedule with no regards to the day of week schedule (except for the do not water day of week). If it's 105 degrees outside, some parts of the yard may get watered two or three times a day and depending on wind and the other criteria on the "do not water" portion, allow or disallow watering. I am about to plant some new seed and if it's cool/overcast, only water once or twice a day, but if it's hot and sunny water every few hours as needed.

If that is not do-able, am/pm would probably suffice for non-calculated scenarios, but I would then have to create some scripts that run hourly and check environmental conditions to water as needed.

BTW, with the latest version, the dependency of the scheduling seems to be very flaky… In the past week only two days did things get watered, and I believe I had to start them manually. I actually have it mcsControlSystems uninstalled at the moment running on manual scripts and timed events. It appears that the scheduling is working, based on the debug values (TurnOn=True, TurnOff=False, Manual=False) but the sprinkler zones never actually turn on. I have mcsTemperature debugging turned on as well, and it doesn’t appear that it’s even trying to turn them on. Sometimes, I can manually turn them on/off using events or remote after resetting the COM port, but not very reliably. It always works from the temp05 debug console within mcsTemperature. And with mcsControlSystems uninstalled/disabled everything seems to run as scheduled.

BTW, when I had mcsControlSystems installed, I had all of my scheduled events disabled.

As far as the files go... They are zipped up and attached.

TIA and keep up the GREAT work! I will definately buy it as soon as these bugs are worked out.

[Michael McSharry]

The calcualted and measured control strategies should be able to support multiple cycles per day. The problem area that I have to work through is how to make it compatible with manual control and the ASP page which makes some assumptions about one water cycle per day.

Done in VB6. Just send me an email indicating your intention to not do things I would not appreciate and I'll return a copy of the source.

I have not looked at your data yet, but I will. You should be able to look at the status variables that are created to determine what criteria is preventing watering.

The subscript error is related to ASP procesing and should not affect the actual control of the zones.

I do not understand the COM port dependency you reference. Could you clarify?