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

Problem on Windows running Mac


okanburada

Question

Hi,

I don't have any PC and don't think to buy it in any near future but running in windows as a virtual machine on Mac VMware Fusion. Other astro apps working without any problem so far but BackyardEOS freezing between exposures saying Busy. First I thought its because of old long USB cables and changed it. But same problem. May be its because of virtual machine but Im wondering is there any other virtual machine platform like parallel Desktop works ok with BackyardEOS? Couldn't upload 518k log file.

Thx

BYE v3.2

Canon 200D

Link to comment
Share on other sites

  • Answers 21
  • Created
  • Last Reply

Top Posters For This Question

Top Posters For This Question

21 answers to this question

Recommended Posts

  • 0

Other folks have used VMware with BYE.

If you have an Anti-virus program running in the VM or even in iOS I would suggest temporarily disabling it to see if it is preventing image download.

Also, be sure that Long Exposure Noise Reduction is disabled in the camera.

Don't try to attach a log file to a post in the forum. Instead, delete all the log files, start a new BYE imaging session, keeping the session short enough to log what is going on when you re-create the issue and follow the linked post (below) from the How-to's Forum. You should also zip the log file to make it smaller before send it to the admins, via the instructions in the link.

 

Link to comment
Share on other sites

  • 0

There is no setting for USB. That is a hardware thing. Also BYE does not know anything about the connection transport. That is all handled in the SDK. That said, if the USB 2.0 camera is plugged into a USB 3.0 port it will automatically operate at USB 2.0 speeds.

I looked at the log file and saw several images being downloaded and stored. The last image was IMG_0031.CR2 was downloaded and saved to Z:\Teleskop Fotograflarim\BackyardEOS\2020-09-13. I will admit that I am not as good as the developers at reading the log files, but all the files seemed to be saved to the Download folder in a reasonable amount of time. From looking at the log entries it seems that it takes about 6 seconds to download and process the image. That does not seem abnormal to me.

With my T5i, BYE 3.2.0 appears to show Busy between the time that the shutter is closed and when the camera signals that the image is ready to be downloaded. For me BYE shows BUSY for about 2 seconds before showing Downloading. So I am not sure that I can see any extended periods in your log file where BYE would be showing BUSY.

Link to comment
Share on other sites

  • 0

According to the USB protocol, the maximum length for USB 2 is 15 feet and USB 2 is 9 feet.

I would try with a shorter cable, I suspect the cable is too long and the data signal is deteriorating be the time it gets to the other end.

In your first post you said " BackyardEOS freezing between exposures saying Busy".

Please clarify this, does it crash, does it recover and continue, do you get an error message?

Link to comment
Share on other sites

  • 0
4 minutes ago, admin said:

In your first post you said " BackyardEOS freezing between exposures saying Busy".

Please clarify this, does it crash, does it recover and continue, do you get an error message?

Yes It does crash. Nothing happens. I should close and reopen it and there is no error message. As I thought and you said before Im suspicious about those long cable. But my balcony just 5 meters away from my iMac :(

Thank you all for your replies anyway 👍

Link to comment
Share on other sites

  • 0

That USB setting in VMware is unknown to BYE.

Also the max length for a high quality perfectly functioning USB 2.0 cable is 5 meters. For USB 3.0 the max length is 3 meters. Of course, you can extend the length with an active extension cable.

The log file shows the following image files as having been downloaded from the camera:

IMG_0001.JPG
IMG_0002.JPG
IMG_0003.JPG
IMG_0004.JPG
IMG_0005.JPG
IMG_0006.JPG
IMG_0007.JPG
IMG_0008.JPG
IMG_0009.JPG Frame & Focus Snap image was deleted per user settings.
IMG_0010.JPG Frame & Focus Snap image was deleted per user settings.
IMG_0011.JPG Frame & Focus Snap image was deleted per user settings.
IMG_0012.JPG Frame & Focus Snap image was deleted per user settings.
IMG_0013.JPG Frame & Focus Snap image was deleted per user settings.
IMG_0014.JPG Frame & Focus Snap image was deleted per user settings.
IMG_0015.JPG Frame & Focus Snap image was deleted per user settings.
IMG_0016.JPG Frame & Focus Snap image was deleted per user settings.
IMG_0017.JPG Frame & Focus Snap image was deleted per user settings.
IMG_0018.JPG Frame & Focus Snap image was deleted per user settings.
IMG_0019.JPG Frame & Focus Snap image was deleted per user settings.
IMG_0020.JPG
IMG_0021.JPG
IMG_0022.JPG
IMG_0023.CR2
IMG_0024.JPG
IMG_0025.JPG
IMG_0026.CR2
IMG_0027.CR2
IMG_0028.CR2
IMG_0029.CR2
IMG_0030.CR2
IMG_0031.CR2

There was no apparent indication that BYE was killed and restarted. The session lasted from 20:21:36 until disconnect at 21:29:29.

I do not see a problem in the log file. I spot checked several image downloads and they lasted about 6 seconds. Hopefully Guylain will see something that I am obviously missing.

Link to comment
Share on other sites

  • 0

I tried Windows with USB 2.0 connection this time BYE crashed several times more than before even without doing anything. Attached log files. 
Below buttons Snap Image, Loop and Live View become disable. Then warning says "OOPs! This is embarrassing. An unhandled error has occurred. "System.OutofMemoryException. 
If this is the case what should be VMware memory and perhaps processor request?

BYELogFiles.zip

Link to comment
Share on other sites

  • 0

If the frequency of crashes changed when you made the change above (which is a change outside BYE) what does that say about the issue?  It tells me that there is an outside force that is at play.

The out of memory is unrelated.  Please download 3.2.1-RC1; I made a change trying to address this.

 

 

 

Link to comment
Share on other sites

  • 0

Hello Admin,

Thank you tired that 3.2.1 RC. Tried focus mode and imaging. And started taking 40 exposures in 55 seconds. In the beginning everything looks ok. Works flawlessly. But when I got to 35th exposure app freeze again. Only cycle around abort was turning. Now Im waiting as it says wait until that time. 

I have waited and nothing happened.
Im sending a new log files. 

logfile-[20200916-22h32m31s147]-[5132]-2020-09-16.txt.zip

Link to comment
Share on other sites

  • 0

To verify whether it is the USB Cable (5 meters or 3 meters or...) or perhaps some issue in Fusion support for USB or something else:  Take the iMac down to near the Scope for an Imaging Session or two using the shorter "Canon-original" USB Cable (changing nothing else).

If you have similar "crash" issues, at least you know to look elsewhere than the 5 meter USB3 Cable.

Link to comment
Share on other sites

  • 0

The proof is in the pudding,  Your camera has initiated a shutdown sequence.  This is usually caused by the camera auto-turning itself off -or- the USB cable got disconnected.  Either way the disconnect was issued outside BYE given that the SDK has fired the event StateEvent_WillSoonShutDown.

2020-09-16 23:21:09,245 [ReadWeatherCenter(Normal)] DEBUG - No weather provider configured.
2020-09-16 23:21:41,480 [OnStateEventHandler] INFO  - StateEvent_WillSoonShutDown Fired! (inParameter=30)
2020-09-16 23:21:41,480 [OnStateEventHandler] INFO  - Running (log): EDSDK.EdsSendCommand(CameraRef, EDSDK.CameraCommand_ExtendShutDownTimer, 0)
2020-09-16 23:21:41,510 [OnStateEventHandler] INFO  - Success: EDSDK.EdsSendCommand(CameraRef, EDSDK.CameraCommand_ExtendShutDownTimer, 0)
2020-09-16 23:21:41,699 [OnStateEventHandler] DEBUG - OnStateEventHandler Fired! (inEvent=772), inParameter=0)

