EOS M3 porting - page 60 - DryOS Development - CHDK Forum

EOS M3 porting

  • 696 Replies
  • 301890 Views
*

Offline Ant

  • ****
  • 491
Re: EOS M3 porting
« Reply #590 on: 20 / July / 2019, 13:14:49 »
Advertisements
Here you can try simple patch allowing to get DoF values(Subject distance) from EF lens. Not tested on fw 120F

Re: EOS M3 porting
« Reply #591 on: 20 / July / 2019, 13:22:11 »
@Ant

Thanks...but not much help to me :-(
Can't compile CHDK.
I'm 'just' a Lua scripting guy ;-)
Also replacement M3 doesn't arrive until Monday, hence don't know FW version.


Re: EOS M3 porting
« Reply #592 on: 21 / July / 2019, 05:13:11 »
@c_joerg

Don’t know if you can throw some light on this question.

When, for example, I use FocusSearchNear, to move from the current position to the macro end of the lens, is there a way to find out how many steps the lens took?

Knowing this will allow me to move back to the start position, as I use MoveFocus, ie by keeping track of the steps.

*

Offline Ant

  • ****
  • 491
Re: EOS M3 porting
« Reply #593 on: 21 / July / 2019, 05:39:39 »
AFAIK after receiving(executing) commands like FocusSearchNear the position counter in the lens is reset to 0.


Re: EOS M3 porting
« Reply #594 on: 21 / July / 2019, 06:20:41 »
:-(

As I feared.

Re: EOS M3 porting
« Reply #595 on: 23 / July / 2019, 02:13:59 »
@c_joerg

Replacement M3 arrived and experimentation restarted  :)

First observation is that call_event_proc("EFLensCom.FocusSearchNear") requires a much longer sleep than MoveFocus, ie to get repeatable upper and lower focus values.

With MoveFocus I find I can 'get away' with sleep(15), ie 15 microseconds. If I use, say, 5, then the upper and lower values vary from run to run.

With FocusSearchNear I need to multiple the sleep by, say, 20, ie get up to 300.

The above observation is from simply repeating my test script, ie move to near then to a stated focus, ie upper, say, greater than the requested distance.

Knowing the above, I can now move on to the next stage and write a demo focus bracketing script.

« Last Edit: 23 / July / 2019, 02:35:47 by pigeonhill »

*

Offline c_joerg

  • *****
  • 1157
Re: EOS M3 porting
« Reply #596 on: 23 / July / 2019, 03:57:10 »
First observation is that call_event_proc("EFLensCom.FocusSearchNear") requires a much longer sleep than MoveFocus, ie to get repeatable upper and lower focus values.

That probably also depends on the last position. The worst case is when you go from far to near.

With MoveFocus I find I can 'get away' with sleep(15), ie 15 microseconds.

Sleep is milliseconds.


With FocusSearchNear I need to multiple the sleep by, say, 20, ie get up to 300.

I would go at least to 1s…but only an estimate…
M100 100a, M3 101a, G9x II (1.00c), 2*G1x (101a,100e), S110 (103a), SX50 (100c), SX230 (101a), S45,
Flickr https://www.flickr.com/photos/136329431@N06/albums
YouTube https://www.youtube.com/channel/UCrTH0tHy9OYTVDzWIvXEMlw/videos?shelf_id=0&view=0&sort=dd

Re: EOS M3 porting
« Reply #597 on: 23 / July / 2019, 07:31:19 »

@c_joerg


 ;) I meant milli seconds :-[





Re: EOS M3 porting
« Reply #598 on: 24 / July / 2019, 01:26:26 »
@c_joerg

In your experiments did you see any difference in response when changing speed in MoveFocus?
I tried to see a difference and can't, ie speed = 0 works OK.

*

Offline c_joerg

  • *****
  • 1157
Re: EOS M3 porting
« Reply #599 on: 24 / July / 2019, 02:04:49 »
In your experiments did you see any difference in response when changing speed in MoveFocus?

I have not done very much but could not see any differences.

I tried to see a difference and can't, ie speed = 0 works OK.

I never checked 0. Only values between 1-255.
May be 0 is slowest possible speed.
Is there any functionality in ML to control the speed?
 
M100 100a, M3 101a, G9x II (1.00c), 2*G1x (101a,100e), S110 (103a), SX50 (100c), SX230 (101a), S45,
Flickr https://www.flickr.com/photos/136329431@N06/albums
YouTube https://www.youtube.com/channel/UCrTH0tHy9OYTVDzWIvXEMlw/videos?shelf_id=0&view=0&sort=dd

 

Related Topics