G11 issues - General Discussion and Assistance - CHDK Forum supplierdeeply

G11 issues

  • 28 Replies
  • 534 Views
*

Offline koshy

  • *****
  • 895
G11 issues
« on: 04 / September / 2019, 18:24:19 »
Advertisements
@reyalp I came across a mildly broken G11. The display acted up when I got it for 20 bucks, somehow garbled, sometimes a strip from the bottom at the top and other glitches. Now it's gone alltogether. Well, I thought PTP to the rescue, I don't need an on camera display for setting continuous shooting etc. for the ND Filter test script. Wasn't lucky though. PTP live view and camera controls fail. Camera is set to foreign language and wants clock to be set, nothing reacts in PTP (up down etc.) and on camera no button presses show in the PTP UI overlay, palette is broken...

So, are you interested in fixing the G11 enough for PTP so that I can configure and test it?
It takes pictures just fine - I think the cable for the LCD is either out of its connector or is broken...
Opening it up is for another day though, preferably after testing ND.

Firmware is 100K (in case we need test builds)
« Last Edit: 06 / September / 2019, 21:36:46 by koshy »

*

Offline koshy

  • *****
  • 895
Re: G11 issues (was Re: Improving CHDK ND filter support)
« Reply #1 on: 04 / September / 2019, 19:56:38 »
Quote from: koshy link=topic=13228.msg141284#msg141284
Opening it up is for another day though, preferably after testing ND.
Well, why wait... Nastier than I thought though. Something corroded the board behind the LCD, cleaned it but to no avail. Maybe I need replacements for both, the connector may be short circuited, so may the cable be. The LCD lights up but that's all. So, maybe a PTP only cam or one for the spare parts box...

Edit: What do you know...
https://www.aliexpress.com/item/32882420024.html
https://www.aliexpress.com/item/32687118547.html
« Last Edit: 04 / September / 2019, 20:03:41 by koshy »

*

Offline reyalp

  • ******
  • 12072
Re: G11 issues (was Re: Improving CHDK ND filter support)
« Reply #2 on: 05 / September / 2019, 01:12:26 »
Camera is set to foreign language and wants clock to be set, nothing reacts in PTP (up down etc.) and on camera no button presses show in the PTP UI overlay, palette is broken...
Did you try
Code: [Select]
=post_levent_to_ui(4484)
to unlock the keys? That should at least let you set the clock and language.

Quote
So, are you interested in fixing the G11 enough for PTP so that I can configure and test it?
Sure. I'll split this into another thread, since I think it will mostly not be ND...
Don't forget what the H stands for.

*

Offline koshy

  • *****
  • 895
Re: G11 issues (was Re: Improving CHDK ND filter support)
« Reply #3 on: 05 / September / 2019, 08:01:08 »
Sure. I'll split this into another thread, since I think it will mostly not be ND...
Thanks, you're right of course. Managed to do the ND related part and posted the CSV.

Buttons work after
Code: [Select]
=post_levent_to_ui(4484)
Palette is broken as shown, CHDK_PTP said something and I'm including the note in the screen grab
With every other button press I see alt mode in the overlay but not on the camera display


*

Offline reyalp

  • ******
  • 12072
Re: G11 issues (was Re: Improving CHDK ND filter support)
« Reply #4 on: 05 / September / 2019, 12:30:49 »
Palette is broken as shown, CHDK_PTP said something and I'm including the note in the screen grab
Thanks. Live view functions are mostly not implemented in this port, so no need for in depth PTP testing until I've had a chance to add them.

One thing you can check for ND support is whether propcase 194 reflects the ND state set in the canon UI. So, use the Canon menu to set ND out, do =return get_prop(194), set it in, get_prop again.
Don't forget what the H stands for.

*

Offline koshy

  • *****
  • 895
Re: G11 issues (was Re: Improving CHDK ND filter support)
« Reply #5 on: 05 / September / 2019, 12:54:33 »
One thing you can check for ND support is whether propcase 194 reflects the ND state set in the canon UI. So, use the Canon menu to set ND out, do =return get_prop(194), set it in, get_prop again.

Code: [Select]
> =return get_prop(194)
5:return:1
> =return get_prop(194)
6:return:0

1 is ND in
0 is ND out

*

Offline reyalp

  • ******
  • 12072
