Ultimate Intervalometer - a script for shooting over a long duration - v4.9 - page 40 - Completed and Working Scripts - CHDK Forum supplierdeeply

Ultimate Intervalometer - a script for shooting over a long duration - v4.9

  • 651 Replies
  • 228528 Views
Advertisements
So in order to run the script according to time specified, do I need to set "shoot when Tv" to "off"?
Yes.

Quote
The problem is that when I set it to "off" my camera doesn't take any shots. Below is the log I got from my another camera (SD880) that I use for testing.
Take a look at what the log tells you.  You have the script configured to start shooting at 8:00 AM and to stop at 5:00 PM.   The log takes place between 1:35 AM and 1:32 AM.  Do you see the problem now?

Sat May 14 01:25:35 2016 === Ultimate v4.1 : 01:25 ===
Day -- Sat May 14 01:25:35 2016 CHDK 1.4.0 ixus870_sd880 101a Nov 23 2015
Day 1 Sat May 14 01:25:39 2016 start time : 08:00 stop time : 17:00
Day 1 Sat May 14 01:25:39 2016 switching to night mode
Day 1 Sat May 14 01:25:45 2016 key pressed
Day 1 Sat May 14 01:25:45 2016 menu key exit
Day -- Sat May 14 01:25:55 2016 === Ultimate v4.1 : 01:25 ===
Day -- Sat May 14 01:25:56 2016 CHDK 1.4.0 ixus870_sd880 101a Nov 23 2015

Day 1 Sat May 14 01:25:59 2016 start time : 08:00 stop time : 17:00
Day 1 Sat May 14 01:25:59 2016 switching to night mode
Day 1 Sat May 14 01:26:00 2016 V: 3.630 T: 24 <no shot>
Day 1 Sat May 14 01:27:00 2016 V: 3.635 T: 24 <no shot>
Day 1 Sat May 14 01:28:00 2016 V: 3.620 T: 24 <no shot>
Day 1 Sat May 14 01:29:00 2016 V: 3.630 T: 25 <no shot>
Day 1 Sat May 14 01:30:00 2016 V: 3.630 T: 25 <no shot>
Day 1 Sat May 14 01:31:00 2016 V: 3.610 T: 25 <no shot>
Day 1 Sat May 14 01:32:00 2016 V: 3.610 T: 26 <no shot>
Day 1 Sat May 14 01:32:06 2016 key pressed
Day 1 Sat May 14 01:32:08 2016 key pressed
Day 1 Sat May 14 01:32:08 2016 menu key exit

Ported :   A1200    SD940   G10    Powershot N    G16

My bad, thanks for the clarification. I made a mistake setting my camera according to 12hr system, e.g. 1 instead of 13.


*

Offline PVL

  • *
  • 2
HI! I am new with CHDK.
I am trying to solve this problem: shooting continuously with a canon camera flying in a drone. I am looking for the right script and I have seen the Ultimate Intervalometer. Question: Can I use it for this application? The shooting times are fast (1- 1.5 seconds) and the plane moves at 10 m/s aprox at 100 m hight.
I bought a Powershot SX610 but I have seen it is not ported yet. So I bought a Powershot N and I am working with it right now.
Any orientation is welcome. Thank you in advance!

Pablo

HI! I am new with CHDK.
I am trying to solve this problem: shooting continuously with a canon camera flying in a drone.
link > KAP UAV Exposure Control Script
Ported :   A1200    SD940   G10    Powershot N    G16


*

Offline PVL

  • *
  • 2
Working! Excellent, thank you very much!

Pablo

Ultimate Intervalometer - a new bug
« Reply #395 on: 13 / July / 2016, 00:33:18 »
I've come across a strange bug. 

While testing some script updates, I've found that my A1200 will occasionally crash the camera when the script switches from day to night operating mode. As configured, this change puts the camera into playback mode, and calling set_lcd_display(false).  The last log entry is always right before it tries to switch to playback mode and the lens retracts but other than that, I don't know exactly where it is crashing.

ROMLOG attached (this same log has been duplicated several times).   

Tonight I added a bunch of print() statements to try and narrow down when things are halting .. and naturally the script no longer crashes on the day to night changeover.

