Forum Replies Created
-
AuthorPosts
-
dblessingMemberThanks, Dan. I thought the same. Last year I did this in the menu program and it worked. However, it seemed that both the interval program and the menu program could not co-exist. If I start both programs up and ran a station from the menu program the interval program would no longer be able to control the sprinklers. It seemed like there was a GPIO conflict in doing things this way. Maybe I just need to dig in to it more and see why they conflicted.
I’d appreciate any thoughts you or anyone else has on why they would conflict. Thanks again.
**Edit – I tried again and this is the error I’m getting: “RuntimeWarning: This channel is already in use, continuing anyway.” when I called GPIO.setup(). It says “continuing anyway” and the program starts. However, as I said, it can’t actually control the sprinklers after that point.
dblessingMemberAt a quick glance, I don’t see why One-Wire stuff wouldn’t work. It would be nice to know what I2C address those sensors use. Currently, with the OS board and the LCD my I2C address table looks like this:
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: 20 -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- 48 -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- 68 -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --
The above is found my running `i2cdetect -y 1` for the Rev2 Pi. Those addresses translate to 0x20, 0x48 and 0x68. The 0x20 is the LCD and the 0x48 and 0x68 are the OSPi. Don’t quote me.
dblessingMemberYep, ray’s exactly right. The only thing I had to do was buy an extra tall stacking header so there was enough pin to plug the OpenSprinkler cables in once the LCD was soldered on. The stacking header can be found at http://www.adafruit.com/products/1112
dblessingMember@ray wrote:
Cool, looks nice and thanks for sharing.
I suspect it can’t fit all together to the current enclosure, since the enclosure (Serpac 032C) isn’t very high. However, if you have some way of making cutouts yourself, you can get Serpac 033 or 133 enclosure, which has extended height and I believe can fit with the base of 032C enclosure:
http://www.serpac.com/sx3x.aspx
Digikey and Mouser both have these enclosures at very reasonable price.Thanks for the tip on the enclosure. I hadn’t figure out what I was going to do yet.
@craigmw wrote:
This looks interesting. Are you directly modifying the code in the interval program, or using the add-on approach that has been included in recent updates? I can see this being very useful for the exactly the purpose you state.
The actual menu control code I am building separately so it can be used regardless of what program you run for the sprinklers. I haven’t quite decided if I will put additional code in the interval add-on or if I will just query the interval program for sprinkler status and have that be configurable in the menu program. It would be really nice if you could check the status of a shift register to get the status of a sprinkler station but from what I see you cannot.
July 29, 2013 at 4:42 pm in reply to: I cannot for the life of me get a scheduled program to run! #24796
dblessingMemberI can confirm that the timezone was the issue. I first set the timezone via an environment variable. Apparently that doesn’t work for this scenario. I followed the instructions in this guide and things started working as expected. http://elinux.org/RPi_Beginners#Timezone
July 27, 2013 at 8:35 pm in reply to: I cannot for the life of me get a scheduled program to run! #24793
dblessingMemberI am also having issues with the scheduled programs. I see them on the program preview but they never run. All other functions work fine. Is there any cron or other piece missing to get scheduled programs to run?
dblessingMemberThanks, Ray. I will give this a shot. I’m definitely in new waters here. I will post back on this site if/when I get this accomplished.
dblessingMemberLooking more…
The OSPi actually uses the 2-I2C/GPIO pins as I2C pins I think. If that’s the case, then It should be no problem to reuse those pins for the LCD since it’s a bus. I’m just learning all of this stuff but I think I have the right idea? 🙂 If anyone can confirm my understanding of the I2C pins that’d be great.
-
AuthorPosts