BinaryRivers.BackyardEOS.Start has stopped working

[arn53114]

I am new to the BYE program, and I am having a couple of issues.  My biggest issue is I keep getting the following error message:

"BinaryRivers.BackyardEOS.Start has stopped working.  A problem caused the program to stop working correctly.  Windows will close the program and notify you if a solution is available."

I have attached a picture of the error message.  I am using a Canon EOS Rebel t6/1300d.  Sometimes the program works like a dream, but most of the time I either get this error message and have to close the program, or my camera locks up and keeps saying "Busy" after taking a couple of pictures.  

Also, even though I have the "Save to" location set to camera, when I take pictures by pressing the shutter button with the camera attached to the computer, it will not save the images to my camera.

I really hope someone can help me figure out what I am doing wrong.  I want to use this program for the eclipse in a few days.

[David]

Hello,

I had the same error message : "binary.rivers....."

The only solution which worked in my case : desactivate my antivirus software ( in my case Avast) before to start BYE.

I hope it will work for you as well

David

[astroman133]

Have you tried a different cable? The Canon SDK is not at all tolerant of trying to use a flaky or intermittent connection.

I would also suggest downloading BYE 3.1.14 RC1 from the pre-release area. It fixes a couple of issues that folks have reported with 3.1.13. You can install it in a different folder so your current version will also be available. I do not expect that the upgrade would have an impact on the crashes that you are experiencing, but it would help you avoid other issues down the road.

[arn53114]

37 minutes ago, astroman133 said:

Have you tried a different cable? The Canon SDK is not at all tolerant of trying to use a flaky or intermittent connection.

I would also suggest downloading BYE 3.1.14 RC1 from the pre-release area. It fixes a couple of issues that folks have reported with 3.1.13. You can install it in a different folder so your current version will also be available. I do not expect that the upgrade would have an impact on the crashes that you are experiencing, but it would help you avoid other issues down the road.

I have tried 3 different cables hoping that was the problem.  The issue persisted across all of them.

Where is the pre-release area? I can't seem to find it.

[astroman133]

Select the Downloads tab and select pre-releases from the Categories list on the right-hand side.

[astroman133]

Also, if you want to take pictures with the shutter button, I would suggest you first disconnect BYE from the camera and unplug the camera from the PC. in other words, when you are tethered to the PC you should only control the camera from the PC.

Do you have other USB devices, besides mouse or keyboard, connected when you are testing BYE with the camera. It could be that the PC's internal USB hub is saturated. This happens with low-powered netbooks, all-in-ones, and tablets.

[admin]

Uninstall and reinstall in a different folder to make sure the new installation is isolated from the first.  If this is an installation gone bad this to fix it.

Regards,

[arn53114]

9 hours ago, admin said:

Uninstall and reinstall in a different folder to make sure the new installation is isolated from the first.  If this is an installation gone bad this to fix it.

Regards,

Uninstalled and reinstalled in new folder...error still occurs

[admin]

Send me the log files.

I have over 10,000+ users out there and this is an odd issue, a far cry from being remotely common.  I would think this would be caused by a driver, but this is just a guess.

Is your computer up do date?  .Net up to date?  Anti-virus up to date and scans are clean?

[arn53114]

Logs have been sent.  Thank you for your help with this!  I know this is not a common problem, and may very well be user error.

 

The problem only occurs when I press the shutter button on the camera while it is connected to the computer.  I followed the advice of astroman133, and do not press the shutter button while connected to the computer.  When I do this, I do not receive the error message. I have successfully been able to run a sequence multiple times tonight and take pictures with the physical shutter button.  I am wanting to be able to take pictures manually (with the camera's shutter button) and transition seamlessly into running a sequence without plugging and unplugging the camera.  Is this possible?

 

Thanks! 

[admin]

IF you dismiss the error dialog by pressing the X does BYE close or does it continue to work? 

[admin]

I see your have your camera set to "Continuous Shooting" in the log file you sent.

Set it to "Single-Frame Shooting" and see if this makes a difference.

You should be able to press the shutter button manually and these images should be downloaded to PC when connected to BYE.  I've done this several times in the past.

 

2017-08-17 21:24:43,962 [Main] INFO  - Registered Property DriveMode            = 'Continuous Shooting'  
2017-08-17 21:24:43,962 [Main] INFO  -    [0, Single-Frame Shooting]
2017-08-17 21:24:43,962 [Main] INFO  -    [1, Continuous Shooting]
2017-08-17 21:24:43,962 [Main] INFO  -    [7, 10-Seconds Self-Timer plus continuous shots]
2017-08-17 21:24:43,962 [Main] INFO  -    [16, 10-Seconds Self-Timer]
2017-08-17 21:24:43,962 [Main] INFO  -    [17, 2-Seconds Self-Timer]

 

Regards,

[arn53114]

If I click X, the program closes.  

I set the camera to single frame shooting, the error continues.

Also, is it normal for the program to not run an exposure sequence correctly? Sometimes, it will shoot the previous exposure instead of the correct one.  I have noticed it mainly occurs on exposures over 2 seconds.  For instance, if I have an exposure sequence loaded as follows: 1sec, 1.6sec, 2sec, 4sec, 6sec.  It is common for the program to shoot the following exposure: 1sec, 1.6sec, 2sec, 2sec, 6sec.

[astroman133]

BYE should run your capture plan, as specified. I have never seen the program run a plan out of sequence or deviate from a specified plan.

In your example you indicate that BYE shot a 2 second exposure when you specified a 4 second exposure. How do you know that the exposure was incorrect?

From timing it yourself?

From looking at the file name?

From looking at the EXIF data?

I am unable to duplicate your results.

[admin]

Everything your are reporting here is NOT normal; there has to be something else coming into play.  We need to figure out what.

First I would try on a different computer and see if it works there.  If it does we can focus on your current computer to find the root cause.  If it does not we can focus our effort on either a camera setting and/or software.

Regards,

[arn53114]

Astroman,

I can see the exposure is incorrect by viewing the photo on the camera after the sequence has completed.  Each photo shows the camera settings for that shot.

[arn53114]

Admin,

I will try a different computer and let you know the results.  However, I will not be able to do this until after Monday.  I will let you know the results after I test it.