KAP & UAV Exposure Control Intervalometer Script - page 51 - Completed and Working Scripts - CHDK Forum supplierdeeply

KAP & UAV Exposure Control Intervalometer Script

  • 1068 Replies
  • 411090 Views
Re: KAP & UAV Exposure Control Intervalometer Script
« Reply #500 on: 23 / June / 2015, 23:08:57 »
Advertisements
RC recevier / autopilot is providing continuously the PWM value not only when change happens.
Yes, that's pretty much standard for every RC system.  It's basically an old semi-analog system where servos need constant position updates.  My question, repeated below, is whether the gentwire-usb2 also provides continuous PWM values (suitably modified) to the camera?  Or does it just provide one pulse each time the control lever position on the transmitter changes?

Quote
at the begining of each shooting session you will see many 210s . before I activate the output the wire gets only 5 volts and no signal.
That's what the gentwire-usb2 documentation says you should see too.  That part  is clear.

Quote
that is why you see so many CH2MID in my logs: ch2 trim is set to 1500.
This is the part that confuses me.  Does the gentwire-usb2 sent only one single pulse each time the servo position for either ch1 or ch2 changes?  Or does it continually send pulses over and over with length determined by the last change made?  And. why does it send so many CHD2MID pulses but only one CH1UP and CH1MID each time?

Quote
I am really looking forward to test the new version!
New version :  kap_uav.lua v3.6 beta6   I have enhanced the PWM code quite a bit.  Note that on line 420 is says :

Code: [Select]
PWM_required_repeats = 0The value set here determines how many identical pulses in a row are needed to trigger any action.  This extra bit of error proofing should almost competely eliminate false actions due to a single pulse error.  However, it only works if the gentwire-usb2 sends multiple pulses at each channel position.

« Last Edit: 23 / June / 2015, 23:12:21 by waterwingz »
Ported :   A1200    SD940   G10    Powershot N    G16

Re: KAP & UAV Exposure Control Intervalometer Script
« Reply #501 on: 24 / June / 2015, 03:03:31 »
Hi WWZ,

B6 test pictures are here:
https://drive.google.com/folderview?id=0Bz9RWJnTBrzIfjRFUlJVMVVRR1VhTnBnMi1jRjFET3ItLXY2R3NaZ25VT0NoeXVGT1ZzX3c&usp=sharing

6-10 have been taken in AUTO camera mode
11-14 Manual Mode
15-19 P mode
(settings on the camera knob)
what really puzzles me is the difference between the first and the 2-5 picture of each batch. I do not see any difference in exif data but there is a significant difference in the looks of the JPG.
Please let me know what you think!
S110, SX200is,

Re: KAP & UAV Exposure Control Intervalometer Script
« Reply #502 on: 24 / June / 2015, 03:24:04 »
Quote
Does the gentwire-usb2 sent only one single pulse each time the servo position for either ch1 or ch2 changes? 
Good question! and I can only answer from experience: yes and no.
let me explain:
I have no Idea how it should work but what I see looks like:
- the G-wire is continuously sends signals to the camera.
- the camera is getting only part of those pulses and not 100%.
- RC PWM output to G-wire ranges between 1499.5 - 1500.5
- the repeats in the Camera input pulses seem to be too erratic (ex.: many CH2MIDs with no changes but only 1 CH1 pulse when it changes.)
Question: does that 1 pwm RC output fluctuation trigger a new impulse from  the G-wire to the camera?

Due to the delays I have in my equipment I cannot identify the source of the camera input changes. I can only speculate based on what I see on the screen and the logs.

If you know the G-wire guys, maybe you can ask them how it should work.
Sorry if I wasn't much of a help! :(
S110, SX200is,

Re: KAP & UAV Exposure Control Intervalometer Script
« Reply #503 on: 24 / June / 2015, 05:14:16 »
Quote
The value set here determines how many identical pulses in a row are needed to trigger any action.  This extra bit of error proofing should almost completely eliminate false actions due to a single pulse error.  However, it only works if the gentwire-usb2 sends multiple pulses at each channel position.

I set the
Code: [Select]
PWM_required_repeats = 3  .

Judging form the logs it looks like the G-wire cycles the output thru the 2 values (60/150mSec).
The camera needs more than 5 seconds to gather the 3 repeats which suggests some delay / gap between the cycles. Camera did not actually do anything just listed the inputs.

I would be happy to dig deeper into the PWM issue, but I have 2 demo flights this week and I need the script to make good quality photos. Right now there are 2 main issues:

1. the camera parameter set from the first picture do not persist to the rest of the series.
2. the parameters of the KAP_UAV script are disregarded.

workarround(all issues): in P I set ISO to auto and the F to the widest range possible. that will force the camera to  keep shutter speed  and use the ISO and aperture to compensate. I hope that will be enough durring a sunny day too.


