envirooreo.blogg.se - Opensprinkler version 2.3 download

#OPENSPRINKLER VERSION 2.3 DOWNLOAD HOW TO#
#OPENSPRINKLER VERSION 2.3 DOWNLOAD CODE#
#OPENSPRINKLER VERSION 2.3 DOWNLOAD PASSWORD#

For example, for cloud-support, we’ve come to the conclusion that it will require an upgraded microcontroller due to the resource limitations of the current hardware. Some of these are purely software, but some will entail hardware changes.

Adding firmware support for using sensors (either digital or analog) to trigger sprinkler events.

Improve the scheduling algorithm to better handle overlapping schedules using a queue.

Support for soil moisture sensor and flow sense (at least flow estimation).

Getting OpenSprinkler certified by the EPA WaterSense program (which requires ET-based water time calculation).

There are quite a few things on our todo list.

#OPENSPRINKLER VERSION 2.3 DOWNLOAD HOW TO#

For the security-minded, I admit that this is far from sufficient, but better than before.įor OSPi/OSBo, all features currently implemented on the OS, such as individual station water time, Zimmerman’s weather-based water adjustment, and support for radio frequency stations, are also immediately available for OSPi/OSBo.ĭetails on this firmware and how to upgrade OS/OSPi/OSBo to use this firmware can be found in this forum post.

#OPENSPRINKLER VERSION 2.3 DOWNLOAD PASSWORD#

Another change is the support for MD5 hashed password, which attempts to address the previous plain-text password to some extent. The program preview will also take into account the sunrise/sunset time of a specific day. Specifically, the program’s first start time (and any of the additional start times) can be defined using sunrise/sunset time +/- an offset (in steps of minutes) up to 4 hours. The main added new feature of this firmware is the support of using sunrise/sunset times in program settings. However, as I said, the point is to make the three platforms maximally compatible, so that any new features introduced in OS will be simultaneously available to OSPi and OSBo. Folks may find C++ based programs less friendly to modify than Dan’s Python-based interval_program.

#OPENSPRINKLER VERSION 2.3 DOWNLOAD CODE#

Other than these, the code is largely shared between them, making it easy to extend in the future.

Also, OSPi/OSBo uses the standard socket to handle Ethernet communication, while OS uses an Arduino EtherCard library. The major differences are that on OS, all non-volatile memory data (such as options, program settings) are stored in EEPROM, while for OSPi/OSBO, these are stored in a local file, which simulates EEPROM.

It’s done this way to share the code between OS, OSPi and OSBo as much as possible. Technically, the unified firmware is written in C++. The purpose is to make a fully consistent firmware for OS, OSPi and OSBo, so that the same firmware and same features are available on all of them. The cross-platform idea was inspired by Rich Zimmerman’s sprinklers_pi program. The biggest benefit of this firmware is that it’s cross-platform - it can compile and run on all OpenSprinkler hardware platforms, including the standard OpenSprinkler (OS), OpenSprinkler Pi (OSPi), and OpenSprinkler Beagle (OSBo). Next, we just released the first version of the Unified OpenSprinkler Firmware, numbered 2.1.3. I only wish that Cyrus Farivar, the author, had talked about the microcontorller-based OpenSprinkler as well, because appearance-wise it looks more elegant. That caused a huge spike of orders, but we managed. First of all, OpenSprinkler Pi got blogged by Ars Technica, which is super cool. This post is to give you some recent updates on OpenSprinkler and upcoming plans. Hey, it’s March already, that means spring will be here soon! Amid an unusually cold winter and freezing weather this winter in New England, we’re finally starting to see some warm winter days.