KAP & UAV Exposure Control Intervalometer Script

flo_vienna

Hi

I posted earlier about getting the script to work and I managed to get it to work with the SimpleShutter cable from http://www.mobilexcopter.com. I managed to trigger the camera using my pc version of mission planner and my RC (chan7).

I tried to use 3DR Tower software to use the structure scanner to fly over an area and automatically take pictures. As S90 is not available in the Tower software I chose S100 but it does not seem to take any pictures. CHDK is running and the KAP_UAV Script is running as well.

Does anybody have experience with 3DR Tower software on android , CHDK , and the KAP_UAV scripts ?
Do I need the script ?

:'(

waterwingz

flo_vienna
I posted earlier about getting the script to work and I managed to get it to work with the SimpleShutter cable from http://www.mobilexcopter.com. I managed to trigger the camera using my pc version of mission planner and my RC (chan7).

I tried to use 3DR Tower software to use the structure scanner to fly over an area and automatically take pictures. As S90 is not available in the Tower software I chose S100 but it does not seem to take any pictures. CHDK is running and the KAP_UAV Script is running as well.

Please copy the KAP.LOG file from the root folder of your SD card and attach it to a post here.

Do I need the script ?

It's possible to trigger shots with just the CHDK USB Remote settings. But it all depends on how you have your flight controller software configured.

flo_vienna

Hi

I actually wanna trigger the camera via the 3DR Tower Software on my android tablet but as there is no S90 to choose, I chose S100 in there. I am not even 100% sure this is the right place but I am a bit unsure how to debug that.

Here is my KAP.log for today:

2016Jul30 15:13:59 KAP 3.8 started - press MENU to exit
2016Jul30 15:13:59 CHDK 1.4.1-4599 s90 100c Apr 18 2016
2016Jul30 15:13:59 Mode😛LAY,Continuous_AF:1,Servo_AF:2 Drive:0
2016Jul30 15:13:59 Tv:1/1000 max:1/2000 min:10 ecomp:0.0
2016Jul30 15:13:59 Av:5.0 minAv:2.8 maxAv:8.0
2016Jul30 15:13:59 ISOmin:100 ISO1:400 ISO2:800 M:0
2016Jul30 15:13:59 Focus:AFL Video:0 USB:2:1 Tmo:0
2016Jul30 15:13:59 AvM:1 int:3 Shts:0 Dly:5 B/L:0
2016Jul30 15:14:00 entering start delay of 5 seconds
2016Jul30 15:14:08 waiting on USB signal
2016Jul30 16:04:39 Menu key exit request
2016Jul30 16:04:39 Logger : log file updated.

Br and thanks 😀

waterwingz

flo_vienna
I actually wanna trigger the camera via the 3DR Tower Software on my android tablet but as there is no S90 to choose, I chose S100 in there.

I took a very quick look at the 3DR Tower git repository but it was not clear what the camera setting is supposed to do. Certainly the code has no way to know if you have an S90 or S100 attached.

Here is my KAP.log for today:

From your log file, it does not look like your system is toggling the USB line to the camera at all. So this does not appear to have anything to do with CHDK or the kap_uav.lua script.

I am not even 100% sure this is the right place but I am a bit unsure how to debug that.

I notice you've posted this issue over on the ardupilot forum (and possibly elsewhere?). That's probably a better place to get an answer.

flo_vienna

Hi

I am still debugging my S90 / Tower app issue. According to the maker of my shutter cable, the pulse sent to the chdk script is hat the pixhawk outputs (like it mirrors it).
How long should a pulse be at least for the OneShot Mode ?

What does this log tell me ? (It shot 1 picture at the beginning but that's all)

2016Aug20 20:32:55 KAP 3.8 started - press MENU to exit
2016Aug20 20:32:55 CHDK 1.4.1-4672 s90 100c Aug 11 2016
2016Aug20 20:32:55 Mode😛LAY,Continuous_AF:1,Servo_AF:2 Drive:0
2016Aug20 20:32:55 Tv:1/1000 max:1/2000 min:10 ecomp:0.0
2016Aug20 20:32:55 Av:4.5 minAv:3.2 maxAv:8.0
2016Aug20 20:32:55 ISOmin:100 ISO1:400 ISO2:800 M:0
2016Aug20 20:32:55 Focus:AFL Video:0 USB:2:1 Tmo:0
2016Aug20 20:32:55 AvM:1 int:2 Shts:0 Dly:5 B/L:0
2016Aug20 20:32:56 entering start delay of 5 seconds
2016Aug20 20:33:04 waiting on USB signal
2016Aug20 20:37:04 USB start signal received
2016Aug20 20:37:08 Mode switched to P
2016Aug20 20:37:11 Logger : log file updated.
2016Aug20 20:37:19 timeout after shoot full
2016Aug20 20:37:13.150 1) IMG_1714.JPG
2016Aug20 20:37:19 meter : Tv:1.0 Av:2.0 Sv:1600 -741:-741
2016Aug20 20:37:19 actual: Tv:10 Av:3.2 Sv:800 Temp:26
2016Aug20 20:37:19 AvMin:3.2 NDF:NDout foc:infinity
2016Aug20 20:38:11 Logger : log file updated.
2016Aug20 20:39:11 Logger : log file updated.
2016Aug20 20:40:11 Logger : log file updated.
2016Aug20 20:41:11 Logger : log file updated.
2016Aug20 20:42:11 Logger : log file updated.
2016Aug20 20:43:11 Logger : log file updated.
2016Aug20 20:43:20 MENU key pressed.
2016Aug20 20:43:20 script halt requested
2016Aug20 20:43:20 Logger : log file updated.

