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

Cannot get 5D Mark II to connect in Win 7 32 bit


fxstbi

Question

I have converted my computer from 64 to 32 bit Windows 7 in order to use the 5D Mark II after learning that BYE won't work with 64 bit.  But I still get the same message that it won't connect.  I know that my computer is detecting the camera due to the connection sound in Windows.  My log looks like this:

 

15:35:11  Licensed to fxstbi

15:35:25  Attempting to connect camera...
15:35:25  Canon drivers 'Canon210\' initialized.
15:35:25  Camera Not Found!  Make sure it's connected to the PC and turned ON :)
 
Can anyone help me?  Any suggested actions I can try?  Thank you!
Link to comment
Share on other sites

  • Answers 4
  • Created
  • Last Reply

4 answers to this question

Recommended Posts

First, someone gave you incorrect information. BYE runs perfectly fine on 64-bit Windows systems from XP to Win10. BYE is designed and runs as a 32-bit application. That does not mean that it will not run on a 64-bit system. I have run several releases of BYE on my 64-bit Windows 7 systems for years without issue! There are some older cameras that are not recognized on 64-bit systems because Canon has chosen to not provide 64-bit kernel-level drivers for them. There is sadly nothing that BYE or other application developers can do about it. Look at the Supported Cameras table on this web site for these restrictions.

 

Now your 5D Mk II is a DIGIC IV camera. Per the BYE driver selection dialog, the Canon210 drivers are for DIGIC II cameras. You should be using the Canon driver set (the Canon215 driver set may also work for you). This is really the version of the Canon SDK that BYE will use. The Canon210 version of the SDK does not support your camera because the 2.10 SDK pre-dates your camera. This is likely the reason for the "Camera not found" error that you are seeing. However there may be other issues that could give the same symptom. These include:

 

1) faulty camera USB port (you can test this with a different camera if you can borrow one from a friend)

2) the camera supports WiFi connections, but you have not disabled WiFi (check the camera users manual for more info about your camera's WiFi capability and how to disable it)

3) bad USB cable between the camera and the PC (Canon uses a standard USB cable so you may have a suitable replacement cable lying around. For testing, keep the cable as short as possible.

 

Before attempting to connect BYE with your camera you should be sure that Windows has recognized your camera (after first connecting the USB cable between the camera and PC and powering on your camera). You should hear the Plug-and-play sound and within a few seconds see the camera listed in the Windows Device Manager.

Link to comment
Share on other sites

Hi,

You are not selecting the correct Canon drivers in BYE when you connect your camera.  Select the latest Canon option in BYE when connecting, not the Canon210 and not the Canon215, select the option one. 

Hope this makes sense.

Regards,

Link to comment
Share on other sites

Thank you both for the information!  Turns out that I had been using the wrong SDK driver, plus I installed Windows 7 N (32bit) and it requires the media upgrade to work with cameras.  So, now that I installed the media upgrade and using the correct SDK driver, everything works great!

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