G7 X porting thread [G7_X]

reyalp

Updated with build r4797 in the usual posts:

100b https://chdk.setepontos.com/d/12692/84
100c https://chdk.setepontos.com/d/12692/85
100d https://chdk.setepontos.com/d/12692/8

The main change is that raw buffers should now be correct in most cases (technical details). This means you can use CHDK raw in many cases where the Canon firmware does not allow Canon raw: With digital zoom, in Auto mode, with "my colors", etc. Of course, the visual effects apply only to the jpeg.

CHDK raw is also now disabled in some modes where it known to be non-functional: HDR, "handheld night scene" and "hybrid auto".

reyalp

Updated with build r4805 in the usual posts:

100b https://chdk.setepontos.com/d/12692/84
100c https://chdk.setepontos.com/d/12692/85
100d https://chdk.setepontos.com/d/12692/8

Added workaround for some UHS cards not using full speed under CHDK technical details. I suspect this may fix occasional boot problems, but haven't used it enough to be sure.

reyalp

Builds for 100b and 100d are now available from the trunk autobuild http://mighty-hoernsche.de/trunk/

The test build for 100c is still waiting for feedback.

mbf_az

Thank you for all your great work!

My Camera: G7X 100d

On May 5, 2017 I downloaded and began testing g7x-100d-1.5.0-4805-full-prealpha
I only tested the following:

Override Tv - LongExp
Override Av
Override ISO
Dark Frame Subtraction
Bracketing in Continuous Mode
interval.bas script

After learning the fundamentals and trying out many of the successful techniques I use for astrophotography using Magic Lantern on an SL1, I found everything to be fully functional except for Dark Frame Subtraction. No matter what I set it to [off,on,auto] it is always enabled in my camera.

I tried downloading and using the meteor2.lua script, but it, too, failed to turn off Dark Frame Subtraction.

On May 13 I downloaded and installed g7x-100d-1.5.0-4827-full_ALPHA, but it has the same behavior.

Specifically, any long shutter speed (5+ seconds in my testing), whether initiated using a CHDK override or a native camera setting, in or out of a script, is followed immediately by a "Busy" for an amount of time about equal to the shutter speed. I have tried any number of different combinations of the features noted above, as well as shooting RAW, JPEG or RAW+JPEG, but nothing causes Dark Frame Subtraction to be turned off.

Just reporting a suspected bug. All the other features make it a great tool for me.
Thanks again

reyalp

mbf_az
After learning the fundamentals and trying out many of the successful techniques I use for astrophotography using Magic Lantern on an SL1, I found everything to be fully functional except for Dark Frame Subtraction. No matter what I set it to [off,on,auto] it is always enabled in my camera.

I tried downloading and using the meteor2.lua script, but it, too, failed to turn off Dark Frame Subtraction.

Thanks for testing and reporting. As mentioned in notes, dark frame control is not implemented yet in this port.

In my experience, the Canon firmware only enables exposures longer than 30s, not 5s. This could depend on ISO or shooting mode, I typically use M and ISO 800 or less.

If you do know settings that trigger it for exposures around 5s, let me know because it will make it easier for me to develop a fix.

62ndidiot

In sx60hs Canon enables darkframe for any exposure of more than 1 second as far as I can tell.

reyalp

62ndidiot
In sx60hs Canon enables darkframe for any exposure of more than 1 second as far as I can tell.

Yes, the small sensor powershots usually do it somewhere around 1-3 seconds. On g7x, I know I've taken a lot of 30s shots without it, but it might depend on settings. The Canon manual is very non-specific, it just says that processing time may be required for longer exposures.

mbf_az

Dark Frame Subtraction test results:

Using g7x-100d-1.5.0-4827-full_ALPHA.
The only CHDK feature I enabled was "Override TV, LongExp".
All other settings were established using the Canon menus.
I tested in both P and M modes. ISO seems to be the only driving factor.
Using times in whole seconds only, these are the times at which Dark Frame Subtraction began. Times less than those shown did not cause Dark Frame Subtraction.

