KAP & UAV Exposure Control Intervalometer Script

waterwingz

afishindouban
I will test for you.

Bobo67
Nice, if you want i'm here for testing the "one shot usb" function with my two Ixus.

Here you go. Beta release of version 2.5 of the kap_uav.lua script is here > kap_uav_2.5_beta.zip

There are new options for the USB Shot Control parameter :

Off : USB power ignored
Interval : intervalometer runs normally when USB power is applied, off when no power
Single : script takes one shot every time the USB power is applied
PWM : script detects width of power pulse and calls a subroutine to a match

Notes :

as written the script assumes Gentles CHDK2 USB cable PWM timing. Edit script for different devices.
for Single and PWM modes, pulses are buffered ( up to 8 ) so if the camera is busy the next pulse is not missed.
PWM mode currently only prints a message (& shoots for shorted pulse). Edit script for different actions.

Update : this has been tested with a pulse width modulated signal from an Arudino microcontroller is I'm pretty sure it works correctly.

Bobo67

Single usb shot work fine, thanks!

afishindouban

just return today, I will test and let you know.

ausdroid

Hi Waterwinz,

Thank you sooo much for this script.

I have an IXUS 132 and do not appear to be able to lock the camera into infinite focus. I have tried AFL and @Shot & MF but it will continue to attempt to focus with the small blue square appearing on the screen. The log shows that it is not focused at infinity, but it does not give me any errors.

Attached Log File.

Thanks.

KAP.log

3.89KB

waterwingz

ausdroid
I have an IXUS 132 and do not appear to be able to lock the camera into infinite focus.

What version of CHDK are you using ? (the full filename of the CHDK zip file you installed) And what version of the script?

I have tried AFL and @Shot & MF but it will continue to attempt to focus with the small blue square appearing on the screen.

Did you disable the Canon ServoAF and ContinuousAF modes? Those modes will override the CHDK Subject Distance Override settings.

The log shows that it is not focused at infinity, but it does not give me any errors.

Looking at the log, Canon auto-focus is probably focusing your pictures probably correctly though CHDK is unable to lock the focus (see previous comment).

nafraf

waterwingz

ausdroid
I have an IXUS 132 and do not appear to be able to lock the camera into infinite focus.

What version of CHDK are you using ? (the full filename of the CHDK zip file you installed) And what version of the script?

In log file:

2014Jun21 16:53:43 KAP 2.4 started - press MENU to exit
2014Jun21 16:53:43 CHDK 1.3.0-3387 ixus132_elph115 100b Mar 17 2014

waterwingz

nafraf

waterwingz

ausdroid
I have an IXUS 132 and do not appear to be able to lock the camera into infinite focus.

What version of CHDK are you using ? (the full filename of the CHDK zip file you installed) And what version of the script?

In log file:
[code]2014Jun21 16:53:43 KAP 2.4 started - press MENU to exit
2014Jun21 16:53:43 CHDK 1.3.0-3387 ixus132_elph115 100b Mar 17 2014
[/code]

thanks 😉

Meanwhile, I'll add a log of ServoAF and ContinuousAF states at the next script update, just for this reason.

gotcha640

Hi there

This is my first post related to KAP, and I really appreciate the script. I took a few pics with the stock intervalometer, but all were blurry.

I'd like to ask for camera and shot specific analysis help, as far as setting the mins and maxes and such, and I'm not sure if it's better to ask here or start a new thread in the general newb forum.

I got three decently clear shots out of about 50 this morning, some cloud cover.

For now, I'm just gonna throw up the first few lines of the log:

2014May23 10:51:00 CHDK 1.2.0-3439 a495 100f May 12 2014
2014May23 10:51:00 Tv:1/1000 max:1/2000 min:10 ecomp:0.0
2014May23 10:51:00 Av:4.0 minAv:2.8 maxAv:8.0
2014May23 10:51:00 ISOmin:100 ISO1:400 ISO2:800
2014May23 10:51:00 MF mode:0 Video:0 USB:false
2014May23 10:51:00 AvM:2 int:30 Shts:0 Dly:60 B/L:0
2014May23 10:51:00 entering start delay of 60 seconds

And a few more lines from the log:

Blurry shot:

2014May23 10:53:38 4) IMG_1535.JPG
2014May23 10:53:39 meter Tv:1/800 Av:4.5
2014May23 10:53:39 actual: Tv:1/1000 Av:- Sv:320
2014May23 10:53:39 AvMin:3.2 NDF:NDin foc:0.9m

I think the "foc:0.9m" is my problem there.

Clearer shot:

2014May23 10:54:38 6) IMG_1537.JPG IMG
2014May23 10:54:39 meter Tv:1/1000 Av:4.5
2014May23 10:54:39 actual: Tv:1/1000 Av:- Sv:200
2014May23 10:54:39 AvMin:3.2 NDF:NDin foc:infinity

"foc:infinity" is the only parameter that I understand well enough to see that it's significantly different.

