Jump to content

Canada's top-tier Telescopes & Accessories
Be as specific as possible when reporting issues and *ALWAYS* include the full version number of the application you are using and your exact *CAMERA MODEL*
NEVER POST YOUR KEY IN ANY PUBLIC FORUM, INCLUDING THE O'TELESCOPE SUPPORT FORUM ::: IF YOU DO YOUR KEY WILL BE DEACTIVATED WITHOUT NOTICE!
  • 0

Backyard EOS not working correctly with EOS 7DMk2


senolite_eos

Question

I am trying out the trial of Backyard EOS and walking through the different intro videos before I want to buy the premium.

The supported camera list says it is supported through usb for the eos 7dMk2
It's not the newest of the newest so I was surprised my trial copy do anything different than the one in the introduction video.

Two issues I came across:

  • Mirror lock option.
    Say I set it to 5 seconds, anti-vibration timer starts, after that, then the mirror flips and then it takes a long time before anything happens (even with a 1 sec image).
    I have to press abort and after about 20-30 secs the mirror comes down and it takes a while before it actually aborts.
  • 5x view in planetary mode
    Basically when I press the button, nothing happens except the window freezes for a few seconds and then returns to normal without any zoom.

Any help would be appreciated, I think both are important features that I need to verify working before I proceed.

Kind regards,

 

 

Link to comment
Share on other sites

  • Answers 14
  • Created
  • Last Reply

14 answers to this question

Recommended Posts

Please, when reporting an issue you should report the specific version of BYE (not "the latest", but BYE 3.1.13), and which SDK/driver (Canon, Canon215, or Canon210) you are using, along with the camera model. It is may also be useful to report which version of Windows (for example Windows 10 x64) you are running. If the issue is connection-related then it is also important to know how the camera is cabled (how long are the cables, are you going through a hub) as well as what other devices are connected.

With BYE 3.1.13 and my T5i I am seeing that the mirror does not flip up at the start of the ant-vibration period, but at the end. The shutter never opens and no picture is ever taken or downloaded. I must resort to killing BYE through the Task Manager because if I click on the "X" close button, BYE's U/I disappears but the orphan executable remains in the task list. This is definitely a bug.

For the 5X zoom issue this may be a limitation of the camera rather than a BYE bug. This has been reported by other users. You can find it by searching through the BYE forum, as I did. It turns out that for some of the newer, higher-end cameras the behavior of whether 5X zoom works depends on which of three AF modes are selected in the camera. The available modes are Face+Tracking, Flexizone-Multi, and Flexizone-Single.   Zoom is not available in Face+Tracking and that may be the default mode.  Once you switch to FZ-Multi zooming should work. 

This may be documented in the camera manual.

 

Link to comment
Share on other sites

Send me the log file.  It is possible that for the 7D MkII you have to set mirror lock manually using the camera menu before using it in BYE... then of course you need to turn it off manually when you don't want to use it.

The log file should help me confirm this or not.

Regards,

 

Link to comment
Share on other sites

Hello,

I am using version 3.1.13 of the software but I am not certain of which SDK or driver I have nor how I can find out.
As stated, the camera model is a Canon 7DMk2 and my OS is a Windows 10 (64 bit) copy.
The cable is the default Canon usb cable provided with the camera, I estimate it to be about a meter in length or so and it is directly connected to a usb port on my pc.
The other devices connected are a mouse and keyboard as well as a WiFi device for internet connection.

The issue with the mirror lock you specified is exactly the same as I experienced, I have sent my logs through email as requested by admin.
It does not matter if I turn on/off mirror lock in the camera itself, the results are the same in BYE.

Your advise on the AF modes did resolve the 5x zoom in planetary mode, very happy that it worked, thank you for mentioning that!

Thank you all very much for your time and help so far, hopefully the mirror lock issue can be resolved.
If you need any further testing from my side with the actual camera, please let me know.

Kind regards,

Link to comment
Share on other sites

Reading the log file you have enabled virtual mirror lock in BYN advance setting.

Please disable this as it is not real mirror lock, it simply uses live view mirror up to lift the mirror and it is not the same as true in-camera mirror lock.

Once deactivated, try taking a picture in BYE with a 5 second mirror lock and send me that log file.

Thank you

Link to comment
Share on other sites

Good news!

I was triggered to do some more investigation by your mentioning of the driver selection.
As shown in your great 2 hour video, you can set it to not ask for the selection again, which I did and selected the top one "Canon" as I thought I had the latest and greatest in DIGIC version.

However if I select the Canon 215 driver, all problems are gone, mirror lock works like a champ...

