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

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

  • 651 Replies
  • 228523 Views
Re: Ultimate Intervalometer - a script for shooting over a long duration - v2.0
« Reply #280 on: 11 / February / 2015, 19:18:24 »
Advertisements
When I run the script with default setting and display blanking mode set to none, it works fine (taking pictures every minute and not turning off the screen). Any suggestions on what parameters I should I try? and if night or day for display blanking mode matters? Thanks

Re: Ultimate Intervalometer - a script for shooting over a long duration - v2.0
« Reply #281 on: 11 / February / 2015, 19:29:55 »
When I run the script with default setting and display blanking mode set to none, it works fine (taking pictures every minute and not turning off the screen).
Okay - so the script runs fine on your camera (D30) except for when it tries to blank the display.  That's a good start.  Night or day blanking mode should do the same thing - which is used depends only on what time it is.

What happens if you try any of the other Display Off mode setting ?

Just to be sure it is not something easy,  what version of CHDK are you using?  Please post the full file name that you loaded on the camera  ( e.g d30-100a-1.3.0-3993-full_BETA.zip )  or go to the CHDK Miscellaneous menu -> Show Build Info and post the CHDK Ver : and Revision : information you see there.

(Once we get through this, if we can't solve it then we will try looking at the script log and CHDK Rom crash log)
« Last Edit: 11 / February / 2015, 19:34:26 by waterwingz »
Ported :   A1200    SD940   G10    Powershot N    G16

Re: Ultimate Intervalometer - a script for shooting over a long duration - v2.0
« Reply #282 on: 13 / February / 2015, 15:50:59 »
When I try any other setting, the camera turns off its main screen and stops taking pictures (so I am assuming it just shuts down). So when I turn it back on the script stopped and isnt taking pictures.

My build info is as follows (I used STICK to download the CHDK also):
CHDK: 1.3.0
Revision: 3973
FW version: 100a
Compiler: GCC 4.4.3

Also on a side question, whenever I take pictures and then delete them, it doesnt free up space on the SD card (as if the photos were still on the camera). Is there a better way to delete images to re-free up space?

Thanks again for all your help.

Re: Ultimate Intervalometer - a script for shooting over a long duration - v2.0
« Reply #283 on: 13 / February / 2015, 18:26:30 »
When I try any other setting, the camera turns off its main screen and stops taking pictures (so I am assuming it just shuts down). So when I turn it back on the script stopped and isnt taking pictures.
Okay - that's the first step then.

Can you go to the Logging script parameter (in the Script menu) and set it to SDCard ? The rerun the tests a couple of times with different Display blanking mode settings - including None.  That should create a nice ultimate.log file in the root directory of the SD card.  Please post that file too.

Also,  please go to the Miscellaneous -> Debug menu and request a ROMLOG.  Find that file in the root of the SD card and post it as well?

Quote
My build info is as follows (I used STICK to download the CHDK also):
CHDK: 1.3.0
Revision: 3973
FW version: 100a
Compiler: GCC 4.4.3
Thanks.

Quote
Also on a side question, whenever I take pictures and then delete them, it doesn't free up space on the SD card (as if the photos were still on the camera). Is there a better way to delete images to re-free up space?
Depending on your computer, it may be creating a TRASH or Recycle Bin folder on your SD card and is then simply moving the pictures to that folder rather than truly deleting them and freeing up the SD card space.  With the SD card plugged into the computer,  try emptying your Trash / Recycle bin?
Ported :   A1200    SD940   G10    Powershot N    G16


Re: Ultimate Intervalometer - a script for shooting over a long duration - v2.0
« Reply #284 on: 25 / February / 2015, 17:49:12 »
Sorry this took so long! I got it working with the BkLite setting but it uses too much battery. The rest of the settings do not work. I wil attach both logs you requested. I also have a detailed set of observations taken while testing all of the different settings. All were done with default settings, except for the time range so that the camera would take pictures. Also, each test was done for about 15 minutes.

Hopefully this can help! Also the various tests, each on a different mode, starts at the beginning of the long and ends at 2/18 at time 12:31:22.

Really appreciate all the help.

Sorry this took so long! I got it working with the BkLite setting but it uses too much battery. The rest of the settings do not work.
The log files look normal.   Let's try a simple test to see if this might be something with the D30 port ?  Here's a simple script that uses the set_lcd_display( )  command to turn the display off for two seconds and then back on.

Code: [Select]
--[[
@title LCD Off
--]]
print("turning off display")
sleep(1000)
set_lcd_display(0)
sleep(2000)
print("display turned back on")
set_lcd_display(1)
sleep(1000)
Does it work?
Ported :   A1200    SD940   G10    Powershot N    G16

Hi!
It did work! So I think what I have to come find out is that I can blank the display using the LCD setting. Since this conservation, I have also switched to the CHDK 1.4, and the camer model to a powershot D20.

I am now trying to experiment with the time setting, such at start at 17:00 and then end at 7:10. The reset hour is at 2 by the way. The test started and the odd parts are: it took its first shot an hour late (18:00), it took the last shot at 22:00 which is before 6:00, and the LCD didnt turn back off sometime around 18:00. does it stop taking picture because its a new day and then the reboot causes the script to restart? here is the log:

Sat Apr 11 08:23:36 2015; === Started: 08:23 ===
Sat Apr 11 08:23:36 2015; CHDK 1.4.0 d20 100b Mar 18 2015
Sat Apr 11 08:23:36 2015; CHDK version 140 okay
Sat Apr 11 08:23:39 2015; starting a new day
Sat Apr 11 08:23:39 2015; start time : 17:00 stop time : 07:10
Sat Apr 11 08:23:39 2015; switching to night mode
Sat Apr 11 08:24:54 2015; set LCD off
Sat Apr 11 10:00:00 2015; No Shot; tv:0.6; t72; a387; s795; b-432; V3963; T27
Sat Apr 11 12:00:00 2015; No Shot; tv:0.6; t72; a387; s795; b-432; V3991; T27
Sat Apr 11 14:00:00 2015; No Shot; tv:0.6; t72; a387; s795; b-432; V4004; T28
Sat Apr 11 16:00:00 2015; No Shot; tv:0.6; t72; a387; s795; b-432; V3995; T29
Sat Apr 11 17:00:09 2015; set LCD on
Sat Apr 11 17:00:09 2015; switching to day mode
Sat Apr 11 17:00:24 2015; set LCD off
Sat Apr 11 18:00:03 2015; Shot; 1; tv:0.6; t72; a387; s795; b-432; V3963; T27
Sat Apr 11 20:00:05 2015; Shot; 2; tv:0.6; t72; a387; s795; b-432; V3958; T31
Sat Apr 11 22:00:07 2015; Shot; 3; tv:0.6; t72; a387; s795; b-432; V3944; T34
Sun Apr 12 00:00:00 2015; starting a new day
Sun Apr 12 00:00:00 2015; start time : 17:00 stop time : 07:10
Sun Apr 12 01:50:01 2015; set LCD on
Sun Apr 12 01:50:01 2015; switching to playback mode
Sun Apr 12 01:50:01 2015; === Scheduled reboot === 

What I am looking for is just for the camera to turn off the LCD between shots at a 2 hour interval, from about 17:00 to 7 the next day for as many days as possible, while keeping the LCD off when not taking pictures in that interval. I am also using an external battery to elongate the battery life.

Thanks so much for your help, sorry to be a bother.


I am now trying to experiment with the time setting, such at start at 17:00 and then end at 7:10.
The script was written on the assumption that most people want to start shooting at either dawn, when the sun comes up, or at fixed time every morning.   Likewise, it assumes that most people want to stop shooting at dusk, or when it gets dark outside, or at a fixed time every evening.

You seem to want to reverse that (shoot at night, sleep during the day) and the script cannot handle that ( i.e. start time > stop time).  Sorry.   It's possible to fix that in the code of course if it's really important to you.


Quote
Thanks so much for your help, sorry to be a bother.
No bother - feedback and questions are always welcome.

Edit : script handles start time > end time correctly.  See later posts on this topic in this thread.

« Last Edit: 23 / April / 2015, 21:07:48 by waterwingz »
Ported :   A1200    SD940   G10    Powershot N    G16


Hi,

I'm completely new to CHDK. In your notes you say this script uses features of the 1.2.0 version of the CHDK. I assume that if I'm running 1.3 it should contain all of the features of 1.2?
The CHDK I've downloaded is 'ixus870_sd880-101a-1.3.0-4152-full'
The "1.3.0" part of the nomenclature I assume is the CHDK version?
If it does not run on 1.3, where can I download 1.2 for my sd880? (I've googled this to no avail).

The reason I want this specific script is that it seems to be ideal for a HAB launch. I've already launched a couple of balloons with GoPros, now I want pictures. The power saving features of this script are key.

Thanks,
Andres

I'm completely new to CHDK. In your notes you say this script uses features of the 1.2.0 version of the CHDK. I assume that if I'm running 1.3 it should contain all of the features of 1.2?
Correct.

Quote
The CHDK I've downloaded is 'ixus870_sd880-101a-1.3.0-4152-full' The "1.3.0" part of the nomenclature I assume is the CHDK version?
Correct.

Quote
If it does not run on 1.3, where can I download 1.2 for my sd880? (I've googled this to no avail).
There are archived builds of the 1.0, 1.1, and 1.2 trees available but you don't need them.

Quote
The reason I want this specific script is that it seems to be ideal for a HAB launch. I've already launched a couple of balloons with GoPros, now I want pictures. The power saving features of this script are key.
Let us know how it goes ?
Ported :   A1200    SD940   G10    Powershot N    G16

 

Related Topics


SimplePortal 2.3.6 © 2008-2014, SimplePortal