M3 etc focus move - page 2 - General Help and Assistance on using CHDK stable releases - CHDK Forum supplierdeeply

M3 etc focus move

  • 48 Replies
  • 1047 Views
*

Offline Caefix

  • *****
  • 856
  • Sorry, busy deleting test shots...
Re: M3 etc focus move
« Reply #10 on: 27 / June / 2022, 12:47:01 »
Advertisements
Attached ROMLOG.LOG from Crash

Code: [Select]
ASSERT!! BrtMthd.c Line 4060
...
00226890: UI:LogicalEvent:0x000011b1:adr:0,Para:0
00227000: UI:LogicalEvent:0x000011b1:adr:0,Para:0
00227110: UI:LogicalEvent:0x000011b1:adr:0,Para:0
00227220: UI:LogicalEvent:0x000011b1:adr:0,Para:0
00227330: UI:LogicalEvent:0x000011b1:adr:0,Para:0
00227440: UI:LogicalEvent:0x000011b1:adr:0,Para:0
00227550: UI:LogicalEvent:0x000011b1:adr:0,Para:0
   
ThereĀ“s a 110 rhythm in it, might be flamenco...  :-*
All lifetime is a loan from eternity.

*

Offline c_joerg

  • *****
  • 1220
Re: M3 etc focus move
« Reply #11 on: 27 / June / 2022, 13:45:49 »
The value
Code: [Select]
FocusPosSize               : 0x1f
is that what we have already seen here:
https://chdk.setepontos.com/index.php?topic=13756.msg140157#msg140157

Only 31 distance values from near to far...
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: M3 etc focus move
« Reply #12 on: 27 / June / 2022, 14:02:08 »
The value
Code: [Select]
FocusPosSize               : 0x1f
is that what we have already seen here:
https://chdk.setepontos.com/index.php?topic=13756.msg140157#msg140157

Only 31 distance values from near to far...

@c_joerg

I remember you did a lot of work looking at the 'resolution' of the Canon focus return, eg only in cm and not many of them.

I hope we find a way to at least count the steps between moves. This way we will at least be able to estimate the inbetween distances.

Fingers crossed ;-)

BTW this is what I do in my bracketing script, ie step forward until I've gone past where I wish to move to, take note of the focus position either side, ie where the Canon return changes, and step back using a simple linear interpolation. Crude maybe: but the best I can do at the moment.

Cheers

Garry

Cheers

Garry

*

Offline Caefix

  • *****
  • 856
  • Sorry, busy deleting test shots...
Re: M3 etc focus move
« Reply #13 on: 27 / June / 2022, 15:03:22 »
The value
Code: [Select]
FocusPosSize               : 0x1f
is that what we have already seen here:
https://chdk.setepontos.com/index.php?topic=13756.msg140157#msg140157

Only 31 distance values from near to far...

Cheers

Garry

and
:) M3M10M100_Focus.lua log told me, that fdl and fdu always change together to
former fdu = newer fdl.
All lifetime is a loan from eternity.


*

Offline srsa_4c

  • ******
  • 4450
Re: M3 etc focus move
« Reply #14 on: 27 / June / 2022, 16:20:50 »
Attached ROMLOG.LOG from Crash
I also got an assert (after half-shoot) on M100 while following the instructions, also BrtMthd.c. The cause might be prior execution of FA.Create and/or InitializeAdjustmentSystem.

*

Offline reyalp

  • ******
  • 13723
Re: M3 etc focus move
« Reply #15 on: 27 / June / 2022, 17:32:55 »
Attached ROMLOG.LOG from Crash
I also got an assert (after half-shoot) on M100 while following the instructions, also BrtMthd.c. The cause might be prior execution of FA.Create and/or InitializeAdjustmentSystem.
Yes, InitializeAdjustmentSystem seems to cause instability on a lot of cams. You could probably call the function directly, I used the eventproc names so it didn't depend on cam/firmware version.

Thanks all for testing.
The value
Code: [Select]
FocusPosSize               : 0x1f
is that what we have already seen here:
https://chdk.setepontos.com/index.php?topic=13756.msg140157#msg140157

Only 31 distance values from near to far...
Thanks for pointing that out. Does seem like not very many...

Presumably ZoomPosSize also gives the number of zoom steps reported back to the firmware.

