Version 3 crash

[bwillimd]

Guylain,

 

Last night BYE v.3 crashed on me while taking the 9th of 25 images.  I was dithering at the time (that was the extent of anything "exotic").  I've never encountered any BYE difficulties before.

 

I don't recall the dialog box's message, but it was similar to "this application is no longer responding, do you want to quit now?"

 

I closed the program, reopened and attempted to reconnect with my Canon 450D.  The program never located the camera, and I had to close the application a second time (I had to use the Program Manager to close the software).

 

I opened it a third time. BYE found the camera.  I started imaging, and at the end of a 420-minute exposure the software "countdown clock" read "BUSY" but never supplied the image, nor did it move on to capture the next image (BUSY remained on the screen).

 

We easily finished the session with a backup laptop and BYE (it's a great program).

 

I thought before I uninstall and reinstall the software I would run this by you.

 

Any thoughts on the issue????  May I send the evening logs to you for a necropsy????

 

Mike

[admin]

Guylain,

 

Last night BYE v.3 crashed on me while taking the 9th of 25 images.  I was dithering at the time (that was the extent of anything "exotic").  I've never encountered any BYE difficulties before.

 

I don't recall the dialog box's message, but it was similar to "this application is no longer responding, do you want to quit now?"

 

I closed the program, reopened and attempted to reconnect with my Canon 450D.  The program never located the camera, and I had to close the application a second time (I had to use the Program Manager to close the software).

 

I opened it a third time. BYE found the camera.  I started imaging, and at the end of a 420-minute exposure the software "countdown clock" read "BUSY" but never supplied the image, nor did it move on to capture the next image (BUSY remained on the screen).

 

We easily finished the session with a backup laptop and BYE (it's a great program).

 

I thought before I uninstall and reinstall the software I would run this by you.

 

Any thoughts on the issue????  May I send the evening logs to you for a necropsy????

 

Mike

 

It's hard to say since it was dithering at the time.  During dithering BYE is pretty much idling.  Do you have your mount+camera+guidecamera+etc on the same USB hub connected to the computer.

 

The only thing that comes to mind is connection issues <_>

 

Keep me posted if it occurs again for sure.

 

Regards,

 

 

[bwillimd]

Sorry, I must not have clear. The crash and other issues did not occur while dithering, I simply had BYE set up to dither during the imaging session.

 

A connection issue is possible. I hadn't thought about that, but tend to doubt it. I wasn't near the set up when it crashed, and a cursory check of the equipment post crash revealed nothing out of sorts.

 

Thanks for the input.

 

Mike

[admin]

Sorry, I must not have clear. The crash and other issues did not occur while dithering, I simply had BYE set up to dither during the imaging session. A connection issue is possible. I hadn't thought about that, but tend to doubt it. I wasn't near the set up when it crashed, and a cursory check of the equipment post crash revealed nothing out of sorts. Thanks for the input. Mike

 

Send me the log files... or post them here and I'll take a look.

[admin]

Hi Mike,

Thank you for sending the log files.

 

Looks like the CanonSDK/Camera firmware had issues trying to open a session to the camera and left the camera in a BUSY state... and when this happens BYE has no were to go.  The issue/bug is inside the Canon SDK and/or camera firmware since it failed to return a value and froze <_>

This is a rare but is somewhat common. The only way out is to cycle the camera by removing the battery for about 30 seconds or so. 

You had several of these errors, which confirms the above statement.
2014-06-22 22:34:51,786 [Main] INFO  - Running (throw): EDSDK.EdsOpenSession(_cameraRef)

2014-06-22 22:36:58,739 [Main] INFO  - Running (throw): EDSDK.EdsSetPropertyData(cameraRef, SaveTo(11), 0, size(4), 2)

2014-06-22 22:36:58,754 [Main] DEBUG - BUSY try 1.....

2014-06-22 22:37:13,808 [Main] ERROR - ERROR EDS_ERR_DEVICE_BUSY : EDSDK.EdsSetPropertyData(cameraRef, SaveTo(11), 0, size(4), 2)

 

 

 

Does this make sense?

[bwillimd]

Thank you, Guylain.

 

Yes, I understand your explanation.  Is there are way to prevent future occurrences, or will I be resigned to powering the camera off and on if the event continues?

 

Mike

[astroman133]

It is possible that the issue us caused by a flaky USB cable.  If it persists, you could troubleshoot with a different, shorter cable.

[admin]

It is possible that the issue us caused by a flaky USB cable.  If it persists, you could troubleshoot with a different, shorter cable.

 

It is worth a try for sure.

 

The call is made to the CanonSDK which it turns talk to the camera via the USB cable.  Anything in between these 2 endpoints can be considered a possible root cause.

 

Regards,

[bwillimd]

Excellent thoughts .... I do use a long USB cable .... I'll make the changes.

 

Mike

[admin]

Excellent thoughts .... I do use a long USB cable .... I'll make the changes. Mike

 

How long?  If you go beyond 10 feet make sure it is an active repeater cable.

 

Regards,

 

 

[bwillimd]

It does exceed 10 feet and does not have an active repeater. Strangely, this is the first issue I've ever experienced like this. Again, thanks.

 

Mike

[dts350z]

Maybe we should have a "how to" on long usb cables, powered hubs, and the like.

 

I'd be happy to contribute a link to what I'm using (10 Meters and powered hub from Amazon).

 

When I did the research I saw one astro review where the guy bought two active calbes. One for Guiding and one for imaging, but I haven't seen any issues (that have been proven/suspected to be cable related) with running everything through one.

 

Sorry for the mild thread-jack