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

IXUS 990 / SD970 IS porting thread

  • 27 Replies
  • 1702 Views
*

Offline koshy

  • *****
  • 1051
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

  • *****
  • 1051
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

  • ******
  • 12690
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

  • ******
  • 12690
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.


*

Offline reyalp

  • ******
  • 12690
Re: IXUS 990 / SD970 IS porting thread
« Reply #24 on: 23 / February / 2020, 19:32:13 »
Here's a test build for 100b, in case anyone shows up with that firmware.

Don't forget what the H stands for.

Re: IXUS 990 / SD970 IS porting thread
« Reply #25 on: 20 / September / 2020, 13:53:46 »
Hi all,
Newbie here. May I ask has anyone finalized porting the CHDK for SD970 IS? Couldn't find any file to try on this camera.

Update: Oh! My bad. Somehow my PC browser could not show the download link on this page. But I managed to use my phone to download the file.
« Last Edit: 20 / September / 2020, 14:31:25 by cameradumpster »

*

Offline reyalp

  • ******
  • 12690
Re: IXUS 990 / SD970 IS porting thread
« Reply #26 on: 20 / September / 2020, 14:21:20 »
Hi all,
Newbie here. May I ask has anyone finalized porting the CHDK for SD970 IS? Couldn't find any file to try on this camera.
A build for firmware 100a is available in the trunk autobuild http://mighty-hoernsche.de/trunk/
A test build for 100b is attached to the post directly above yours.
Don't forget what the H stands for.

Re: IXUS 990 / SD970 IS porting thread
« Reply #27 on: 20 / September / 2020, 14:35:55 »
A build for firmware 100a is available in the trunk autobuild http://mighty-hoernsche.de/trunk/
A test build for 100b is attached to the post directly above yours.

Thanks! I'm exploring the functions now.


 

Related Topics