Can someone confirm if GetEFLensFocusPositionWithoutLensCom and GetEFLensFocusPositionWithLensCom return the same value as FocusPos? You should be able to just do like
Code: [Select]
print(call_event_proc('GetEFLensFocusPositionWithoutLensCom'))
print(call_event_proc('GetEFLensFocusPositionWithLensCom'))
If it returns -1, then it might need the FA.Create and/or InitializeAdjustmentSystem

I assume *WithLensCom* directly queries the lens, while the other uses some cached value. It might be useful to know when they differ.
Don't forget what the H stands for.

*

Offline c_joerg

  • *****
  • 1220
Re: M3 etc focus move
« Reply #16 on: 28 / June / 2022, 01:13:16 »
Attached ROMLOG.LOG from Crash
I also got an assert (after half-shoot) on M100 while following the instructions, also BrtMthd.c. The cause might be prior execution of FA.Create and/or InitializeAdjustmentSystem.

I haven't had a crash when using a script. Maybe coincidence
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

*

Offline Caefix

  • *****
  • 856
  • Sorry, busy deleting test shots...
Re: M3 etc focus move
« Reply #17 on: 28 / June / 2022, 12:10:52 »
Code: [Select]
--[[
@title AdjLog_1
@chdk_version 1.4
--]]

call_event_proc('FA.Create')
call_event_proc('StartLogOut',-2,0x1000,0)
call_event_proc('InitializeAdjustmentSystem')
call_event_proc('PrintFALensInfoData')
call_event_proc('GetEFLensFocusPositionWithoutLensCom')
call_event_proc('GetEFLensFocusPositionWithLensCom')
call_event_proc('OutputLogToFile')
--call_event_proc('TerminateAdjustmentSystem')
Code: [Select]

Firmware Ver GM1.10D
Mar 18 2016  08:31:04

---- FA LensInfo ---
 LensID                     : 0x1039
 FocalLength                : 0015 [mm]
 FL_Wide                    : 0015 [mm]
 FL_Tele                    : 0045 [mm]
 AbsDisFar                  : 0034 [cm]
 AVEF                       : 0x25
 AVO                        : 0x25
 AVMAX                      : 0x50
 LensType (0:EF 1:EFM)      : 0x1
 ExtenderType (0xFF:Non)    : 0xff
 PO                         : 0x23
 PO 0                       : 0x116
 PO 5                       : 0x102
 PO 10                      : 0x112
 PO 15                      : 0x10
 ZoomPos                    : 0x3f
 ZoomPosSize                : 0x3f
 FocusPos                   : 0x1a
 FocusPosSize               : 0x1f
--------------------

EFLens FocusPosition  : 37
EFLens FocusPosition  : 37

 FileName A/AdjLog.txt

 BuffSize 4096



Firmware Ver GM1.10D
Mar 18 2016  08:31:04

---- FA LensInfo ---
 LensID                     : 0x1039
 FocalLength                : 0024 [mm]
 FL_Wide                    : 0015 [mm]
 FL_Tele                    : 0045 [mm]
 AbsDisFar                  : 65535 [cm]
 AVEF                       : 0x2a
 AVO                        : 0x2a
 AVMAX                      : 0x55
 LensType (0:EF 1:EFM)      : 0x1
 ExtenderType (0xFF:Non)    : 0xff
 PO                         : 0x36
 PO 0                       : 0xba
 PO 5                       : 0xaf
 PO 10                      : 0xb4
 PO 15                      : 0xb9
 ZoomPos                    : 0x23
 ZoomPosSize                : 0x3f
 FocusPos                   : 0x0
 FocusPosSize               : 0x1f
--------------------

