OpenSprinkler (not OSPi!) Firmware 2.0.6 Released

[Ray]

Hi All,

[Update: this firmware has now been replaced by firmware 2.0.7. If you are still using 2.0.6, it’s highly recommended that you upgrade to 2.0.7, which has better microSD card support (e.g. no restriction to 2GB, FAT16). Firmware 2.0.7 has also added watchdog timer, which can help solve the lock-up issue some users encountered. Please check the announcement here: viewtopic.php?f=2&t=758]

OpenSprinkler firmware 2.0.6 has been checked into Github. This firmware supports logging (requires a microSD card of 2GB or less, formatted to FAT16). The logging is supported by the OpenSprinkler mobile app (courtesy of Samer to add the logging support). This firmware also included minor improvements to the ‘auto-reconnect’ feature to avoid the controller frozen when it can’t establish network connection.

Some technical details:
– A log record is generated when a sprinkler station closes. The record includes program index, station index, station run time, and the time stamp (epoch time) when the station closes.
– All records of the same day are written into a file named xxxxx.txt where xxxxx is the epoch time in days (in other words, epoch time divided by 86400). For example, all records generated on June 13, 2014 are written into a file named 16234.txt.
– You can directly check the file content by http://x.x.x.x/16234.txt, where x.x.x.x is your controller’s ip address. But usually you don’t need to check the file content manually — when using the app, its logging feature will automatically retrieve the log files, aggregate the data and visualize them.
– The ‘auto-reconnect’ feature has two changes: 1) a ‘Reconnecting’ message is displayed on the LCD when network is lost and the controller tries to re-establish ip. Therefore, if the controller is frozen, from the LCD you can see whether it’s getting stuck reconnecting; 2) the timeout for reconnecting is reduced to 30 seconds.

How to Upgrade to Firmware 2.0.6 (Updated):
Please use the OpenSprinkler Firmware Updater tool to upgrade to 2.0.6. Instructions: http://rayshobby.net/?page_id=732#upload

Keep in mind that to enable the logging feature you need to insert a microSD card (2GB or less, formatted to FAT16). For example, this one: http://www.amazon.com/SanDisk-MicroSD-TransFlash-Adapter-camcorder/dp/B000VOU91U.

Please post your comments / feedback / bug report here. Thanks!

[rogerlcobb]

Again, I have followed the steps, successfully replaced the files and folders and I still cannot connect to upgrade my 2.1v from 2.0.4 to 2.0.6.

Anyone else having issues connecting to and flashing their system to the latest firmware?

Thanks!

[Terrman]

2Gb microSD cards are hard to come by these days – will a 4Gb with a 2Gb volume work?

[Ray]

Again, I have followed the steps, successfully replaced the files and folders and I still cannot connect to upgrade my 2.1v from 2.0.4 to 2.0.6.

Can you be more specific what problems you’ve encountered? Such as cannot run the updater program, or cannot find the device, or error during upgrade?

[Ray]

2Gb microSD cards are hard to come by these days

.
Unfortunately because of the tinyFAT library that the firmware uses, it cannot work with cards above 2GB in size. Note that in the post above I included a link to example 2GB card. These are still widely available on Amazon.

[mb42]

I have been able to download the new firmware and GUI, enter bootloader mode and my Windows 7 PC recognizes the USB device in Device Manager – after installing the driver. My question is this; how do I then launch the GUI and proceed from there? I see no straightforward way to launch the GUI and I am stumped. I have expanded the zip, but see no obvious exe to launch the GUI.

All of the instructions for a firmware update seem to end at downloading the firmware updating tool. No real instructions beyond that seem to exist – or I am simply not looking in the right spot.

Help from experienced firmware updaters would be appreciated.

[iDoug]

What am I missing?

1. Downloaded the uploader and the new firmware.
2. Overwrote the firmware folder with the firmware folder that has 2.0.6.
3. Unplugged all connections to the OpenSprinkler.
4. While plugging in a USB cable, I held down the B2 button. OpenSprinkler does not appear to be on as the display does not light up. The display does light up when not pressing the B2 button.
5. Double clicked on osFirmwareUpdater.app. GUI is displayed with Hardware: OpenSprinkler_v2.1 and Firmware: 2.0.6.
6. Click the UPLOAD button. Bottom text field displays this message: “avrdude: no programmer has been specified on the command line or the config file Specify a programmer using the -c option and try again”

REF:
Mac OSX 10.9.3
OpenSprinkler v2.1u with firmware 2.0.5 (purchased 5/27/2014)

[Ray]

I have expanded the zip, but see no obvious exe to launch the GUI.