I intend to get out again this afternoon or tomorrow morning, and I'd like to know what I should try changing.

My preferred method of messing with this kind of thing is to save my own edits as revs, for specific conditions. I'm thinking I could set "foc:infinity" in the script, and possibly Tv min:1/1000.

Is there anything else I should be looking at, or should those two get me better pics?

Happy to post the pics, but I didnt see many others doing that.

Thanks for any help.

waterwingz

gotcha640
I'd like to ask for camera and shot specific analysis help, as far as setting the mins and maxes and such, and I'm not sure if it's better to ask here or start a new thread in the general newb forum.

Here works fine for me - and I suspect I'll be answering most of your questions. However, I'm travelling for the next couple of days on a photography trip somewhat at "the ends of the earth" so network connectivity might make my response time a little slow.

2014May23 10:51:00 Tv:1/1000 max:1/2000 min:10 ecomp:0.0

You probably want to crank Tv max up. Way up.

2014May23 10:53:39 AvMin:3.2 NDF:NDin foc:0.9m
I think the "foc:0.9m" is my problem there.

That's one problem. With MF Mode set to zero, the script will not attempt to lock focus at infinity for you and is doing its best to autofocus instead.

Also, the ND filter is engaging - probably because its a bright day and you have set the maximum shutter speed quite slow.

My preferred method of messing with this kind of thing is to save my own edits as revs, for specific conditions. I'm thinking I could set "foc:infinity" in the script, and possibly Tv min:1/1000.

You do all that with the setup parameters in the script menu. You can even save as many as 10 different combinations of parameters for later use. If you are not familiar with that, scroll down in the CHDK script menu - the kap_uav.lua script has a lot of things you can adjust to suit your application.

Happy to post the pics, but I didnt see many others doing that.

We can cross that bridge when we come to it.

gotcha640

Regarding the shutter speed, the a495 specs show max shutter speed 1/2000. Will it make any difference to set it higher?

Regarding the focal length and MF mode, what's the recommended setting?

Last, the three times I've been out, a set of two AA batteries has lasted about 30 minutes. Is this expected, because the script is using a lot of processing power? Or am I doing something wrong? I've used fairly new Eneloops, and brand new disposable Duracells.

lapser

gotcha640
Regarding the shutter speed, the a495 specs show max shutter speed 1/2000. Will it make any difference to set it higher?

It might, but it won't be a lot of difference. On the SX260, the shutter speed maxed out at about 1/3500. Anything faster didn't change the actual exposure of the picture.

Regarding the focal length and MF mode, what's the recommended setting?

The ideal is to set it at the hyperfocal distance, which is as close as the camera will focus and still have infinity be in focus. That way pictures of ground objects will be sharper at low altitude.

If you're setting it manually before starting the script, you could crank the focus up to infinity and then back off one notch. A script can find the hyperfocal distance and set it to that, if it has that feature.

Last, the three times I've been out, a set of two AA batteries has lasted about 30 minutes. Is this expected, because the script is using a lot of processing power? Or am I doing something wrong? I've used fairly new Eneloops, and brand new disposable Duracells.

I would try AA lithium batteries. They're advertised to last 7 times longer, so they should last a few minutes longer, at least 😀 They are more expensive, though.

There may be camera settings that are using a lot of power. Image stabilization might be using a lot of juice. You could try shutting it off and see if the pictures are still sharp. GPS also uses a lot of power, if the camera has it. Shutting the display off saves about 10 or 15% power use.

waterwingz

lapser

gotcha640
Regarding the shutter speed, the a495 specs show max shutter speed 1/2000. Will it make any difference to set it higher?

It might, but it won't be a lot of difference. On the SX260, the shutter speed maxed out at about 1/3500. Anything faster didn't change the actual exposure of the picture.

Try it and see. Just be sure to compare the actaul images rather than reported settings. Some cameras have been reported to go up over 1/5000. Unlike ISO and f-stops, this is one setting where CHDK can usually substantially extend the available range.

Regarding the focal length and MF mode, what's the recommended setting?

The ideal is to set it at the hyperfocal distance, which is as close as the camera will focus and still have infinity be in focus. That way pictures of ground objects will be sharper at low altitude.

If you're setting it manually before starting the script, you could crank the focus up to infinity and then back off one notch. A script can find the hyperfocal distance and set it to that, if it has that feature.

In practice, using hyperfocal distance rather than infinity does not produce any measurable difference in the resulting images with Canon P&S cameras. The lens depth of field is so high that it's not worth the effort to even try. So for the kap_uav.lua script, you can just have the script set the focus at infinity and be done with worrying about that.

Last, the three times I've been out, a set of two AA batteries has lasted about 30 minutes. Is this expected, because the script is using a lot of processing power? Or am I doing something wrong? I've used fairly new Eneloops, and brand new disposable Duracells.

I would try AA lithium batteries. They're advertised to last 7 times longer, so they should last a few minutes longer, at least 😀 They are more expensive, though.

