Waterwings thanks for quick response.
This specific script is NOT essential. But the reason I am interested... I need to build an installation for a several month long time lapse. I have been running tests with current proven intervalometers, such as "Selective Intervalometer" and the basic Intervalometers in the current chdk load. They are working OK,
BUT, I am concerned about burning out the cmos sensor by having it being live (powered on) for several months. (Its fine if the camera runs out its life on this project, I actually expect that, but I just dont want the camera to die three weeks into a 5 month job.) - (Another concern is that because the cmos is constantly powered, that might cause camera to go into shut-down, if the temp exceeds a safety threshold. In testing today, the cmos sensor seemed to stay constant at 105 degrees F. )
So, I was investigating wether there are any scripting routines out there, which dont keep the cmos sensor fired up continuously.... thats is that the script shifts the camera into some status in which the script is still running but the sensor is not powered, then comes alive to shoot for awhile, then back to waiting. ( I wonder if the sensor is not powered while the camera is in play mode?)
Any ideas or suggestions you have much appreciated. (I have rudimentary programming skills, but pretty new to chdk)
mk