- This topic is empty.
-
Posts
-
Hey all,
I setup the devkit version of the OpenSprinkler 2.0 hardware this weekend, and it seems like the board is crashing/hanging after some event that I can’t quite pinpoint. The controller works perfectly when I run the schedule in test mode, but on a schedule it seems to hang every time. The screen stays on, but the buttons are not responsive and trying to access the web interface times out.
I’ve seen references to a bad solenoid problem, but I’m not sure how to diagnose that. Anyone have other ideas?
The first thing to try is to unplug the common wire terminal (so the solenoids will not be activated) and see if the controller still crashes. If not, that means the problem is either a defective solenoid, or the PTC fuse under high temperature (as discussed in this thread: viewtopic.php?f=9&t=84). If the controller still crashes even after the common wire is disconnected, you should return the controller for a replacement. Send email to [email protected] for support.
@ray wrote:
The first thing to try is to unplug the common wire terminal (so the solenoids will not be activated) and see if the controller still crashes. If not, that means the problem is either a defective solenoid, or the PTC fuse under high temperature (as discussed in this thread: viewtopic.php?f=9&t=84). If the controller still crashes even after the common wire is disconnected, you should return the controller for a replacement. Send email to [email protected] for support.
I’m pretty sure it isn’t a heat problem. It’s consistently under 70F here now, and the controller is in my garage, which is typically cooler than that. Will the defective solenoid show when the controller crashes after a particular zone?
Well, you can tell if the controller crashes when running a particular zone. OpenSprinkler currently does not have circuitry to automatically detect defective solenoids, so you need to find it out manually. I don’t have much experience with defective solenoid, but I guess there are quicker ways to test, such as testing the coil resistance (if the resistance is too low compared to other good solenoids, that indicates a problem).
I am seeing a similar problem. I just got the kit (2.0) last weekend and haven’t set up a program/schedule yet. But I have left the unit on and noticed it has been needing a reboot about once a day. I will spend some more time checking it out this weekend, but I wanted to report it.
There may be a stability issue that I am not aware of (although I have a test 2.0 circuit that has been running weeks without a problem). Do keep me updated about your findings.
I’ve just installed the 2.0 OpenSprnkler replacing current Iritrol; I’m certain there is no problem with solenoids. I ran some tests in manual mode, also had some schedule programmed in. Everything worked until today’s afternoon when controller become irresponsive. I’ve also noticed the date on display was Tue 02-27 (which happened in 2007) . The LCD’s network status stuck in “connected”. Switching the controller on/off restored the connection and the date. However, having read previous comments in the thread I believe there’s a common issue with 2.0 hardware.
OK, if anyone can please send me back your OpenSprinkler 2.0, I will take a look and diagnose the problem. I have a 2.0 board at hand and I have not encountered a similar problem. Please contact me directly at [email protected]. Thanks.
Let me wait a few days, if after a week the issue re-occurs I’ll send you my board. I forgot to mention, I have one ext board, not sure if it matters.
OK, keep me updated. As I am going to officially release 2.0 soon, it would certainly be good for me to iron out any technical issue quickly. Thanks.
One quick question: everyone who encountered issues with 2.0 development board: could you check the PCB and let me know if you have a black PCB or green PCB? They have slightly different schematics. If I can identify it’s always the green version that leads to the issues, that can help me narrow down the problem. Thanks.
Mine’s actually black, but in my case the cause might be clock-related and have nothing with PCB design.
I am fairly confidence I’ve figured out the source of the problem, and reported it in this blog post:
http://rayshobby.net/?p=5962Anyone who has received the 2.0 development board and is having issue with it can email me at [email protected] for a free replacement. Thanks for your patience!
- You must be logged in to reply to this topic.