M6 Mark ii- Hope for support?

[Valdraz 0]

This page suggests it will have remote shooting support, they specifically note the cameras that do not support remote shooting.

https://developers.canon-europe.com/developers/s/article/Latest-EOS-SDK-Version-3-x

 I might pick one up to try.  Has anyone else tried?

[Valdraz 0]

figured this out- you need to manually set mirrorless cameras to take exposures with the lens removed.  You can add it on a custom menu

[admin 393]

So far the M series have been left out... But the possibility for remote shooting may change that. 

However, the EOS R and RP are currently supported in the pre-release  3. 1.18 RC5. 

For the M series I will need someone with a M6 and I may have to wait for the SDK to be available in America. 

Regards. 

[s3igell 289]

Hmmm... 

The Canon USA Specs page does look promising:

• USB-C Connection Port
• Bulb Function - 1-sec to 99hrs-59min-59sec
• Built-In Intervalometer functionality
• Shooting Modes: "Night Portrait" and "Handheld Night Sceen"

However, BYE has been bitten by Canon Mirrorless Design Decisions before.  And the Spec Sheet for this Model is more of the same:

• Remote Shooting Control is referenced ONLY via Bluetooth
• Bluetooth Connectivity is via an Apple / Android App (which they explicitly state may be only lightly supported by Canon)
• There is NO External Remote Control Port, hence the Built-In Intervalometer functionality

So, I won't be an Early Adopter...

But, if you do, consider sharing with Guylain in order to facilitate Support for the M6mkII in BYE.

[admin 393]

I agree with s3igell.

If you truly want a mirrorless, the Nikon Z6/Z7 are currently supported with the latest pre-release.  The Canon EOS R  is also supported in the latest pre-release.  I did add support for the Canon EOS RP but I still need confirmation form anyone that has one to confirm it works but I'm confident it will since the EOS R is now working.

Regards,

[astroman133 687]

It should not matter how the SDK communicates with the camera (wired USB, Bluetooth, or WiFi), in should only matter that the SDK does support the camera for remote tethered shooting. So a telltale question is "Does the EOS Utility support the camera?"

[grnbrg 0]

Just downloaded the latest EOS Utility, and plugged in my shiny new M6mkII.

Full remote USB control, and made a couple of 60 second bulb exposures. 

 

Brian.

[astroman133 687]

That seems hopeful.

 

S3igell, your post seems contradictory...in that it says that the camera has a USB-C port, but later it says "There is NO External Remote Control Port"

So what is the USB-C port for, if not remote control?

I read some articles about using the EOS Utility with the M6 Mk II and a USB connection so it does seem possible. However, it may be many months before Canon releases an SDK in North America with support for the camera.

[grnbrg 0]

7 minutes ago, astroman133 said:

S3igell, your post seems contradictory...in that it says that the camera has a USB-C port, but later it says "There is NO External Remote Control Port"

So what is the USB-C port for, if not remote control?