There may be camera settings that are using a lot of power. Image stabilization might be using a lot of juice. You could try shutting it off and see if the pictures are still sharp. GPS also uses a lot of power, if the camera has it. Shutting the display off saves about 10 or 15% power use.

Camera settings can change battery life quite a bit. But what you need to remember is that normally these cameras power off after 30 seconds if there is no activity, resulting on a perceived long battery life. With an intervalometer script, the camera processor never shuts down and draws power continuously. It's not a question of the script using a lot of processor power - it's just a question of not shutting down after a shot is taken. The display off settings in the script parameters can help as lapser noted.

afishindouban

waterwingz

afishindouban
I will test for you.

Thanks. I now have all the code changes done to add the two new USB modes - single shot per USB pulse and Gentles pwm detection mode - in addition to the old mode of intervalometer while USB power is present. Not quite sure how to tell the lens to retract in single shot per USB pulse mode though.

If I can find another hour today and my Arduino test rig will fire up and send precision pulses, I'll do some testing prior to sending you a new version.

Hi waterwingz, gentle PWM drive mode test ok. So good. Thank you so much. Now it's works perfect.

waterwingz

Version 3.0 now posted to the CHDK KAP_UAV wiki page and download site.

Support added for single shot per usb pulse mode and gentWIRE-USB2 pwm type devices. I also snuck in a restore of the console timeout interval (the script sets it really long on entry) and logging of the camera mode and focus modes when the script starts.

Thanks to afishindouban and Bobo67 for testing the latest changes.

bchristal

Need quicker shot interval

Hi all,

I'm using a Elph 300 in a fixed wing for aerial mapping. I can't slow the plane down any more. The fastest I can get pictures are about 3.5 seconds apart. That just doesn't get enough overlap to build a map. What are the best settings to achieve smallest shot interval, or is that just a limitation on the camera? Also, is there a known canon point and shoot that takes that fastest pictures?

Thanks!

Brian

waterwingz

bchristal
I'm using a Elph 300 in a fixed wing for aerial mapping. I can't slow the plane down any more. The fastest I can get pictures are about 3.5 seconds apart. That just doesn't get enough overlap to build a map.

That seems a bit slow but consistent with my results.Do you have "RAW/DNG" enabled? That will slow things down.

What are the best settings to achieve smallest shot interval, or is that just a limitation on the camera?

That's a limit when you cycle through a complete "shooting" cycle. A fast Class 10 SD card can help a bit. After that you need a different script. Try these on the ground and see how fast you can get :
http://chdk.wikia.com/wiki/Fast_Shooter_Intervalometer
http://chdk.wikia.com/wiki/UBASIC/Scripts:_A_fast_%22intervalometer%22
They can probably be tweaked a bit for UAV work if you find they work for you.

Also, is there a known canon point and shoot that takes that fastest pictures?

I don't believe anyone has done a comparison across the brand.

srsa_4c

bchristal
What are the best settings to achieve smallest shot interval, or is that just a limitation on the camera?

waterwingz
That seems a bit slow but consistent with my results.Do you have "RAW/DNG" enabled? That will slow things down.

+ 'review' should be off in the Canon menu + AFL or MF to eliminate refocusing

waterwingz

srsa_4c
+ 'review' should be off in the Canon menu + AFL or MF to eliminate refocusing

Good point on the "review".

FWIW, the script's "focus @ infinity" setting let's you pick AFL or MF to lock focus and warns you if it doesn't work.

bchristal

Thanks guys!!!

Review was set at 2 seconds. Camera now snapping pictures at < 2 seconds. Can't wait to go fly. 😀

Brian

M141

Hi,
I had to register, just to say big thanks to Waterwingz and everybody who have been developing this script! So thank you and awesome work! 😀

At the moment i'm using 2.4 version of script with Arducopter quadrocopter and diy brushless gimbal. Camera is ELPH300(IXUS 220HS) with 1.2.0-3418 CHDK. Not yet using usb-remote, but soon will. So far i've been done aerial mapping or just shooting generic photos.

I'm still playing with gimbal and script settings and i have few questions:

1. What metering mode we should use in genarally? Does is make any difference for exposure or will chdk/KAP&UAV overdrive this setting anyway?

2. Not sure about what is possible with usb remote. Is it possible to do following at one flight:
a. turn camera and script running on/off?
b. Zoom in/out?
c. Change camera mode between video and script mode? Recording video on/off?
I can use Arduino to generate pulses, but not sure what are actually the limits and is possible.

Also i might found two little bugs or things to improve?
1.
@param e Exposure Comp (stops)
@default e 6
@values e -2.0 -1.66 -1.33 -1.0 -0.66 0.33 0.0 0.33 0.66 1.00 1.33 1.66 2.00 <--missing "-" for negative 0.33??

2. When using Video Interleave and Video Duration the camera stops responsing after hitting Interrupt button, when camera is taking video. Have to take battery out to reset. Interrupt works if it is done during photo shoot.

ps. sorry my english 😉
Regards Jani

« Previous Page Next Page »