Hello, I am new to CHDK and Ultimate Intervalometer. I'm using CHDK 1.3 on a PowerShot S90 and would like to acquire 1 image every hour for about 3 weeks. If things work well, I would be repeating it often.
How important is the automatic reboot of Ultimate Intervalometer? Are there well-known CHDK stability issues that will cause a 3-week time lapse to fail? There is also a mention of a tick counter overflowing -- would that happen within 3 weeks and if so, what are the consequences of the overflow?
So far, I have not had luck with Ultimate Intervalometer's camera_reboot() function. The camera crashed and became unresponsive. To systematically test it, I changed the minimum range and value of "@param l Days between resets" from 1 to 0, and then set the camera's clock to 10 minutes before the reset hour parameter. That way I know a camera reboot will happen now, without having to wait until tomorrow. Each time I tried this, the camera crashed (with lens extended, LED no longer blinking, screen black, buttons other than on/off unresponsive) after camera_reboot() is called.
By adding a bunch of printf() statements, I isolated the problem to the call to set_record(0) in the call to switch_mode(0) within camera_reboot(). The last line of ultimate.log shows the debugging printf statement I placed just before set_record(0) is called.
I'm running an actual time lapse now, hoping it will last for up to 3 weeks without a reboot, but if failure is inevitable and rebooting will be necessary, I can either decide to manually restart everything every few days (not as convenient) or figure out why my camera is crashing from the set_record(0) statement.
Any insights or suggestions?
Thank you.
