eos M10 port - page 31 - DryOS Development - CHDK Forum
supplierdeeply
« previous next »
Pages: 1 ... 26 27 28 29 30 [31] 32 33   Go Down

eos M10 port

  • 323 Replies
  • 217545 Views
*

Offline srsa_4c

  • ******
  • 4448
Re: eos M10 port
« Reply #300 on: 19 / December / 2020, 14:44:52 »
Advertisements
Quote from: riccardo on 14 / December / 2020, 08:48:22
I just did a quick try using the "update method", everything seems fine: took some pictures and videos without any problems.
Thanks for the feedback, I have enabled autobuild (trunk only for now).
Logged
*

Offline laasworld

  • *
  • 3
Re: eos M10 port
« Reply #301 on: 24 / March / 2022, 12:29:28 »
Hi! I'm a bit late to the party, but I just bought a used M10 from ebay. The initial plan was to use it for astrophotography but naturally I became interested in other topics and how to exploit the hardware for other uses, hence I stumbled across CHDK.

I was already running the firmware to v1.1.1a, though I see now the link to the firmware dumps (nice!). I'd like to report that the "trunk" auto-build version appears to work perfectly fine, besides the flicker which I already found the note about how to minimize. I've tested the motion detection and the interval scripts for now, but I'm a tinkerer so you may hear back from me about other aspects as either feedback or questions. I can also volunteer to test other things upon request.

Many thanks to those who have contributed to this project, it seems like an excellent addition to the native software! At less than €200 for a used kit, I'm overjoyed at the value of this thing and even more so with the help of CHDK =D
Logged
*

Offline c_joerg

  • *****
  • 1212
Re: eos M10 port
« Reply #302 on: 24 / March / 2022, 13:28:23 »
Quote from: laasworld on 24 / March / 2022, 12:29:28
At less than €200 for a used kit, I'm overjoyed at the value of this thing and even more so with the help of CHDK =D

The camera seems to be reasonably priced considering I paid for a new kit €222 once...
Logged
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 Mlapse

  • ****
  • 458
  • S95 S110
Re: eos M10 port
« Reply #303 on: 24 / March / 2022, 15:58:38 »
Quote from: laasworld on 24 / March / 2022, 12:29:28
Hi! I'm a bit late to the party,
it seems like an excellent addition to the native software

better late than never :)
i'd say chdk is the best investment canon never made.
Logged
frustration is a key ingredient in progress
*

Offline laasworld

  • *
  • 3
Re: eos M10 port
« Reply #304 on: 25 / March / 2022, 11:59:04 »
I'm not sure whether I'm missing anything, but I can report some extra findings from v1.1.1a, in case it's useful for anyone:
- the script from http://chdk.setepontos.com/index.php?topic=10864 has allowed me to confirm a very short motion detection delay down to ca. 50-130 ms without any tweaking except for the trigger threshold, based on a 1080p/60fps YouTube video manually started on my smart TV*, and I can throw a drink coaster into the FoV and it will crisply snap it just inside the leading edge of the photo; still unknown how much further down the delay can be pushed, but I'm impressed for now, unless lightning proves I need even shorter delay
- after manually adding "111a" to v0.8 of https://chdk.setepontos.com/index.php?topic=13956.0, the automatic power-down/power-on works as expected, and the script continues to pick back up after reloading CHDK, so at least that particular Lua script's native calls work as expected
- until I reinstalled to a freshly-formatted fat32 (for auto-boot), I had basically no flicker from anything (but disabled OSD); after reinstalling, there's a bit of flicker while the camera is being jostled about, but the menus are still perfectly usable during <ALT> mode while preparing for a shot
- there appears to be a *bug* when I change the <ALT> button to WiFi, because then the PlayBack button no longer functions at all; it's best to leave <ALT> set to PlayBack so that both modes can be activated via short- or long-press

*the TV's native refresh rate is 60 Hz and an ultra-slow-mo (16x @ 480fps) confirms that I can see time steps of ca. 16 ms matching both the TV's and video's 60fps
Logged
*