waterwingz

flo_vienna
Acording to the maker of my shutter cable, the pulse sent to the chdk script is hat the pixhawk outputs (like it mirrors it).

This one ? Simple Canon shutter - Pixhawk version

How long should a pulse be at least for the OneShot Mode ?

It should catch anything longer that a couple of milliseconds.

What does this log tell me ? (It shot 1 picture at the beginning but that's all)

Basically, it tells you what you just said - i.e. it shot 1 picture at the beginning but that's all.

However, the "shoot full" timeout message is interesting. It looks like there was almost no light - where you shooting in a dark room?

flo_vienna

Hi

Yeah I am using the cable you mentioned.
Right now the pulse is around 1/10 sec long and the cam should shoot as fast as possible. You are indeed correct, the light was not the best here, yet it was not dark but now I know what this error message means.

I am still wondering if it's some issue of the Tower App or the pulse sent or the App doesn't correctly send the commands to trigger but the people there are a bit unresponsive so maybe I need to dive into the app code ...

waterwingz

flo_vienna
I am still wondering if it's some issue of the Tower App or the pulse sent or the App doesn't correctly send the commands to trigger but the people there are a bit unresponsive so maybe I need to dive into the app code ...

At this point, I don't think it the kap_uav.lua script, or how you have set it up, that is causing the problem. So I've attached a simple script that measure the width of each USB pulse and prints the result to the camera LCD. It also reports the time between pulses. You might want to use it to test if pulses are being generated (and how long they are) while you work on your flight controller setup. Should be accurate down to about 1 mSec resolution.

usbtest.lua

722b

flo_vienna

Thanks 😀

Going to do some tests 😀

waterwingz

flo_vienna
Going to do some tests 😀

You can ensure the USB test script is working by using a standard USB cable between your camera & PC. Just plug & unplug the cable a few times while the script is running and your should see timing values scroll up the screen.

nuno

With Canon IXUS 160

2016Aug28 18:46:20 KAP 3.7 started - press MENU to exit
2016Aug28 18:46:20 CHDK 1.4.1-4634 ixus160_elph160 100a May 27 2016
2016Aug28 18:46:20 Mode😛LAY,Continuous_AF:0,Servo_AF:0 Drive:0
2016Aug28 18:46:20 Tv:1/1000 max:1/2000 min:10 ecomp:0.0
2016Aug28 18:46:20 Av:4.0 minAv:2.8 maxAv:8.0
2016Aug28 18:46:20 ISOmin:100 ISO1:400 ISO2:800 M:0
2016Aug28 18:46:20 Focus:AFL Video:0 USB:2:1 Tmo:0
2016Aug28 18:46:20 AvM:2 int:15 Shts:0 Dly:0 B/L:0
2016Aug28 18:46:21 waiting on USB signal
2016Aug28 18:49:14 USB start signal received
2016Aug28 18:49:17 Mode switched to P
2016Aug28 18:49:20 Logger : log file updated.
2016Aug28 18:49:27 timeout after shoot full
2016Aug28 18:49:21.490 1) IMG_0384.JPG
2016Aug28 18:49:27 meter : Tv:1/320 Av:3.2 Sv:100 750:750
2016Aug28 18:49:27 actual: Tv:1/1000 Av:- Sv:250 Temp:27
2016Aug28 18:49:27 AvMin:3.2 NDF:NDout foc:1.2m
2016Aug28 18:49:28.040 2) IMG_0385.JPG
2016Aug28 18:49:32 meter : Tv:1/1000 Av:3.2 Sv:250 750:750
2016Aug28 18:49:32 actual: Tv:1/1000 Av:- Sv:250 Temp:27
2016Aug28 18:49:32 AvMin:3.2 NDF:NDout foc:infinity