In the unzipped folder, do you see a subfolder named application.windows or something like that? Go to that folder and you should find an executable program there.

[Ray]

“avrdude: no programmer has been specified on the command line or the config file Specify a programmer using the -c option and try again”

Can’t think of any reason why you should see this error. I am traveling today but I will get back tomorrow to check it on my Mac.

[mb42]

@ray wrote:

I have expanded the zip, but see no obvious exe to launch the GUI.

In the unzipped folder, do you see a subfolder named application.windows or something like that? Go to that folder and you should find an executable program there.

In the “application.windows64” folder I see the following:
lib
source
osFirmwareUpdater.bat

When I attempt to run the batch file, I get an error: “‘java’ is not recognized as an internal or external command”

Anyway, I just downloaded the 32-bit version of the firmware updater as well. Looks like it contains an exe file. I will give that a try tonight. A detailed set of instructions for updating firmware (step-by-step) would be fantastic! I don’t want to turn my device into a brick.

[rhldr]

If it’s any consolation, I was never able to get the 64bit version to work either. Just like you, I downloaded the 32bit version and use it now.

[Ray]

OK, I will check the 64-bit version. The programs are written in Processing and exported using Processing as well. I am pretty sure we checked all platforms and made sure the updater program works on all. But you are right that the 32-bit version can work just fine on 64-bit Windows.

the ‘java not recognized as … command’ message means you need to install Java. You can go to java.com to download tne install Java. But before you do that, try the 32-bit version to see if that works.

[iDoug]

Any news on this message: “avrdude: no programmer has been specified on the command line or the config file Specify a programmer using the -c option and try again”?

[mb42]

@ray wrote:

OK, I will check the 64-bit version. The programs are written in Processing and exported using Processing as well. I am pretty sure we checked all platforms and made sure the updater program works on all. But you are right that the 32-bit version can work just fine on 64-bit Windows.

I did use the 32-bit version last night and it worked fine. There seems to be files missing from the 64-bit zip file.

[Ray]

Any news on this message: “avrdude: no programmer has been specified on the command line or the config file Specify a programmer using the -c option and try again”?

Just tried it on my Macbook Air OSX 10.9.3 and everything went ok. I am curious: are you seeing other messages in the output other than the one you typed above? Or is that the only message you see?

[iDoug]

Yes, that is the only message I see.

Upon starting the application, the Console shows this message:
6/26/14 9:42:39.255 AM JavaApplicationStub[1679]: Unrecognized Java VM option ignored:
There are no other messages displayed in the Console. Either after pressing the Upload button or upon quitting the application.

I have the application located here:
/Applications/Utilities Extras/OpenSprinklerUpdater/application.macosx/osFirmwareUpdater.app

Also, have the Arduino application version 1.5.5 and Java for OS X 2013-005.

[Ray]

@iDoug: found the bug (for some reason the program worked fine on my Macbook Air but not on an older Macbook). Anyways, it’s fixed and the firmware updater has been streamlined, mainly consolidating all versions and pulling the executables out to make them more obvious. Please download the new package from here:
http://rayshobby.net/?page_id=732#upload
Let me know if this works. Thanks.

[iDoug]

Hi Ray,

I think you are getting closer. I ran the application if attempted to load the firmware and when I check the web page it does say 2.0.6. All of my settings have been erased.

However, there appears to be several error messages. I would love to provide them. But, that is not possible with the existing update application. The scroll does not flow smooth enough to read all the messages, let alone, be able to hand type each character (I tried). There is no ability to copy the text in that field. I cannot find where these messages might have been written to a log file.

PLEASE, PLEASE, PLEASE, help me to help you. Provide some means that I can share the error messages. Also, as important: Provide a means to backup and restore of the settings.

Now, I am unsure if this will work.

[Ray]

@iDoug: if the webpage says firmware 2.0.6, it means you’ve upgraded it successfully. Regarding the error message, did you check the instructions, which explicitly mention that you can ignore those warning messages?
http://rayshobby.net/?page_id=732#upload

[iDoug]

I saw those messages and a bunch of other errors and warnings. They do not give me a comfortable feeling. Especially, if I cannot read them all. How do I know they were not something I need to deal with? I really need to be able to read them and possibly learn from them.

[Ray]

Sigh, I have a feeling that letting users see the output messages complicates things… They are just the output from running the avrdude command. If you want to take a close-up look at the messages, you can bypass the GUI and run avrdude in command line directly. For exmaple:
avrdude -c usbasp -p m644p -U flash:w:firmware2.0.6.hex
is what it’s really running.

[Ray]

A new firmware 2.0.7 is released. Plesae check the details here: viewtopic.php?f=2&t=758. Thanks.

[Author]

Posts