October 28, 2017 at 10:09 am #48157
As you know I have over 15 OS 2.1,2.2 and 2.3AC units working and I have not run in to much issue. Recently we purchased quite a few of the os3’s and I began to deploy them 2 weeks ago. I use them for my irrigation and area common lights. The common lights are based on Sunset and Sunrise. I have come to find out that my lights are not staying on and they are not being logged because it appears that the OS3 is rebooting. It got to a point where anytime I tried to call up a log it would reboot. So I swapped the controller with another new one and it is doing the same thing. The reboot when trying to view the log started again as well 3 days later. But the rebooting happened from day 1.
I am going to set up a few bench tests today. There is something definitely wrong here.
My deployed controller has 2 expansion units, my lights are on station 40. I have a tp link nanoap powered through the USB port on the OS3 (I have tried it without it connected to the OP3 usb port and this happens as well.)
Please help as this is a critical problem.November 1, 2017 at 11:53 am #48183
I continue to struggle with this. Sadly the controller offers no real trouble shooting help. The log is not available. When the controller reboots there is no info on its up time. I have looked at the api and I did not see a variable logging the controllers start up time, as this may be helpful.
I have changed out relays, controllers, I may try swapping the expansion units.November 1, 2017 at 12:26 pm #48184
Just a thought – could it be a power problem? Maybe the OS3 is losing power for some reason?November 1, 2017 at 1:06 pm #48185
Thanks for chiming in. I have pulled my nano router off the controllers usb port. (Ray had suggested that I power them from the OS 3 usb port. I was not a big fan of wifi only). It is now powered separately but from the same power source. The router maintains an up time and does not show a loss of service. When I had it plugged in to the controller it would reset as well.
My setups are unique as I use ubiquity Line of site radios in the field to supply internet to these units. I have over 15 of the 2.3-2.1 units deployed without issue. This is the first 3.0 that I have deployed with the same setups and it has been a problem. I have done my best trying to isolate the issue. I found another thread where someone reported rebooting but it was on a 2.3 DC unit. Which I have one of those and it appears to be working without issue.
As a backup I am also using a Levington smart switch as a fall over now so my lights stay on, but I 30 irrigation stations that are being disruptive.
Once it get to a point where I can no longer view the logs, I have to reset to defaults and reprogram. Once this is done the rebooting appears to only happen at night when the lights are on and possibly when the stations are running.
It is frustrating but I am trying to solve the problem and come up with proper diagnosing steps to be able to quickly resolve issues in the future.November 6, 2017 at 11:17 am #48219
I think I am close to narrowing the problems down. My field unit has not reset all week. Ever since I stopped powering the nano Router from the usb port of the OP3. I was able to reproduce it on my bench as well without any load on it other than the nano router. Once it gets to the point where it resets every time you try to access the log, the only way to fix it is to factory reset the controller.
With that said, since I have pulled the nano router off from the OP this has not happened. Which is good news, I can work with this. I do suspect that this behavior is triggered under certain conditions and it seems to revolve around writing to the sd card and having a power source running on the controller. I have not troubleshooted as to whether its any device powered by the controller from the usb port or not at this point.
Hopefully this will help others and I am not sure if this can be resolved with a firmware update or not. But I believe it can be avoided.November 7, 2017 at 1:24 pm #48224
Just when I though I was in the clear all OS3 units are resetting. My 2.3 and below units are not. The two in my office with nothing connecting are resetting and the one in the field.
Ray and Samer, there is definitely an issue here that needs to be addressed. Please post here. Ray you have my cell number please contact me. Hopefully a firmware can fix the problem, but it needs to be addressed.
EdNovember 7, 2017 at 8:03 pm #48230
Hi, I just wanted to say I have read your thread and wish I could offer some advice. What I will do though is let Ray know, if he doesn’t already. I’m sure he will reply soon enough but just wanted to say something so you don’t think this is falling on deaf ears!
Thanks for all the detail!
Sent from my iPhone using TapatalkNovember 10, 2017 at 4:41 pm #48244
Thanks for responding. I have yet to hear from Ray. I sent him and email the other day as well. Looks like he is not interested. It may just be best to RMA the 15 OS3 and 30 expansions kits and go with the 2.3’s. I was hoping we could find a fix for the 3’s. Have you heard back from Ray at all?
EdNovember 30, 2017 at 10:37 pm #48409
Just a quick update (since I haven’t checked the forum recently): we’ve communicated with Ed over support and it has been sorted out that this is due to a bug in the firmware, which trigger a buffer overflow problem when the amount of log data retrieved for display exceeds the buffer size (8KB). This doesn’t happen often because usually there isn’t that much log data, but if you have a large number of zones, and the app retrieves a whole week’s log data this can be triggered. We’ve already fixed this issue internally and will be testing it more comprehensively and release an update asap.
In the meantime, if you don’t view log (or if you use a script to view log on a day by day basis), the bug shouldn’t trigger.December 6, 2017 at 12:19 pm #48479
I wanted to update the thread. Ray did reach out to me and I made my program and controllers available to him for diagnostics. I am now running a test fw fix which appears to have corrected the reset issues. This firmware has been running now for 3 days, so when I hit the 1 to 2 weeks mark then I will mark this a success. Ray and Samer thanks for that. Also thanks for adding the up time variable. I know your thoughts was to put this in the about box, but maybe it can be put just under the weather info on the main page so its something in plain site for immediate diagnostics. Hopefully Samer can get to this sooner than later as it would have certainly helped in diagnosing this problems and may give an early indicator for other problems in the future.February 17, 2018 at 5:17 pm #48937
Sorry but I seem to have totally lost track of where I posted this information. We discovered there was a bug in the log retrieving code (it’s a buffer overflow bug) that causes the controller to reboot if the log data to be retrieved is larger than some certain amount (4K if I recall corrected). We fixed it in firmware 2.1.7(2):
However, it seems we currently don’t published the compiled OS 3.0 firmware in the Compiled firmware Github repository:
which is alarming to me as I thought we have don so. Well, I must be going out of mind with the things I am juggling with… Anyways, I am posting OpenSprinkler 3.0 firmware 2.1.7(2) here (with some minimum instructions) and will add that to the Github page later today. Sorry about that!
To update firmware on OS 3.0, download the firmware here, unzip it to a .bin file, then open a browser and type in http://x.x.x.x/update, where x.x.x.x is your OpenSprinkler’s IP address. You should then see the update interface. Select the .bin file you just unzipped (don’t select the zip file!), then type in your device’s password, and click Update.
In the rare case if the update fails, you can unplug OpenSprinkler’s power, replug it, and then try again. There is always a way to update firmware through USB port, but generally over the air update should work fine.
Attachments:March 16, 2018 at 11:34 pm #49366
I tried doing the update described above and the controller rebooted and now is in a loop “Resetting” “Rebooting please wait” so I guess it can no longer load the firmware.
Have plugged into the usb port which creates a comm port on the computer. Can you please point me to the url with instructions how to load the firmware now that the controller is in this state.
ThanksMarch 17, 2018 at 12:10 am #49367
I have tried running OpenSprinkler Updater Version 1.0.4 but it is unable to detect the controller.
I run the updater as “administrator” which helped but it still cannot see the device, windows has assigned com 6 to the USB device.March 17, 2018 at 6:49 pm #49371
I left the controller powered down for a few hours and when power was re applied it began behaving normally.
So all is good now.
ThanksMay 16, 2018 at 3:02 pm #49976
@cwjanes: OS 3.0 does not use the same firmware updater as previous versions (2.x). Over the air update as described above is the best way. The resetting issue you encountered earlier, I suspect is due to flash memory not properly re-initialized (the firmware detects data in the flash memory and decides whether to re-initialize the flash or not, I guess maybe some condition triggered it to decide not to re-initialize, which caused the resetting issue).May 18, 2018 at 8:26 am #50074
I have updated the firmware over the air as described above with the attached bin file. Update was successful, but logging in to the controller results only a black screen both on web and in application too.
any idea what went wrong?
thxMay 19, 2018 at 12:41 pm #50092
Does the LCD display anything? Try to open a browser window in private browsing mode and see if that makes any difference. It’s possible that the browser cached some files which may be outdated. If the problem persists, you can submit a support ticket.May 21, 2018 at 12:53 pm #50123
Reset solved the issue. Thanks for the reply.May 23, 2018 at 5:59 pm #50156
I had the same issue after the update of the firmware… a reboot loop. The OS had been shutdown for hours to see if I can get the system back as other users, but after plugging it back in, I am stuck in the same resetting/reboot loop. Any thing I can try to get my controller back?
ThanksMay 23, 2018 at 7:36 pm #50159
Have you tried factory resetting the unit like szaky did? This usually fixes the issue. But of course you need to re-setup the unit in adhoc mode. (Connecting directly to the OS3 unit via wifi and setting up the wifi again.)May 23, 2018 at 8:19 pm #50160
Thanks for the reply, I did try the factory reset by holding down the B1 button when applying power the unit… but it automatically going into the loop without asking for the factory reset.
MarcMay 23, 2018 at 9:08 pm #50165
How are you powering it up? VIA the usb or with the connector? Try to power it up both ways and see what happens.May 23, 2018 at 9:36 pm #50172
I just tried both power sources and I am getting the same result. I get the openprinkler wifi splash page, then init file system, then “reseting please wait…”, then rebooting.May 23, 2018 at 9:50 pm #50174
I do have two of the controllers, and the second controller that I have not attempted to update, the reset procedure is working as expected.May 26, 2018 at 12:59 am #50222
We are about to release firmware 2.1.8 (the firmware file is ready, still finishing up documents etc). You can download the firmware here:
2.1.8 should trigger a full flash memory reset which should eliminate the reboot cycle problem. @marc2: if your controller went into reboot cycle, you will have to upload firmware through microUSB port. I see that you have submitted a support ticket and will continue the conversation there. In order to upload from USB port, I need to know your operating system (Windows, Mac, Linux?) so that we can send the appropriate firmware upload tool.
- You must be logged in to reply to this topic.