Offline pigeonhill

  • *****
  • 998
Re: eos M10 port
« Reply #305 on: 06 / June / 2022, 17:33:26 »
@reyalp @philmoz

I will hopefully get my M10 in a day or so and I will need to tweak my M3 Lua script for use on the M10. For example getting the Canon lower and upper distances, which on the M3 (lower) looks like this:

Code: [Select]
function get_focus_distance_lower() -- returns lower focus distance in mm, but note 'accuracy' is 1cm from Canon
    local x = -1
    if (bi.platsub=="101a") then
        x=peek(0x00244918, 2)
      elseif (bi.platsub=="120f") then
        x=peek(0x0024495C, 2)
      elseif (bi.platsub=="121a") then
        x=peek(0x0024495C, 2)
    else
        error('Not 101a, 120f or 121a')
    end
    if x == -1 then return -1 else return x*10 end
end

Is there an easy way to find, or look up, the M10 peek addresses?

Or do I request that info from one of you ;-)

Cheers

Garry
Logged
*

Offline philmoz

  • *****
  • 3408
    • Photos
Re: eos M10 port
« Reply #306 on: 06 / June / 2022, 18:48:59 »
Quote from: pigeonhill on 06 / June / 2022, 17:33:26
Is there an easy way to find, or look up, the M10 peek addresses?


If no one already knows the values then it should be possible to find them by comparing the M10 and M3 firmware dissassembly - I did a quick check on one M10 firmware version to find the 'lower' value.


Can you also post the M3 'upper' values / code you are using for reference.

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)
*

Offline c_joerg

  • *****
  • 1212
Re: eos M10 port
« Reply #307 on: 07 / June / 2022, 01:25:04 »
Quote from: pigeonhill on 06 / June / 2022, 17:33:26
Is there an easy way to find, or look up, the M10 peek addresses?

Or do I request that info from one of you ;-)

You can find it in the same script you copied the rest from ;)
https://chdk.setepontos.com/index.php?topic=13756.0

You could then also insert the M100 right away. It's my favorite camera right now.
« Last Edit: 07 / June / 2022, 01:27:39 by c_joerg »
Logged
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 pigeonhill

  • *****
  • 998
Re: eos M10 port
« Reply #308 on: 07 / June / 2022, 01:31:24 »
@philmoz

Here is the upper function:

Code: [Select]
function get_focus_distance_upper() -- NOTE - NOT USED IN THIS SCRIPT (left here as a reference)
    local x = -1
    if (bi.platsub=="101a") then
        x=peek(0x00244916, 2)
      elseif (bi.platsub=="120f") then
        x=peek(0x0024495A, 2)
      elseif (bi.platsub=="121a") then
        x=peek(0x0024495A, 2)
    else
        error('Not 101a, 120f or 121a')
    end
    if x ~= -1 then return x*10 else return x end
end

Plus here is the function to get lens info, which may also need an M10 specific tweak?

Code: [Select]
function lens_name()
    local pname = 0
    if (bi.platsub == "101a") then
        pname = 0x00244969
    else
        pname = 0x002449ad
    end
    local len = peek(pname-1,1)
    local i = 0
    local t = {}
    while i < len do
        local c = peek(pname + i, 1)
        if c == 0 then break end
        table.insert(t, string.char(c))
        i = i + 1
    end
    local name = table.concat(t)
    return name
end

Finally, I don't know what build variant I will be getting until it arrives, later this week.

Cheers

Garry
Logged
*

Offline pigeonhill

  • *****
  • 998
Re: eos M10 port
« Reply #309 on: 07 / June / 2022, 01:34:57 »
@c_joerg

We crossed in our posts.

Quote
you can find it in the same script you copied the rest from ;)
https://chdk.setepontos.com/index.php?topic=13756.0

Many thanks for the reminder. BTW will the lens name function need a tweak on the M10?

@philmoz looks like I may have all the info I need from @c_joerg .
Logged
Pages: 1 ... 26 27 28 29 30 [31] 32 33   Go Up
« previous next »
 

Related Topics