zone 1 does not stop

[GaryDN]

This started yesterday once a zone starts it will not stop, sometimes the next zone will run will the first is running. they dont seem to end.
attached is the ini file but not sure where the log file is, or do you want the HS logs?

thanks for the help

[Michael McSharry]

The Run Log page shows the control for OFF and ON. Look there first. The Serial IO page shows the low level communications with Rain8Net. Debug logs are enabled at the bottom of the Other Page. A facility is provided to email them to yourself or they can be obtained from the \html\mcsSprinklers\Data folder where each new log contains the datetime when it was created.

If the Run Log shows the OFF command then look at Serial IO Page to confirm the Rain8 Acknowledged it. If the Run Log does not show it then a debug log file will be needed for analysis.

[GaryDN]

you can see the run log is not turning off the front yard after 12 minutes, it does turn off the zone after 28 minutes, so it is communicating with the controller.

debug and pixs attached



[ATTACH]n1409061[/ATTACH]

[Michael McSharry]

If you were to look in the Serial IO page and I believe in the HS log too you will see that the communication with the Rain8Net is not good. You also see it in your screen shots with Red color on the status for R9. The debug stops at 12:44, but below is an extract until then.

8/6/2020 12:23:26 PM 637323134069516576 | mcsSprinklers | Zone R9 has been declared failed after multiple attempts due to timeout in expected response
8/6/2020 12:25:21 PM 637323135210798773 | mcsSprinklers | Zone R9 has been declared failed after multiple attempts due to timeout in expected response
8/6/2020 12:27:20 PM 637323136409420240 | mcsSprinklers | Zone R9 has been declared failed after multiple attempts due to timeout in expected response
8/6/2020 12:29:20 PM 637323137609166836 | mcsSprinklers | Zone R9 has been declared failed after multiple attempts due to timeout in expected response
8/6/2020 12:31:21 PM 637323138811991970 | mcsSprinklers | Zone R9 has been declared failed after multiple attempts due to timeout in expected response
8/6/2020 12:33:20 PM 637323140009423989 | mcsSprinklers | Zone R9 has been declared failed after multiple attempts due to timeout in expected response
8/6/2020 12:35:21 PM 637323141211168311 | mcsSprinklers | Zone R9 has been declared failed after multiple attempts due to timeout in expected response
8/6/2020 12:37:20 PM 637323142409646502 | mcsSprinklers | Zone R9 has been declared failed after multiple attempts due to timeout in expected response
8/6/2020 12:39:20 PM 637323143609741937 | mcsSprinklers | Zone R9 has been declared failed after multiple attempts due to timeout in expected response
8/6/2020 12:41:21 PM 637323144811267977 | mcsSprinklers | Zone R9 has been declared failed after multiple attempts due to timeout in expected response
8/6/2020 12:43:20 PM 637323146009460480 | mcsSprinklers | Zone R9 has been declared failed after multiple attempts due to timeout in expected response

In essence mcsSprinklers sends a command, but the Rain8Net is not responding such as the pair below.

8/6/2020 12:25:00 PM 637323135009989814 | mcsSprinklers Debug | NET(0) OUT | 40, 01, 31
8/6/2020 12:25:06 PM 637323135060139117 | mcsSprinklers Debug | Net Send Timeout

My experience with the Rain8Net is that it is sensitive to the COM port providing sufficient negative swing voltage. If memory serves me it needs to be under 0.2v and many of the USB/Serial devices do not get this close to zero. The hardware is interfaced via RS232. RS232 has a -12V and +12V voltage swing, but common practice with computers is to use 5V and Gnd for the COM ports. The Rain8Net PRO improved on this with use of the MAX32 chip at the connector interface.

I'm guessing that the valve turned OFF due to the timer inside the Rain8Net. The debug log did not extend to cover the 12:47 OFF in the log. I would like to see the log that covers this time so I can be certain I understand the behavior that was seen by mcsSprinklers.

mcsSprinklers should do better at handling this failure mode. Protections are oriented to auto mode operations and this one is a Manual mode one. I will look into this.

I also suggest that you reprogram your timers in the Rain8Net to be consistent with the maximum you want a zone to run on any given cycle. I think 12 is your max times so something like 15 minutes in the Rain8Net would provide a more effective watchdog.

[Michael McSharry]

I did update mcsSprinklers to consider a failed zone to have been at the commanded state rather than assuming it was OFF in manual mode. Update at http://mcsSprinklers.com/mcsSprinklersP_2_20_4_32.zip

[GaryDN]

I will email you the rest of the log and reset the serial connections. maybe even try a differnt serial to usb controller and update to the version you have here. thanks!

[GaryDN]

so I did some resetting connectors and loaded the new software. still did not work. I did change ports for the serial connection and now it seems to work. going to run it a few days and see

thanks

[Michael McSharry]

Please send the log with the newer version so I can see what is happening.

[GaryDN]

I cant find your email address the logs are to large for posting

[Michael McSharry]

mcsSolutions at CenturyTel dot net