Canon EOS M3 (Mirrorless) not working

[smersh007]

EOS M3 is DIGIC 6 so I would have thought it is compatible

I do NOT have EOS utility installed as it is not supplied with the camera.

 

The camera connects but it is unable to take a frame 

 

Note that I have successfully used a Canon 40D with BYE

 

BYE is able to display the correct camera settings (e.g. AV, ISO, Image quality, WB, Battery etc) 

 

I'm getting various errors in the log.

 

 

 

17:52:45  Licensed to ##########

17:54:22  Attempting to connect camera...

17:54:22  Canon drivers 'Canon\' initialized.

17:54:22  DEVICEINFO DESCRIPTION IS Canon EOS M3

17:54:22  DEVICEINFO NUMBER IS 844135995.

17:54:22  YOUR *REAL* MODEL NUMBER IS 57933824(3740000)

17:54:22  Generic model 153 assumed!

17:54:25  153 CONNECTED!

17:54:25  Unable to set ImageQuality, current setting is assumed!

 

after trying to take a frame...

 

17:55:26  Unable to set ImageQuality, current setting is assumed!

17:55:41  Imaging session started.

17:55:42  Unable to set ImageQuality, current setting is assumed!

17:55:42  Imaging session cancelled

17:55:42  ERROR EDS_ERR_INTERNAL_ERROR : EDSDK.EdsSetPropertyData(cameraRef, SaveTo(11), 0, size(4), 2) 

 

 

[alexsr]

And there is no physical port on the camera to plug in an intervalometer either, sad but true.

 

Regards,

 

It seems that the intervalometer functions are available throughout bluetooth. Please take a look at this:

 

https://youtu.be/syZEcaGW_ug?t=6m10s

 

I still keep the hopes of using an EOS M with this SW

 

Please let me know what you find out.

 

Alex

[s3igell]

We have all been hopeful that Canon would see the synergy between the Mirror-less M-series and Astrophotography.  But except for persistent rumors that "the Next Canon M will Support AP Imaging", we are all left "Hoping".

 

Sorry that you've gotten bitten by this "Gap" between Expectation and Implementation...

[admin]

Any of the EOS M# series are not supported as this time and there is no plan to offer support unless Canon adds a true/physical intervalometer port.

[cjcj1949]

I have downloaded the latest version of BYEOS. I am using WIN10 and a 1300d. The camera connects but the connect button does not change to disconnect. The connect log states that the 1300d has been recognised then it says that my my real serial number is not the same as reported and that Generic model 153 assumed!

 

17:49:07  Licensed to c...1949
17:50:20  Attempting to connect camera...
17:50:20  Canon drivers 'Canon215\' initialized.
17:50:20  DEVICEINFO DESCRIPTION IS Canon EOS 1300D
17:50:20  DEVICEINFO NUMBER IS 3470492101.
17:50:20  YOUR *REAL* MODEL NUMBER IS 4294967294(FFFFFFFE)
17:50:20  Generic model 153 assumed!
17:51:11  Copy to clipboard

[admin]

You're using the wrong Canon SDK files for your newer 1300D model.

Choose the top option "Canon" instead of "Canon215" when connecting your camera in BYE and you;ll be fine.

Please start a new thread instead of replying to an old one in the future; your issue has nothing to do with the original post regarding a M series camera.

Regards,

[cjcj1949]

I thought I had started a new thread. I thought the option I chose was for a digic 4 processor. I see my camera is a digic 4+.. All works now. Thanks for prompt reply.

 

[admin]

2 hours ago, cjcj1949 said:

I thought I had started a new thread. I thought the option I chose was for a digic 4 processor. I see my camera is a digic 4+.. All works now. Thanks for prompt reply.

 

Awesome, glad it worked.

[admin]

The M3 is not supported; Canon does NOT allow BULB exposures over a computer for this model and its SDK is limited.  As a result it is not supported.

 

Please see the camera support grid; the link is in the page footer as well.

 

Regards,

[smersh007]

That's pretty disappointing Canon. I bought this camera for astro photography...and now it's useless!

[admin]

That's pretty disappointing Canon. I bought this camera for astro photography...and now it's useless!

 

And there is no physical port on the camera to plug in an intervalometer either, sad but true.

 

Regards,