EFLens FocusPosition  : 0
EFLens FocusPosition  : 0
37 before, 0 after a shoot_half.  :-[
Edit: Script crashing when run twice or WITH shoot_half after first run. (BrtMthd.c)

Edit2: The crashing shoot_half were manually in non<Alt>...
With these lines appended it seems not to crash.
Quote
press("shoot_half")
sleep(2000)
release("shoot_half")
call_event_proc('TerminateAdjustmentSystem')
« Last Edit: 28 / June / 2022, 13:31:27 by Caefix »
All lifetime is a loan from eternity.


*

Offline c_joerg

  • *****
  • 1220
Re: M3 etc focus move
« Reply #18 on: 28 / June / 2022, 15:54:00 »
Can someone confirm if GetEFLensFocusPositionWithoutLensCom and GetEFLensFocusPositionWithLensCom return the same value as FocusPos? You should be able to just do like
Code: [Select]
print(call_event_proc('GetEFLensFocusPositionWithoutLensCom'))
print(call_event_proc('GetEFLensFocusPositionWithLensCom'))
If it returns -1, then it might need the FA.Create and/or InitializeAdjustmentSystem

I have always to call both, otherwise i got -1.

I am a bit confused. There were some inexplicable values. Sometimes with crashes.

The following script on M3 with 15-45

Code: [Select]
call_event_proc('FA.Create')
call_event_proc('InitializeAdjustmentSystem')

call_event_proc("EFLensCom.FocusSearchNear")
sleep(500)
print(call_event_proc('GetEFLensFocusPositionWithoutLensCom'))
print(call_event_proc('GetEFLensFocusPositionWithLensCom'))

call_event_proc("EFLensCom.MoveFocus",1,10)
sleep(500)
print(call_event_proc('GetEFLensFocusPositionWithoutLensCom'))
print(call_event_proc('GetEFLensFocusPositionWithLensCom'))

call_event_proc("EFLensCom.MoveFocus",10,10)
sleep(500)
print(call_event_proc('GetEFLensFocusPositionWithoutLensCom'))
print(call_event_proc('GetEFLensFocusPositionWithLensCom'))

call_event_proc("EFLensCom.MoveFocus",10,10)
sleep(500)
print(call_event_proc('GetEFLensFocusPositionWithoutLensCom'))
print(call_event_proc('GetEFLensFocusPositionWithLensCom'))


call_event_proc("EFLensCom.FocusSearchFar")
sleep(500)
print(call_event_proc('GetEFLensFocusPositionWithoutLensCom'))
print(call_event_proc('GetEFLensFocusPositionWithLensCom'))

give this results

Code: [Select]
-314
-314
-311
-311
-301
-301
-291
-291
633
633
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: M3 etc focus move
« Reply #19 on: 28 / June / 2022, 16:27:02 »
Can someone confirm if GetEFLensFocusPositionWithoutLensCom and GetEFLensFocusPositionWithLensCom return the same value as FocusPos? You should be able to just do like
Code: [Select]
print(call_event_proc('GetEFLensFocusPositionWithoutLensCom'))
print(call_event_proc('GetEFLensFocusPositionWithLensCom'))
If it returns -1, then it might need the FA.Create and/or InitializeAdjustmentSystem

I have always to call both, otherwise i got -1.

I am a bit confused. There were some inexplicable values. Sometimes with crashes.

The following script on M3 with 15-45

Code: [Select]
call_event_proc('FA.Create')
call_event_proc('InitializeAdjustmentSystem')

call_event_proc("EFLensCom.FocusSearchNear")
sleep(500)
print(call_event_proc('GetEFLensFocusPositionWithoutLensCom'))
print(call_event_proc('GetEFLensFocusPositionWithLensCom'))

call_event_proc("EFLensCom.MoveFocus",1,10)
sleep(500)
print(call_event_proc('GetEFLensFocusPositionWithoutLensCom'))
print(call_event_proc('GetEFLensFocusPositionWithLensCom'))

call_event_proc("EFLensCom.MoveFocus",10,10)
sleep(500)
print(call_event_proc('GetEFLensFocusPositionWithoutLensCom'))
print(call_event_proc('GetEFLensFocusPositionWithLensCom'))

call_event_proc("EFLensCom.MoveFocus",10,10)
sleep(500)
print(call_event_proc('GetEFLensFocusPositionWithoutLensCom'))
print(call_event_proc('GetEFLensFocusPositionWithLensCom'))


call_event_proc("EFLensCom.FocusSearchFar")
sleep(500)
print(call_event_proc('GetEFLensFocusPositionWithoutLensCom'))
print(call_event_proc('GetEFLensFocusPositionWithLensCom'))

give this results

Code: [Select]
-314
-314
-311
-311
-301
-301
-291
-291
633
633

@c_joerg I could get excited about the above as it looks reasonable to me, IF the following fits:

1. I'm not sure what focal length you ran the test at
2. I assume you started near the macro end and the counter was set at zero at that position
3. You then moved to the macro (near) end, by 314 steps, ie giving a count of -314
4, At the macro end the step count looks as if if hasn't 'stabilised', hence moving 10 didn't work out
5. Subsequent moves, by 10, appear to be stable
6. Finally you moved to the infinity end, ie steps from the start position being 633, ie 633+314 steps in total

But then again I could be 100% wrong ;-)
« Last Edit: 28 / June / 2022, 17:31:50 by pigeonhill »

 

Related Topics