Tagged: firmware 2.1.9
March 26, 2020 at 1:19 pm #64826
problem solved !
the card was bad. Yesterday I have formated the original card and it looks good in laptop.
I have no other card at home, but this time I have an idea that I have an other device at home.
It has some other plroblems, and there is an a card in it. So I changed the cards, and it works!!
Thank you very much for your help and your time.
Last question. Can I sand you back the other device? Last year we had some letter cahnging about it.
When that device went wrong I bought an other one because it was summer, I have to use that.
First time that device does not handle the extender board.
This time I cannot switch it on.
best regards feriMarch 27, 2020 at 10:35 am #64833
Sure, please reply to whichever last email you are referring to so that we can continue from there and arrange for a support request.March 28, 2020 at 3:18 pm #64859
I had this same problem. Turning on debug gave a lot of errors along the build process. My installation is several years old, so I decided to swap in a new sdcard with the latest raspbian image and everything worked fine after that.
tl;dr Try upgrading raspbian.April 11, 2020 at 5:01 pm #65102
I would like to upgrade my device to the new firmware with GUI based updater but it stuck on the downloading firmware option..
In the begin I can’t see version numbers it will be seen on the picture I have taken..
I would like to use this updater because it is simple and I like it….
I used the run as admin mode tried the compatibility mode but these were unsuccessful things..
Thanks for help!April 11, 2020 at 5:06 pm #65113
If you want to use the GUI based updater, do NOT click on Download Firmware — the updater program hasn’t been changed for a long time and the original download link is no longer available. Instead, the firmware files are together with the GUI program. So all you need to do is to Upload. Again, do NOT click ‘Download Firmware’.
Please also note that the GUI program only has firmware up to 2.1.7. If you want to update to 2.1.9 you should follow the instructions and use the avrdude program to update.
The GUI program is just a wrapper for the avrdude command. But as operating system updates often render previously compiled programs obsolete, we don’t have enough resources to keep updating the GUI program and make sure it works with the current operating systems. So we stopped maintaining the GUI and instead recommend you to use avrdude, which does not have operating system compatibility issues.April 14, 2020 at 8:18 pm #65176
Recently I’ve got my OS active which is really a good thing. But one open point is the soil moisture metering. Already before reading here I found the description refered to in .
Which is from my point of view not a bad one. Also vegetronix sounds reasonable.
With the first option I would miss the possibility of data logging. I mean it would be interesting to have a chart with the reported values.
With vegetronics I’m not sure if the sensor is made ready for permanant use (keep in the ground) and I still don’t have a data logger.
Another option would be to combine it with https://sensebox.kaufen/product/sensebox-mini
But this board is a bit an overload to just have the data of the soil sensor.
BTW: the logged values would be transmitted to openHAB
So I struggle a bit to decide what project to focus on. What would you guys suggest?
StefanApril 14, 2020 at 8:28 pm #65179
Some of the design challenges of a soil sensor include how to power it over long time, and how to transmit the data out. For good and reliable sensing, it’s often necessary to bury the sensor underground, but that makes it harder to power over a long time and have a reliable wireless transmission method. Many years ago I took a look at some of the available options:
but none of them seems a great option. I am not sure what’s the state of the art. I see Vegetronix mentioned quite often — the VH400 sensor is a wired sensor, to go wireless you need a WiFi hub, powered by 9V battery. I don’t know if this is a long-term solution or not — it seems cumbersome to have to replace the battery once every few months. So honestly I don’t know which way to proceed.May 4, 2020 at 7:40 am #65645
I have tried to install Firmware 2.1.9 on my Open Sprinkler 2.3 DC hardware but it is not successful.
The installation procedure seems to work without any errors but no firmwware change occurs. I am not sure what the problem is.
Here is a screenshot of the procedure in terminal.
And also, a screenshot of my
Attachments:May 4, 2020 at 7:41 am #65666
Please note that in the command you ran, ‘_U’ is a typo, it should be ‘-U’ — i.e. a dash, not a underline.
Also, what follows that is NOT ‘flash:wos_219.hex’, it should be ‘flash:w:os_219.hex’. It’s better that you copy-paste the command from the instructions:
which will reduce the chance of error in typing the command.
May 5, 2020 at 3:23 pm #65731
- This reply was modified 3 months ago by Ray.
Thanks, successfully installed!May 13, 2020 at 11:55 pm #65941
I saw in the donwload section what looks like a firmware 2.1.9 v3:
os_219_3.hex 2020-04-06 00:00 218K
Is that it? what are the difference with v2/v1 ?May 14, 2020 at 12:03 am #65972
Minor revisions (like 2.1.9 (0) or (1) or (2) or (3)) are usually bug fixes. Details can be found at github commit history:
For example, minor revision (3) has the following changes: fix bug with program moveup api; increased ether buffer size for OS 2.3 and 3.0; improve NTP; fix bug in server_change_station that causes buffer overflow when there are a large number of zones.
The latest firmware is the default firmware file you see at the download folder. Previous firmwares are in the archived subfolder.
- You must be logged in to reply to this topic.