Frequent Unhandled exception

[Mike]

I have frequently experienced an unhandled exception while using Backyard EOS V3.0.0 Premium edition. This unhandled exception only occurs while using BYE. It happens while using BYE alone or with the whole pallet of apps while imaging. The details of the exception with the BYE log at time of the error pasted to the bottom are attached.

While imaging I can just click "Continue", but on nights where I'm capturing Darks and the computer is unattended BYE shuts down by itself after some period of time. I'd really like to find a solution to the problem as it is using up a lot of my dark capture time. I also realize that it might not be a BYE problem. I just thought I'd try here because it only happens with BYE and that seems like the first branch in the troubleshooting tree.

Thanks for giving it a look.

Clear skies,

Mike

BYE_Exception.txt

[Mike]

A little more information. Tonight I have a capture plan for Darks running again. After about 2 hrs 45 min and 15 frames into the capture plan I got the Unhandled Exception again. The Queue box indicated 1 "waiting for processing". The 1 flashed for about the next 5 minutes while the next frame was capturing.

 

I clicked Suspend and at the end of the capture that was in progress. The pending Queue went to 2. I waited about a minute with no change. I clicked resume and the next frame started while the 2 flashed.

 

Next I clicked abort and ended up with a flashing 3. At that point I clicked Disconnect Camera, then Reconnect Camera, adjusted the capture plan and started capture again. During the next Capture the Queue started flashing 4.

 

Next I Clicked Disconnect Camera and tried to shutdown BYE. I got a warning that BYE was trying to download images and was asked if I really wanted to do that. I declined clicked Connect and tried starting capture. The Flashing 4 returned.

 

Next I Clicked Disconnect, turned the camera off then on again. I then restarted the capture plan. The Queue cleared. When the first image in the restarted capture plan finished capturing and indicated Downloading the Queue went to 5.

 

I aborted and waited for the download to complete. I t did not. The Queue went to 6.

 

Once again I Clicked Disconnect and this time I disconnected and reconnected the USB cable at the camera. I restarted the capture plan, waited about 45 seconds and aborted. You guessed it, the Queue went to 7.

 

This time I Clicked Disconnect and closed the program. When given the warning that there were images awaiting download I clicked Quit, the restarted BYE. I reloaded the capture plan, adjusted it for the exposures already captured and restarted the capture plan. After 45 seconds I clicked Abort. The Queue flashed 1 for a couple of seconds then cleared. I restarted the capture plan.

 

After the first full capture the Queue cleared after four seconds.

 

I hope this helps with diagnostics.

 

Mike

[admin]

Unhandled exception are NOT suppose to occur <_>

 

Please send me the log files at support@binaryrivers.com and I will take a look.

 

Regards,

[ftheadley]

A little more information. Tonight I have a capture plan for Darks running again. After about 2 hrs 45 min and 15 frames into the capture plan I got the Unhandled Exception again. The Queue box indicated 1 "waiting for processing". The 1 flashed for about the next 5 minutes while the next frame was capturing.

 

I clicked Suspend and at the end of the capture that was in progress. The pending Queue went to 2. I waited about a minute with no change. I clicked resume and the next frame started while the 2 flashed.

 

Next I clicked abort and ended up with a flashing 3. At that point I clicked Disconnect Camera, then Reconnect Camera, adjusted the capture plan and started capture again. During the next Capture the Queue started flashing 4.

 

Next I Clicked Disconnect Camera and tried to shutdown BYE. I got a warning that BYE was trying to download images and was asked if I really wanted to do that. I declined clicked Connect and tried starting capture. The Flashing 4 returned.

 

Next I Clicked Disconnect, turned the camera off then on again. I then restarted the capture plan. The Queue cleared. When the first image in the restarted capture plan finished capturing and indicated Downloading the Queue went to 5.

 

I aborted and waited for the download to complete. I t did not. The Queue went to 6.

 

Once again I Clicked Disconnect and this time I disconnected and reconnected the USB cable at the camera. I restarted the capture plan, waited about 45 seconds and aborted. You guessed it, the Queue went to 7.

 

This time I Clicked Disconnect and closed the program. When given the warning that there were images awaiting download I clicked Quit, the restarted BYE. I reloaded the capture plan, adjusted it for the exposures already captured and restarted the capture plan. After 45 seconds I clicked Abort. The Queue flashed 1 for a couple of seconds then cleared. I restarted the capture plan.

 

After the first full capture the Queue cleared after four seconds.

 

I hope this helps with diagnostics.

 

Mike

[admin]