ISO - Time in seconds
125 - 36
200 - 36
400 - 36
800 - 18
1600 - 5
3200 - 5
6400 - 5
12800 - 5

I hope this is helpful.
As always, thank you for your efforts.

reyalp

mbf_az
Dark Frame Subtraction test results:

Thanks, that was very helpful. I added dark frame control support in build 4841.

In my testing, I found sensor temperature was factor too, I had to use 20 seconds to be sure to get a dark frame at ISO3200, but after it ran for a while it was triggered at shorter times.

mbf_az

Thanks for (letting me turn off) Dark Frame Subtraction! That was really fast.
I have not tested it extensively, but it works on a few simple tests. I look forward to using it out in the field on the next new moon.

000gui

It seems that the G7 X has well progressed and is almost final.
As the G7 X and the G5 X share a lot of components, is there any chance that the G5 X will be ported anytime soon?

I don't know anything about porting but I would be happy to run tests to help debugging.

m4mmon

Hello,
First sorry if it has already been reported elsewhere, I am not sure this is G7 X specific: displaying grids does not seem to work properly, like if the screen was way too large for the grid specification, they do not occupy the screen as they should.Example, with "Rules & cross hairs" from standard CHDK distribution.
Example:

Should I start trying to tweak the grids, or should it be taken care of by CHDK code, independantly of screen size?

reyalp

m4mmon
Hello,
First sorry if it has already been reported elsewhere, I am not sure this is G7 X specific: displaying grids does not seem to work properly, like if the screen was way too large for the grid specification, they do not occupy the screen as they should.Example, with "Rules & cross hairs" from standard CHDK distribution.

This is a general problem with CHDK grids not knowing about different screen sizes. See https://chdk.setepontos.com/d/13239

It would be good to find a general solution, but for now you make your own grids for G7 X. The screen is 720x480

m4mmon

Thank you for your quick reply.I managed to do it, in case someone is interested, here are the converted standard CHDK grids.I used a crude conversion rule, but I do not think it is noticeable.

grids_720x480.zip

4.6KB

hiker_jon

Hi,
Some G7X observations. I love the camera, but realize that perhaps Canon released it before getting all the bugs out of it. Has anyone noticed that:
1. The camera software can crash if you turn off the camera too soon after taking a picture.
2. Sometimes the camera does not respond to half-press. Could be hardware, but I have seen this reported elsewhere.
3. A hardware issue is that the in and out of the lens can suck dust into the lens. This has happened to me. Can't get it repaired because Canon will replace it with a Mark II to which CHDK has not been ported.

Jon

hiker_jon

Hi,
Question about software: In this camera when zoomed in on an image pressing the set button moves the image to the focus point. I would like to stop this behavior and substitute my own routine. Any idea how to do this? I know how to get the "set" key press, but how do I stop the Canon software?

Jon

reyalp

hiker_jon
1. The camera software can crash if you turn off the camera too soon after taking a picture.

I haven't noticed this, but I usually wait for the camera to finish doing what it's doing. Does this happen when not running CHDK?

2. Sometimes the camera does not respond to half-press. Could be hardware, but I have seen this reported elsewhere.

I've found the half press to be a bit finicky, but I'm not sure I would describe it as not responding to half press.

Another issue I've noticed is that clicking the power or playback button very quickly doesn't always boot the camera. This happens on my camera without CHDK.

Question about software: In this camera when zoomed in on an image pressing the set button moves the image to the focus point. I would like to stop this behavior and substitute my own routine. Any idea how to do this? I know how to get the "set" key press, but how do I stop the Canon software?

Are you trying to do this in your own C code, in script or ???

In alt mode, CHDK prevents physical key presses from reaching the canon firmware, so you might want to look at how that is done (mostly core/kbd_common.c kbd_update_key_state)

You can also write a script that listens for key presses and generates different either passes them through to the canon firmware or generates other key presses. My contae script is an example of this http://chdk.wikia.com/wiki/Lua/Scripts:_Continuous_Autoexposure (search for -- keyboard module in the source)

