Continued crashing

[astronut892010]

My BYE premium has a tendency to crash fairly frequently after the first few images.  I am connected, tracking, and capturing, then suddenly the screen freezes and I get a notice from Windows that BYE has stopped working and offers a choice to wait or close the program.  My only real response is to close since it does not respond.  Can someone help me with diagnostics or other info to help me troubleshoot this.  It has been frustrating to say the least.  Thank you. I really like the product and have had a blast using it.

[admin]

Thanks for the new log file.

I see that you also have RAW + JPG selected.  From the log file the camera is indicating that an image in its memory are ready to download but it fails downloading the second file.

 

These are events:

11-27 23:18:36,525 [Main] DEBUG - ObjectEvent_DirItemRequestTransfer: (inRef=277936984)
2017-11-27 23:18:36,737 [Main] DEBUG - ObjectEvent_DirItemRequestTransfer: (inRef=277938072)

 

This is the first image download

2017-11-27 23:18:37,346 [OnStateEventHandler] DEBUG - OnStateEventHandler Fired! (inEvent=795), inParameter=0)
2017-11-27 23:18:38,761 [OnDirItemRequestTransfer(277936984)] INFO  - Running (log): EDSDK.EdsGetDirectoryItemInfo(inDirItemRef, out dirItemInfo)
2017-11-27 23:18:38,765 [OnDirItemRequestTransfer(277936984)] INFO  - Success: EDSDK.EdsGetDirectoryItemInfo(inDirItemRef, out dirItemInfo)
2017-11-27 23:18:38,765 [OnDirItemRequestTransfer(277936984)] INFO  - Running (log): EDSDK.EdsCreateFileStream(dirItemInfo.szFileName, EDSDK.EdsFileCreateDisposition.CreateAlways, EDSDK.EdsAccess.ReadWrite, out stream)
2017-11-27 23:18:38,770 [OnDirItemRequestTransfer(277936984)] INFO  - Success: EDSDK.EdsCreateFileStream(dirItemInfo.szFileName, EDSDK.EdsFileCreateDisposition.CreateAlways, EDSDK.EdsAccess.ReadWrite, out stream)
2017-11-27 23:18:38,770 [OnDirItemRequestTransfer(277936984)] INFO  - Running (log): EDSDK.EdsDownload(imgRef, dirItemInfo.Size, stream)
2017-11-27 23:18:39,670 [OnDirItemRequestTransfer(277936984)] INFO  - Success: EDSDK.EdsDownload(imgRef, dirItemInfo.Size, stream)
2017-11-27 23:18:39,670 [OnDirItemRequestTransfer(277936984)] INFO  - Running (log): EDSDK.EdsRelease(stream)
2017-11-27 23:18:39,674 [OnDirItemRequestTransfer(277936984)] INFO  - Success: EDSDK.EdsRelease(stream)
2017-11-27 23:18:39,674 [OnDirItemRequestTransfer(277936984)] INFO  - Running (log): EDSDK.EdsDownloadComplete(imgRef)
2017-11-27 23:18:39,680 [OnDirItemRequestTransfer(277936984)] INFO  - Success: EDSDK.EdsDownloadComplete(imgRef)
2017-11-27 23:18:39,683 [OnDirItemRequestTransfer(277936984)] INFO  - Flush Running: (277936984)
2017-11-27 23:18:39,866 [OnStateEventHandler] DEBUG - StateEvent_JobStatusChanged Fired! (inParameter=0) (inContext=0)
2017-11-27 23:18:39,866 [OnStateEventHandler] DEBUG - Items transfered!

 

This is the second image download

