- This topic is empty.
July 5, 2014 at 4:45 pm #23026
A new firmware 2.0.7 has just been released for the microcontroller-based OpenSprinkler. This version includes the following changes:
1. Improved microSD card support by switching to use the Arduino SdFat library (https://code.google.com/p/sdfatlib/). This eliminates the restriction of 2GB card. You can now use microSD card of any size, formatted to either FAT16 or FAT32. The SdFat library also supports creating sub-diectories, which is useful to keep files organized.
2. Added watchdog timer to automatically restart the controller after timeout (2 minutes by default). This will hopefully address the lock-up issue that some users encountered.
3. Added support to auto-detect the number of expansion boards. In the ‘Options’ page, the ‘# of exp boards’ now shows the number of auto-detected expansion boards.
4. Minor improvements to the web interface, including links to the user manual, changing some label text for clarity.
If you need the logging feature, it’s highly recommended that you upgrade to 2.0.7, because the previous SD card library used in 2.0.6 can cause log file corruption problems on certain SD cards.
How to Upgrade to Firmware 2.0.7:
Please use the OpenSprinkler Firmware Updater tool, available at: http://rayshobby.net/?page_id=732#upload
Thanks!July 8, 2014 at 5:03 am #27446
I’m not able to update my brand new OpenSprinkler v2.1s. When I plug it into my Windows 7 machine, it shows up as “Unknown Device”, not USBasp, and Windows does not find a compatible driver. (I downloaded the USBasp driver, and pointed Windows at the directory, and no dice.)
When I plug it into my linux machine and run lsusb, the device doesn’t show up at all.
Is there anything else to try?
Thanks.July 8, 2014 at 5:57 am #27447
Your problem sounds very like the problem I had, see “Windows Driver Operation/Openspri kler Recognition Problems”.
Briefly, if you hold pushbutton B2 any longer than 2 seconds after plugging in USB cable it Seems to prevent/corrupt the id string sent from the Opensprinkler as it tries to identify itself to Windows.July 8, 2014 at 9:17 pm #27448
I, too, glossed over that part of the instructions. I’ll give it a try when I get home.July 9, 2014 at 6:14 am #27449
I finally got upgraded to 2.0.6 a few weeks ago and now I see 2.0.7 is available. . .I am using the logging with a 2gb card, but it seems I should upgrade. . .but I can’t seem to this time. . .
avrdude: error: could not find USB device “USBasp” with vid=0x16c0 pid=0x5dcavrdude done. Thank you
I have reset the device lots of time trying to release immediately and various other times. On OSX. . .just redownloaded whole gui upload tool. . .same error.
Do I have to disconnect expansion module and common during update process?July 9, 2014 at 5:47 pm #27450
Ok, I finally got it work, I think. The advice about not holding the button for more than 2 seconds was spot on. I think the instruction could probably be written a bit better for those of us that skim over instructions. 🙂
Upon installing the drive, I got the message that “Windows can’t verify the publisher of this driver software”, and I clicked “install anyway”. This part seems pretty normal, as I’ve seen this before. But after that, I get the message that it can’t verify the digital signature. What? I thought I just took care of that! I’ve never this happen before. So ended up following the Windows 8 instructions for disabling signature checking, even though I’m running Windows 7.
I ran the updater, and it produced some errors. Unfortunately, the updater won’t let me copy the output to the clipboard, so I guess I won’t post it here. But the device says it’s running 2.0.7, now, so I guess it worked.
All in all, I have to say this was a rather painful process. Is it possible to implement a network firmware update mechanism? Perhaps save the firmware image to the SD card over the network, and then reboot and have the boot loader update from the SD card? A no-tool/no-driver firmware update would be so much easier to use.
Also, I really didn’t like that I had to download a 158 MB zip file (that unzips to 455 MB) containing all sorts of stuff I don’t need. I would much rather download just the tool and the firmware that I need.
Anyway, OpenSprinkler otherwise seems like a great product!July 9, 2014 at 6:03 pm #27451
No success for me still. Definitely tried less than 2 seconds. Network update would be great!!
Sent from my iPhone using TapatalkJuly 10, 2014 at 2:10 pm #27452
Do I have to disconnect expansion module and common during update process?
No you don’t need to disconnect expansion board.July 10, 2014 at 2:19 pm #27453
I still can’t get it to work. Even restarted the osx laptop
Sent from my iPhone using TapatalkJuly 10, 2014 at 2:28 pm #27454
For those who haven’t been able to upgrade, here are some notes that may help (most of these are already mentioned in the instructions and the GUI)
1. Make sure to check if you have OpenSprinkler 2.1 or 2.0, they have different procedures:
– OS 2.1: the 24VAC terminal block is orange-colored, to enter bootloading mode, unplug all power, then press and hold button B2 while plugging in a USB cable, and release B2 after 2 seconds. The LCD screen must remain OFF, if the LCD lights up, you need to repeat the above step.
– OS 2.0: the 24VAC terminal block is green-colored. There is NO need to enter bootloading: just select OpenSprinkler 2.0 from the dropdown list, and click on Upload.
2. Driver (for Windows):
– OS 2.1: requires USBasp driver. Windows 7 64-bit and Windows 8 require signed drivers. To get around it, it’s probably the easiest to boot Windows into a mode that disables driver signature enforcement. For Windows 7, I think you can press F8 during system booting process, and select the correct option that disables driver signature enforcement. For Windows 8, you can follow the instructions here: http://letsmakerobots.com/node/36841
Note that because the driver is unsigned, you need to install the driver every time you re-boot. And you also have to re-install the driver even when you plug the device into a different USB port! (Cheers, Microsoft!) Frankly, when I designed OS 2.1, I never thought the driver issue would be so annoying. If I had known this, I would definitely opt to use a different bootloader.
– OS 2.0: requires USBtinyISP driver. Adafruit has released a signed driver for USBtinyISP, please use their updated driver: https://learn.adafruit.com/usbtinyisp/driversJuly 10, 2014 at 2:48 pm #27455
Thanks. Already studied those. No success on my MacBook Air. Upgraded from same machine to .6 a few weeks back. I have tried more than 2 seconds and less than 2. I have 2.1 (only a few weeks ago).
Sent from my iPhone using TapatalkJuly 10, 2014 at 2:52 pm #27456
@TechFan: could you try a different USB port and different USB cable? I assume you did make sure the screen remains OFF following the bootloading procedure.July 10, 2014 at 2:59 pm #27457
Did both already. And yes.
Sent from my iPhone using TapatalkJuly 10, 2014 at 5:41 pm #27458
Hmm, this is puzzling, especially since you have successfully updated the firmware once before. I can’t think of any obvious reason. The message you encountered means the operating system cannot detect the USBasp device. If you have access to another computer you may want to try it on another computer. Also, I am wondering if this has to do with USB 3.0 (I doubt that, because I have a fairly recent Macbook Air and I can successfully upgrade firmware using it).July 10, 2014 at 6:35 pm #27459
2011 MacBook here. Do you know how to check that the OS device is found in osx. Haven’t needed to do that. Easy in windows. I’ll try another computer tonight. Didn’t want to deal with installing a driver. Would having SD card installed affect? I tried removing it before restarted computer. Still didn’t work.
Sent from my iPhone using TapatalkJuly 11, 2014 at 5:50 am #27460
Got it to update from my old Win7 x86 laptop once I got it to install the driver correctly.
Not sure what the problem is/was on my mac.August 6, 2014 at 8:46 am #27461
Hi all, here is Ottorino from Florence, Italy.
Here on Debian Jessie Linux I was not able to update the firmware no matter how compulsively measure the two seconds, no matter if the usb cable was inserted before or later in the computer !!
I finally succeded to update the firmware to 2.0.7.
Apparently the problem was the 3.0 USB plugs (the blue ones) on my fujistu.
Performing the upgrade procedure with standard usb, I encountered no problems at all.August 11, 2014 at 3:34 pm #27462
OK. Thanks for reporting. I wasn’t aware of the incompatibility with USB3.0. Will check and see if there is a solution somewhere.
- You must be logged in to reply to this topic.