Virtual mirror lock did nothing different turned on or off, I can send the log if you like but selecting the different driver made the difference.
Hopefully this also helps Astroman133...

Kind regards,

 

driver selection.png

Link to comment
Share on other sites

3 hours ago, senolite_eos said:

Hello,

I am using version 3.1.13 of the software but I am not certain of which SDK or driver I have nor how I can find out.
As stated, the camera model is a Canon 7DMk2 and my OS is a Windows 10 (64 bit) copy.
The cable is the default Canon usb cable provided with the camera, I estimate it to be about a meter in length or so and it is directly connected to a usb port on my pc.
The other devices connected are a mouse and keyboard as well as a WiFi device for internet connection.

The issue with the mirror lock you specified is exactly the same as I experienced, I have sent my logs through email as requested by admin.
It does not matter if I turn on/off mirror lock in the camera itself, the results are the same in BYE.

Your advise on the AF modes did resolve the 5x zoom in planetary mode, very happy that it worked, thank you for mentioning that!

Thank you all very much for your time and help so far, hopefully the mirror lock issue can be resolved.
If you need any further testing from my side with the actual camera, please let me know.

Kind regards,

After you click on BYE's Connect button, you are given a window which asks you to "Select your driver". The choices are Canon, Canon210, and Canon215. There is a comment for each option which describes which choice is appropriate for which camera. Very old cameras should choose Canon210. Newer cameras should choose Canon215, and the newest cameras should choose Canon. Sometimes a camera model will work with more than one choice.

BYE uses Canon software called the EOS Software Development Kit (SDK) to manage communication with their cameras. On an irregular basis, but usually once or twice a year, Canon releases a new version of the SDK. A new version usually drops support for some old cameras and add support for new models. In order for BYE to support the widest range of EOS cameras, Guylain provides old versions of the SDK, as well as the newest version.

If you only ever need to use one driver/SDK you can also select "Remember my selection and don't ask me again." Then your selection will always be automatically chosen. If at some point in the future you need to use BYE with a different camera, you can go into the Advanced Settings and select "Ask for camera drivers" , save your change and re-connect.

At this point, you need not answer the question. Guylain can tell which SDK/driver you selected by looking in the log file that you sent. I just thought this explanation may help you or other new users in the future.

Link to comment
Share on other sites

2 hours ago, senolite_eos said:

Good news!

I was triggered to do some more investigation by your mentioning of the driver selection.
As shown in your great 2 hour video, you can set it to not ask for the selection again, which I did and selected the top one "Canon" as I thought I had the latest and greatest in DIGIC version.

However if I select the Canon 215 driver, all problems are gone, mirror lock works like a champ...

Virtual mirror lock did nothing different turned on or off, I can send the log if you like but selecting the different driver made the difference.
Hopefully this also helps Astroman133...

Kind regards,

 

driver selection.png

 

Virtual mirror lock DID do something, i can see it in the log file.

This makes no sense, Canon should work if Canon215 does.  I need/want to fix this for sure.

Please send me the Canon215 logfile and a new Canon log file.  Make sure virtual mirror lock is disabled in both.

Regards,

 

Link to comment
Share on other sites

Guylain,

I see the same behavior as senolite_eos with BYE 3.1.13 and my T5i.

When using the Canon SDK  I am seeing that the mirror does not flip up at the start of the ant-vibration period, but at the end. The shutter never opens and no picture is ever taken or downloaded. I must resort to killing BYE through the Task Manager because if I click on the "X" close button, BYE's U/I disappears but the orphan executable remains in the task list.

When using the Canon215 SDK the behavior is as expected.

Log files are attached.

Let me know if I can help you test, before releasing this.

 

CanonSDK-logfile-[20170805-11h16m14s112]-[12216]-2017-08-05.txt

Canon215SDK-logfile-[20170805-11h22m09s567]-[10848]-2017-08-05.txt

Link to comment
Share on other sites

That definitely did the trick.

I am seeing equal and expected results both in the Canon driver as well as in the Canon 215 driver.
For completeness, I have added both logs again.

Thank you again for resolving this so quickly.
Do I get to keep the RC software? ;)

canon215-driver-logfile-[20170807-16h38m56s588]-[10248]-2017-08-07.txt

canon-driver-logfile-[20170807-16h37m38s615]-[9044]-2017-08-07.txt

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.


×
×
  • Create New...

Important Information

This site uses cookies to offer your a better browsing experience. You can adjust your cookie settings. By closing this banner, scrolling this page, clicking a link or continuing to browse otherwise, you agree to the use of cookies, our Privacy Policy, and our Terms of Use