Link to comment
Share on other sites

  • 0
16 minutes ago, admin said:

I see the same thing.

Also,please to go settings -> advance settings and select "Maximum Stability".  You have ExifRead/Write enabled and other stuff.

Where? In PC or canon or BYE. Ok I can find it I think. 
 

 

15 minutes ago, admin said:

The proof is in the pudding,  Your camera has initiated a shutdown sequence.  This is usually caused by the camera auto-turning itself off -or- the USB cable got disconnected.  Either way the disconnect was issued outside BYE given that the SDK has fired the event StateEvent_WillSoonShutDown.

2020-09-16 23:21:09,245 [ReadWeatherCenter(Normal)] DEBUG - No weather provider configured.
2020-09-16 23:21:41,480 [OnStateEventHandler] INFO  - StateEvent_WillSoonShutDown Fired! (inParameter=30)
2020-09-16 23:21:41,480 [OnStateEventHandler] INFO  - Running (log): EDSDK.EdsSendCommand(CameraRef, EDSDK.CameraCommand_ExtendShutDownTimer, 0)
2020-09-16 23:21:41,510 [OnStateEventHandler] INFO  - Success: EDSDK.EdsSendCommand(CameraRef, EDSDK.CameraCommand_ExtendShutDownTimer, 0)
2020-09-16 23:21:41,699 [OnStateEventHandler] DEBUG - OnStateEventHandler Fired! (inEvent=772), inParameter=0)

 

Should I disable Auto Power off?
 

19 minutes ago, astroman133 said:

I may be misreading the log, but it seems as though the camera initiated the shutdown that caused BYE to hang.

Were you running off the battery or permanent power? Were there any settings that would cause the camera to shut down? or the USB hub?

 

No battery was full but not a permanent power. If there is any settings that can cause to shut down I don't know what it is. Not an expert. But I think if its connected to PC then it shouldn't be shut down isn't it? But yes. It is connected to USB Hub Oh may be that's the problem. Now I will try without any USB Hub. :)

Thanks

Link to comment
Share on other sites

  • 0
20 minutes ago, okanburada said:

Should I disable Auto Power off?

You should have every "auto" Power-off DISABLED - on the Camera and the iMac (you can let it Blank the Screen if that does NOT put the CPU to Sleep mode; but No to USB going to Sleep, Drive going to Sleep, VM going to Sleep).

Link to comment
Share on other sites

  • 0

If your battery was full then there only 1 more culprit... this is USB connection related.  There are no other possibility for a camera disconnect....either the camera turned off or it lost connection to the camera.

So, it seems that we are back to square 1.  You need to figure out where the USB connection is faulting... either physically or logically via VMWare.

Link to comment
Share on other sites

  • 0

Hi folks,

I think my problem resolved with removing Belkin USB Hub from my Mac connection. I took a 3 series of 40 exposure for test. No crash or freeze experienced.

Thank you for helping me. Cos my licence days was ending and Im going to decide to buy it. Its very useful application. Now Im gonna pay for it with inner piece. :)

Have a good day to you all.

Attached log files anyway.

logfile-[20200917-11h36m07s798]-[10080]-2020-09-17.txt.zip

Link to comment
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