Closed Paddy-Wa closed 10 years ago
Hmmm. Interesting. This seems to be an incompatibility with the wiringPi library and the i2c library that drives the hwclock. I can duplicate this on my side by setting the output type in sprinklers_pi to NONE and then reboot. When I reboot I can read the clock just fine and still access sprinklers_pi. When I go set the output type to anything other than NONE, the hwclock immediately stops working...
I'll dig into this. Good catch...
Just a guess, maybe you are setting the pin input/output type for one of the i2c pins? GPIO 2,3 and maybe 4 are used for I2C and external clock. If sprinklers_pi tries to initialize those pins (or set them to 0) it could break I2C.
On Wed, Nov 20, 2013 at 1:02 PM, rszimm notifications@github.com wrote:
Hmmm. Interesting. This seems to be an incompatibility with the wiringPi library and the i2c library that drives the hwclock. I can duplicate this on my side by setting the output type in sprinklers_pi to NONE and then reboot. When I reboot I can read the clock just fine and still access sprinklers_pi. When I go set the output type to anything other than NONE, the hwclock immediately stops working...
I'll dig into this. Good catch...
— Reply to this email directly or view it on GitHubhttps://github.com/rszimm/sprinklers_pi/issues/8#issuecomment-28912914 .
That's exactly the issue nhorvath. I put up a new release 1.0.7 that fixes just this bug. Thanks for the help guys...
Sorry to be a pest. I'm finding that the hwclock becomes unreachable as soon as I change the settings to OpenSprinkler. Additionally I am not able to get the hwclock back until I remove sprinklers_pi (make remove) and reboot.