Announce: non-intervalometer timelapse script, uses clock time, repeats daily - Completed and Working Scripts - CHDK Forum  

Announce: non-intervalometer timelapse script, uses clock time, repeats daily

  • 29 Replies
  • 16653 Views
Advertisements
This script takes up to 12 shots per day on a schedule -- set each shoot time as hh:mm wall clock time.  Has battery low detect, AF lock option, MF mode restore after camera idle, AF normal or macro option, flash control option from daylapse.  A new synchronise to camera clock zero seconds option as well as test options like shoot in one minute if there's no future scheduled shots today, exit after today's last shot.

~~Has a documentation file!~~

http://bugsplatter.id.au/chdk/hmm_wrks.bas
http://bugsplatter.id.au/chdk/hmm_wrks.txt

Ran script overnight to take 3 shot exposure bracketing at half past 6, 7, 8, 9, 10...  Camera slept through midnight and woke before first shot, slept (idle mode) between shoot sequences.

Today I added bells & whistles, and documentation for it.  Feedback welcome.

parameters
```````````
        Shoot Time a hhmm   0-2400
        Shoot Time b hhmm   0-2400
        Shoot Time c hhmm   0-2400
        Shoot Time d hhmm   0-2400
        Shoot Time e hhmm   0-2400
        Shoot Time f hhmm   0-2400
        Shoot Time g hhmm   0-2400
        Shoot Time h hhmm   0-2400
        Shoot Time i hhmm   0-2400
        Shoot Time j hhmm   0-2400
        Shoot Time k hhmm   0-2400
        Shoot Time l hhmm   0-2400
        MF Distance    mm 10-65535
        Options A       &    0-255
        Options B       &    0-255
        Low Battery    mV    >2000


Script does a proper clean exit when 'shoot' is pressed to interrupt, has a wake option (press 'set') to view status, displays next shoot target time and seconds remaining countdown.  Though setup as an endless script, shutdown on script exit due to interrupt or low battery properly parks the lens and powers down.  The 'press shoot to interrupt' option may return cam to chdk by pressing 'set' button to stop the shutdown timer.
« Last Edit: 07 / July / 2009, 02:53:49 by bugsplatter »

You may be interested in SDM 1.81 to be released in a few weeks.
It  has a new uBasic command 'sleep_until' or 'start_time' that allows you to start any operation at a particular time.
After completing the operation, you can then sleep (with display off) for 24 hours.
It also has a command 'stop_time' to terminate otherwise continuous sequences.


David

*

Offline Hacki

  • ****
  • 359
  • EOS 80D
It  has a new uBasic command 'sleep_until' or 'start_time' that allows you to start any operation at a particular time.
After completing the operation, you can then sleep (with display off) for 24 hours.
It also has a command 'stop_time' to terminate otherwise continuous sequences.


That sounds interesting. We should defenitely backport that to chdk, despite the difficulties.

Regards.

You may be interested in SDM 1.81 to be released in a few weeks.
It  has a new uBasic command 'sleep_until' or 'start_time' that allows you to start any operation at a particular time.
After completing the operation, you can then sleep (with display off) for 24 hours.
It also has a command 'stop_time' to terminate otherwise continuous sequences.

Hi David,
Such a steep learning curve I'm traveling with chdk and ubasic interface to cam at the moment, I'd only be more confused by trying SDM.  I can do start_time and stop_time in script, so don't see a need to explore SDM yet.  My interest is in improving CHDK, not simply trying to get a timelapse happening per se.

That's why I'm exploring cam power consumption and intend to join the porting effort because the A series cams I have are not yet fully supported.  Then, there's Lua to learn.  Lots of stuff to play with for the time being :)

And there's the odd question like why does get_day_seconds not match the cam's clock seconds while 'get_time 0' does, running around in my head.  (Compare 'get_day_seconds % 60' with 'get_time 0').



*

Offline PhyrePhoX

  • *****
  • 2254
  • make RAW not WAR
    • PhyreWorX
It  has a new uBasic command 'sleep_until' or 'start_time' that allows you to start any operation at a particular time.
After completing the operation, you can then sleep (with display off) for 24 hours.
It also has a command 'stop_time' to terminate otherwise continuous sequences.

That sounds interesting. We should defenitely backport that to chdk, despite the difficulties.

Regards.


one would think David is actively avoiding this topic about backporting, see also here. instead he is more or less advertising his SDM (Super Data Maker by now?) build all the time. and 1.81 is not even out yet. like i would go to a coca cola fanboy forum talking about the new pepsi diet coke that will be out later this year. I really dont understand the motivation behind this. Sure, promoting one's own build is perfectly legit. But i would assume that a forked project's maintainer would collaborate with the "mother" project in a nicer way.
just saying.

This script takes up to 12 shots per day on a schedule -- set each shoot time as hh:mm wall clock time.  Has battery low detect, AF lock option, MF mode restore after camera idle, AF normal or macro option, flash control option from daylapse.  A new synchronise to camera clock zero seconds option as well as test options like shoot in one minute if there's no future scheduled shots today, exit after today's last shot.

~~Has a documentation file!~~

http://bugsplatter.id.au/chdk/hmm_wrks.bas
http://bugsplatter.id.au/chdk/hmm_wrks.txt

Ran script overnight to take 3 shot exposure bracketing at half past 6, 7, 8, 9, 10...  Camera slept through midnight and woke before first shot, slept (idle mode) between shoot sequences.

Today I added bells & whistles, and documentation for it.  Feedback welcome.

parameters
```````````
        Shoot Time a hhmm   0-2400
        Shoot Time b hhmm   0-2400
        Shoot Time c hhmm   0-2400
        Shoot Time d hhmm   0-2400
        Shoot Time e hhmm   0-2400
        Shoot Time f hhmm   0-2400
        Shoot Time g hhmm   0-2400
        Shoot Time h hhmm   0-2400
        Shoot Time i hhmm   0-2400
        Shoot Time j hhmm   0-2400
        Shoot Time k hhmm   0-2400
        Shoot Time l hhmm   0-2400
        MF Distance    mm 10-65535
        Options A       &    0-255
        Options B       &    0-255
        Low Battery    mV    >2000


