KAP & UAV Exposure Control Intervalometer Script

srsa_4c

4451

Re: KAP & UAV Exposure Control Intervalometer Script

« Reply #730 on: 14 / February / 2016, 09:11:45 »

Advertisements

Quote from: Toshopo on 14 / February / 2016, 04:54:49

the camera message is
a camera error was detected
will shut down
restart your camera.

I have a suspicion. Your cam might be broken. Try using it without CHDK for more than a minute.

To retrieve the camera's error list, use the following short Lua script (copy the 2 lines to a plain text file, name it errlist.lua, copy it to the card and execute it).

Code: [Select]

call_event_proc("UI.Create")
call_event_proc("UIFS_WriteFirmInfoToFile",0)

This will produce a text file in the root of the card.

You need to enable "Lua native calls" in the Miscellaneous menu before running the script.

Logged

waterwingz

12139

Re: KAP & UAV Exposure Control Intervalometer Script

« Reply #731 on: 14 / February / 2016, 10:11:08 »

Quote from: srsa_4c on 14 / February / 2016, 09:11:45

I have a suspicion. Your cam might be broken. Try using it without CHDK for more than a minute.

Or his camera simply may not work well at -25 deg C (as I suggested a couple of posts earlier).

Seems like a simple test is to run either intervalometer with the camera at room temperature. Does it also crash?

If so, you will need some good insulation around the camera when you attempt your balloon project. Also, I recently read about a "GoPro" balloon flight by a high school student - he solved the temperature problem using Hand Warmers to wrap the camera.

Logged

Ported : A1200 SD940 G10 Powershot N G16

Toshopo

14

Re: KAP & UAV Exposure Control Intervalometer Script

« Reply #732 on: 14 / February / 2016, 10:39:24 »

Quote from: srsa_4c on 14 / February / 2016, 09:11:45

I have a suspicion. Your cam might be broken. Try using it without CHDK for more than a minute.

Well see srsa4. The camera shutdown after 1 minute with a E32 error

Thank you for you help !

Logged

srsa_4c

4451

Re: KAP & UAV Exposure Control Intervalometer Script

« Reply #733 on: 14 / February / 2016, 18:31:12 »

Quote from: Toshopo on 14 / February / 2016, 10:39:24

Well see srsa4. The camera shutdown after 1 minute with a E32 error

That's what I suspected - E32 means there's a problem with the image stabilizer. As far as I know, it's usually caused by a broken flex cable inside the lens unit (see ebay item 251353559253). That flex cable is also responsible for operating the mechanical shutter and the ND filter - if it breaks completely, you'll lose them too.