The USB-C port allows full remote control.  I suspect (but haven't tested) that you can also do full remote control over wifi.  Bluetooth likely only allows remote shutter, at best -- when using the Android camera app, many of the more complex functions when only connected with Bluetooth started the auto-wifi-setup routine....

There is also the standard 2.5mm (?) phono jack used by the standard Canon wired remote shutter release.  I haven't tested that, either, but it's fairly definitively labelled.

 

grnbrg.

[admin 393]

Forget wifi and forget bluetooth for now.  

You said "The USB-C port allows full remote control.".  Did you try it or is just from the documentation?  It's not clear.

For now, connect your camera with the USB cable.  Then start Canon EOS Utility software and try to take bulb images with EOS Utility.  Does it work?  If no there is no hope.  If yes there is hope and we'll go form there... but you have to start with EOS Utility and hard wired with a USB cable. 

Keep us posted,

Regards,

[grnbrg 0]

2 minutes ago, admin said:

You said "The USB-C port allows full remote control.".  Did you try it or is just from the documentation?  It's not clear.

USB.  Full remote control. 

Camera connected via USB, EU allowed live view, modification of most of the common shooting settings, and I did two 60 second bulb exposures, one with the mechanical shutter, and one with the new full electronic shutter.  Behaviour is essentially identical to my other Canon DSLRs.

A BYE 3.1.18RC6 log file of the attempted connection is in your inbox. 

 

grnbrg.

[admin 393]

21 minutes ago, grnbrg said:

USB.  Full remote control. 

Camera connected via USB, EU allowed live view, modification of most of the common shooting settings, and I did two 60 second bulb exposures, one with the mechanical shutter, and one with the new full electronic shutter.  Behaviour is essentially identical to my other Canon DSLRs.

A BYE 3.1.18RC6 log file of the attempted connection is in your inbox. 

 

grnbrg.

Okay, thank you for the log file.  I'll try to send you a download link tomorrow to try.  

Regards,

[admin 393]

I just sent you a download link to try with your M6 MkII.

Please report your findings here on the forum.

 

[grnbrg 0]

Well, that was fast. 

The M6mkII connected to BYE without incident.  Focus/LiveView mode worked.  I added a simple series of images, two bulb and one programmed shutter speed, different ISO settings and different apertures, with files to be placed on the PC and camera, and hit the button.

Two minutes later I had 3 sets of images on my laptop,  all exposed as intended.  Both JPG and CR3 files.  The JPGs were previewed in BYE as the exposure series was taken, as well.  The only questionable issue I see is that the reported EXIF data for many fields appears to be interpreted incorrectly - my 90 second exposure, for example, is being reported as a 1 second video file.    Nothing wrong with the images, just the EXIF text files.

Log and a sample EXIF file attached.

But 3.1.18RC7 support for the M6mkII is functional, and entirely usable.  (At least based on a quick run though...)  I await the next test build.

Thanks!

 

grnbrg.

logfile-[20191005-21h16m10s317]-[1084]-2019-10-05.txt M6mkII-Test_LIGHT_90s_100iso_f8_20191005-21h17m43s258ms.CR3.EXIF.txt

[admin 393]

CR3 is a new format  and exiftool is not supporting them at the moment so exif is what it is based on what exif tool can extract out of it.

I'm glad that the M6 MkII is fully functional.  It's a nice change from the the earlier M# models.

Regards,

[grnbrg 0]

At the risk of asking a stupid question...

Why not use the JPG (if available) for the EXIF data?  It should be essentially (if not completely) identical.

Is there anything specific you'd like me to try with RC7?

 

grnbrg.

[Valdraz 0]

This is exciting, I'm still hunting for mine locally.

And a low profile way to connect the thing...

[Valdraz 0]

I've got my camera on the way, any chance you could send me that download link as well?

[grnbrg 0]

16 minutes ago, Valdraz said:

I've got my camera on the way, any chance you could send me that download link as well?

 

It's (now) in the pre-release section:  https://www.otelescope.com/files/file/80-backyardeos-3118-pre-release/

It looks like there is also an unreleased RC8 build that works with the M50, but I haven't seen a link.

I'd love to see an M5 build, but my reading of the EOS Utilities manual seems pretty clear that remote control of the M5 (and older) mirrorless is unlikely.  Now all I need is Magic Lantern support for the M6mkII, and I'll be out of things to hope for. 

 

 

grnbrg.

[Valdraz 0]

thanks for that

 

[Valdraz 0]

Odd- day one when I got the camera I hooked up BYE and took some 5 minute test exposures with success

 

today, really trying to shoot and i get this

21:47:20  BackyardEOS 3.1.18 RC11
21:47:30  Attempting to connect camera...
21:47:30  Canon drivers 'Canon\' initialized.
21:47:31  EOS-M6MkII CONNECTED!
21:48:06  Imaging session started.
21:48:07  Capture Error: General camera error.
21:48:08  Imaging session cancelled
21:48:08  ERROR 36107 : EDSDK.EdsSendCommand(cameraRef, 4, 65539) 
21:48:08  Imaging session cancelled

[astroman133 687]

You probably need to provide the complete log file.

[admin 393]

46 minutes ago, Valdraz said:

figured this out- you need to manually set mirrorless cameras to take exposures with the lens removed.  You can add it on a custom menu

Glad you figured it out.

Regards,