I tired doing this a different way. Using an ATTINY85 to directly drive the two LEDs
with a PWM. Keeping in mind human eye has persistence could I reduce duty cycle,
hence average current needed from battery, by doing a low duty cycle drive of LEDs.
So here we have upper traces, drive to 1 LED, its connected PWM pin >> LED >> pin
to ground to turn on LED.
So blue trace is PWM output, running at 1/16 duty cycle.
Datasheet says I will get ~ 40 ma out of pin when high sourcing current, so 1/16 duty cycle
= ~ 2.5 mA average being supplied from battery. I have not yet tried a lower duty cycle, like
1/64.
So one would either make measurements of integrated brightness or subjective observation
and play with duty cycle to take advantage of eye persistence property. Which cuts power
needed.
Video, note Iphone seems to suppress RED, these are two LEDs connected to ATTINY85, one red,
one yellow. Video attached.
I used mBlock to create program code -
You drag functional blocks onto canvas on right, config, like set pin numbers associated with PWM, LEDs,
and hit upload. It generates the Arduino code which you program into ATTINY85 in this case. If you are
not a coder this is not a bad way of starting, and you can see C like code mBlock generates for the pro-
cessor. Kids in 6'th grade doing this to program simple robots.
Another vehicle to see if design can be improved.
Note the curves of source current out of a pin on ATTINY85 are typical, not maxes. So I am thinking
to insure pin max allowed current in datasheet not exceeded maybe add a diode in series with LED
to move up and to the left of this graph pin current for ATTINY85.
I did not add the A to D blocks to handle the daylight sensor, thats trivial to do, ATTINY85 will handle that as well.
So solution is 8 pin ATTINY85, 2 LEDs, 2 diodes, daylight sensor, and a R to use with it to set V divider.
Regards, Dana.