IXUS 990 / SD970 IS porting thread - page 3 - DryOS Development - CHDK Forum supplierdeeply

IXUS 990 / SD970 IS porting thread

  • 23 Replies
  • 697 Views
*

Offline koshy

  • *****
  • 1037
Re: IXUS 990 / SD970 IS porting thread
« Reply #20 on: 11 / February / 2020, 20:59:58 »
Advertisements
Oops, my mistake. It should be the set_led value that makes the AF turn on, while I was looking at the canon number. I think the set_led value should be 3. You can check in chdkptp like =set_led(3,1)
Actually mine  ;) I didn't get the difference between set_led value and Canon number and put the set_led values on the according table. So, that needs to be fixed in lib.c to

Code: [Select]
static char led_table[]={0, // green
                          1, // orange, right
                          2, // yellow, left
                          // 3,4,5,6,7,
                          8, // blue
                          9 // af
                          };
Which has now been tested. Of course that makes it
Code: [Select]
define CAM_AF_LED 4

The MD_Tune.bas yields:
Min: 20
Max 3300
Avg: 533
I got these after 100 iterations
« Last Edit: 11 / February / 2020, 21:01:51 by koshy »
Koshy had a little ELPH which wasn't white as snow but everywhere that Koshy went the ELPH was sure to go. (actually an SD, but that detail ruins the rhyme...)

*

Offline koshy

  • *****
  • 1037
Re: IXUS 990 / SD970 IS porting thread
« Reply #21 on: 11 / February / 2020, 21:14:47 »
See https://chdk.fandom.com/wiki/Testing#mftest.lua
Something acts up with this. I get an error
Code: [Select]
Line 47: attempt to index global 'log' (a nil value)
For the other test I don't have the memory browser in the debug menu on my build (based on 5420).
« Last Edit: 11 / February / 2020, 21:16:57 by koshy »
Koshy had a little ELPH which wasn't white as snow but everywhere that Koshy went the ELPH was sure to go. (actually an SD, but that detail ruins the rhyme...)

*

Offline reyalp

  • ******
  • 12366
Re: IXUS 990 / SD970 IS porting thread
« Reply #22 on: 11 / February / 2020, 21:27:56 »
Oops, my mistake. It should be the set_led value that makes the AF turn on, while I was looking at the canon number. I think the set_led value should be 3. You can check in chdkptp like =set_led(3,1)
Actually mine  ;) I didn't get the difference between set_led value and Canon number and put the set_led values on the according table. So, that needs to be fixed in lib.c to

Code: [Select]
static char led_table[]={0, // green
                          1, // orange, right
                          2, // yellow, left
                          // 3,4,5,6,7,
                          8, // blue
                          9 // af
                          };
Which has now been tested. Of course that makes it
Code: [Select]
define CAM_AF_LED 4
Thanks, I'll add those added in 5423.

Quote
The MD_Tune.bas yields:
Min: 20
Max 3300
Avg: 533
I got these after 100 iterations
That looks like some triggers were missed, probably due to scene. You should be able to see if the camera blinks the LED without triggering MD. For reliable triggering, I'd suggest a blank wall a foot or two from the camera under fairly low light. 20 iterations should be plenty if it's triggering reliably.
« Last Edit: 12 / February / 2020, 00:12:15 by reyalp »
Don't forget what the H stands for.

*

Offline reyalp

  • ******
  • 12366
Re: IXUS 990 / SD970 IS porting thread
« Reply #23 on: 11 / February / 2020, 21:38:22 »
See https://chdk.fandom.com/wiki/Testing#mftest.lua
Something acts up with this. I get an error
Code: [Select]
Line 47: attempt to index global 'log' (a nil value)
That suggests opening the file failed. Try replacing line around 45 that says
Code: [Select]
    filename = "A/mf_"..cam..".csv"
with
Code: [Select]
    filename = "A/mftest.csv"

Quote
For the other test I don't have the memory browser in the debug menu on my build (based on 5420).
Memory browser is under miscellaneous -> tools. The option to show the values is under debug.
Don't forget what the H stands for.


 

Related Topics