2017-11-27 23:18:41,920 [OnDirItemRequestTransfer(277938072)] INFO  - Running (log): EDSDK.EdsGetDirectoryItemInfo(inDirItemRef, out dirItemInfo)
2017-11-27 23:18:41,925 [OnDirItemRequestTransfer(277938072)] INFO  - Success: EDSDK.EdsGetDirectoryItemInfo(inDirItemRef, out dirItemInfo)
2017-11-27 23:18:41,925 [OnDirItemRequestTransfer(277938072)] INFO  - Running (log): EDSDK.EdsCreateFileStream(dirItemInfo.szFileName, EDSDK.EdsFileCreateDisposition.CreateAlways, EDSDK.EdsAccess.ReadWrite, out stream)
2017-11-27 23:18:41,929 [OnDirItemRequestTransfer(277938072)] INFO  - Success: EDSDK.EdsCreateFileStream(dirItemInfo.szFileName, EDSDK.EdsFileCreateDisposition.CreateAlways, EDSDK.EdsAccess.ReadWrite, out stream)
2017-11-27 23:18:41,929 [OnDirItemRequestTransfer(277938072)] INFO  - Running (log): EDSDK.EdsDownload(imgRef, dirItemInfo.Size, stream)
2017-11-27 23:18:41,942 [OnDirItemRequestTransfer(277938072)] INFO  - WARNING EDS_ERR_INTERNAL_ERROR : EDSDK.EdsDownload(imgRef, dirItemInfo.Size, stream) 
2017-11-27 23:18:41,942 [OnDirItemRequestTransfer(277938072)] INFO  - Running (log): EDSDK.EdsDownloadCancel(imgRef)
2017-11-27 23:18:41,948 [OnDirItemRequestTransfer(277938072)] INFO  - Success: EDSDK.EdsDownloadCancel(imgRef)

 

I do see a "Object reference not set to an instance of an object." exception.  This is usually means there is an unhandled error and this is a bug.  However, I'm not sure this is the root cause and could be a side effect of the first error above.

I will try to handle the error below in a future build; this may help but since this is not the root cause I'm not sure if something else will surface.  

2017-11-28 02:29:57,707 [Main] ERROR - Object reference not set to an instance of an object.
2017-11-28 02:29:57,708 [Main] ERROR -    at BinaryRivers.Common.MessageBusArgs.CameraPropertyChangedArgs.get_IsNotSupported()
   at BinaryRivers.Controls.Centers.CameraInformationCenter.Timer1Tick(Object sender, EventArgs e)

 

[astroman133]

First, please make sure that you are able to re-create your issue when using the latest release of BYE; currently 3.1.16.

Second, when reporting an issue, please tell the community which version of BYE you are using and what camera model you are controlling.

Glitches such as you are reporting are often caused by a cabling problem.  Typical reasons are a flaky cable, or a cable that is too long. BYE uses Canon-provided software to communicate with the camera. This software (" the EOS SDK") is sensitive to communications outages, even momentary outages. Try running BYE while your camera is connected to the PC with only the short USB cable that came with the camera; remove any hubs and cable extensions. If the problem persists, you should also try with a different short cable and perhaps on a different PC (you can install BYE on multiple PCs as long as you only use it on 1 system at a time).

Finally, if the problem persists, you should follow the instructions that are detailed in a pinned post in the How To's forum for how to submit your log files to the authors for help in troubleshooting your issue.

[admin]

This looks like a cabling issue as astroman suggested.  

Version of BYE?

Are yo using a USB hub?  How many devices are connected to this hub?

[astronut892010]

I just upgraded my software before making my post and have not been able to try the update yet.  Thank you for the update Guylain.  I am using a 15 foot cable due to using a refractor and needing some slack to my computer without having to keep moving the computer while transitioning targets.  I have a shorter cable, but run into counterbalance issues while tracking due to tension from the cable weight.  I am not connecting through a hub but directly to a USB 3.0 port.  The camera is a Canon 80D, unmodified model.  Thank you for the referral to the How To forum and posting log files.  Forgive me, I am very new to using forums etc. and really appreciate the quick assistance.  After posting, noticed intermittent notices of connecting to the camera from Windows which would suggest a data drop-out or disconnect from my camera.  I will try isolating the cause from cabling etc.  What are the recommended lengths or specifications to minimize noise and dropouts?

[admin]

At 15 feet you are at the maximum length per the USB 2 protocol.

I would use an active repeater cable.  I suspect the signal is getting too week at 15 feet and this seems to be the cause based on past experience.

