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

BYEOS Unhandled exception and crash.


Midnight Dan

Question

When I set up a long imaging run (3-4 hours), I usually come back to see one or two dialogs stacked on top of BYEOS.  The first one says there was an unhandled exception and allows me to continue or quit.  If there is only the one dialog, I can continue.  It appears that the software continued to capture images if I wasn't there when this dialog is up.  If I find there are two dialogs, the top one says the application has stopped working and I have to re-launch to continue.

 

Initially I though this might be a USB problem because, between the camera and computer in my observatory, I have 2 hubs and 3 cables, one of which is 14 feet long.  However, I started creating a dark library where I have the camera connected to the computer with a single short cable.  I'm getting the same behavior.

 

Any ideas on the cause of this or suggestions for debugging? Is there some kind of log file associated with BYEOS that I can send in to help understand what's happening?

 

I'm using:

Dell Latitude E6410 Laptop, Core i5, 2.4GHz

8GB Ram

Windows 7 Profession, SP1, 64 bit

BYEOS 3.0.3 Premium Edition

 

 

Link to comment
Share on other sites

  • Answers 15
  • Created
  • Last Reply

15 answers to this question

Recommended Posts

Dan,

 

Look in the BackyardEOS forum.  The first, pinned, topic is entitled "BackyardEOS 3.1.0 Release Candidate 05 is ready for download".  Select that topic and scroll to the oldest message.  It has a link to download RC 5.  When you start it, just paste in your 3.0 license and you should be good to go.  It installs in a separate directory so it does not replace your current release, however the license will only be good for a few weeks...By that time Guylain will have announced the production release of 3.1 or have a new beta RC for testing. It also has a new user manual that can be launched via the start menu or from within BYE.

 

 

Link to comment
Share on other sites

OK, seems like the same problem with this release, but a little different behavior in BYEOS.  The log history window shows:

-Out of Memory

-Imaging session cancelled

-ERROR EDS_ERR_INVAID_HANDLE:EDSDK.EdsSendCommand(CameraRef,4,65539)

-Camera Shutdown

-Imaging Session Cancelled

 

So it seems like BYEOS handles the problem more gracefully and disconnects the camera instead of crashing.  Nonetheless, the problem is still occurring and I can't do long imaging runs of more than a couple hours or so.

 

The initial error reported is Out of Memory, but I don't see how that can be.  I have 8 gig of RAM, and it should be fully accessible with a 64-bit OS installed. I was taking 10-minute darks, so there was plenty of time to clear the buffer of the previous image before the next one was done.  Also, BYEOS was the only app running on the computer.

 

Any thoughts on where to go from here?

Link to comment
Share on other sites

OK, seems like the same problem with this release, but a little different behavior in BYEOS.  The log history window shows:

-Out of Memory

-Imaging session cancelled

-ERROR EDS_ERR_INVAID_HANDLE:EDSDK.EdsSendCommand(CameraRef,4,65539)

-Camera Shutdown

-Imaging Session Cancelled

 

So it seems like BYEOS handles the problem more gracefully and disconnects the camera instead of crashing.  Nonetheless, the problem is still occurring and I can't do long imaging runs of more than a couple hours or so.

 

The initial error reported is Out of Memory, but I don't see how that can be.  I have 8 gig of RAM, and it should be fully accessible with a 64-bit OS installed. I was taking 10-minute darks, so there was plenty of time to clear the buffer of the previous image before the next one was done.  Also, BYEOS was the only app running on the computer.

 

Any thoughts on where to go from here?

 

Out-of-memory does not mean you ran out of memory, it usually means that an object, usually an image, does not fit int the memory [ space ] allocated to it... and it throws and out-of-memory exception.  This is probably it.  Why?  I don't know yet.

 

The EDS_ERR_INVALID_HANDLE error means the Canon SDK failed to execute a command.  I really need the full log file.  An excerpt is not sufficient.  Let's just hope it's not a physical issue with the camera, that would s**k <_>

 

Regards,

Link to comment
Share on other sites

Hi Guylain:

 

How do I get you the logs?  There seem to be two recorded at about the right time last night.  One is labeled backgroundworker.  Do you want both?  Should I email them to you - at what address?  Or is there a place to post them here in the forum?  I don't see a way to attach to this post.

Link to comment
Share on other sites

Hi Guylain:

 

How do I get you the logs?  There seem to be two recorded at about the right time last night.  One is labeled backgroundworker.  Do you want both?  Should I email them to you - at what address?  Or is there a place to post them here in the forum?  I don't see a way to attach to this post.

 

Send them to support@binaryrivers.com.

 

I don't need the backgroundworker log for this issue, just the regular one.

 

Regards,

Link to comment
Share on other sites

Ok, I just sent it. Thanks for taking a look!

 

Hi Dan,

 

