Forum Replies Created
-
Posts
-
It’s possible the import got disrupted for some reason. You can modify the .json file, leaving only the stations data, and just import that, see if it works. I attached the modified .json file here. It’s the original json with all sections other than “stations” removed.
Well, I got the same error about uploading file, so here is the file content:
{"stations":{"masop":[255,255,255],"masop2":[0,0,0],"ignore_rain":[0,0,0],"ignore_sn1":[0,0,0],"ignore_sn2":[0,0,0],"stn_dis":[2,128,255],"stn_spe":[0,0,0],"stn_grp":[0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0],"snames":["Lawn","Front Yard","Ferns","Retaining Wall","Driveway","Dry Creek Bed","S07 - Unused","S08 - Unused","Hill #1","Hill #2","Hill #3","Hill #4","Hill #5","Hill #6","Hill #7","S16","S17","S18","S19","S20","S21","S22","S23","S24"],"maxlen":32}}I believe this issue has been resolved via support ticket. For the record: any changes to expanders (such as adding an expander, changing its index) are effective after rebooting the controller. This is because the firmware detects expanders when it boots, and doesn’t defect any expander changes while it’s powered on.
The official OpenSprinkler v3 enclosure is designed and owned by SeeedStudio. I will see if it can be posted, but it’s a design meant for injection molding so the enclosure thickness may not be suitable for 3D printing, and it has many small structures which are definitely too small and thin for 3D printing.
@km9830, please be more specific. How are you accessing the controller, what error messages are you getting. Are you able to go to:
https://demo.opensprinkler.com/
and see the interface there? There are several different scenarios discussed above, just saying ‘getting the same issue’ doesn’t give us enough details to help you diagnose.Error 0x2D is due to SD card issues. It has nothing to do with wired Ethernet. Yes, try to change the microSD card — it’s located close to the top edge of the circuit board. Any size is fine, probably 4GB and 8GB is the most common, you almost can’t find anything smaller, and larger is more expensive.
Also, I would highly recommend you to upgrade your firmware to 2.2.1(0). Your current firmware 2.1.9 is outdated and has known issues with the current UI/app. Upgrading to the latest firmware will solve this problem.
https://openthings.freshdesk.com/support/solutions/articles/5000381694Please check the HTTP API document:
https://openthings.freshdesk.com/support/solutions/articles/5000716363-os-api-documents
page 5, section 12, “Manual Station Run” /cm. The ‘ssta’ parameter can be used to skip a current running or scheduled station.Per the support article for MQTT:
https://openthings.freshdesk.com/support/solutions/articles/5000859089-how-to-use-mqtt
the /cm command is also supported by MQTT.I am a bit confused. You said “I have a ospi board v1.4 circa 2012 that’s running fine” — but what RPi are you using with it? Don’t you have a RPi plugged into the OSPi at the moment? Otherwise, how is it running fine? You can update the firmware on any RPi — the firmware runs fine regardless of the RPi version.
One possible reason is you may be using ETo weather algorithm and the returned data by ETo is now quite large and exceeds the storage allocated to it in your firmware. So the bottomline is your firmware 2.1.9(9) is outdated. If you are not ready to upgrade your firmware yet, you can try the following:
Download the API testing script:
https://openthings.freshdesk.com/support/solutions/articles/5000716363-os-api-documents
open it in a browser, put in your controller’s IP and device password, then choose Change Options (/co) API at the end. Type in option name:
uwt
and value
0
This will reset the weather algorithm to 0. After that, power cycle your controller (remove power and then plug in power again). That should fix the issue, if the issue is indeed caused by the weather data.You can also use the script to save a copy of your configurations (the Get Json All /ja API). But in the end the only solution is to upgrade your firmware to the latest 2.2.1, which should solve this problem for good. Firmware update instructions are here:
https://openthings.freshdesk.com/support/solutions/articles/5000832310Yes it works, and I always recommend Pi 0 (instead of 4 or 5) because it’s cheaper, draws way less power, and is sufficient to run the firmware.
Thanks for pointing it out. Yes we are aware of this. The plan is to gradually migrate those back to opensprinkler.com, which is already the main store front of everything we sell currently. At some point the cloud server at cloud.openthings.io will be migrated to a different domain name and we are working on it.
The latest firmware automatically identifies the gpio chip number:
https://github.com/OpenSprinkler/OpenSprinkler-Firmware/blob/master/gpio.cpp#L529
For RPi 5, I believe it will find gpiochip4. I am not sure where you changed gpiochip0 to gpiochip0, but it’s likely where you made the change is for other RPi versions, so it doesn’t matter.The power issue isn’t just that the onboard 24VAC to 5VDC converter isn’t capable of delivering 5A; note that 5V*5A=25Watt, which means the 24VAC power adapter needs to output at lest 25Watt. Most common 24VAC power adapters is only rated for 0.5A up to 1A, so the power adapter itself isn’t capable of delivering 25 Watt to begin with.
Honestly I would always recommend using RPi 0 with OSPi — it’s the cheapest and it requires minimum power. RPi 5 is so power hungry that it’s approaching a mini PC which should use its own power supply. We could use a beefier voltage regulator but first, the issue is that the 24VAC adapter isn’t able to provide that much power to begin with; second, if RPi foundation releases RPi 6, that may require even higher power, and at this rate there is no way we can keep up. So if you must use RPi 5, the only viable way is to give it its own power supply.
What are you using to power the board? If you are only using the 24VAC power adapter, that is probably insufficient. RPi 5 calls for 5V 5Amp, which is beyond the capability of the OSPi’s on-board voltage regulator. You need to use a USB-C power adapter to provide additional power.
Can I ask you to not duplicate the same message on the forum and also on github? This reduces my work of having to respond the same thing to both places.
Our German distributor, Stefan, does still have a few latch expanders. Latch expander MUST be used with latch main controller — non-latch main controller does NOT have the internal circuitry to operate latch expanders. You can contact Stefan to see if he has a latch main controller that you can swap with, or as I said, you can send a support ticket to us and we can sell you a latch driver board. You just need to replace your main controller’s driver board and it can become a latch controller.
1) You can submit a support ticket at:
support.opensprinkler.com
and arrange to purchase a Latch driver board. It’s a lot cheaper than buying a new controller and you can replace the driver yourself. This way you can reuse the same logic board and enclosure.2) There is no easy way to modify the DC driver board for latching valves. Latching valves require an H-bridge to operate because you need to be able to reverse the polarity when opening vs. when closing, which the DC driver doesn’t have. At best, some latching valves have 3 wires in which case it can take 2 ports on DC controller to operate. Still, even that requires a firmware update, which is probably not worth your time.
3) We no longer sell latching expanders — the demand for latching controller is very small to begin with. It make no economic sense to carry latching expander any more. You can NOT use DC expander for latching valves, again, because the way they work is quite different.
That’s a good call: stn_seq has been removed since it has been replaced by stn_grp. I will fix the document.
Allowing arbitrary reordering of zones in a program would require substantial changes to the program data structures as well as the UI design. This is not something that’s easy to do at the moment, not because it’s technically difficult, but because it involves a lot of changes to the program data structure and UI, and making them backward compatible is hard.
But, some limited support for reordering is coming up in the next firmware, as I explained here:
https://github.com/OpenSprinkler/OpenSprinkler-Firmware/issues/232#issuecomment-2256420560
it’s not arbitrary reordering, but it give you a few options to run zones in forward or reverse order of zones indices, forward or reverse order of zone names, alternating (i.e. program’s first run in forward order, second run in reverse order etc.), and completely random ordering.If you have been looking for an arbitrary reordering of zones feature in a sprinkler controller, that means it’s not a common feature — on traditional sprinkler controllers, you just name a set of zones and the water time of each zone, and it waters them in the order of the station index. I haven’t seen a sprinkler controller that allows arbitrary reordering of zones.
Although the firmware code is written in C++, it mostly uses C only features.
In addition, you can always use a script to send command to OpenSprinkler to run zones in any way you want.
The PoE support issue is a hardware issue — it’s because the wired Ethernet module, which is an off-the-shelf part, uses a Ethernet jack that’s not compatible with PoE. This is not something updating firmware can resolve.
One issue we see once in a while is switches or routers that have PoE(Power over Ethernet) turned on. The OpenSprinkler wired Ethernet module is apparently not compatible with PoE so make sure it’s not turned on at the router/switch that OpenSprinkler is plugged into.
You want to use DS1307 or PCF8563? With DS1307, it has dedicate battery backup pins, so the backup battery voltage doesn’t have to be the same as the supply voltage. In fact, you don’t need to use a supercap, you can use a 3V lithium coin battery, connect the positive to DS1307’s VBat pin, and negative to ground. That way you don’t need the diode and the super capacitor.