Try a shorter cable as a test.

[astronut892010]

I will.  Unfortunately, even being in Southern California, we are still subject to things called clouds. ;-)  Also, very high humidity here near the ocean. I will repost once I try the fixes proposed and the new software.  Guylain, I really appreciate your labor of love in this product.  It has worked very well for me.

[astroman133]

But, you can test with the shorter cable while sitting at the kitchen table. All you need is BYE to connect to the camera. The camera doesn't even need a lens. You just want to see if it works or crashes. The pictures are irrelevant. So do your testing when it is cloudy or the sun is out, but don't waste dark skies doing testing!

[astronut892010]

As astroman suggested, I have had my camera set up with the laptop running BYE 3.1.16 with both long (15-ft) and shorter (10-ft) cables.  Shorter cable just arrived yesterday.  Ran test on both battery and AC power.  Problem does not recur.  However, when imaging the other night, had multiple crashes.  Granted, inside a climate controlled environment is not the same as a cool, humid outside night.  Likewise, no other applications were running on the system during the inside test because I did not have the full mount head and other configuration items running.  A "test like you fly" exception.  I will look up the How To section for log file data next.  Wanted to post progress.  Thanks for the assistance.

[astronut892010]

I have sent the log files to the designated email address.  Sorry for the multiple files, I do not remember exactly when the various crashes occurred.  There were several that night and I restarted BYE several times.  Appreciate any insights. Thanks,

[astroman133]

Have you done a field test with the shorter 10 ft. cable yet? If you are unable to re-create the crashes with the shorter cable, then it seems likely that the longer cable was flaky...either faulty or too long.

If the problem persists, then please send only the log file with the errors. That make it more likely that a culprit will be found if it is indeed being logged. If BYE appears to hang, it is likely that the hanging is inside of the Canon SDK. If that is the case the BYE log files may not be revealing.

Keep us updated.

Thanks.

[astronut892010]

I ran the test tonight with the shorter cable, and it crashed partway into the imaging plan I set up for four hours.  Here is the short extract from the log in BYE.  As you can see the download timed out and the session was cancelled.

Let me know if you need the full log file.

Thanks,