this set wrong?

waterwingz

nuno
this set wrong?

That looks like a normal log file. Are you having a problem with using the script? Can you tell me what is not working? And tell me what equipment you are using?

nuno

IÂ´m using canon ixus 160

The picture (Attachment) is not in focus.
The problem is the set uav.kap or the UAV vibration?

waterwingz

nuno
The picture (Attachment) is not in focus. The problem is the set uav.kap or the UAV vibration?

Blurred UAV pictures can be caused by several things. Determining the actual cause can take some time and patience.

In this case, the shutter speed at 1/1000 is quite fast so this is likely not a problem with motion blur.

The camera is set to focus at infinity using CHDK , but some Powershots do not actually focus well this way. You can test this by using the script to take pictures of distant objects with camera held steady (tripod?) on the ground. If distant objects are crisply focussed, then the script & camera are working properly with focus at infinity.

Try disabling the "Focus @ Infinity" option in the script parameters menu. Do the photos look better?

If the camera focuses correctly at infinity, that leave UAV vibration as the problem. How is your camera mounted to the UAV?

The picture might be in focus but vibration makes it appeard blurred.

lanzo

waterwingz

bchristal
However, I have a customer with a different S110. His flashes the LED for close to 1 second. That causes extra CAM events in the Pixhawk log. A resistor change may help hold the hi / lo state, but I'd like to figure out why the LED stays on so long on his S110. It's not the shutter speed. That will make the LED stay on if you make it long.

If all the hardware is the same then i guess that leaves two options.

The most likely option would be some difference in either the Canon menu settings or the CHDK settings. I'm not too sure what that might be but having RAW Enabled (either Canon RAW or CHDK RAW/DNG) would certainly do it.

The other option might be a slow SD card, or maybe an almost full one, or one with a really large log file. The script writes to the log file in between the points where it turns the LED on and off.

Any idea where to start?

I can add something to log the actual on & off times for the LED if you can get him to run a test version and report back.

Hi waterwingz and friends, I'm very happy using the kap_uav_3-7a.lua waterwingz kindly modified some month ago.
I'm going to install an emlid RTK system, how about using the Canon S110 LED to log picture time, is it possible and how to do it? I bought a cable for Sony hotshoe, easy to remove the hotshoe adapter and the RTK has a logging software.
Thank you

waterwingz

lanzo
I'm going to install an emlid RTK system, how about using the Canon S110 LED to log picture time, is it possible and how to do it? I bought a cable for Sony hotshoe, easy to remove the hotshoe adapter and the RTK has a logging software.

I'm not sure that I fully understand your request. The existing script already has the ability to "blink" any of the camera's LEDs at the exact moment the exposure starts (or at least as close as technically possible). Do you need something else or different?

lanzo

waterwingz

lanzo
I'm going to install an emlid RTK system, how about using the Canon S110 LED to log picture time, is it possible and how to do it? I bought a cable for Sony hotshoe, easy to remove the hotshoe adapter and the RTK has a logging software.

I'm not sure that I fully understand your request. The existing script already has the ability to "blink" any of the camera's LEDs at the exact moment the exposure starts (or at least as close as technically possible). Do you need something else or different?

What is the parameter on the script and how do you catch the "blink" of the led on the S110? Thank you
I found this:
@param h Shot Sync LED
@default h 0
@values h Off 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15

waterwingz

lanzo
What is the parameter on the script
<snip>
I found this:
@param h Shot Sync LED
@default h 0
@values h Off 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15

Every Canon P&S camera is a bit different from the others. But a CHDK script can turn each of the camera's LED's on & off. It does this using the LED number - which is simply a value assigned during CHDK porting to each LED by the developer. There is no standardization about what number turns on which LED as each camera is different. So you have to either read the developer's notes (usually in the camera's lib.c file), or pick the number by trial & error, or use a small script that scrolls through all values slowly allowing you to figure out what number corresponds to each LED.

and how do you catch the "blink" of the led on the S110? Thank you

I'm not sure that you understand what is intended here? The script will cause your camera (your S110) to turn an LED on when the camera's shutter opens, and off again shortly after it closes. It's up to your flight controller and its hardware to detect that "blink" and do something with it.

lanzo

Yes mate, I am searching for someone who already did the hardware to detect the "blink"

waterwingz

lanzo
Yes mate, I am searching for someone who already did the hardware to detect the "blink"

I worked with bchristal on the original implementation. You can try sending him a PM and I'll send him an email directly to ask.

« Previous Page Next Page »