I'd like feedback on what cams the script works on, I'll start a list of known working cams. Also, if you have problems I may be able to work around them, or add related features, if they're not too large and fit with the design or application of this script.
Well, the basic features seem to work fine on my (digic2) A620. The camera woke up, as scheduled, at 4am and took a photo every 2.5mins until around 7:30am, at which point it ran out of batteries (I had already taken a 552 image timelapse, one image every 30sec, without the LCD ever switching off on the same set/charge batteries). Seems fine.
Is there a reason why I wouldn't set the low-battery level to -1 (or something really low) and just have the camera drain the juice completely? I did this with the above mentioned test. I knew the batteries were quite low on juice (CHDK battery meter showed around 40% charge). If the camera is going to switch off at the end, it's not as though you have to worry about the script not 'cleaning up' after itself.
I don't suppose the LCD sleep mode settings could be activated/overridden from within the script? It's a little unintuitive to go to the regular Canon menu and set the sleep option (BTW, the A620 also has the 10, 20, 30sec, 1, 3, 3min options). Actually this is why my first time lapse always had the LCD on (a little to my surprise), because I didn't realise I had to change the regular Canon option. Mind you, with photos every 30 sec, I guess the LCD would only be off about half the time (for 15 sec each time). Now my camera LCD goes to sleep really fast in normal usage too, until I get around to resetting that option (so, this is why I ask the question, because it could become 'annoying').
What do you do about time lapses that span big changes in light, ie from night to day, or day to night? We have some limits to deal with as far as shutter speeds allowed in Av mode (1sec limit). I'm curious to see about DanielF's scripts answers to the issue.