Camera Error after 5 Hours

[bcall]

I've got a recurring problem where my capture plan works perfectly every night for 5-6 hours, then I get a camera error and no more subs are taken. I've attached last night's log, which is typical of what happens each session.

Details: BYE 3.1.16; Canon T6i. I capture raws + jpegs (because my CS5 Adobe Bridge can't read the T6i's raw files) and I capture straight to an external hard drive on my laptop, not the camera's card.

On the log, the last successful sub recorded is at 04:09:08,029. That's when the fun begins. At 04:09:43,799 I get a General Camera Error, followed quickly by an error telling me there's a problem with the camera's card.

Again, I do not record to the camera's card (even though I have a card inserted). And I've checked, and nothing ever gets recorded to the card. But this error apparently stops my capture plan, night after night.

I would love to know what is really happening and how to fix it. Any help at all would be appreciated!

logfile-[20180602-22h02m34s568]-[1504]-2018-06-03.txt

[astroman133]

That is a bizarre threading issue that take 4-5 hours of doing the same thing to manifest itself. The error may be non-fatal, but it appears to stop the capture plan...Not good!

[admin]

I just thought of something.   Try introducing a 2 second pause between images.  I'm curious if this will make a difference in the long run.  If the camera is truly busy this may (or may not) make a difference.  Just a thought.

[admin]

37 minutes ago, astroman133 said:

That is a bizarre threading issue that take 4-5 hours of doing the same thing to manifest itself. The error may be non-fatal, but it appears to stop the capture plan...Not good!

<<GEEK TALK ON>>

Yes, very bizarre.  It is a simple check to see we are in the UI thread and if not an invoke is initiated... which .net guarantees that the control will now be updated in the UI thread.  However, in this case .net pukes on the invoke claiming it is not on the UI thread post invoke.  It does not make any sense.

<<GEEK TALK OFF>

However, I do believe this cross-thread issue has nothing to do with the original camera busy error which is the real issue here.  The cross thread issue is a nuisance for sure but it is not a fatal error that would cause the camera to puke (sort a speak) after 4-5 hours.

[bcall]

2 hours ago, admin said:

I just thought of something.   Try introducing a 2 second pause between images.  I'm curious if this will make a difference in the long run.  If the camera is truly busy this may (or may not) make a difference.  Just a thought.

Before I posted this problem for the first time I set a 5-second delay between shots to see if that would fix it, and it didn't.

I am testing again tonight using a different keep-awake app to see if that helps. So you're thinking the unhandled exception error has nothing to do with the shutdown of the capture plan? That would mean I have two separate, weird things going on?

[admin]

11 hours ago, bcall said:

Before I posted this problem for the first time I set a 5-second delay between shots to see if that would fix it, and it didn't.

I am testing again tonight using a different keep-awake app to see if that helps. So you're thinking the unhandled exception error has nothing to do with the shutdown of the capture plan? That would mean I have two separate, weird things going on?

Yes, unrelated.  The unhandeled error is actually a .net error, not a BYE error.  BYE just catches the error and logs it.  The error originates from the .net libraries.  Is your computer up to date, including the .net framework?

Your real fatal error is the camera throwing the error after 4-5 hours.   The unhandled error is a non fatal and your plan continues so for this reason I'm 100% positive they are unralated.

[bcall]

Okay. Success, but no answers, really.

I finally tested everything ON ANOTHER LAPTOP. Same camera, same USB cable, same BYE settings...and it works perfectly. So I've taken control of my wife's old Acer i3 (which was just sitting around, anyway) as my new capture computer. I'll still process on a faster machine, but now I can run full capture plans.

Obviously, something on my everyday, do-everything laptop was screwing up BYE. We'll never know what, exactly.

Thank you for sticking with this issue!

[admin]

Glad you found an alternative... gremlins