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 connect 550d to BEOS


8324689

Question

Hi there

Im going crazy!

Im running VMware hosting Windows on OSX and everything has been working perfect for all programs.

Ive followed the manual set the camera to M etc and BEOS freezes after asking me for what driver to use

Windows can see the 550d and everything seems fine

 

please help!

Thanks

Link to comment
Share on other sites

  • Answers 20
  • Created
  • Last Reply

20 answers to this question

Recommended Posts

OK!!!

Got it!! 

Im so happy. For the benefit of anyone having the same problem.

I could see an option in the Virtual Machine that stated usb3. 

I wanted to change i but couldn't figure out how

So....

You must close down the VM and set the USB port to USB2 and then open the VM again.

I have to say VMware tech support is the best I have ever come accross. 

They dont charge it is free unlike a lot of other companies.

 

Thanks for the input and Im sure Ill have a few more question on other topics in the future but BEOS based!

Link to comment
Share on other sites

Windows seeing the camera is NOT a confirmation what the camera is properly connected/configured for camera control.

 

Your first thing is to install EOS Utility and confirm it does connect with EOS Utility.  If BYE does not connect then chances are EOS Utility will not either.  In which case you need to make EOS Utility connect first.  This will ensure you all the correct drivers outside BYE.

 

Keep us posted.

Link to comment
Share on other sites

Hmmm yes EOS utility just freezes as well unfortunately

 

Any ideas?

 

Many thanks 

 

Check to see if you have a PC Communication menu option in your camera menu  If yes make sure it is not set to PTP.  Just a guess though.

Link to comment
Share on other sites

I believe that you misunderstood my question.  In your original post you said that "BEOS freezes after asking me for what driver to use".

 

BYE 3.1.6 pops up a window after you click on the Connect button. That popup window has 3 choices (Canon, Canon215, and Canon210). These correspond to the 3 versions of the Canon SDK that are bundled with BYE.  My question was which one are you choosing? I would suggest choosing Canon215!

 

It may be related to your issue, but since the EOS Utility is also failing, that is not likely.

 

Which version of Windows are you running under VMWare? I would confirm that Windows is actually seeing the camera (look in the Windows Device Manager) and that Windows has access to the USB port. You may need to enable this in VMWare. This has caused connection issues for others trying to run BYE in a virtual machine under OSX.

 

Also, what do you mean by "BEOS freezes"?  Your definition of "freezing" may not be the same as mine and I just want to understand what you are seeing.  My definition of "freezing" is that the application is displayed, but the content of the application's windows does not change and the application becomes unresponsive.  I typically have to kill an unresponsive, frozen app from the Task Manager.

Link to comment
Share on other sites

Am I understanding this correctly?  She is trying to run a Windows Virtual Machine on a Mac and having these driver issues?  Doesn't BYE come in a Mac version?  Same thing with Canon EOS Utilities?

 

Not running Virtual Machine and sticking with Mac operating system should clear all of this up I would think.

 

I know my 550D connects just fine on my Windows 10 Laptop with no issues at all. 

Link to comment
Share on other sites

Am I understanding this correctly?  She is trying to run a Windows Virtual Machine on a Mac and having these driver issues?  Doesn't BYE come in a Mac version?  Same thing with Canon EOS Utilities?

 

Not running Virtual Machine and sticking with Mac operating system should clear all of this up I would think.

 

I know my 550D connects just fine on my Windows 10 Laptop with no issues at all. 

 

Absolutely not!  BYE/BYN is a .net application and only runs on Windows.

 

https://www.otelescope.com/index.php?/topic/454-mac-version-of-bye

Link to comment
Share on other sites

The Canon EOS Utility is available from Canon for either Windows or OS X.  It is obviously not a .NET application.

 

While Microsoft designed .NET to be cross-platform, that support is not mainstream.  Mono is an open-source cross-platform project that provides a run-time environment for .NET applications on OS X but for a complex, mature app like BYE/BYN it is not a trivial effort to get the app to run with Mono.  It would mean a serious re-design effort to make it work, if it is even possible.

 

Sporadically over the past few years, several others have been successful getting BYE to run in a Windows VM on a Mac (mostly using Parallels or Boot Camp) so it appears to be possible.

 

The OP is using VMWare and I do not recall anyone else who has posted to this forum who was also using this virtualization software. The best approach may be to talk to the support folks at VMWare for guidance.

Link to comment
Share on other sites

Hello

Yes I am using Canon215 driver.

People all over the net are having this issue connecting a 550d to a windows machine (not specifically VMware) VMware works great.....

This is not a fault of Beos but more of one from Canon I think

 

Im on Windows 8.1

Freezing as in non responsive yes

 

Would be great to sort this

 

i am a he not a she!

 

Thanks

 

alan

Link to comment
Share on other sites

People all over the net are having this issue connecting a 550d to a windows machine (not specifically VMware) 

 

I'd be interested as to where "all over the net" comes from...

 

Many BYE Users, myself included, regularly Image with a 550D tethered to a Windows PC (Win7 in my case) with nary an Issue.

In fact, a quick Search of the Support\BackyardEOS Forum seems to indicate that This Thread is the only one with a 550D Connectivity Issue that hasn't already been resolved as User Error.

 

Please realize that your VMware environment is going to be rather complex, and hence will come with its own set of challenges.

 

Perhaps you can start by ensuring your 550D does in deed connect successfully to a friends Windows PC using Canon's EOSUtility (less to install/uninstall for your friend).

 

Please advise of the results...

Link to comment
Share on other sites

S3igell beat me to it.  I would agree with him and disagree with you that there is a systemic (as in all over the Internet) issue with the 550D not connecting to Windows PCs. Search through this forum for confirmation. There are probably hundreds of T2i owners with BYE.

 

People who are new to BYE and tethering Canon cameras occasionally have connection issues initially, but it is often due to a bad cable, incorrect windows drivers, or pilot error.  A good portion of my posts here and in the Yahoo group, previously, are trying to help users sort out those issues. For almost everyone these initial problems are now behind them.

 

Does the OSX version of the Canon EOS Utility work with the 550D?

 

What about the Windows version via VMWare?

 

The main components here are the computer, the cabling and the camera.  You need to try different combinations and see which of the three is always associated with the connection failure.

 

Things to try:

 

1) read the manual for the T2i and make sure that the communication-related settings in the camera's menus make sense for tethering.

2) same camera and cable with your Mac. Try to connect the EOS Utility under OSX to the camera. If that succeeds then it is likely that the configuration if VMWare is at fault.

3) same camera and cable with a Windows PC.  This will prove that the camera and cable are good and again point to the VMWare configuration as the culprit.

4) some folks have had issues with the low-level Windows driver. You could download and install the Canon utilities from their web site in your Windows 8.1 VM. This may replace the Windows driver. It will also allow you to test the EOS Utility.  If the EOS Utility will not connect, neither will BYE.

5) try a different USB cable that is known to be good.

6) try a different camera with each of the above.

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