However, with CHDK it's possible to prevent camera shutdown caused by E32. If you'd like to keep using it, you can ask for a special CHDK build. (I wouldn't use that camera for an important mission like yours, though.)

(note to others: the hacky E32 patch I posted in the forum is no longer usable on current CHDK source, I'm working on a proper one)

Logged

OhSnap

32

Re: KAP & UAV Exposure Control Intervalometer Script

« Reply #734 on: 20 / February / 2016, 15:12:36 »

Hello people,
Been setting up my canon IXUS 240HS with KAP UAV for a while now, and have a couple of notes/questions to ask.
First of all my photos were all over-exposed with default settings- What is the best way to reduce the exposure to normal levels? Is Exposure Compensation the way to go?
Secondly I run an NDVI filter on one of my cams, should I use the ND Filter setting or that would alter the results?

Thanks in advance!

Logged

waterwingz

12139

Re: KAP & UAV Exposure Control Intervalometer Script

« Reply #735 on: 20 / February / 2016, 15:31:53 »

Quote from: OhSnap on 20 / February / 2016, 15:12:36

First of all my photos were all over-exposed with default settings-

This is the second time this has been reported as an apparent issue. See :
http://chdk.setepontos.com/index.php?topic=10822.msg126149#msg126149
Having looked at the images there, I saw a lot of contrast which I believe can be a challenging shooting situation of you want everything correctly exposed.

Please post the kap.log file from the top level folder on your SD card and a link to one of the overexposed photos saved on a download site (like box.com).

Quote

What is the best way to reduce the exposure to normal levels? Is Exposure Compensation the way to go?

Obviously it would be best to figure out why the pictures appear to be overexposed. Do you have that issue using the script to take images in normal lighting on the ground or just when the camera is "airborne"?

Quote

Secondly I run an NDVI filter on one of my cams, should I use the ND Filter setting or that would alter the results?

Assuming the filter is mounted in front of the lens, you should probably set the ND Filter option in the script menu to Off.

Logged

Ported : A1200 SD940 G10 Powershot N G16

OhSnap

32

Re: KAP & UAV Exposure Control Intervalometer Script

« Reply #736 on: 20 / February / 2016, 16:06:47 »

Thank you for the answer, pictures appear brighter than normal even when the camera is on the ground, airborne photos (cam pointing downwards) however are even brighter and often over-exposed.
I have attached the log file.
Here's a photo with default settings : https://www.dropbox.com/s/uned8y5y2j5nlca/IMG_0048.JPG?dl=0

KAP.log (48.64 kB - downloaded 20 times.)

Logged

waterwingz

12139

Re: KAP & UAV Exposure Control Intervalometer Script

« Reply #737 on: 20 / February / 2016, 16:58:27 »

Quote from: OhSnap on 20 / February / 2016, 16:06:47

I have attached the log file.

There are several potentially interesting things in the log indicating that the camera / script was having trouble setting the exposure.

Please describe in detail how you are triggering the camera? It looks like you are trying to use a USB remote connected signal? What setup are you using to create that?

Logged

Ported : A1200 SD940 G10 Powershot N G16

OhSnap

32

Re: KAP & UAV Exposure Control Intervalometer Script

« Reply #738 on: 20 / February / 2016, 18:10:01 »

The camera was mounted on a quadcopter and was indeed being triggered by a usb cable. I am using a Pixhawk autopilot that also controls the camera trigger and shoots at regular distance intervals. The usb cable I used is the one sold by http://www.tuffwing.com/ .

Logged

waterwingz

12139

Re: KAP & UAV Exposure Control Intervalometer Script

« Reply #739 on: 20 / February / 2016, 20:02:52 »

Quote from: OhSnap on 20 / February / 2016, 18:10:01

The camera was mounted on a quadcopter and was indeed being triggered by a usb cable. I am using a Pixhawk autopilot that also controls the camera trigger and shoots at regular distance intervals. The usb cable I used is the one sold by http://www.tuffwing.com/ .

I'm not a pixhawk expert but it would be good to know how you set it up to trigger the camera.

The log file is strange - it looks like the camera tries to shoot, fails, and tries again. Over and over. And each shot attempt causes a timeout.

Code: [Select]

2016Feb16 14:21:23    CHDK 1.4.1-4381 ixus240_elph320hs 101a Jan 27 2016
2016Feb16 14:21:23    Mode:PLAY,Continuous_AF:0,Servo_AF:0 Drive:0
2016Feb16 14:21:23     Tv:1/1000 max:1/2000 min:10 ecomp:0.0
2016Feb16 14:21:23     Av:4.0 minAv:2.8 maxAv:8.0
2016Feb16 14:21:23     ISOmin:100 ISO1:400 ISO2:800 M:0
2016Feb16 14:21:23     Focus:OFF  Video:0 USB:2:1 Tmo:0
2016Feb16 14:21:23     AvM:2 int:1 Shts:0 Dly:0 B/L:0
2016Feb16 14:21:24    waiting on USB signal
2016Feb16 14:22:42    USB start signal received
2016Feb16 14:22:46    Mode switched to P
2016Feb16 14:22:46    Logger : log file updated.
2016Feb16 14:22:53    timeout after shoot full
2016Feb16 14:22:47.500 1) IMG_0048.JPG
2016Feb16 14:22:53     meter : Tv:1/200 Av:2.8 Sv:100 649:649
2016Feb16 14:22:53     actual: Tv:1/1000 Av:- Sv:400
2016Feb16 14:22:53             AvMin:2.8 NDF:NDout foc:infinity
2016Feb16 14:22:55    timeout on hook_shoot.is_ready
2016Feb16 14:22:55.760 2) IMG_0048.JPG
2016Feb16 14:22:58     meter : Tv:1/1000 Av:2.8 Sv:400 649:649
2016Feb16 14:22:58     actual: Tv:1/1000 Av:- Sv:400
2016Feb16 14:22:58             AvMin:2.8 NDF:NDout foc:infinity
2016Feb16 14:23:12    timeout after shoot full
2016Feb16 14:23:06.790 3) IMG_0049.JPG
2016Feb16 14:23:12     meter : Tv:1/200 Av:2.8 Sv:100 646:646
2016Feb16 14:23:12     actual: Tv:1/1000 Av:- Sv:400
2016Feb16 14:23:12             AvMin:2.8 NDF:NDout foc:infinity
2016Feb16 14:23:15    timeout on hook_shoot.is_ready
2016Feb16 14:23:15.050 4) IMG_0049.JPG
2016Feb16 14:23:17     meter : Tv:1/1000 Av:2.8 Sv:400 646:646
2016Feb16 14:23:17     actual: Tv:1/1000 Av:- Sv:400
2016Feb16 14:23:17             AvMin:2.8 NDF:NDout foc:infinity
2016Feb16 14:23:25    timeout after shoot full
2016Feb16 14:23:19.180 5) IMG_0050.JPG
2016Feb16 14:23:25     meter : Tv:1/200 Av:2.8 Sv:100 623:623
2016Feb16 14:23:25     actual: Tv:1/1000 Av:- Sv:500
2016Feb16 14:23:25             AvMin:2.8 NDF:NDout foc:infinity
2016Feb16 14:23:27    timeout on hook_shoot.is_ready
2016Feb16 14:23:27.440 6) IMG_0050.JPG
2016Feb16 14:23:30     meter : Tv:1/1000 Av:2.8 Sv:500 623:623
2016Feb16 14:23:30     actual: Tv:1/1000 Av:- Sv:500
2016Feb16 14:23:30             AvMin:2.8 NDF:NDout foc:infinity
2016Feb16 14:23:38    timeout after shoot full

Logged

Ported : A1200 SD940 G10 Powershot N G16