Script not working like expected (G7X) - General Help and Assistance on using CHDK stable releases - CHDK Forum  
« previous next »
Pages: [1] 2 3   Go Down

Script not working like expected (G7X)

  • 21 Replies
  • 10135 Views
*

Offline Skumgummifabriken

  • *
  • 10
Script not working like expected (G7X)
« on: 11 / July / 2018, 16:37:23 »
Advertisements
I'm not sure what category to put this in, but I ended up here for now.

First, to clarify where I'm coming from; I have a Canon S110 that I'm using 90% just for UAV aerial photography. That is only because of CHDK and the "kap uav" script that is available somewhere. This works very well.

However I recently got a used G7 X pretty cheap. As it is listed as compatible with CHDK I gave it a try today. I know it is a "trunk" build and not "stable", but I only care for the script, not any other functions which may be broken or not.

But the script doesn't actually work like I'm used to with the S110.

1. It seems to like getting stuck at one exposure value, in this case my lowest setting of 1/800. I have set it to 1/800 - 1/2000.
2. Aperture value doesn't change like expected. It seems to be way random and the camera/script likes staying on high numbers a lot, like f11 even though it's not even set in the script! I Have set the script settings to use f 1.8 to 8.

This makes every picture underexposed, especially when it's on 1/800 and f11.

I have never experienced any problems with CHDK or this script before, even though I have been using it for many years. So I have no idea where to start looking when trying to fix this.
Any suggestions?

« Last Edit: 11 / July / 2018, 16:52:42 by Skumgummifabriken »
Logged
*

Offline reyalp

  • ******
  • 14082
Re: Script not working like expected (G7X)
« Reply #1 on: 11 / July / 2018, 16:58:58 »
It would be helpful to have a log from a run showing the incorrect behavior.

In my experience, script exposure overrides generally work on G7 X, so we need to figure out what is causing problem in this particular case. I can try running kap_uav on my G7 X later, but it's possible @waterwingz will be able to see what's wrong immediately from the logs.
Logged
Don't forget what the H stands for.
*

Offline waterwingz

  • ******
  • 12139
    • Waterwingz
Re: Script not working like expected (G7X)
« Reply #2 on: 11 / July / 2018, 17:07:05 »
A log file would certainly be a good place to start. An underexposed image listed in the log - unedited with original EXIF info would be good too.
Logged
Ported :   A1200    SD940   G10    Powershot N    G16
*

Offline Skumgummifabriken

  • *
  • 10
Re: Script not working like expected (G7X)
« Reply #3 on: 11 / July / 2018, 17:31:02 »
Hi,

I didn't even know there was logs.. The only log I could find however, were KAP.log.
Will that work?

I put a few photos here, its 12MP unaltered camera jpeg.
http://zufall.nu/temp/chdk/

IMG_0140.JPG is an example of what looks kinda correct, but the numbers aren't right:

It's f 5.6, 1/800 ISO 500.
while it should have been something like:
f 2-3, 1/1250-1600, iso 200-400

The calculation seems messed up and almost backwards

Does it matter which mode the scripts run in? Fully manual, P?
I have always used C to get my manual focus saved.

« Last Edit: 11 / July / 2018, 20:48:12 by Skumgummifabriken »
Logged
*

Offline reyalp

  • ******
  • 14082
Re: Script not working like expected (G7X)
« Reply #4 on: 11 / July / 2018, 22:56:46 »
The first thing that jumps out in the log for me is AvMin
Code: [Select]
2018Jul11 16:20:20.530 1) IMG_0012.JPG
2018Jul11 16:20:22     meter : Tv:1/500 Av:4.0 Sv:200 999:999
2018Jul11 16:20:22     actual: Tv:1/1600 Av:11.0 Sv:800 Temp:32
2018Jul11 16:20:22             AvMin:11.0 NDF:NDout foc:13.6m
It looks like the script thinks the minimum available Av is F11, and the other problems stem from that.

Testing some more, it appears propcase MIN_AV is not correct (similar to the problem on elph180, it sometimes contains the min value but not always).

I've checked in a fix which will appear in autobuild 5073.
Logged
Don't forget what the H stands for.
*

Offline Skumgummifabriken

  • *
  • 10
Re: Script not working like expected (G7X)
« Reply #5 on: 12 / July / 2018, 09:58:01 »
Ok so I copied over a new chdk, the script seems to work much better now.

But I think something is up with the iso values, it doesn't seem to use my set values properly, it's always something in between.

If I put Max1 @ 800 and Max2 @ 1600 it always uses 1000 as the highest value.
Logged
*

Offline waterwingz

  • ******
  • 12139
    • Waterwingz