The initial error is a "Device Busy" error trying to start the BULB sequence... followed by blank camera properties... which is an indication that the camera has somehow lost connection with the SDK.  The "ERROR EDS_ERR_INVALID_HANDLE" is just a side effect and not the root cause.

 

Can you reproduce this all the time?  Is it possible that you wiggled the usb cable at the time?  Do you get the same thing using EOS Utility?  Does it do the same thing using another computer?

 

Keep me posted,

 

Guylain

 

 

2014-10-01 22:10:12,426 [CameraTakePictureOnMessageRecieved] INFO  - Running (throw): EDSDK.EdsSendCommand(cameraRef, 4, 65539)

2014-10-01 22:10:12,441 [CameraTakePictureOnMessageRecieved] DEBUG - Device Busy trying to start BULB sequence

2014-10-01 22:10:12,441 [OnStateEventHandler] INFO  - CameraPropertyChangedArgs fired: AeMode               = ''

2014-10-01 22:10:12,972 [OnStateEventHandler] INFO  - CameraPropertyChangedArgs fired: Artist               = ''

2014-10-01 22:10:12,972 [OnStateEventHandler] INFO  - CameraPropertyChangedArgs fired: Av                   = ''

2014-10-01 22:10:12,972 [OnStateEventHandler] INFO  - CameraPropertyChangedArgs fired: BatteryLevel         = ''

2014-10-01 22:10:12,972 [OnStateEventHandler] INFO  - CameraPropertyChangedArgs fired: CameraName           = ''

2014-10-01 22:10:12,972 [OnStateEventHandler] INFO  - CameraPropertyChangedArgs fired: Copyright            = ''

2014-10-01 22:10:12,972 [OnStateEventHandler] INFO  - CameraPropertyChangedArgs fired: DelayShutterMilliseconds = ''

2014-10-01 22:10:12,972 [OnStateEventHandler] INFO  - CameraPropertyChangedArgs fired: DriveMode            = ''

2014-10-01 22:10:12,972 [OnStateEventHandler] INFO  - CameraPropertyChangedArgs fired: Firmware             = ''

2014-10-01 22:10:13,268 [OnStateEventHandler] INFO  - CameraPropertyChangedArgs fired: ImageQuality         = ''

2014-10-01 22:10:13,268 [OnStateEventHandler] INFO  - CameraPropertyChangedArgs fired: Iso                  = ''

2014-10-01 22:10:13,440 [OnStateEventHandler] INFO  - CameraPropertyChangedArgs fired: LensStatus           = ''

2014-10-01 22:10:13,440 [OnStateEventHandler] INFO  - CameraPropertyChangedArgs fired: LiveviewAutoFocusMode = ''

2014-10-01 22:10:13,502 [CameraTakePictureOnMessageRecieved] ERROR - ERROR EDS_ERR_INVALID_HANDLE : EDSDK.EdsSendCommand(cameraRef, 4, 65539)

2014-10-01 22:10:13,502 [CameraTakePictureOnMessageRecieved] ERROR -    at BinaryRivers.Common.ProviderInterfaces.Camera.CameraControllerBase.RunAndThrow(Func`1 function, String info)

   at BinaryRivers.Camera.Canon.Extentions.CameraModelExtentions.<>c__DisplayClass19.<TakePictureSdkBulb>b__11()

   at BinaryRivers.Common.ProviderInterfaces.Camera.CameraControllerBase.DoWithCameraLocked(Action action)

   at BinaryRivers.Camera.Canon.Extentions.CameraModelExtentions.TakePictureSdkBulb(CameraModel cameramodel, Boolean start, Single mirrorlockseconds)

   at BinaryRivers.Camera.Canon.CameraModel.DoTakePictureBulb(Boolean start, Single mirrorlockseconds)

   at BinaryRivers.Common.Model.CameraModelBase.TakePictureBulb(Single durationseconds, Single mirrorlockseconds, String progresstext)

   at BinaryRivers.Common.Model.CameraModelBase.<>c__DisplayClass1.<CameraTakePictureOnMessageRecieved>b__0()

 

 

 

Link to comment
Share on other sites

Hi Guylain:

 

I saw that error midway through the log.  Not sure if the cable was wiggled at that time since there was no indication at the computer that anything was amiss at that point.  This does seem to happen all the time, but at various times after startup.  It usually takes in the range of 1-3 hours after I start imaging.  I have not tried it with EOS utility or another computer.

 

I'll do some more testing based on your suggestions and see what happens.  The plan is to try a different cable (in case connectivity is the issue), a different computer, and perhaps EOS utility if it will let me set up a long imaging run.  It may be a week or more before I get back to you.  I have some busy days coming up, and these tests take hours to run.  Thanks!

Link to comment
Share on other sites

Hi Dan,

 

My first test would be to connect the camera directly in a USB port, not shared with other devices on a hub.  If this solves the issue then the cause is probably data saturation on the usb cable.

 

Keep me posted,

 

Regards.

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