my first real post about a completed project...
I've always fancied doing timelapse with my D90, and the last time I looked, there was only 3rd party wired-only units that were limited by their own designs (only 999 pictures or so forth, preset timers, expensive). So a while back I looked again and saw that a few people had made various incarnations using their arduino and things like variable resisters/rotary encoders, etc. I always liked them, but didn't have any of that kit hanging around. So I used what I had...
So, my implementation uses a nuelectronics LCD shield instead... http://www.nuelectronics.com/estore/index.php?main_page=product_info&products_id=2
I figured it also can give feedback on the number of photos took, when the next one is due to be taken, etc. It also means that the settings are menu driven - for example, intervals can be displayed as 1s, 5s, 1m, 1h, etc, and the no of photos can be chosen directly too.
The sketch for it is here: http://www.hagane.org.uk/arduino.php
if anyone's interested in taking a look? I welcome feedback and (if anyone actually thinks it's usable?) feature requests.
On the hardware side, it just needs the LCD-shield and an IR LED hooked up to pin 13. The input buttons are (from left to right) start/stop, decrease interval/no of photos, up, down, increase interval/no of photos, reset.
A few notes:
- Uses the Nikon IR Library from Gustav von Roth. It's awesome, and I don't think I'd have had the knowledge/skills to find the IR timings myself... http://www.vonroth.com/Arduino/NikonIrControl/
- Uses the LCD_4bitmod library from nuelectronics, as their shield's geared up to use it.
- I know the code/variable naming is on the messy side. I'm rusty from my last 'real' coding stuff 6 years back. I do plan to clean it up sometime.
- Would be nicer if it used interrupts. Unfortunately the shield's buttons are on an analogue pin, and from the hour or so research I did when I was sketching, you can't use arduino interrupts on analogue pins. Please correct me if I'm wrong?
- I am relying on delays. I know this is bad (boo, hiss, etc) and have been thinking of changing over to millis timing, but for me this is a 1.0 release. Wanted to see if anyone would actually be interested in me developing it further or whether everyone's happy with the other solutions out there...
- If anyone wants photos, let me know. At this stage it's just naked, on a seeedstudio acrylic harness.