16:47:49  Licensed to astronut892010
16:47:49  Processor Affinity
16:51:33  Attempting to connect camera...
16:51:34  Canon drivers 'Canon\' initialized.
16:51:36  80D CONNECTED!
16:51:47  Unable to set LiveviewAutoFocusMode, current setting is assumed!
16:52:06  Unable to set LiveviewAutoFocusMode, current setting is assumed!
17:20:57  Imaging session started.
17:21:17  LIGHT BOX TEST_FLAT_1s_200iso_20171127-17h21m00s598ms.CR2
17:21:28  LIGHT BOX TEST_FLAT_1s_200iso_20171127-17h21m09s492ms.CR2
17:21:36  LIGHT BOX TEST_FLAT_1s_200iso_20171127-17h21m19s856ms.CR2
17:21:59  LIGHT BOX TEST_FLAT_1s_200iso_20171127-17h21m30s691ms.CR2
17:22:06  LIGHT BOX TEST_FLAT_1s_200iso_20171127-17h21m43s068ms.CR2
17:22:18  LIGHT BOX TEST_FLAT_1s_200iso_20171127-17h21m54s974ms.CR2
17:22:27  LIGHT BOX TEST_FLAT_1s_200iso_20171127-17h22m05s558ms.CR2
17:22:35  LIGHT BOX TEST_FLAT_1s_200iso_20171127-17h22m17s780ms.CR2
17:22:45  LIGHT BOX TEST_FLAT_1s_200iso_20171127-17h22m30s969ms.CR2
17:22:55  LIGHT BOX TEST_FLAT_1s_200iso_20171127-17h22m41s150ms.CR2
17:23:06  LIGHT BOX TEST_FLAT_1s_200iso_20171127-17h22m51s549ms.CR2
17:23:16  LIGHT BOX TEST_FLAT_1s_200iso_20171127-17h23m01s979ms.CR2
17:23:27  LIGHT BOX TEST_FLAT_1s_200iso_20171127-17h23m12s496ms.CR2
17:23:37  LIGHT BOX TEST_FLAT_1s_200iso_20171127-17h23m22s953ms.CR2
17:23:47  LIGHT BOX TEST_FLAT_1s_200iso_20171127-17h23m33s372ms.CR2
17:23:58  LIGHT BOX TEST_FLAT_1s_200iso_20171127-17h23m43s663ms.CR2
17:24:08  LIGHT BOX TEST_FLAT_1s_200iso_20171127-17h23m53s820ms.CR2
17:24:18  LIGHT BOX TEST_FLAT_1s_200iso_20171127-17h24m04s151ms.CR2
17:24:29  LIGHT BOX TEST_FLAT_1s_200iso_20171127-17h24m14s552ms.CR2
17:24:39  LIGHT BOX TEST_FLAT_1s_200iso_20171127-17h24m24s977ms.CR2
17:24:49  LIGHT BOX TEST_FLAT_1s_200iso_20171127-17h24m35s303ms.CR2
17:24:59  LIGHT BOX TEST_FLAT_1s_200iso_20171127-17h24m45s610ms.CR2
17:25:10  LIGHT BOX TEST_FLAT_1s_200iso_20171127-17h24m55s881ms.CR2
17:25:21  LIGHT BOX TEST_FLAT_1s_200iso_20171127-17h25m06s225ms.CR2
17:25:31  LIGHT BOX TEST_FLAT_1s_200iso_20171127-17h25m17s236ms.CR2
17:25:41  LIGHT BOX TEST_FLAT_1s_200iso_20171127-17h25m27s600ms.CR2
17:25:52  LIGHT BOX TEST_FLAT_1s_200iso_20171127-17h25m37s928ms.CR2
17:26:02  LIGHT BOX TEST_FLAT_1s_200iso_20171127-17h25m48s388ms.CR2
17:26:13  LIGHT BOX TEST_FLAT_1s_200iso_20171127-17h25m58s748ms.CR2
17:26:18  Imaging session completed successfully
17:26:23  LIGHT BOX TEST_FLAT_1s_200iso_20171127-17h26m09s047ms.CR2
17:29:00  Imaging session started.
17:29:35  PREVIEW_20171127-17h29m04s571ms.JPG
17:29:43  Imaging session completed successfully
17:32:03  Imaging session started.
17:32:27  PREVIEW_20171127-17h32m06s759ms.JPG
17:32:35  Imaging session completed successfully
17:38:00  Imaging session started.
17:41:18  NGC 7160 BYE CABLE TEST_LIGHT_180s_200iso_+23c_20171127-17h38m02s961ms.CR2
17:44:27  NGC 7160 BYE CABLE TEST_LIGHT_180s_200iso_+23c_20171127-17h41m13s368ms.CR2
17:47:39  NGC 7160 BYE CABLE TEST_LIGHT_180s_200iso_+23c_20171127-17h44m23s774ms.CR2
17:50:51  NGC 7160 BYE CABLE TEST_LIGHT_180s_200iso_+23c_20171127-17h47m34s508ms.CR2
17:54:01  NGC 7160 BYE CABLE TEST_LIGHT_180s_200iso_+23c_20171127-17h50m45s743ms.CR2
17:57:12  NGC 7160 BYE CABLE TEST_LIGHT_180s_200iso_+23c_20171127-17h53m56s618ms.CR2
18:00:21  NGC 7160 BYE CABLE TEST_LIGHT_180s_200iso_+23c_20171127-17h57m07s773ms.CR2
18:06:18  NGC 7160 BYE CABLE TEST_LIGHT_180s_200iso_+23c_20171127-18h03m06s883ms.CR2
18:09:28  NGC 7160 BYE CABLE TEST_LIGHT_180s_200iso_+23c_20171127-18h06m16s790ms.CR2
18:12:38  NGC 7160 BYE CABLE TEST_LIGHT_180s_200iso_+23c_20171127-18h09m26s806ms.CR2
18:15:47  NGC 7160 BYE CABLE TEST_LIGHT_180s_200iso_+23c_20171127-18h12m36s462ms.CR2
18:18:57  NGC 7160 BYE CABLE TEST_LIGHT_180s_200iso_+23c_20171127-18h15m46s337ms.CR2
18:22:07  NGC 7160 BYE CABLE TEST_LIGHT_180s_200iso_+23c_20171127-18h18m56s008ms.CR2
18:25:17  NGC 7160 BYE CABLE TEST_LIGHT_180s_200iso_+23c_20171127-18h22m05s649ms.CR2
18:28:26  NGC 7160 BYE CABLE TEST_LIGHT_180s_200iso_+23c_20171127-18h25m15s586ms.CR2
18:31:36  NGC 7160 BYE CABLE TEST_LIGHT_180s_200iso_+23c_20171127-18h28m25s180ms.CR2
18:34:46  NGC 7160 BYE CABLE TEST_LIGHT_180s_200iso_+23c_20171127-18h31m35s134ms.CR2
18:37:56  NGC 7160 BYE CABLE TEST_LIGHT_180s_200iso_+23c_20171127-18h34m44s900ms.CR2
18:41:06  NGC 7160 BYE CABLE TEST_LIGHT_180s_200iso_+23c_20171127-18h37m54s727ms.CR2
18:44:15  NGC 7160 BYE CABLE TEST_LIGHT_180s_200iso_+23c_20171127-18h41m04s728ms.CR2
18:47:25  NGC 7160 BYE CABLE TEST_LIGHT_180s_200iso_+23c_20171127-18h44m14s571ms.CR2
18:50:35  NGC 7160 BYE CABLE TEST_LIGHT_180s_200iso_+23c_20171127-18h47m24s352ms.CR2
18:53:45  NGC 7160 BYE CABLE TEST_LIGHT_180s_200iso_+23c_20171127-18h50m33s993ms.CR2
18:56:55  NGC 7160 BYE CABLE TEST_LIGHT_180s_200iso_+23c_20171127-18h53m43s665ms.CR2
19:03:54  Imaging session cancelled
19:04:58  Image download timeout, process terminated after 239 seconds
19:06:01  Camera SHUTDOWN!