Script does a proper clean exit when 'shoot' is pressed to interrupt, has a wake option (press 'set') to view status, displays next shoot target time and seconds remaining countdown.  Though setup as an endless script, shutdown on script exit due to interrupt or low battery properly parks the lens and powers down.  The 'press shoot to interrupt' option may return cam to chdk by pressing 'set' button to stop the shutdown timer.


Hey guys and gals,

first post, just got the CDHK going on my sx200is, awesome.

Main reason I did this is to do a time lapse shoot over 6 months, I have found and got an interelover (spelling) script up and running which is great, but this looks like it will be a lot more useful for my needs. Basically shoot every hour between 7:30 and 5:30 each and every day.

The text quoted, will that be enough to copy and paste into a text file to save as a .lua and run the script (I am dreaming aren't I?)

The links above are dead, so if anyone can help it would be much appreciated.

Try: http://bugsplatter.id.au/chdk/archive/

I just restored it, offered without support as my A590 died last year and I thus no longer run CHDK.

Cheers,
Grant.

*

Offline reyalp

  • ******
  • 13792
Quote
It  has a new uBasic command 'sleep_until' or 'start_time' that allows you to start any operation at a particular time.
After completing the operation, you can then sleep (with display off) for 24 hours.
It also has a command 'stop_time' to terminate otherwise continuous sequences.
That sounds interesting. We should defenitely backport that to chdk, despite the difficulties.
This should be easy to implement in lua, no need for extra C code. Good candidate for a standard library.
Don't forget what the H stands for.


Try: http://bugsplatter.id.au/chdk/archive/

I just restored it, offered without support as my A590 died last year and I thus no longer run CHDK.

Cheers,
Grant.

Thanks for that much appreciated. Should make life a bit easier for me :)

Having trouble getting this to work, I think I am struggling with the basics,

I load the card and the script and this keeps popping up, my knowledge of code is very limited so I would appreciate any help.


 

Related Topics