in reply to Re^3: Continuous or timed?
in thread Continuous or timed?

... year's(or 10 years) worth of sunrise sundown times ...

The Earth's rotation is slowly slowing and days are getting longer, but the year-to-year change over ten or twenty years is small. If one were only concerned with 1-2 minute resolution, one could store, say, 62 or 183 sunup/sundown pairs (the day-to-day variation is also small). Since sunup and sundown only happen during certain periods of the day, these times might be stored as one byte each. This is a very small table.

Be that as it may, I'm not convinced one should be concerned with time as much as with light. What does it matter if, in midwinter, the curtains open at "sunup" when the sky is so overcast that it's like the middle of the night? A photocell/light level interface seems more important.

I agree with stevieb: These considerations and others suggest a microcontroller solution. A system running Linux seems like overkill indeed.


Give a man a fish:  <%-{-{-{-<

Replies are listed 'Best First'.
Re^5: Continuous or timed?
by Bod (Parson) on Dec 12, 2020 at 17:36 UTC

    These considerations and others suggest a microcontroller solution. A system running Linux seems like overkill indeed

    If I were starting this now and the only outcome was to open and close curtains then I would be using a microcontroller.

    I first heard about the Raspberry Pi many years ago and have been meaning to experiment with one periodically ever since so this is a good 'excuse'. Plus, it forces me to improve my Linux skills which in and of itself is a good outcome.

    Besides, when this project was started, microcontrollers were not on my radar...

      ... Raspberry Pi ... meaning to experiment with one ... this is a good 'excuse'.

      Understood. "... and then I'd get a chance to play with X ..." has been a determining consideration in many personal (and one or two professional :) projects of mine.


      Give a man a fish:  <%-{-{-{-<