EOS M3 porting - page 54 - DryOS Development - CHDK Forum supplierdeeply
« previous next »
Pages: 1 ... 49 50 51 52 53 [54] 55 56 57 58 59 ... 67   Go Down

EOS M3 porting

  • 665 Replies
  • 251828 Views
*

Offline c_joerg

  • *****
  • 1005
Re: EOS M3 porting
« Reply #530 on: 13 / July / 2019, 09:24:39 »
Advertisements
Quote from: pigeonhill on 13 / July / 2019, 08:40:04
Looking to up my Lua scripting experience with the EOSM family.
Could a kind EOSM3 user give me an update on where the EOSM3 CHDK rests at the moment, ie are things stable and is Lua accessible etc.


All my lua scripts are very stable on the EOS M3. I basically use them for time lapse. But also Focus Stacking works quite well
Logged
M100 100a, M3 101a, 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
*

Offline pigeonhill

  • *****
  • 543
Re: EOS M3 porting
« Reply #531 on: 13 / July / 2019, 09:38:47 »
@c_joerg


Many thanks for the confirmation.


BTW do know if CHDK Lua can drive the EOSM focus motors?
Logged
*

Offline c_joerg

  • *****
  • 1005
Re: EOS M3 porting
« Reply #532 on: 13 / July / 2019, 09:58:26 »
Quote from: pigeonhill on 13 / July / 2019, 09:38:47
BTW do know if CHDK Lua can drive the EOSM focus motors?
Do you mean EFM lens? Yes
https://chdk.setepontos.com/index.php?topic=13756.20
« Last Edit: 13 / July / 2019, 10:02:17 by c_joerg »
Logged
M100 100a, M3 101a, 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
*

Offline pigeonhill

  • *****
  • 543
Re: EOS M3 porting
« Reply #533 on: 13 / July / 2019, 10:10:22 »
@c_joerg

Fantastic!
Just purchased an M3 on Camera Jungle  :)
It's good to know you are an M3 user  ;)
Looking forward to scripting some of my 'stuff' on the M3, ie focus stacking script.
Cheers
Garry
« Last Edit: 13 / July / 2019, 10:18:39 by pigeonhill »
Logged
*

Offline pigeonhill

  • *****
  • 543
Re: EOS M3 porting
« Reply #534 on: 14 / July / 2019, 06:49:23 »
@c_joerg

Have taken a look at your script that logs the EOSM3 focus steps using call_event_proc("EFLensCom.MoveFocus",steps,speed): thanks for sharing.

While I wait for my ‘new’ M3 to arrive, I have a question that I hope you can answer.

I have not attempted to use call_event_proc("EFLensCom.MoveFocus",steps,speed) before, ie with my G7X or G1X; I wonder if using this proc call would be a better approach to controlling focus position than using set_focus(x).  What do you think?

Also, do I assume the standard set_focus(x) works on the M3?

Hope you can throw some education my way ;-)

Cheers

Garry
Logged
*

Offline c_joerg

  • *****
  • 1005
Re: EOS M3 porting
« Reply #535 on: 14 / July / 2019, 09:18:09 »
Quote from: pigeonhill on 14 / July / 2019, 06:49:23
I have not attempted to use call_event_proc("EFLensCom.MoveFocus",steps,speed) before, ie with my G7X or G1X; I wonder if using this proc call would be a better approach to controlling focus position than using set_focus(x).  What do you think?

 call_event_proc work only on EOS M, set_focus only on P&S cams.

 The problem with call_event_proc is that you can not enter absolute distances.

 The only distance information which you have is Focus Distance Upper und Lower in some very inaccurate steps.

 Download M3M10_Focus.lua at  Reply #30.


 I'm also not quite clear what impact the speed has.

Quote from: pigeonhill on 14 / July / 2019, 06:49:23
Also, do I assume the standard set_focus(x) works on the M3?

 No
« Last Edit: 14 / July / 2019, 09:23:26 by c_joerg »
Logged
M100 100a, M3 101a, 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
*

Offline pigeonhill

  • *****
  • 543
Re: EOS M3 porting
« Reply #536 on: 14 / July / 2019, 09:31:35 »
@c_joerg

Many thanks for the info.

Looks like I need to start learning how to use call_event_proc("EFLensCom.MoveFocus",steps,speed) to move the lens to a specified position that I calculate.

Cheers

Garry
Logged
*

Offline c_joerg

  • *****
  • 1005
Re: EOS M3 porting
« Reply #537 on: 14 / July / 2019, 09:40:23 »
Quote from: pigeonhill on 14 / July / 2019, 09:31:35
Looks like I need to start learning how to use call_event_proc("EFLensCom.MoveFocus",steps,speed) to move the lens to a specified position that I calculate.


I'm currently driving the focus manually to a specific position and then just moving a few steps forward for stacking. Ultimately, the interface to the EF lenses would have to be the same with an DSLR as with an EOS M. Everything that is possible with ML should also be possible with CHDK.
Logged
M100 100a, M3 101a, 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
*

Offline pigeonhill

  • *****
  • 543
Re: EOS M3 porting
« Reply #538 on: 14 / July / 2019, 09:50:19 »
@c_joerg

Thanks.

I’m assuming when calling call_event_proc("EFLensCom.MoveFocus",steps,speed) one can use positive and negative steps?

Also, what is the impact of using speed?

Also, when I looked at your tables for the 11-22 at 11mm, the data seem to indicate that there was no real advantage between using 1 or 10 steps, as the focus hadn’t moved when using multiple 10 steps. Or is it that the focus does actually change and only the reporting (upper and lower) remains fixed.

If the focus really does change, then using step = 1 should allow fine focus control.

Or am I expecting too much?
Logged
*

Offline c_joerg

  • *****
  • 1005
Re: EOS M3 porting
« Reply #539 on: 14 / July / 2019, 10:02:54 »
Quote from: pigeonhill on 14 / July / 2019, 09:50:19
I’m assuming when calling call_event_proc("EFLensCom.MoveFocus",steps,speed) one can use positive and negative steps?

Yes.
You can also use call_event_proc("EFLensCom.FocusSearchFar") and call_event_proc("EFLensCom.FocusSearchNear")

Quote from: pigeonhill on 14 / July / 2019, 09:50:19
Also, what is the impact of using speed?
I don’t know. May be you lose steps if the speed is to high-

Quote from: pigeonhill on 14 / July / 2019, 09:50:19
Also, when I looked at your tables for the 11-22 at 11mm, the data seem to indicate that there was no real advantage between using 1 or 10 steps, as the focus hadn’t moved when using multiple 10 steps. Or is it that the focus does actually change and only the reporting (upper and lower) remains fixed.
The real focus changes with every step, but not the distance information.

Quote from: pigeonhill on 14 / July / 2019, 09:50:19
If the focus really does change, then using step = 1 should allow fine focus control.

Yes the focus changes with every step…
« Last Edit: 14 / July / 2019, 10:05:40 by c_joerg »
Logged
M100 100a, M3 101a, 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
Pages: 1 ... 49 50 51 52 53 [54] 55 56 57 58 59 ... 67   Go Up
« previous next »
 

Related Topics