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*
PLEASE READ ==> If you get a StructureMap or EdsInitializeSDK() error please RE-INSTALL before posting in the forum <==
  • 0
sreegururaj

Canon 1500D support

Question

Hello there! Using a trial version. Tried connecting my Canon 1500D. The software does not seem to connect. Is there support available for 1500D? (I also have a 1000D/ Rebel XS and i'm able to connect it ) Thanks in advance. Regards, Sreegururaj

Share this post


Link to post
Share on other sites

9 answers to this question

Recommended Posts

  • 0

Sreegururaj,

The 1500D is not in the list of supported camera models. (Scroll to the bottom if this page and select Supported Cameras below BackyardEOS).

You are using a Trial license which means that you are either using version 3.1.18 or the version 3.2.0 Release Candidate. When you attempt to connect BYE with the 1500D, be sure to use the Canon driver, not the Canon 210 driver. The error information that is reported in the log file as a result of the connection attempt may be helpful to Guylain to be able to add support for the camera. You should find that information because he will likely ask you for it. Also, version 3.2.0 RC may support some models that are not supported in 3.1.18.

Share this post


Link to post
Share on other sites
  • 0

What version are you using with the 1500D.  Please try with 3.2.0 pre-release. It will not work but you should be getting numbers like the following in the message center. Send me those numbers.

14:26:58  DEVICEINFO DESCRIPTION IS MTP USB Device
14:26:58  DEVICEINFO NUMBER IS 2971957769.
14:26:58  YOUR *REAL* MODEL NUMBER IS 2147484722(80000432)

 

Thank you.

Share this post


Link to post
Share on other sites
  • 0

Thanks, but that log file is not useful.  No camera was connected to Windows when this was taken.

Make sure your 1500D is connected to your PC and that Windows sees it first. Then try BYE 3.2.0.  Send me that log file.

Thank you.

Share this post


Link to post
Share on other sites
  • 0

I don't know whether it is relevant to this issue, but in North America, the T7 is the 2000D, but I saw release information that in India the T7 is the 1500D. That is pretty bizarre! Would it prevent the 1500D from being recognized by the North American version of the SDK?

Share this post


Link to post
Share on other sites
  • 0

Yes, that would be bizarre. The 'D' name is purely marketing though.  This is why I choose t rely on the internal model number which should be identical and the logfile should give me that number if that model is supported by the current SDK.

Share this post


Link to post
Share on other sites
  • 0

According to your log file you are running Windows 8 (2020-04-15 17:16:28,416 [Main] INFO  - Microsoft Windows NT 6.2.9200.0).

Does your camera show up in Windows Device Manager when plugged in and powered on? It may show as an unknown device. This could happen if there is no driver as part of Windows 8 that supports that camera, since the camera is newer than Windows 8. You might try to have Windows try to find an appropriate driver online.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Answer this question...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


×
×
  • 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