G11 issues - page 2 - General Discussion and Assistance - CHDK Forum supplierdeeply

G11 issues

  • 28 Replies
  • 549 Views
*

Offline koshy

  • *****
  • 897
Re: G11 issues
« Reply #10 on: 08 / September / 2019, 19:56:37 »
Advertisements
I want to know which LED number corresponds to which LED. e.g. set_led(0,1) turns on Upper LED adjacent to EVF

Here you go:

0 Upper LED near EVF in Green
1 Upper LED near EVF in Orange
2 Lower LED near EVF
3 LED in power button
4 - I don't see it
5 LED next to ISO Dial
6 LED next EV +/- Dial

*

Offline reyalp

  • ******
  • 12072
Re: G11 issues
« Reply #11 on: 08 / September / 2019, 20:05:57 »
I want to know which LED number corresponds to which LED. e.g. set_led(0,1) turns on Upper LED adjacent to EVF

Here you go:

0 Upper LED near EVF in Green
1 Upper LED near EVF in Orange
2 Lower LED near EVF
3 LED in power button
4 - I don't see it
5 LED next to ISO Dial
6 LED next EV +/- Dial
Thanks, does 4 maybe control the AF assist LED on the front of the cam?
Don't forget what the H stands for.

*

Offline koshy

  • *****
  • 897
Re: G11 issues
« Reply #12 on: 08 / September / 2019, 20:20:39 »
Thanks, does 4 maybe control the AF assist LED on the front of the cam?
Not that I can see it. Tried various modes, nothing seems to blink or flicker either...

*

Offline reyalp

  • ******
  • 12072
Re: G11 issues
« Reply #13 on: 08 / September / 2019, 21:16:36 »
Not that I can see it. Tried various modes, nothing seems to blink or flicker either...
It should be pretty bright. Does it come on if you half press with AF assist enabled in the canon UI? It's in the circular window below / left of the viewfinder in https://www.dpreview.com/files/p/articles/4213966607/Images/Intro.jpeg

One reason I'd like to find it is that it would let us run mdtest, which would help verify the live view buffer variables.
Don't forget what the H stands for.


*

Offline koshy

  • *****
  • 897
Re: G11 issues
« Reply #14 on: 08 / September / 2019, 21:32:40 »
Does it come on if you half press with AF assist enabled in the canon UI?
Yes, AF Beam was turned on on the Canon Menu and it comes on in a dark room on half press just fine.
It did not light up with any of the LED calls. Anything else to try to find it?

*

Offline reyalp

  • ******
  • 12072
Re: G11 issues
« Reply #15 on: 08 / September / 2019, 22:50:28 »
Yes, AF Beam was turned on on the Canon Menu and it comes on in a dark room on half press just fine.
It did not light up with any of the LED calls. Anything else to try to find it?
You could try calling the LEDDrive function directly like
Code: [Select]
=return call_func_ptr(0xff85f674, LED_number,state)
LED_number is different from the numbers used by set_led. The set_led values you tested effectively ruled out 0,1,2,3,9,14,15, so it probably only makes sense to try 4-8 and 10-13. Some numbers might control multiple LEDs. On elph130, unsupported values returned 3, while calls that controlled an LED returned 0.
state for LEDDrive is reverse of set_led, so 0 is on, 1 is off.
Don't forget what the H stands for.

*

Offline koshy

  • *****
  • 897
Re: G11 issues
« Reply #16 on: 10 / September / 2019, 12:24:27 »
You could try calling the LEDDrive function directly
Thanks. 10 and 11 both turn the AF Beam LED on and off. No discernible difference between the two. You can turn on with 11, then turn off with 10, too.

Code: [Select]
> =return call_func_ptr(0xff85f674, 4,0)
8:return:3
> =return call_func_ptr(0xff85f674, 5,0)
9:return:3
> =return call_func_ptr(0xff85f674, 6,0)
10:return:3
> =return call_func_ptr(0xff85f674, 7,0)
11:return:3
> =return call_func_ptr(0xff85f674, 8,0)
12:return:3
> =return call_func_ptr(0xff85f674, 10,0)
13:return:0
> =return call_func_ptr(0xff85f674, 10,1)
14:return:0
> =return call_func_ptr(0xff85f674, 11,0)
15:return:0
> =return call_func_ptr(0xff85f674, 11,1)
16:return:0
> =return call_func_ptr(0xff85f674, 12,0)
17:return:3
> =return call_func_ptr(0xff85f674, 13,0)
18:return:3
> =return call_func_ptr(0xff85f674, 10,0)
19:return:0
> =return call_func_ptr(0xff85f674, 11,0)
20:return:0
> =return call_func_ptr(0xff85f674, 10,1)
21:return:0

*

Offline reyalp

  • ******
  • 12072
Re: G11 issues
« Reply #17 on: 11 / September / 2019, 00:53:18 »
10 and 11 both turn the AF Beam LED on and off. No discernible difference between the two. You can turn on with 11, then turn off with 10, too.
Thanks. Just mentioning in case you weren't looking at the other LEDs: On my elph130, I found some values controlled multiple LEDs, so 12 controlled both the power and AF leds, while 4 only controlled AF.

New build attached. set_led(4,...) should now control the AF.

You can try running MD_tune as described on https://chdk.fandom.com/wiki/Testing#MD_tune.bas

Note the display will have to be enabled (like for PTP live view), since it MD also relies on the viewport.

If you have chdkptp setup, you could also run
Code: [Select]
chdkptp -e"exec require'camtests'.runbatch{bench=true,xfersizebugs=true,filexfer=true}"
and report if there are any crashes or failures.
Don't forget what the H stands for.


*

Offline koshy

  • *****
  • 897
Re: G11 issues
« Reply #18 on: 11 / September / 2019, 09:18:11 »
Thanks. Just mentioning in case you weren't looking at the other LEDs: On my elph130, I found some values controlled multiple LEDs, so 12 controlled both the power and AF leds, while 4 only controlled AF.
The others default to "on" but since I also turned off AF beam by 10 and 11 I would have noticed if one would have been turned off with it.

You can try running MD_tune as described on https://chdk.fandom.com/wiki/Testing#MD_tune.bas
Put the cam under a pillow... Wasn't sure if it would end but after 500+ runs decided that I'd look at the script ;-) No errors.

*

Offline reyalp

  • ******
  • 12072
Re: G11 issues
« Reply #19 on: 11 / September / 2019, 15:50:17 »
Put the cam under a pillow... Wasn't sure if it would end but after 500+ runs decided that I'd look at the script ;-) No errors.
Great, from the response times it looks like buffers are correct for fast MD. I'll check these changes in once I implement them for the other firmware versions.
Don't forget what the H stands for.

 

Related Topics