June 7, 2015 at 6:40 pm #38248
We’ve just released OpenSprinkler Unified Firmware 2.1.5. This firmware includes the fix to a major DHCP bug (see below), and added a couple of new features.
– Fixed a major DHCP bug that causes repeated DHCP requests when leaseTime is infinity (e.g. with DHCP reservation). Note that this is only relevant to OS; it does not affect OSPi or OSBo.
– Fixed a bug that causes the controller to get stuck in ‘Connecting…’ when the last successful weather call expires.
– Fixed a bug that causes master station to not run when rain sensing or rain delay is in effect.
– Added support for changing weather parameters for the Zimmerman method (requires microSD card and App version 1.4.4)
– Added support for DC powered OpenSprinkler (with built-in boost converter)
– Added support for I2C LCD (to be used with future OpenSprinkler hardware)
– Added firmware minor version number
– Added support to display hardware version and type on start-up (OS only)
Upgrade OS 2.0/2.1/2.2/2.3 to Firmware 2.1.5:
Please follow the OS Firmware Upgrade Instructions.
Upgrade OSPi/OSBo to Firmware 2.1.5:
Please follow the OSPi/OSBo Firmware Upgrade Instructions.
1. We discovered a DHCP-related bug (in the EtherCard library for Arduino) earlier today. This bug causes the device to send repeated DHCP requests if the DHCP lease time issued by the router is infinity (-1), which is often the case when you have set up DHCP reservation for OpenSprinkler. This actually explains several strange issues we’ve seen previously, related to DHCP and network connectivity. So it’s highly recommended you upgrade to this new firmware as soon as possible. Note that this bug only affects OpenSprinkler, not OSPi or OSBo.
2. This firmware supports editing the parameter weights used in Zimmerman weather algorithm. Specifically, the app sends the parameters to the controller and the controller stores them to the microSD card. When making weather query, the controller passes the parameters to the cloud server, thus the parameters will affect the returned water level. Currently three parameters are editable: temperature, humidity, precipitation. The weight associated with each parameter ranges from 0 to 100%. 0 means that parameter does not participate in the calculation at all; 100% means full weight. For example, if all three weights are 0, that means none will influence the water level, therefore the water level is always 100%. If all three weights are 100%, it’s equivalent to the original Zimmerman algorithm. You can adjust the weight accordingly to change the influence of the three factors.
To use this feature on OS, you will need to have a microSD card installed (all OS 2.3 units come with built-in microSD card). For OSPi/OSBo, it’s automatically supported with no extra requirement.
3. Support for I2C LCD and DC powered OpenSprinkler are also added in this firmware. These are in preparation for the upcoming hardware. In particular, DC powered OpenSprinkler will use 9VDC and is meant for both 24VAC sprinkler solenoids as well as DC solenoids. It’s mainly for International markets where 24VAC power supply is difficult to source. I will make a separate announcement when it’s ready to be released.June 8, 2015 at 2:52 am #38258
Tnx for the update of the Zimmerman parameters.
My first impression seems very promising.
I just noticed that after the update my config was lost, I had to import the backup again.
After the update I needed to configure the Zimmerman parameters before the program became visible.
This was not an issue for me, and I don’t know if it was an issue related to my setup or if it was by design.
Tnx for the good work.June 8, 2015 at 10:40 am #38259
In regard to the config being lost after upgrade, this is something that is expected. When the firmware updates a major version, it deletes the EEPROM and this is done since the layout is no longer compatible with the new one and resources needed to convert between all various firmware jumps could get quite complex.
Instead, we allow the app to export and import the config, as you did.
What do you mean you had to configure the parameters before the program became visible?
Thanks for the feedback!June 8, 2015 at 12:34 pm #38261
After the upgrade I logged on and imported the config from version 2.1.4.
Everything seemed OK, except that I did not see my 2 programs.
After I configured the “Adjustment Method Options” the 2 programs became visible.June 8, 2015 at 3:16 pm #38263
Ah okay now I understand.
The app immediately asks for the programs after adding them from the backup and sometimes the controller needs a second to save everything and report it. The app however won’t check again for another 30 seconds so it’s likely your other activity allowed time for it to re-poll.
I’ll find a better way to update the programs after an import, possibly adding a small delay.
Thanks!June 9, 2015 at 4:44 am #38268
Added support for changing weather parameters for the Zimmerman method
Excellent! thank you! shall upgrade over the weekend.June 10, 2015 at 5:10 am #38296
A question about the Weather Diagnostics.
I use the following weather station: http://www.wunderground.com/personal-weather-station/dashboard?ID=IVLAAMSG160#history
The site is reporting the following data
jun 10, 2015
Temp: 19.1 °C
Temp: 8.7 °C
Temp: 13.9 °C
My OS reports:
Min Humidity: 45%
Max Humidity: 87%
Mean Temp: 12.5 °C
Why is the OS showing different data than I find on Wunderground?
Is it also possible to be able to configure not to use the average temp, but the max temperature (or the average daytime temp) because in Belgium we have cold nights, so the average is Always low.
Since the 2.1.5 version I am able to lower the temp impact, so this is already very nice.June 11, 2015 at 8:19 pm #38339
While I’ve been very pleased so far with my ospi opensprinkler I am now quite angry. The firmware upgrade instructions worked perfectly. Why didn’t you tell us that our current config would be wiped and that it should be saved? I did see the “export configuration” option but didn’t really know why I would want to do that.
Now I have to re-enter my entire config and we’re supposed to be heading out of town for a couple of weeks so I’ll have put in some late hours getting this all set up again.
Aargh!June 11, 2015 at 8:31 pm #38340
Linux binary requires some Debug files;
./osFWUpdater_x64: symbol lookup error: ./osFWUpdater_x64: undefined symbol: _ZN6QDebugD1Ev
I already installed the libqt5serialport5, but not sure what’s next, I’m searching Google for the meantime
EDIT: Recompiled, and loaded perfectlyJune 11, 2015 at 8:49 pm #38342
I’ve suggested before to save the config file as part of the update process. Open Updater, Save config, Download latest, Update, Restore config all in one process. Seems like a simple solution.June 12, 2015 at 10:28 am #38357
+1 on the update process saving and restoring the configuration.June 12, 2015 at 2:57 pm #38379
Any idea about the difference I see between what my OS is reporting and the data on Wunderground?
(See my post from June 10, 2015 at 5:10 am)June 21, 2015 at 10:58 am #38582
No success here on MATE Mint
I get the same error as cuteboi
./osFWUpdater_x64: symbol lookup error: ./osFWUpdater_x64: undefined symbol: _ZN6QDebugD1Ev
I cannot recompile
I get the prompt after qmake but this what I get after “make”
g++ -c -m64 -pipe -O2 -Wall -W -D_REENTRANT -DQT_NO_DEBUG -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o mainwindow.o mainwindow.cpp
In file included from /usr/include/qt4/QtGui/QComboBox:1:0,
/usr/include/qt4/QtGui/qcombobox.h: In member function ‘void MainWindow::on_btnDetect_clicked()’:
/usr/include/qt4/QtGui/qcombobox.h:233:10: error: ‘void QComboBox::currentIndexChanged(int)’ is protected
void currentIndexChanged(int index);
mainwindow.cpp:51:66: error: within this context
make: *** [mainwindow.o] Errore 1
No matter if I run both commands as sudoJune 21, 2015 at 11:35 am #38583
If you are in Linux then you can update manually using avrdude (no GUI just CLI). I’m on my mobile now but if you provide your OpenSprinkler hardware version I can reply in a few minutes with the specific command needed to update.June 21, 2015 at 1:08 pm #38584
The one with one orange socket. 2.1 right?June 21, 2015 at 3:18 pm #38586
Customize Zimmerman method params is nice option, but why is it not possible to set more then 100%, for example wanna set the rain to have higher impact for calculation. ThanksJune 22, 2015 at 3:12 am #38599
Is this the right command ?
https://opensprinkler.com/forums/topic/firmware-update-problems-hardware-version-2-1/#post-36533June 22, 2015 at 6:07 am #38602
Is there any way of subscribing via email, RSS feed or whatever other mechanism to firmware updates announcements only ?
2.1.5 has the very important modifiers for the zimmerman algo but I stumbled on it’s announcement just by chance visiting the forum (and missed 2.1.4 entirely).
Thank you very much.June 22, 2015 at 8:23 am #38605
The application will actually notify you when an update is available. You should see the notification on the top right corner of screen. The notification will also show you the changelog.
Hope this helps!June 22, 2015 at 3:03 pm #38614
Thank you so much Samer ! I really feel dumb for not noticing ! 🙂 Take care.June 22, 2015 at 7:52 pm #38624
No problem at all and just so you know, when you dismiss the popup it will never show it again for that version number. However, if a newer update comes out, the popup will re-appear.
Thanks!June 23, 2015 at 9:11 pm #38657
@radas: the reason the weights are capped at 100% is that almost everyone who needed the adjustment felt the original weights are too aggressive, therefore we provided options to reduce the weight of each factor. Technically there is no difficulty at all to allow the weight beyond 100%, but we haven’t heard any request before yours.June 26, 2015 at 12:26 pm #38742
Just for the records.
On updating the firmware, also the logs are canceled, not only the programs.June 26, 2015 at 3:53 pm #38747
The logs are not shown after upgrading from firmware prior to 2.1.0. This is because the way logs are stored changed in 2.1.0. Any update after that will not cause loss of log data.
Update: Also, the log data from before is still present on the SD but has been moved to a LOGS sub directory.
- You must be logged in to reply to this topic.