July 21, 2020 at 5:26 pm #67455
Just got the latest firmware installed and can now log into the controller through the W5500 Ethernet connection, with all my programs intact. I will start running things manually over the next week and will let you guys know what I find.
Thanks Ray!July 21, 2020 at 11:21 pm #67459
Still no controller crashes, but I can no longer view the log entries. Whenever I ask OS (app or browser) to display the log entries, the cursor spins for several seconds and then it tells me “Error retrieving log data. Please refresh to try again.”, and refreshing doesn’t work either.
Before I try rebooting, I wanted to find out if there’s anything else I should try.
Is it possible this is related to the 2048 byte buffer issue?July 22, 2020 at 7:37 am #67464
Try to change the log period to a day. Br default it’s 7 days. If you have a lot of log records over 7 days it will not be able to retrieve that many. Restricting it to one day and see if it shows up.July 22, 2020 at 12:35 pm #67467
Yep… that did the trick. So does this mean it’s caused by the 2048 byte buffer issue?July 23, 2020 at 12:27 pm #67489
Yes, it’s possibly related. I’ve just posted a script that can be used for diagnosing certain firmware issues:
you can try the ‘Json log (jl)’ API, start with ‘Today’, then go back to 1 day, 2 days and so on. It’s possible that at some point the json log data gets truncated, becoming invalid. If the 2K theory is correct, you can check the number of characters in the log data at that point and it’s probably more than 2K. Updating your firmware to the Jul18 version should fix this issue.
July 27, 2020 at 12:25 am #67549
- This reply was modified 1 week, 6 days ago by Ray.
@bena: it just occurred to me that when your controller lost connection, you should check if the IP address may have changed — maybe your router assigned a different IP to it upon DHCP renew. You can always click B1 on the controller to find out. If the IP indeed changed, you can either set a DHCP reservation on your router to reserve a fixed IP, or set a static IP on OpenSprinkler.July 27, 2020 at 7:59 am #67556
Hmm, I’ll double check when it happens again. The last time I checked, the OpenSprinkler continued to respond to pings on the expected IP address. But theoretically, another device could have taken over the IP and started responding. I don’t think that’s the case, but I’ll check.July 31, 2020 at 9:45 am #67655
To confirm my previous observation, in my case the IP address does not change on the OpenSprinkler display after it becomes unresponsive.July 31, 2020 at 10:04 am #67658
@beta: I am not sure what else to try honestly. So far your is the only case where even with W5500 it loses response. I honestly don’t know where to start to diagnose the problem.July 31, 2020 at 10:44 am #67660
Actually, your work to debug the ENC28J60 module is helping. As discussed in the other thread, I’ve reverted to the ENC28J60 module with the debug firmware and as you identified it detected late collisions on my network. Since I’m seeing the same behavior with both the ENC28J60 and W5500, I can focus on troubleshooting my cabling for now.August 5, 2020 at 6:51 pm #67741
Sorry this took so long to reply to… got lost in the shuffle. If I reduce the number of days of log entries I ask for it is able to display them. I tried using the API debug script you provided, but I think I might need to go back more than 6 days to see a failure, because I’ve had the system disabled for a couple of days. All I can say is that from within the OS app (iOS or macOS), reducing the number of days eliminates the error.
And BTW, so far no lockups / freezes, so the W5500 sure looks like it has completely solved my crashing problem.
If you figure out what’s going on with the ENC28J60 module, do you think the older 2.3AC hardware might start working again? I have another sprinkler system I would like to convert to OS, and if I can re-use my old hardware that would be great.
Thanks Ray.August 5, 2020 at 6:59 pm #67742
Regarding log: there is a variant of the jl API that allows you to retrieve log data from any specified start date and end date. Details can be found in the API document:
About ENC28j60: as I said in this post:
I’ve done everything I can to debug and the latest version is 2.1.9(7) available for both OS 3.2 and OS 2.3. If this still doesn’t solve the freezing issue, I don’t know what else to try — there is no means for me to debug since I cannot reproduce the problem.August 5, 2020 at 7:17 pm #67743
Okay, it looks like I get to 1883 characters of returned log data when it runs into errors, so I guess the remaining bytes in the 2K buffer are part of the packet formatting?
Does 2.1.9(7) solve this 2K buffer problem when using the W5500? I’m currently running 2.1.9(4).August 5, 2020 at 11:11 pm #67749
Per my post here:
is your controller running Jul 18 version of the W5500 firmware? If not, you should update. If you are not sure, use the test API script and check the debug (/db) API, it shows the date the firmware was compiled.
There is no 2.1.9(7) for W5500 yet — all the minor revisions from (5) to (7) are meant to address ENC28J60 and none of them has to do with W5500.
- You must be logged in to reply to this topic.