[astronut892010]

I sent the log files to support@otelescope as requested.  looking forward to feedback and insights.

 

[admin]

I never got them but judging by what you posted this is no evidence of any crash, the download simple timed out.  This is ususaly causes by the camera not firing the image ready to download event.  The full log file should help.

[astronut892010]

I just resent the log file as both a direct attachment and as a OneDrive file for sharing.

thank you.

Jay

[astronut892010]

also, this time it did not behave the same as the other events. During the other events, the BYE screen would freeze, Windows would report the program is not responding and ask if I want to wait or close the program.  Sometimes I would wait, other times I would close the program.  This time, I was away from the computer for at least three hours and returned showing the camera was shutdown and the imaging session was cancelled.  I had never seen those messages before because the program was hung.  I had previously sent log files to the email specified from another evening where my imaging was terminated early several times through the night.  Again, any help is appreciated.

[admin]

Well, you have a few errors in there but the first error is always the one to look at since the others are often caused by the first one.

This is what I see.

2017-11-27 17:21:14,420 [BackgroundWorkerPolling] INFO  - C:\Users\Jay\Pictures\BackyardTEMP\BackgroundWorker\task-2ca0c689-8720-4262-a900-952ae9d11b59-callback.dat
2017-11-27 17:21:15,627 [OnDirItemRequestTransfer(5287432)] INFO  - Running (log): EDSDK.EdsGetDirectoryItemInfo(inDirItemRef, out dirItemInfo)
2017-11-27 17:21:15,631 [OnDirItemRequestTransfer(5287432)] INFO  - Success: EDSDK.EdsGetDirectoryItemInfo(inDirItemRef, out dirItemInfo)
2017-11-27 17:21:15,631 [OnDirItemRequestTransfer(5287432)] INFO  - Running (log): EDSDK.EdsCreateFileStream(dirItemInfo.szFileName, EDSDK.EdsFileCreateDisposition.CreateAlways, EDSDK.EdsAccess.ReadWrite, out stream)
2017-11-27 17:21:15,665 [OnDirItemRequestTransfer(5287432)] INFO  - Success: EDSDK.EdsCreateFileStream(dirItemInfo.szFileName, EDSDK.EdsFileCreateDisposition.CreateAlways, EDSDK.EdsAccess.ReadWrite, out stream)
2017-11-27 17:21:15,665 [OnDirItemRequestTransfer(5287432)] INFO  - Running (log): EDSDK.EdsDownload(imgRef, dirItemInfo.Size, stream)
2017-11-27 17:21:15,684 [OnDirItemRequestTransfer(5287432)] INFO  - WARNING EDS_ERR_INTERNAL_ERROR : EDSDK.EdsDownload(imgRef, dirItemInfo.Size, stream) 
2017-11-27 17:21:15,684 [OnDirItemRequestTransfer(5287432)] INFO  - Running (log): EDSDK.EdsDownloadCancel(imgRef)
2017-11-27 17:21:15,690 [OnDirItemRequestTransfer(5287432)] INFO  - Success: EDSDK.EdsDownloadCancel(imgRef)
 