Re: Script not working like expected (G7X)
« Reply #6 on: 12 / July / 2018, 10:47:49 »
Quote from: Skumgummifabriken on 12 / July / 2018, 09:58:01
But I think something is up with the iso values, it doesn't seem to use my set values properly, it's always something in between.
Please post a new log file here?
Logged
Ported :   A1200    SD940   G10    Powershot N    G16
*

Offline Skumgummifabriken

  • *
  • 10
Re: Script not working like expected (G7X)
« Reply #7 on: 12 / July / 2018, 18:06:46 »
All of these ended up at iso 1000. Here's the log:

Code: [Select]
2018Jul13 00:00:09    KAP 3.8 started - press MENU to exit
2018Jul13 00:00:09    CHDK 1.5.0-5073 g7x 100d Jul 12 2018
2018Jul13 00:00:09    Mode:M,Continuous_AF:0,Servo_AF:0 Drive:0
2018Jul13 00:00:09     Tv:1/1600 max:1/2000 min:1/1000 ecomp:0.0
2018Jul13 00:00:09     Av:2.8 minAv:1.8 maxAv:8.0
2018Jul13 00:00:09     ISOmin:80 ISO1:800 ISO2:1600 M:0
2018Jul13 00:00:09     Focus:OFF  Video:0 USB:0:1 Tmo:0
2018Jul13 00:00:09     AvM:1 int:4 Shts:0 Dly:2 B/L:1
2018Jul13 00:00:09    entering start delay of 2 seconds
2018Jul13 00:00:14    Logger : log file updated.
2018Jul13 00:00:16.080 1) IMG_0402.JPG
2018Jul13 00:00:18     meter : Tv:1/1250 Av:3.5 Sv:hi -1164:-1164
2018Jul13 00:00:18     actual: Tv:1/1000 Av:1.8 Sv:1600 Temp:27
2018Jul13 00:00:18             AvMin:1.8 NDF:NDout foc:infinity
2018Jul13 00:00:20.100 2) IMG_0403.JPG
2018Jul13 00:00:22     meter : Tv:1/1250 Av:3.5 Sv:hi -1164:-1164
2018Jul13 00:00:22     actual: Tv:1/1000 Av:1.8 Sv:1600 Temp:27
2018Jul13 00:00:22             AvMin:1.8 NDF:NDout foc:infinity
2018Jul13 00:00:25    Warning : unable to focus / set exposure
2018Jul13 00:00:25.340 3) IMG_0404.JPG
2018Jul13 00:00:27     meter : Tv:1/1250 Av:3.5 Sv:3200 258:258
2018Jul13 00:00:27     actual: Tv:1/1000 Av:1.8 Sv:1600 Temp:27
2018Jul13 00:00:27             AvMin:1.8 NDF:NDout foc:infinity
2018Jul13 00:00:28.570 4) IMG_0405.JPG
2018Jul13 00:00:30     meter : Tv:1/1250 Av:3.5 Sv:hi 57:57
2018Jul13 00:00:30     actual: Tv:1/1000 Av:1.8 Sv:1600 Temp:27
2018Jul13 00:00:30             AvMin:1.8 NDF:NDout foc:infinity
2018Jul13 00:00:30    MENU key pressed.
2018Jul13 00:00:30    script halt requested
2018Jul13 00:00:30    Logger : log file updated.
It works excellent in normal daylight though :)
« Last Edit: 12 / July / 2018, 20:02:54 by Skumgummifabriken »
Logged
*

Offline waterwingz

  • ******
  • 12139
    • Waterwingz
Re: Script not working like expected (G7X)
« Reply #8 on: 13 / July / 2018, 11:42:58 »
Quote from: Skumgummifabriken on 12 / July / 2018, 18:06:46
All of these ended up at iso 1000. Here's the log:
According to your log file, the script set the ISO to 1600 (which is the highest value you allowed in your script parameters setup). 

Why to you believe the images were actually shot at ISO 1000?

If the images were shot at 1000 then there is something wrong with the ISO override range for the camera I think?

Can you manually override the ISO value from the CHDK menus to 1600 as a test?
Logged
Ported :   A1200    SD940   G10    Powershot N    G16
*

Offline Skumgummifabriken

  • *
  • 10
Re: Script not working like expected (G7X)
« Reply #9 on: 13 / July / 2018, 14:39:59 »
Quote from: waterwingz on 13 / July / 2018, 11:42:58
Why to you believe the images were actually shot at ISO 1000?

Because it says so. See attached photo, it should have been at 1600.

What does the "hi -1164:-1164" etc mean?


Quote from: waterwingz on 13 / July / 2018, 11:42:58
Can you manually override the ISO value from the CHDK menus to 1600 as a test?

Yes, that works fine. When set at 1600, the camera gives me 1600 every time.
Logged
Pages: [1] 2 3   Go Up
« previous next »
 

Related Topics