Code: [Select]
2015Jun24 09:41:15     * usb pulse = idle pulse (210 mSec)
2015Jun24 09:41:16     * usb pulse = ch2mid (150 mSec)
2015Jun24 09:41:16     * usb pulse = ch1mid (60 mSec)
2015Jun24 09:41:22     * usb pulse = idle pulse (210 mSec)
2015Jun24 09:41:23     * usb pulse = ch2mid (150 mSec)
2015Jun24 09:41:25     * usb pulse = idle pulse (210 mSec)
2015Jun24 09:41:25     * usb pulse = ch2mid (150 mSec)
2015Jun24 09:41:27     * usb pulse = ch1mid (60 mSec)
2015Jun24 09:41:30     * usb pulse = idle pulse (200 mSec)
2015Jun24 09:41:30     * usb pulse = ch2mid (150 mSec)
2015Jun24 09:41:31     * usb pulse = ch1mid (60 mSec)
2015Jun24 09:41:35     * usb pulse = idle pulse (210 mSec)
2015Jun24 09:41:36     * usb pulse = ch2mid (150 mSec)
2015Jun24 09:41:37     * usb pulse = ch1mid (60 mSec)
2015Jun24 09:41:50     * usb pulse = idle pulse (210 mSec)
2015Jun24 09:41:50     * usb pulse = ch2mid (150 mSec)
2015Jun24 09:41:51     * usb pulse = ch1mid (60 mSec)
S110, SX200is,


Re: KAP & UAV Exposure Control Intervalometer Script
« Reply #504 on: 24 / June / 2015, 07:10:12 »
I'll take a look at the log today. I'll also ping James Gentles - I have his email address somewhere.

I keep forgetting to remind you to delete the log file from your SD card occasionally. Each flight & test I'd just added you the end off the existing log so the file is getting quite large note.
« Last Edit: 24 / June / 2015, 14:46:35 by waterwingz »
Ported :   A1200    SD940   G10    Powershot N    G16

Re: KAP & UAV Exposure Control Intervalometer Script
« Reply #505 on: 24 / June / 2015, 08:07:56 »
6-10 have been taken in AUTO camera mode
11-14 Manual Mode
15-19 P mode
I took a quick look but the image names in your upload don't seem to match the image names in the log.  When I try to match up timestamps, they are slightly off.  I need a little more study to discover the sequence.  According to the log file, the darker correctly exposed image is the second picture in each sequence for example


Quote
what really puzzles me is the difference between the first and the 2-5 picture of each batch. I do not see any difference in exif data but there is a significant difference in the looks of the JPG.
You have the script exposure setting set strangely.   You have ISO pegged very high the shutter speed locked at 1/2000.  I guess it's possible that the camera cannot actually keep up with the requests of the script.  But that's just a guess.

What happens when you reshoot the sequence in P mode only (which gets rid of the various auto focus interactions) and use :

Tv min :         1/100
Target Tv :    1/1000
Tv max:         1/1600

Av low :         2.8
Av Target     2.8
Av Max :       8.0

ISO Min :      100
ISO Max1:    800
ISO Max2:  1600

Ported :   A1200    SD940   G10    Powershot N    G16

Re: KAP & UAV Exposure Control Intervalometer Script
« Reply #506 on: 24 / June / 2015, 11:09:04 »
Quote
What happens when you reshoot the sequence in P mode only (which gets rid of the various auto focus interactions) and use :

Below is the log for 3 tests:
1. exact settings that you suggested,
2. exact settings that you suggested  + ISO in P mode set to auto
3. settings that you suggested but all TV values set to 1/2000+ ISO in P mode set to auto
Pics are on the Drive.

