Canon G7X Mark II CHDK

philmoz

3450

Re: Canon G7X Mark II CHDK

« Reply #10 on: 26 / December / 2021, 21:57:52 »

Advertisements

Quote from: tribomber on 26 / December / 2021, 18:29:44

Attached are two ROMLOGs.
-- ROMLOG17 - MF at infinity. Mode P. scripted set_focus 65530. Crash.
-- ROMLOG18 - MF at infinity. Mode P. scripted set_aflock 1. Crash.

If you can provide a minimal script that crashes, or let us know which script you are using (with what settings), it will help to investigate.

Once I can reproduce it the problem will be easier to address.

Phil.

Logged

CHDK ports:
sx30is (1.00c, 1.00h, 1.00l, 1.00n & 1.00p)
g12 (1.00c, 1.00e, 1.00f & 1.00g)
sx130is (1.01d & 1.01f)
ixus310hs (1.00a & 1.01a)
sx40hs (1.00d, 1.00g & 1.00i)
g1x (1.00e, 1.00f & 1.00g)
g5x (1.00c, 1.01a, 1.01b)
g7x2 (1.01a, 1.01b, 1.10b)

tribomber

9

Re: Canon G7X Mark II CHDK

« Reply #11 on: 27 / December / 2021, 16:55:44 »

Thanks so much for the interest and help. Attached are two scripts. They were indeed "minimal" as you asked...I whittled them down from others as I began to isolate the problem. focus_check2.bas produced ROMLOG17 and focus_check3.bas produced ROMLOG18.

focus_check2.bas (5.32 kB - downloaded 9 times.)

focus_check3.bas (5.32 kB - downloaded 8 times.)

Logged

philmoz

3450

Re: Canon G7X Mark II CHDK

« Reply #12 on: 28 / December / 2021, 01:48:57 »

Quote from: tribomber on 27 / December / 2021, 16:55:44

Thanks so much for the interest and help. Attached are two scripts. They were indeed "minimal" as you asked...I whittled them down from others as I began to isolate the problem. focus_check2.bas produced ROMLOG17 and focus_check3.bas produced ROMLOG18.

Both of those scripts run on my G7X2 without any crash. As posted neither script does very much as many calls are commented out and they both end early (via 'end' statement).

I played with the focus_check2.bas script a bit, uncommenting lines and moving the 'end' statement to later - still no crashes, and the subject distance gets set correctly (-1 for infinity).

Logged

CHDK ports:
sx30is (1.00c, 1.00h, 1.00l, 1.00n & 1.00p)
g12 (1.00c, 1.00e, 1.00f & 1.00g)
sx130is (1.01d & 1.01f)
ixus310hs (1.00a & 1.01a)
sx40hs (1.00d, 1.00g & 1.00i)
g1x (1.00e, 1.00f & 1.00g)
g5x (1.00c, 1.01a, 1.01b)
g7x2 (1.01a, 1.01b, 1.10b)

tribomber

9

Re: Canon G7X Mark II CHDK

« Reply #13 on: 28 / December / 2021, 07:30:58 »

Quote from: tribomber on 27 / December / 2021, 16:55:44

Both of those scripts run on my G7X2 without any crash. As posted neither script does very much as many calls are commented out and they both end early (via 'end' statement).

Yes, the "not doing very much" and "ending early" are deliberate. Both scripts were cut down from earlier scripts that were trying to do more...much of which remains at the tail of these scripts either commented out or after the end command. Yet even so, on my camera, those short scripts crash the camera...as have those same commands in longer, more involved scripts.

Beyond that, it's interesting to hear that your camera does not crash. Could there be some settings I have amiss or other such configuration? Earlier in this thread I listed the setting used that I thought were pertinent. Perhaps there are others?

Regardless of how much time you and others care to invest in this, I do thank you for your help thus far. I will continue testing and experimenting.

Logged

Caefix

945
Sorry, busy deleting test shots...

Re: Canon G7X Mark II CHDK

« Reply #14 on: 28 / December / 2021, 10:02:30 »

Quote from: tribomber on 28 / December / 2021, 07:30:58

Earlier in this thread I listed the setting used that I thought were pertinent. Perhaps there are others?

Cam looses settings when crash happens before cam was rebooted, maybe an unwanted reactivated?

... Script 2 calls set_focus without AFL, ... not recommended.

Script 3 only sets set_af_lock 1 .

Maybe cam is already in AFL and a 2nd call confuses something?

Btw.: A nice feature of ubasic:

Each run of a script leaves values X=?, following runs continue calculating with this values if not (re)set to default or in header.