As this is the default script configuration, and the script has been downloaded over 4000 times,  it's curious that this has not come up before.  And I'm quite sure it's not related to my recent code updates ("famous last words") as I did not touch the display management or day/night parts of the code.

Testing this will be painful - @reyalp or @srsa_4c if the ROMLOG gives any hints I'd be "all ears".  Otherwise I'll keep working to narrow down exactly where this is happening.
Ported :   A1200    SD940   G10    Powershot N    G16

*

Offline reyalp

  • ******
  • 14098
Re: Ultimate Intervalometer - a new bug
« Reply #396 on: 13 / July / 2016, 01:15:58 »
Testing this will be painful - @reyalp or @srsa_4c if the ROMLOG gives any hints I'd be "all ears".  Otherwise I'll keep working to narrow down exactly where this is happening.
Are you deleting images?

Code: [Select]
ASSERT!! MetaCtgParser.c Line 735
Occured Time  2016:07:10 21:00:11
Task ID: 34013254
Task name: MetaCtg
Looks familiar https://chdk.setepontos.com/index.php?topic=11481.0
Don't forget what the H stands for.

Are you deleting images?
Yup.   Trying to track and delete the oldest image from the current run each time the SD card gets full.

Quote
Looks familiar https://chdk.setepontos.com/index.php?topic=11481.0
Thanks - sounds like exactly the same thing.   

I guess I could disable the ability to idle in playback mode at night once image deletion is required. The kind of nasty hack where you keep your fingers crossed once it's enabled.
Ported :   A1200    SD940   G10    Powershot N    G16


*

Offline reyalp

  • ******
  • 14098
Thanks - sounds like exactly the same thing.   
Yeah, almost certainly the same issue, same thing happens if you delete manually.
Quote
I guess I could disable the ability to idle in playback mode at night once image deletion is required. The kind of nasty hack where you keep your fingers crossed once it's enabled.
You could try replacing the jpegs with 0 byte files, e.g f=io.open(filename,"wb") ; f:close()
I don't know what the canon OS would think of that, but it should be pretty quick to try. If zero byte fails I guess you could write a tiny jpeg instead (take a 640x480 low quality shot of a blank scene, hard code it in the script as a string...)

Another option would be to only do the deleting in playback mode. AFAIK switching to and from record is fine if the deleting is done in playback.

Also, as mentioned at the end of the thread, the error only seems to happen with full res jpegs :blink: that might be an avenue for investigation, or at least be a workaround for timelapses where the final product doesn't need full res.
Don't forget what the H stands for.

Quote from: waterwingz link=topic=9969.msg129285#msg129285

I guess I could disable the ability to idle in playback mode at night once image deletion is required. The kind of nasty hack where you keep your fingers crossed once it's enabled.
You could try replacing the jpegs with 0 byte files, e.g f=io.open(filename,"wb") ; f:close()
I don't know what the canon OS would think of that, but it should be pretty quick to try. If zero byte fails I guess you could write a tiny jpeg instead (take a 640x480 low quality shot of a blank scene, hard code it in the script as a string...)

Another option would be to only do the deleting in playback mode. AFAIK switching to and from record is fine if the deleting is done in playback.

Also, as mentioned at the end of the thread, the error only seems to happen with full res jpegs :blink: that might be an avenue for investigation, or at least be a workaround for timelapses where the final product doesn't need full res.
Thank for that.  Some really useful work-around ideas there! However all three require some level of user setup stuff that the script can't really control in isolation.

The zero length file trick (if it works) will require manual SD card cleanup when the script is done to get rid of all the bogus files.  And the really small valid jpg option means the user has to copy two files onto his camera correctly (script + jpg) - unless the jpg data is small enough to store in an initialized array and thus travel with the script.  And disabling large file formats seems like too much of a limited option (assuming it works at all for every camera).

So I'm leaning towards the "only delete in playback mode" option.  Simple to code and probably the most reliable.  However, it will require the user to set the lens retract delay in the Canon menu to something other than zero to minimize wear & tear on the lens assembly.
« Last Edit: 13 / July / 2016, 14:08:59 by waterwingz »
Ported :   A1200    SD940   G10    Powershot N    G16

 

Related Topics


SimplePortal 2.3.6 © 2008-2014, SimplePortal