hiker_jon

Thanks for the answers. Here are my replies.
1. Happens when not running CHDK. I have two cameras, happens in both. Not all the time, though. Randomly and rarely. Camera is dead with lens out. You have to repeatedly press power and play to get it to reboot (or remove the batteries).
2. When it happens half press does not work. You cannot focus the camera. This can last for a while then mysteriously it goes away.

Set button when zoomed: I am writing c-code, but have limited understanding of CHDK. I've looked at core/kbd_common.c and kbd_update_key_state, but have no clue how it works or where alt mode is tested and how the key press is ignored in that mode. Is it the return value of kbd_process?
I want to only ignore the set button when in play or in review mode.

reyalp

hiker_jon
1. The camera software can crash if you turn off the camera too soon after taking a picture.

I haven't noticed this, but I usually wait for the camera to finish doing what it's doing. Does this happen when not running CHDK?

2. Sometimes the camera does not respond to half-press. Could be hardware, but I have seen this reported elsewhere.

I've found the half press to be a bit finicky, but I'm not sure I would describe it as not responding to half press.

Another issue I've noticed is that clicking the power or playback button very quickly doesn't always boot the camera. This happens on my camera without CHDK.

Question about software: In this camera when zoomed in on an image pressing the set button moves the image to the focus point. I would like to stop this behavior and substitute my own routine. Any idea how to do this? I know how to get the "set" key press, but how do I stop the Canon software?

Are you trying to do this in your own C code, in script or ???

In alt mode, CHDK prevents physical key presses from reaching the canon firmware, so you might want to look at how that is done (mostly core/kbd_common.c kbd_update_key_state)

You can also write a script that listens for key presses and generates different either passes them through to the canon firmware or generates other key presses. My contae script is an example of this http://chdk.wikia.com/wiki/Lua/Scripts:_Continuous_Autoexposure (search for -- keyboard module in the source)

reyalp

hiker_jon
1. Happens when not running CHDK. I have two cameras, happens in both. Not all the time, though. Randomly and rarely. Camera is dead with lens out. You have to repeatedly press power and play to get it to reboot (or remove the batteries).

I have not experienced this. What canon firmware versions do your cameras have?

2. When it happens half press does not work. You cannot focus the camera. This can last for a while then mysteriously it goes away.

Or this. Possibly mode / settings dependent?

Set button when zoomed: I am writing c-code, but have limited understanding of CHDK. I've looked at core/kbd_common.c and kbd_update_key_state, but have no clue how it works or where alt mode is tested and how the key press is ignored in that mode. Is it the return value of kbd_process?

Yes, the return value of kbd_process tells it whether the keyboard should be blocked (this doesn't exactly correspond to "alt" mode, but close enough). If it is, then the key mask is used to force the bits in kbd_new_state into the unpressed state, and then combined with the values in override state (for scripted keypresses etc)

If you simply wanted to hide the set button, you could just OR that bit value into the appropriate bit in physw_status.

Michel2e

If I can share, some comments hereunder

hiker_jon
Has anyone noticed that:
1. The camera software can crash if you turn off the camera too soon after taking a picture.

this never happened using Canon with no chdk, but I rarely turn off quickly

2. Sometimes the camera does not respond to half-press. Could be hardware, but I have seen this reported elsewhere.

Yes I've noticed this a couple of times camera in hands.
additionnally, using camera with script (SDM) for kap, sometimes the camera crashes for unknown reasons. (approx once every 200 shots), maybe at this phase because it uses to happen more often when using the get_shooting script command. I've banned this command.

3. A hardware issue is that the in and out of the lens can suck dust into the lens. This has happened to me. Can't get it repaired because Canon will replace it with a Mark II to which CHDK has not been ported.

Had the same trouble, occasionnally.
additionnaly sometimes the lens is blocked mid position. So far on/off restarts.

Michel

« Previous Page Next Page »