Re: G11 issues (was Re: Improving CHDK ND filter support)
« Reply #6 on: 07 / September / 2019, 23:52:15 »
1 is ND in
0 is ND out
Thanks. Here's a test build (it's for 100j, which is the build we use for 100k). This should have the palette and current live view buffer implemented.

A couple things to check:
1) Turn on "Miscellaneous stuff->Debug->Show misc values". The 2nd and 3rd values are labeled AVB and VB. In rec mode, AVB should cycle in the range 0-2, and VB should be a long hex value like 0x40587700, also cycling. I don't need the specific values of VB, just want to know if it cycles values like that, probably all starting with 0x4.

2) Which LEDs are controlled by set_led(), like
Code: [Select]
=set_led(0,1)
... check which led is on
=set_led(0,0)
=set_led(1,1)
... etc
Only 0-6 need to be checked.
Don't forget what the H stands for.

*

Offline koshy

  • *****
  • 895
Re: G11 issues
« Reply #7 on: 08 / September / 2019, 19:11:04 »
Thanks, what a nice thing to try Sunday night :-)
Something caught me off guard. Not much worked while having the defunct display folded away. Once I realized that I should probably open it, things came together...

1) Turn on "Miscellaneous stuff->Debug->Show misc values". The 2nd and 3rd values are labeled AVB and VB. In rec mode, AVB should cycle in the range 0-2, and VB should be a long hex value like 0x40587700, also cycling. I don't need the specific values of VB, just want to know if it cycles values like that, probably all starting with 0x4.
Yes 0-2 and three values in the 0x4... range

2) Which LEDs are controlled by set_led(), like
Code: [Select]
=set_led(0,1)
... check which led is on
=set_led(0,0)
=set_led(1,1)
... etc
Only 0-6 need to be checked.

Don't know what you expect. I think there are 5 LEDs. 2 orange next to +/-EV and ISO dials, one in the power button, two adjacent to the EVF. Four are on when booting the camera. Only the lower one next to the EVF is not. With the command ony one LED reacts in various ways:
Code: [Select]
=set_led(0,1) Upper LED adjacent to EVF on continuous
=set_led(0,2) Upper LED adjacent to EVF blinks slow
=set_led(0,3) Upper LED adjacent to EVF blinks fast
=set_led(0,4) Upper LED adjacent to EVF blinks faster than 2, slower than 3
=set_led(0,5) Upper LED adjacent to EVF blinks fast 4 or five times, then off
=set_led(0,6) Upper LED adjacent to EVF blinks slow again
=set_led(0,7) Upper LED adjacent to EVF on continuous
« Last Edit: 08 / September / 2019, 19:25:20 by koshy »


*

Offline reyalp

  • ******
  • 12072
Re: G11 issues
« Reply #8 on: 08 / September / 2019, 19:39:51 »
Thanks, what a nice thing to try Sunday night :-)
Something caught me off guard. Not much worked while having the defunct display folded away. Once I realized that I should probably open it, things came together...
Yeah, it presumably shuts off all the display stuff when it's not visible. Do the UI colors look approximately OK?

Quote
Don't know what you expect. I think there are 5 LEDs. 2 orange next to +/-EV and ISO dials, one in the power button, two adjacent to the EVF. Four are on when booting the camera. Only the lower one next to the EVF is not. With the command ony one LED reacts in various ways:
Code: [Select]
=set_led(0,1) Upper LED adjacent to EVF on continuous
I should have been clearer. The *first* parameter is the LED number (which should be tested from 0-6). The second value sets the state of the LED: 1 turns on (solid), 0 turns off, other values may blink, but I don't care about those.

I want to know which LED number corresponds to which LED. e.g. set_led(0,1) turns on Upper LED adjacent to EVF, set_led(1,1) turns on ...
Don't forget what the H stands for.

*

Offline koshy

  • *****
  • 895
Re: G11 issues
« Reply #9 on: 08 / September / 2019, 19:49:51 »
Do the UI colors look approximately OK?
Yes I think so.

I should have been clearer. The *first* parameter is the LED number (which should be tested from 0-6). The second value sets the state of the LED: 1 turns on (solid), 0 turns off, other values may blink, but I don't care about those.
Wonderful. I don't know if it was my bad but this made me laugh, thanks for that. I'll re-try.

 

Related Topics