Forum Replies Created
-
AuthorPosts
-
dpackhamParticipantLove summer break University as well 🙂
cant wait to test it out. let me know if you need any help/testing
dpackhamParticipantSame here
dpackhamParticipantit wont even build for me now. bummer sounded really cool
dpackhamParticipantDid ET ever get included? sounds great
dpackhamParticipantThats where i started. Â should I not update that image? Â should it work out of the box? Â I did try the wifi pluged direct into the PI but read that it may take too much power and brown out the Pi
dpackhamParticipantWhat’s a good range for the open sprinkler pi board? Mine runs at 149f all summer in an in closure.
Sent from my SM-G900T using Tapatalk
June 14, 2014 at 12:43 am in reply to: Python Interval Program 1 year aniversary and version 2.0 #27134
dpackhamParticipanti noticed a BUNCH of files in the session dir… when do those get deleted?
dpackhamParticipant+1 is there a reason that you need stop time?
dpackhamParticipantpicture?
June 12, 2014 at 12:56 am in reply to: Python Interval Program 1 year aniversary and version 2.0 #27126
dpackhamParticipantCool. Thanks
June 12, 2014 at 12:14 am in reply to: Python Interval Program 1 year aniversary and version 2.0 #27124
dpackhamParticipantahh i was NFS mounting it to a NAS.
hmm many json files. what should i move to the NAS and link back?
THanks
June 11, 2014 at 10:05 pm in reply to: Python Interval Program 1 year aniversary and version 2.0 #27122
dpackhamParticipantdid the logfile location change? i cant find it anymore
dpackhamParticipantmind sharing the code so I can get some ideas? ill share back what I get for the door sensor 🙂
dpackhamParticipantYeah. The 2x code would be cool as well.
Sent from my SM-G900F using Tapatalk
dpackhamParticipantCool on getting it working and the watchdog stuff.
dpackhamParticipantcool so the DIY kit running 1.8.x can be logged with the external web app ?
Thanks
dpackhamParticipantdoes the current DIY kit allow logging of watering times with the remote web servers? or do we need the 2.0 version to get the graphs?
Thanks
dpackhamParticipantyeah maybe a web based push of the log info via a simple url and PHP catch script that would store it in the sql db
dpackhamParticipantahh… I follow. one option is to use that web based interface and that will do the logging right?
dpackhamParticipantnoticed that you had some dupes in defines.h here is my working ones
// ===== Added for Freetronics LCD Shield =====
#define PIN_LCD_RS 8 // LCD rs pin – default = 19
#define PIN_LCD_EN 9 // LCD enable pin – default = 18
#define PIN_LCD_D4 2 // LCD d4 pin – default = 20 -DKP- or D2 for the LCD shield stacked on a net card that uses D4 for the SDcard
#define PIN_LCD_D5 5 // LCD d5 pin – default = 21
#define PIN_LCD_D6 6 // LCD d6 pin – default = 22
#define PIN_LCD_D7 7 // LCD d7 pin – default = 23
#define PIN_LCD_RS 8 // LCD rs pin – default = 19
//#define PIN_LCD_BACKLIGHT 10 // LCD backlight pin – default = 12 -DKP- net shield uses D10 as well. so I have backlight always on
#define PIN_LCD_CONTRAST 36 // LCD contrast pin – default = 13
#define PIN_ETHER_CS 37 // Ethernet controller chip select pin – default = 4
#define PIN_SD_CS 38 // SD card chip select pin – default = 0
#define PIN_RAINSENSOR 39 // rain sensor is connected to pin D3 – default = 11
#define BUTTON_ADC_PIN A0 // A0 is the button ADC input
dpackhamParticipantand I got the web interface to pull from it. all is good 🙂
dpackhamParticipantok so here is how i got it to work with the Net+LCD shield…
D4 is used on my ethernet card for the MicroSDcard slot so I had to bend the D4 pin on the LCD shield so it did NOT insert into the ethernet shield. then I jumpered the D4 LCD pin to the D2 on the ethernet shield that is a pass thru from the Mega board.
D10 also gets in the way…
i changed this code in defines.h
#define PIN_LCD_D4 2 // LCD d4 pin – default = 20 or D2 for the LCD shield stacked on a net card that uses D4 for the SDcard
to be a “2” instead of a “4′
ALSO I disabled this
//#define PIN_LCD_BACKLIGHT 10 // LCD backlight pin – default = 12
and commented OUT = // every line that tried to use it. backlight works fine
now NTP and everything works 🙂
Dave P
dpackhamParticipant@rszimm wrote:
Dave, my release (which I’ve been calling sprinklers_pi) was originally built on a 2560 with the W5100 ethernet interface. You should be able to get it running. It’s essentially the exact same code as here: viewtopic.php?f=28&t=244 except it doesn’t support the graphing logging stuff. Besides that however, you wouldn’t really know you were running the raspberry pi version or the version on the 2560. If you’re at all interested, (or anyone else is), I could polish that code up and ship it over…
can you enable logging with the microsd card?
dpackhamParticipantI have also tried the alternate code based on the _pi code. but I don’t see any logging?
more hmm…
-
AuthorPosts