« Last Edit: 28 / December / 2021, 10:36:39 by Caefix »

Logged

All lifetime is a loan from eternity.

srsa_4c

4451

Re: Canon G7X Mark II CHDK

« Reply #15 on: 28 / December / 2021, 10:39:49 »

Quote from: tribomber on 26 / December / 2021, 18:29:44

Attached are two ROMLOGs.
-- ROMLOG17 - MF at infinity. Mode P. scripted set_focus 65530. Crash.
-- ROMLOG18 - MF at infinity. Mode P. scripted set_aflock 1. Crash.

Both logs show a failed assert in the ClearEventFlag fw function, which was called by MoveFocusLensToDistance. It seems the init_required_fw_features() workaround is missing from the 1.5 branch version of this port.
The trunk (1.6) version should work normally.

Logged

philmoz

3450

Re: Canon G7X Mark II CHDK

« Reply #16 on: 28 / December / 2021, 18:28:32 »

Quote from: srsa_4c on 28 / December / 2021, 10:39:49

Quote from: tribomber on 26 / December / 2021, 18:29:44
Attached are two ROMLOGs.
-- ROMLOG17 - MF at infinity. Mode P. scripted set_focus 65530. Crash.
-- ROMLOG18 - MF at infinity. Mode P. scripted set_aflock 1. Crash.
Both logs show a failed assert in the ClearEventFlag fw function, which was called by MoveFocusLensToDistance. It seems the init_required_fw_features() workaround is missing from the 1.5 branch version of this port.
The trunk (1.6) version should work normally.

Thanks srsa_4c.

@tribomber - I would recommend using the 1.6 version (http://mighty-hoernsche.de/trunk/download_trunk.htm) as there are a number of other improvements for the G7X2 that are not in the 1.5 version.

You can also try the version with the new display drawing code that pretty much eliminates the flickering of the CHDK UI, it is otherwise identical to the 1.6 version. The downloads for this are at https://drive.google.com/drive/folders/1drk1xi6kMMIeF5xSqXgnpjGCffF8CVkd?usp=sharing

Logged

CHDK ports:
sx30is (1.00c, 1.00h, 1.00l, 1.00n & 1.00p)
g12 (1.00c, 1.00e, 1.00f & 1.00g)
sx130is (1.01d & 1.01f)
ixus310hs (1.00a & 1.01a)
sx40hs (1.00d, 1.00g & 1.00i)
g1x (1.00e, 1.00f & 1.00g)
g5x (1.00c, 1.01a, 1.01b)
g7x2 (1.01a, 1.01b, 1.10b)

tribomber

9

Re: Canon G7X Mark II CHDK

« Reply #17 on: 28 / December / 2021, 18:41:55 »

Thanks reyalp, srsa_4c, and philmoz. I was scratching my head about why I used 1.5.1 if 1.6 was available. Just went back and looked and saw that 1.5.1 is listed as "stable" while 1.6 is listed as "dev." Regardless, I will try 1.6 and the non-flickering version at that. Might not get it done for another day or two, but I will update how it goes. Again, thanks so much to everyone for helping me through this.

Logged

tribomber

9

Re: Canon G7X Mark II CHDK

« Reply #18 on: 28 / December / 2021, 20:12:02 »

I figured I'd share some old videos created from long-duration, CHDK scripted, time-lapse photos at 30-minute intervals on my Canon G12. The G12 is what I intend to replace with the G7X2 at the start of 2022 and why I'm eager to ensure CHDK scripts work well with the G7X2. The camera is suction-cupped against the glass overlooking a beautiful spot on the upper Mississippi River in Brainerd, Minnesota, USA.

A video with 30-minutes images for several days - late Dec 2012 to early Jan 2013:

A video with noon photos from every day of 2013:

A video a friend made (I don't have the expertise) from my 2019 SD card with EVERY photo (still at 30 minute intervals) except those with less than x amount of light. In other words, the DAYTIME photos. This one runs long and fast:

I look forward to replacing my tired, workhorse G12 with the G7X2 and continuing to capture long-term time-lapse photos...and maybe making videos...for years to come. The river is a living, changing thing, and I love capturing it with its seasonal and yearly changes. Much thanks to those who enable that.

Logged

tribomber

9

Re: Canon G7X Mark II CHDK

« Reply #19 on: 30 / December / 2021, 17:54:34 »

Quote from: tribomber on 28 / December / 2021, 18:41:55

I will try 1.6 and the non-flickering version at that. Might not get it done for another day or two, but I will update how it goes. Again, thanks so much to everyone for helping me through this.

Yep, working! Thanks all!

Logged