Improving CHDK ND filter support

waterwingz

G10 1.03c

ndtest.csv

4.07KB

koshy

reyalp
Hmm, I would have expected it to be a 0 = ND out, 1 = ND in. Perhaps propset one doesn't have a prop for ND. https://chdk.fandom.com/wiki/PropertyCase lists 100 as custom WB.

Played with it some more, 100 and 101 vary, no on/off 0/1 kind of change.

reyalp

koshy
So, that works. Some voltage on the cable does wonders 😉
The ND test fails as posted.

The ndtest fails because the remote hook times out. 😐:

Did you have "enable sync" set in the remote test? The non-sync remote works without the hook.

With settings
Switch type: One push
Control Mode: Normal
Enable Sync: (*)

If the remote hook is working correctly, the behavior will be
+5V on, camera goes through half press, screen probably goes black, waits (up to 10s)
+5V off, shoots

If the hook isn't called, it will shoot as soon as the +5 goes on.

koshy
Played with it some more, 100 and 101 vary, no on/off 0/1 kind of change.

OK, thanks. Seems like propset 1 doesn't have a ND prop.

philmoz

IXUS 310 (Elph 500) HS - after fixing the issue in quick mode.

ndtest-ixus310.csv

4.01KB

reyalp

philmoz
IXUS 310 (Elph 500) HS - after fixing the issue in quick mode.

Great, thanks. That's one of two Ixus that appear to actually have both ND and iris. The other is ixus300_sd4000. The manuals for both of these mention an "ND" message that can appear in a section called "what if". Ixus 310 (but not 300) also mentions it in the aperture specs.

With your and waterwingz results, only 4 ND+iris cams are untested.
~~G11~~
G15
G9
~~S110~~

We don't necessarily need them all, just noting what's left.

All seem to have the "port needs ND in shoot hook for quick" issue. G7 also requires it in cont.

c_joerg

reyalp
[With your and waterwingz results, only 4 ND+iris cams are untested.
G11
G15
G9
S110

S110 und G1x attached.
Do you need some runs of my other cameras?

ndtest_S110_103a.csv

3.98KB

ndtest_G1x_100e.csv

4.03KB

koshy

reyalp
Did you have "enable sync" set in the remote test? The non-sync remote works without the hook.

No did not have it set. With it unset 5V on half press / LED keeps blinking however long it takes, even minutes / 5V off shoot.
With it being set 5V on shoots directly. Apart from "enable sync" settings as seen in screen shot.

koshy

reyalp
With your and waterwingz results, only 4 ND+iris cams are untested.
G9

Seeing that my mind just said, hey you got one of those! To compare something with Canon RAW / CHDK DNG the other year I don't quite recall (and eventually I didn't even do it). So, I'll see where that G9 is and will finally put it to some other use I guess.

Edit: Found it, result attached.

ndtest_g9-100d-1.5.0-5249-full.csv

4.09KB

koshy

reyalp
Results for the others are good if you can test them, but definitely not urgent.
We have really good coverage by normal CHDK standards 😀

Advancing on to incredible coverage it seems with all the tests of the newer models from the others.
Anyway, before I forget here are those 4 more As...

4_new_As.7z

3.41KB

reyalp

Thanks everyone 😀

I updated the list on https://chdk.setepontos.com/d/13228/167

@koshy:
Can you try the attached build on G9?

For A530, your result confirms the remote hook still isn't being called, I'll need to look at that some more.

c_joerg
Do you need some runs of my other cameras?

I don't think so, none of the others mentioned in your sig have an ND. Thanks.

g9-100d-1.5.0-5249-reyalp-ndtest-1.zip

808.98KB

koshy

reyalp
@koshy:
Can you try the attached build on G9?

Sure

ndtest_g9-100d-1.5.0-5249-reyalp-ndtest-1.csv

4.06KB

koshy

reyalp

koshy
a3000 is missing here, also Dry r43 but we didn't test it yet.

Hmm, I have a3000 recorded as tested, but perhaps it was a mistake.

Here we go on that one.

ndtest_a3000-100d-1.5.0-5249-full.csv

5.03KB

Caefix

{=) Found again & CHIMPed & tested ixus160

--[[
@title ND_test.Lua
@subtitle :...,....1....,....2....,....3....,....4....,....5
@param N ND AUS ein
@values N AUS ein
]]--

for i=1,9 do
set_nd_filter(1+i%2)
click("shoot_half")
print (i,-get_av96(),-get_tv96())
wait_click(999)
sleep(999) end
set_nd_filter(2-(N or 2)%2)
sleep(999)

This miniscript returns !=0 only after a shot here.
There are 2 groups of cams...

PS: Have done a rerun with SX610 just for fun.
... same group.

ndtest-IXUS160_ELPH160-100a-CHDK_DE-1.5.0-5249.zip

2.14KB

ndtest-SX610HS-100a-CHDK_DE-1.5.0-5249-12967.csv

16.26KB

reyalp

@koshy I think I found my mistake in the last A530 build. Please try this one. Thanks

a530-100a-1.5.0-5250-reyalp-remote-test-2.zip

855.2KB

reyalp

Caefix
{=) Found again & CHIMPed & tested ixus160

Thanks.

I'm not clear about the script. Does this show some problem?

Note in Lua, the code

set_nd_filter(2-(N or 2)%2)

probably doesn't do what you want. Only nil and false are false, so "N or 2" is always N (since N is a menu param in this script).

koshy

reyalp
@koshy I think I found my mistake in the last A530 build. Please try this one. Thanks

Nice work, that gets it. USB remote now works as it should - with synch enabled. 5V on: half press, black screen for like 10 sec, 5V off during that period shoots. ND test attached.

ndtest_a530-100a-1.5.0-5250-reyalp-remote-test-2.csv

5.29KB

Caefix

🤣 Ixus145...

Aye, a fast script once written for some trouble of the day, no literature.
Intention: Watching, feeling, hearing the cam & ND work.
I expected as a sideeffect updated values in print() after "click",
but I seem to get 0 or the values of the last shot.
Btw.: I feel a reaction at 'ND not enabled port' SX700e.

ndtest-IXUS145_ELPH135-100c-CHDK_DE-1.5.0-5250.csv

5.18KB

reyalp

Caefix
Ixus145...

Thanks again 😀

Aye, a fast script once written for some trouble of the day, no literature.
Intention: Watching, feeling, hearing the cam & ND work.
I expected as a sideeffect updated values in print() after "click",

Normally, Canon firmware doesn't known about ND override, so get_tv96 shouldn't change (maybe a little if Canon auto-exposure comes out different, but not because of ND). get_av96 also usually won't change in current CHDK, except on ports like elph175_elph180 that set the prop. In the in the future, more ports will probably do this.

Btw.: I feel a reaction at 'ND not enabled port' SX700e.

Yes, this camera almost certainly does not have ND. SX710 100% for sure doesn't and appears to be the same optics.

Caefix

...SX710.
Yes - no ND, I would "see" it, but set_nd is not ignored, thereÂ´s a vibration in the lens.
Maybe aperture reacts, shouldnÂ´t that be another statement?

reyalp

Caefix
Yes - no ND, I would "see" it, but set_nd is not ignored, thereÂ´s a vibration in the lens.
Maybe aperture reacts, shouldnÂ´t that be another statement?

Yes, on most cameras without ND, the Canon "ND" functions still exist and aperture to minimum / maximum. See https://chdk.setepontos.com/d/13228/39

However, current SX700 builds should have the ND functions disabled since r4974. Maybe you're using an old build?

« Previous Page Next Page »