Forum Replies Created
Unfortunately I don’t know the part number — the factory sourced all the parts and we don’t know the part number for this header. I do know its spec: it’s SMD 2×4 female pin header, 3.5mm height. If you don’t need to fit everything into the OpenSprinkler enclosure, you can use standard 2×4 female header (or even 1×4 female header as only the top 4 pins are used). This will make the LCD sit higher than expected (so it won’t fit into the OpenSprinkler enclosure, but otherwise it works just fine).
Reboot loop is quite unusual — it would have to do with flash memory, either there is a flash memory corruption or maybe it needs to perform a full flash reset. If you encounter a reboot loop, I would recommend you to submit a support ticket.
Great, thanks for the update!
It’s on our todo list. Technically it’s not difficult as it pretty much just involves duplicating the existing code for master 1 and 2. It does, however, involve a bunch of changes both in the firmware as well as the UI, and it’s currently a low priority item on our todo list. I know this is often easy said than done: but honestly, the reason this entire project is made open-source is to give users the freedom to change the programs and extend features in any way they want, and that they don’t have to be bottlenecked by how quickly we can implement these features.
Hmm, this sounds quite unusual as the ‘NTP syncing’ step is guarded by a timeout (60 seconds by default) so it really shouldn’t be stuck like that for more than 60 seconds. Has this happened again?
The program preview (UI) and firmware use different scripts to calculate sunrise/sunset time, which may result in the difference. Also, if you are previewing today’s program, the UI will use the firmware’s sunrise/sunset time because those are variables the firmware will report to the UI. However, if you are previewing the programs for the next few days, the UI will use its own script to calculate sunrise/sunset time because the firmware does not keep track of the forecast sunrise/sunset times. To diagnose this further, the best way is for you to submit a support ticket with your controller’s configurations saved as a file, so we can import it and try to reproduce the issue on our end.
@venki.das: there is no need to post the same question on multiple threads. Please specify which version of OpenSprinkler you have, and what firmware version.
@venki.das: what version of OpenSprinkler do you have?
I would suggest that you send the controller back to us so we can replace the top layer with another board that has WiFi chip with external antenna plug. If it’s not convenient for you to send it back, you can purchase such a top board and replace it on your controller by yourself. In either case, you can submit a support ticket with the request.
The details of the weather algorithm are documented in the support article here:
the reason it’s not included in the firmware is that the weather adjustment methods are decoupled from the firmware — it’s hosted on the OpenSprinkler cloud server and new weather algorithms may be added at any time without modifying the firmware.
You can customize the weather algorithm by hosting it on your own server and change the weather url to point to your own server. The weather code and instructions can be downloaded here:
Well, this is a tricky question to answer and it depends on your specific setup. For example, here are two options to begin with:
– extend your valve wires to closer to where the office router is, so that OS can reach the WiFi signal, and still get physically connected to your valves.
– use WiFi range extender or set up a mesh network so the WiFi signal can reach further into the field
Sure, good suggestion. Will do.
are you able to change other settings, like number of zones, location etc?December 15, 2019 at 10:51 am in reply to: Program stops when wifi is lost and fails to resume #63663
I am trying to understand the issue: I don’t think the program simply stops when the wifi is lost, the only reason program stops is if the controller reboots. Which firmware version are you on? If you are on the latest 2.1.9(2) it records reboot reason which will help diagnose the situation.
there is no firmware 2.9. could you go to the ‘About’ page and check the firmware version?
I can’t answer questions 1 and 2, but regarding 3: no, there is no new hardware release on the horizon. new firmware can always be uploaded to your controller when they are released.December 15, 2019 at 10:47 am in reply to: HELP – OS 3.0 DC with 24v AC solenoids – Issues with Master .. water pressure ? #63657
What’s your master solenoid’s brand name and model number? Is it a pump start relay or is it a solenoid?
You can do a git checkout of an earlier version of the firmware.December 12, 2019 at 4:34 pm in reply to: Program stops when wifi is lost and fails to resume #63632
I think I got confused: by saying “upgraded the OS on the wireless router”, I guess you mean the operating system on your wireless router? I thought “OS” means OpenSprinkler, but given your description, it sounds like by OS you mean operating system.December 10, 2019 at 12:12 am in reply to: Program stops when wifi is lost and fails to resume #63596
By “did an upgrade on the OS for our wireless router” did you mean you upgraded the firmware on the OS, or did you mean you upgraded the router?
The controller works either in WiFi or wired Ethernet mode, but not both. If you plug in the wired Ethernet module, it will only function in wired Ethernet mode and will NOT transmit any WiFi signal.
Besides, to use WiFi you actually have to configure it to log onto your WiFi router. If you never configure it, of course it will never send any WiFi signal.
Yes, you can. This can be done by using the ‘HTTP Station’ feature — you can take a look at the OSBee API to see what command to use to trigger a zone to run on OSBee, and basically set up a zone on your OpenSprinkler as HTTP zone with that command. This way, when the zone is turned on or off, it send a HTTP command to OSBee to trigger the actual zone action.
The current version of OpenSprinkler 3.0 allows an Ethernet add-on: you can purchase OpenSprinkler 3.0 with the wired Ethernet add-on.
@JonInAz: what specific error message are you getting? “unsuccessful” does not give enough details for diagnosing the problem.November 25, 2019 at 1:38 pm in reply to: OSPi 12vdc – should there be a ground between COM socket and transitor ground? #63394
First thing is to check the orange terminal block: on your picture, the pin on the left (closer to a row of 5 or 6 ground pins) should be ground, and the pin on the right (closer to the COM) terminal is the COM wire. So obviously these two pins (on the orange terminal clock) are NOT connected — the two sharp triangles facing each other are called PCB spark gaps, they are for releasing high voltage charges but are normally completed separated from each other.
Next, if you are using 12VDC to power the board, DC power has polarity. So make sure the negative of the power goes to the ground pin on the orange terminal block, and the positive goes to the other (i.e. COM wire).
If the power is connected correctly, the power supply’s negative pin is obviously shared with the circuit ground, and that in turn should be shared with each of your transistors’ emitter pins.