Rapid intervalometer script? - page 2 - Script Writing - CHDK Forum  

Rapid intervalometer script?

  • 14 Replies
  • 5552 Views
*

Offline barret

  • ***
  • 125
  • S3 & a550
Re: Rapid intervalometer script?
« Reply #10 on: 11 / April / 2009, 11:07:17 »
Advertisements
what's the upper limit of time that camera can shoot in continuous mode? can i use it for continuous 8 hour shooting? that's 480 minutes = 28800 seconds = 28800000 milliseconds.
« Last Edit: 11 / April / 2009, 11:10:09 by barret »

*

Offline fudgey

  • *****
  • 1705
  • a570is
Re: Rapid intervalometer script?
« Reply #11 on: 11 / April / 2009, 13:45:34 »
what's the upper limit of time that camera can shoot in continuous mode? can i use it for continuous 8 hour shooting? that's 480 minutes = 28800 seconds = 28800000 milliseconds.

There's probably no limit (but I'm not sure) other than the usual i.e. battery power unless externally powered and too many shots on the card eventually requiring too much RAM for file tables, and tick count wrapping around after a month or something like that.

Re: Rapid intervalometer script?
« Reply #12 on: 10 / June / 2009, 02:15:15 »
what's the upper limit of time that camera can shoot in continuous mode? can i use it for continuous 8 hour shooting? that's 480 minutes = 28800 seconds = 28800000 milliseconds.

There's probably no limit (but I'm not sure) other than the usual i.e. battery power unless externally powered and too many shots on the card eventually requiring too much RAM for file tables, and tick count wrapping around after a month or something like that.

I'm running A590 IS with a small script to shoot each five seconds (cam staring out the window, make movie of clouds), yesterday the camera locked up (power down with lens out) when the 8GB memory was half full with >7000 1600x1200 files.  Camera running from mains power.  Day before cam took ~13,000 640x480 files (dawn to dusk) without a problem. CHDK version very recent .772, I think. 

Early days for me + CHDK scripts...


*

Offline fudgey

  • *****
  • 1705
  • a570is
Re: Rapid intervalometer script?
« Reply #13 on: 10 / June / 2009, 16:09:07 »
I'm running A590 IS with a small script to shoot each five seconds (cam staring out the window, make movie of clouds), yesterday the camera locked up (power down with lens out) when the 8GB memory was half full with >7000 1600x1200 files.  Camera running from mains power.  Day before cam took ~13,000 640x480 files (dawn to dusk) without a problem. CHDK version very recent .772, I think. 

You may want to read this, even if it's a bit technical: http://chdk.wikia.com/wiki/CHDK/Camera_RAM_memory_usage. In a nutshell, it seems it's possible to run out of RAM by shooting too many images and that it's possible to make that happen sooner rather than later by e.g. not starting the script right after power-on, which could explain both the crash and the variance in your mileage...

How quickly does your camera power on to play mode with normal responsiveness when you have 13000 photos on the card? Mine takes its time...it's around 15 seconds compared to normal instantaneous boot.


Re: Rapid intervalometer script?
« Reply #14 on: 10 / June / 2009, 19:55:42 »

You may want to read this, even if it's a bit technical: http://chdk.wikia.com/wiki/CHDK/Camera_RAM_memory_usage. In a nutshell, it seems it's possible to run out of RAM by shooting too many images and that it's possible to make that happen sooner rather than later by e.g. not starting the script right after power-on, which could explain both the crash and the variance in your mileage...

How quickly does your camera power on to play mode with normal responsiveness when you have 13000 photos on the card? Mine takes its time...it's around 15 seconds compared to normal instantaneous boot.

Ah, but I'm a brain-burned, mad, technical person :)

Play mode is very slow starting on A590 like you found, cam sits there flashing green LED near viewfinder for a long time, also the windoze Zoom program refused to communicate -- plugging in a 'doze or linux USB cable made the camera issue "Communications Error" and refuse to talk -- however Zoom program has no problem reading the SDHC card in a USB reader.

As far as A590 recording images, it creates a new /DCIM/???CANON directory each 2000 images.  Cam is up to /DCIM/110CANON now.

I'll clear the image files before each timelapse session now.  The crash happened during a second session where I hadn't cleared the image files from first session.  Was also using the 1600x1200 timestamped image option.

Soon I'll rewrite my timelapse script to use the clock rather than tick counter for low drift, also want try Lua.  My chdk page is http://bugsplatter.id.au/chdk/ where I'll dump info as I discover it.  Also plan to measure power consumption in various modes.  One day do my own builds, list is endless :)

 

Related Topics