Code: [Select]
2015Jun24 16:58:00.600 1) IMG_0170.JPG
2015Jun24 16:58:00     meter : Tv:1/1250 Av:4.0 Sv:1600 609:609
2015Jun24 16:58:00     actual: Tv:1/1000 Av:2.8 Sv:500
2015Jun24 16:58:00             AvMin:2.8 NDF:NDout foc:infinity
2015Jun24 16:58:02    timeout on hook_shoot.is_ready
2015Jun24 16:58:02.800 2) IMG_0186.JPG
2015Jun24 16:58:03.000 3) IMG_0186.JPG
2015Jun24 16:58:04.020 4) IMG_0187.JPG
2015Jun24 16:58:05.040 5) IMG_0188.JPG
2015Jun24 16:58:05    Total shots count reached.
2015Jun24 16:58:05    script halt requested
2015Jun24 16:58:05    Loggger : log file updated.
015Jun24 17:01:27    KAP 3.6b6 started - press MENU to exit
2015Jun24 17:01:27    CHDK 1.3.0-4132 s110 102b Mar 31 2015
2015Jun24 17:01:27    Mode:P,Continuous_AF:0,Servo_AF:0
2015Jun24 17:01:27     Tv:1/1000 max:1/2000 min:1/100 ecomp:0.0
2015Jun24 17:01:27     Av:2.8 minAv:2.8 maxAv:8.0
2015Jun24 17:01:27     ISOmin:100 ISO1:800 ISO2:1600 M:0
2015Jun24 17:01:27     Focus:MF  Video:0 USB:0 Tmo:0
2015Jun24 17:01:27     AvM:3 int:0 Shts:5 Dly:0 B/L:0
2015Jun24 17:01:30    Loggger : log file updated.
2015Jun24 17:01:31.550 1) IMG_0189.JPG
2015Jun24 17:01:31     meter : Tv:1/200 Av:2.0 Sv:n/a 677:677
2015Jun24 17:01:31     actual: Tv:1/1000 Av:2.8 Sv:320
2015Jun24 17:01:31             AvMin:2.8 NDF:NDout foc:infinity
2015Jun24 17:01:32.600 2) IMG_0190.JPG
2015Jun24 17:01:33.610 3) IMG_0191.JPG
2015Jun24 17:01:34.630 4) IMG_0192.JPG
2015Jun24 17:01:35.640 5) IMG_0193.JPG
2015Jun24 17:01:35    Total shots count reached.
2015Jun24 17:01:35    script halt requested
2015Jun24 17:01:36    Loggger : log file updated.
2015Jun24 17:03:24    KAP 3.6b6 started - press MENU to exit
2015Jun24 17:03:24    CHDK 1.3.0-4132 s110 102b Mar 31 2015
2015Jun24 17:03:24    Mode:PLAY,Continuous_AF:0,Servo_AF:0
2015Jun24 17:03:24     Tv:1/2000 max:1/2000 min:1/2000 ecomp:0.0
2015Jun24 17:03:24     Av:2.8 minAv:2.8 maxAv:8.0
2015Jun24 17:03:24     ISOmin:100 ISO1:800 ISO2:1600 M:0
2015Jun24 17:03:24     Focus:MF  Video:0 USB:0 Tmo:0
2015Jun24 17:03:24     AvM:3 int:0 Shts:5 Dly:0 B/L:0
2015Jun24 17:03:28    Mode switched to P
2015Jun24 17:03:30    Loggger : log file updated.
2015Jun24 17:03:32.700 1) IMG_0194.JPG
2015Jun24 17:03:32     meter : Tv:1/200 Av:2.0 Sv:n/a 671:671
2015Jun24 17:03:32     actual: Tv:1/2000 Av:2.8 Sv:640
2015Jun24 17:03:32             AvMin:2.8 NDF:NDout foc:infinity
2015Jun24 17:03:33.710 2) IMG_0195.JPG
2015Jun24 17:03:34.730 3) IMG_0196.JPG
2015Jun24 17:03:35.770 4) IMG_0197.JPG
2015Jun24 17:03:36.790 5) IMG_0198.JPG
2015Jun24 17:03:36    Total shots count reached.
2015Jun24 17:03:36    script halt requested
2015Jun24 17:03:37    Loggger : log file updated.
« Last Edit: 24 / June / 2015, 11:16:56 by netptl39 »
S110, SX200is,

Re: KAP & UAV Exposure Control Intervalometer Script
« Reply #507 on: 24 / June / 2015, 12:37:16 »
Those pictures look a little better.   I think those setting should work for your coming demonstration if we don't find anything else first.

Unfortunately,   you changed the camera position with each shot so it's hard to compare the exposures between them.  But IMG_0186 & IMG_0187 are almost the same scene and 187 looks a little darker than 186 even though the EXIF exposure information is the same.  And to make things stranger,  the exif time stamp information says the images were taken 3 seconds apart - even though you shot rate was pretty close to one second per shot?

The image numbers in the log are also off by one - I have a theory that I can test on my S100 for that issue.

Ported :   A1200    SD940   G10    Powershot N    G16


Re: KAP & UAV Exposure Control Intervalometer Script
« Reply #508 on: 24 / June / 2015, 13:13:32 »
Found the problem with the image numbering! 

And it's very possible that the same bug was throwing off the exposure between shots. 

FWIW,  there was a bug preventing the script's continuous shooting mode from waiting for each shot to finish writing to the SD card prior to starting the next shot.  I fixed that and for reasons I don't fully understand,  my S100 is shooting at about 900 mSec per shot!  Bonus!

download link > kap_uav.lua 3.6 beta7
Ported :   A1200    SD940   G10    Powershot N    G16

Re: KAP & UAV Exposure Control Intervalometer Script
« Reply #509 on: 24 / June / 2015, 23:48:45 »
I suggest that you NOT use Auto mode.

OK, understood :) , I will do only P mode with the Focus @ infinity enabled/disabled.

Thank you.

Hello,

2 flights done yesterday , the quality of the pictures is better in P mode than in Auto mode. Regarding the quality of the pictures for P mode with Focus @ infinity enabled/disabled I do not see a big difference , please find below the results from yesterday.

http://fastupload.rol.ro/88895d79027f234fc1916b10cdfdc6ca.html


 

Related Topics