The camera is firing the event indicating an image is ready to download but the camera is not providing the image and it throws a EDS_ERR_INTERNAL_ERROR error when that same image is being downloaded. 

Do you have a card in the camera?  Maybe this could cause this.  Just a hunch.

Regards,

[astronut892010]

This is almost like a chat session.    I do have a card, but I have disabled writing to the card.  I will remove the card and see what comes of it next.

[astronut892010]

This is strange.  I aborted the image, but BYE shutdown the camera.

Here is thelog.

21:56:54  Licensed to astronut892010
21:56:54  Processor Affinity
21:59:17  Attempting to connect camera...
21:59:17  Canon drivers 'Canon\' initialized.
21:59:19  80D CONNECTED!
22:01:09  Imaging session started.
22:01:31  PREVIEW_20171127-22h01m12s993ms.JPG
22:01:36  Imaging session completed successfully
22:02:20  Imaging session started.
22:02:45  PREVIEW_20171127-22h02m23s728ms.JPG
22:02:55  Imaging session completed successfully
22:07:34  Imaging session started.
22:10:50  MAIA NEBULA FR CABLE TEST_LIGHT_180s_200iso_+14c_20171127-22h07m36s962ms.CR2
22:14:00  MAIA NEBULA FR CABLE TEST_LIGHT_180s_200iso_+16c_20171127-22h10m46s587ms.CR2
22:17:11  MAIA NEBULA FR CABLE TEST_LIGHT_180s_200iso_+17c_20171127-22h13m57s071ms.CR2
22:20:23  MAIA NEBULA FR CABLE TEST_LIGHT_180s_200iso_+17c_20171127-22h17m07s649ms.CR2
22:23:39  MAIA NEBULA FR CABLE TEST_LIGHT_180s_200iso_+18c_20171127-22h20m19s164ms.CR2
22:26:51  MAIA NEBULA FR CABLE TEST_LIGHT_180s_200iso_+19c_20171127-22h23m34s801ms.CR2
22:29:59  MAIA NEBULA FR CABLE TEST_LIGHT_180s_200iso_+19c_20171127-22h26m46s649ms.CR2
22:33:09  MAIA NEBULA FR CABLE TEST_LIGHT_180s_200iso_+19c_20171127-22h29m55s681ms.CR2
22:36:16  MAIA NEBULA FR CABLE TEST_LIGHT_180s_200iso_+20c_20171127-22h33m04s636ms.CR2
22:39:27  MAIA NEBULA FR CABLE TEST_LIGHT_180s_200iso_+20c_20171127-22h36m14s607ms.CR2
22:40:18  Imaging session completed successfully
22:40:21  ABORT_LIGHT_45s_200iso_+20c_20171127-22h39m24s930ms.CR2
22:41:13  Camera SHUTDOWN!