A little more information. Tonight I have a capture plan for Darks running again. After about 2 hrs 45 min and 15 frames into the capture plan I got the Unhandled Exception again. The Queue box indicated 1 "waiting for processing". The 1 flashed for about the next 5 minutes while the next frame was capturing.

 

I clicked Suspend and at the end of the capture that was in progress. The pending Queue went to 2. I waited about a minute with no change. I clicked resume and the next frame started while the 2 flashed.

 

Next I clicked abort and ended up with a flashing 3. At that point I clicked Disconnect Camera, then Reconnect Camera, adjusted the capture plan and started capture again. During the next Capture the Queue started flashing 4.

 

Next I Clicked Disconnect Camera and tried to shutdown BYE. I got a warning that BYE was trying to download images and was asked if I really wanted to do that. I declined clicked Connect and tried starting capture. The Flashing 4 returned.

 

Next I Clicked Disconnect, turned the camera off then on again. I then restarted the capture plan. The Queue cleared. When the first image in the restarted capture plan finished capturing and indicated Downloading the Queue went to 5.

 

I aborted and waited for the download to complete. I t did not. The Queue went to 6.

 

Once again I Clicked Disconnect and this time I disconnected and reconnected the USB cable at the camera. I restarted the capture plan, waited about 45 seconds and aborted. You guessed it, the Queue went to 7.

 

This time I Clicked Disconnect and closed the program. When given the warning that there were images awaiting download I clicked Quit, the restarted BYE. I reloaded the capture plan, adjusted it for the exposures already captured and restarted the capture plan. After 45 seconds I clicked Abort. The Queue flashed 1 for a couple of seconds then cleared. I restarted the capture plan.

 

After the first full capture the Queue cleared after four seconds.

 

I hope this helps with diagnostics.

 

Mike

 

Thanks, this is with BYE 3.0.3 or BYE 3.1 RC01?

 

Regards,

[ftheadley]

After about a one year break from the Canon 500D I decided to give it a try again instead of the mono CCD. I started BYEOS v3.0.3 on my HP iCore7, 8GB, 750GB HD, connected the 500D with a 2m cable to a USB3.0 port and began the imaging session by collecting 120 second darks. All functioned well through the first nine of 36 images when an "out of memory" error occurred. I rebooted everything and finished the session. The following day a similar event occurred with the same error message. Upon reviewing the logs I find many warnings and reference to EDSDK. How can I verify that I have the correct and most up to date support programs for BYEOS?

 

Frank Headley

27 N - 121 W

[admin]

After about a one year break from the Canon 500D I decided to give it a try again instead of the mono CCD. I started BYEOS v3.0.3 on my HP iCore7, 8GB, 750GB HD, connected the 500D with a 2m cable to a USB3.0 port and began the imaging session by collecting 120 second darks. All functioned well through the first nine of 36 images when an "out of memory" error occurred. I rebooted everything and finished the session. The following day a similar event occurred with the same error message. Upon reviewing the logs I find many warnings and reference to EDSDK. How can I verify that I have the correct and most up to date support programs for BYEOS?

 

Frank Headley

27 N - 121 W

 

BYE v3.0.3 is the latest.

 

EDIT:  I'm no longer using the Canon SDK to load images in v3.1 so this should be fixed when I release 3.1 sometime this summer.

 

Regards,

[Mike]

I'm using 3.0.0 premium.

[admin]

I'm using 3.0.0 premium.

 

It doesn't hurt to upgrade to v3.0.3.  It's free.

 

Regards,

[astroman133]

Is it possible that Frank's issue is due to the fact that he is using USB 3.0?  If I remember correctly, others had problems using USB 3.0 ports.

[admin]

Is it possible that Frank's issue is due to the fact that he is using USB 3.0?  If I remember correctly, others had problems using USB 3.0 ports.

 

Anything is possible... that would be the first reported case where the Canon SDK/Driver would fail under USB 3.0 if that would be the case.

 

Do you have a USB 2.0 hub you can connect into your computer, then the camera in the USB hub?

 

Regards,

[astroman133]

There was someone, back in late April, who reported eliminating lockups in BYE by switching from a USB 3.0 to a USB 2.0 connection.

[admin]

There was someone, back in late April, who reported eliminating lockups in BYE by switching from a USB 3.0 to a USB 2.0 connection.

 

Oh... that one slipped, I don't remember <_>

 

Thanks for pointing it out Rick.

 

Regards,

[ftheadley]

There was someone, back in late April, who reported eliminating lockups in BYE by switching from a USB 3.0 to a USB 2.0 connection.

 

Oh... that one slipped, I don't remember <_<

 

Thanks for pointing it out Rick.

 

Regards,