March 4, 2015 at 4:48 am #35806
What does the new unified firmware mean for OSPi?
Am I missing something? It looks like it is a replacement for OSPi to be more like the other versions (but missing features like plug-ins).March 4, 2015 at 8:32 am #35809
The announcement has explained it:
“The purpose of this is to make a fully consistent firmware for OS, OSPi and OSBo. The program is written in C++, so it’s not as modification-friendly compared to Dan’s Python-based interval_program. Also, there is no plugin architecture currently. However, as I said, the primary goal of this is to make OSPi and OSBo’s firmware maximally compatible with OS, so that any new features introduced in OS will also be simultaneously available to OSPi and OSBo.”March 4, 2015 at 6:37 pm #35818
Dan in CAParticipant
The Python program is actually an independent project started back when things were more DIY oriented.
To avoid confusion I have been considering changing the name. Any suggestions for a new name would be welcome.
DanMarch 19, 2015 at 1:52 am #36107
Hey Dan, I appreciate all the effort you have put into this… What’s the chance of some kind of happy reunion of technologies, so we can use the unified platform for our day-to-day use, but also a python-based framework for adding functionality for smarter additions?March 22, 2015 at 1:41 pm #36188
Dan in CAParticipant
A very interesting suggestion!
Python is used as a scripting language with many types of programs.
In fact, before Ray introduced the first OSPi board, I had written some Python code to control the Arduino based OpenSprinkler from a Raspi. There is still a post on my (currently neglected) blog about it:
I will give this some thought and try some experiments to see what can be done. Probably many/most of the current plugins would need to be re-written. It would be nice to let Ray take care of the core functionality and I could spend more time working on plugins to add new capabilities. My original goal was to have a system that can be easily modified.
As we enter a fourth year of extreme drought here in California the State Water Resources board is starting to implement some strict water use restrictions. It is an interesting time to be tinkering with irrigation software.
DanApril 20, 2015 at 4:47 pm #36954
So, do I get it right when I interpret this as follows?
For the OSPi there is currently a choice of running the unified soft/firmware and/or the interval_program.
Will the Android app work with both?
/Jonas…April 20, 2015 at 5:11 pm #36955
The Android app currently supports both and yes you are correct you have a choice between the Python firmware (Dan’s OSPi) or the C++ firmware (Ray’s Unified).August 8, 2015 at 9:15 pm #39761
Are there some changes to OS that are currently not available on an OSPi still running the inervals peogramme 2.2.43 ?August 9, 2015 at 1:07 am #39770
The two are completely different at this point.
The Python program was based on firmware 1.8.3 and has not adopted many of the new features especially with 2.1.0+ (such as the per station watering times).
The Python program just got renamed to SIP by Dan and has taken a different direction from the Unified firmware. The focus around the Python version are plugins and easy user customization and additions.August 9, 2015 at 8:12 am #39781
Thank you for the useful informstion.August 12, 2015 at 3:48 pm #39846
Will the python version adopt any of the newer features like the per station watering times?August 12, 2015 at 4:36 pm #39847
That project is run by Dan Kimberling who contributes everything in his free time. I believe he has a rewrite planned but I am not sure of the planned feature changes.
- You must be logged in to reply to this topic.