[astronut892010]

Oh, and the SD card has been removed.

[admin]

That is not a full log and does not do me any good.  I need for full log.

[astronut892010]

I sent you an email with the full log plus the logs from the background workers this evening as well.

[admin]

Okay, I see you played with the advance settings.  Please restore them to default value, then restart BYE.

I also see you are playing the the screen stretch.  Don't do that for now, keep your interaction to the minimum and simply take images without card.

[astronut892010]

I followed your instructions.  Reset advance settings to default.  Reset screen stretch.  Restarting BYE.  Setting up a 3-hour imaging pass on the Cone nebula (just to have data to view).

starting now.

[astronut892010]

So far so good.  I will let you know how the rest of the night goes.

[astronut892010]

Well, good news and bad news.  The 3-hour imaging session worked correctly.  When I started collecting flats, things went well until near the end of 30 frames, then the screen froze at Downloading.  I got Windows messages saying the program is not responding.  Then another smaller window that the debug script had an error.  Then Windows closed the program.  I will send a copy of the log file.

[astroman133]

What exposure were you using for the flats? Was your guiding software still running when you were shooting flats?

Your thread is long, but you have said that you are not able to recreate your issue with the camera connected to the PC and BYE, but without any other equipment (mount, focuser, guide camera, etc.). Is that correct?

If so, then I would do some more bench testing. I would add the guide camera to the mix...That is, set up PHD to loop (no need to really guide), and set BYE up to run a capture plan that has both exposures for shooting light frames and flat frames.

I do not believe that there is any fundamental issue with BYE or more users would be seeing similar issues. This is more likely due to some issue with your PC, the cabling, or the camera itself.

Low-powered PCs like netbooks or tablets can suffer from USB overload. Downloading images from your 80D and a guide camera at the same time could be causing the image to fail to download.

[astronut892010]

astroman, I am running on an i7 fifth generation laptop and connected through USB 3.0 ports.  I think the guiding software was running at the same time, PHD2.  During my last bench test, I included bias shots to emulate short exposure flats.  Since I had a lens cap on for the duration of the test, actually trying to take AV flats would not have worked.  Setting BYE back to defaults through Advance settings and removing the SD card seems to have helped the consistency of the imaging plan for at least a 3-hour duration.  While BYE, the software package, may not have a problem.  How it is interacting in my system (computer, camera, cabling, environment, etc.) is a problem since I currently cannot predict if I will get a full imaging session with my setup.  I really appreciate the team's help in trying to troubleshoot and isolate the culprit so I can continue to use the BYE product that I really, really like.

[astronut892010]

astroman, also, my flats were shot at approx 1s at iso 200.

[astroman133]

OK, so PC horsepower should not be an issue.

Unfortunately your issue seems to be occurring not in BYE, but in the Canon SDK that BYE uses. The SDK is particularly sensitive to momentary communication glitches.

From a cabling standpoint, you are plugging a USB 2.0 cable from the camera into a USB 3.0 port on the PC. Do you have any USB 2.0 ports on the PC? If so, you could test the camera when plugged into a 2.0 port. PC's have built-in USB hubs. Often, if one USB 2.0 device is plugged into a USB 3.0 hub, the entire hub is slowed to USB 2.0 speeds. If your guide camera were a USB 3.0 device, it too would be slowed down to USB 2.0 speed, if it were plugged in next to where the 80D is connected. Also, if the PC has USB ports on both sides of the PC then there are usually different hubs for each side. Plugging the USB 2 and USB 3 devices into ports on opposite sides of the PC may allow the USB 3 devices to operate at full speed.

Please check out and report what kind of USB ports the PC has and where they are located. If it has one or more USB 2.0 ports, try plugging the 80D into one of them and do some testing to simulate capture of lights and flats. Try it both with and without operating the guide camera with PHD.

Thanks for your patience.

[admin]

Oh, since the error occurs on the second download try taking raw images only, no jpg, and see if this makes a difference.