Cannot capture image with Canon 600D with BYE 3.2.2

[srowlands]

Whilst I have used Canon 600D with BYE 3.2.2 successfully some time back, I now cannot get BYE to capture at all. I have attached the most recent log files.

I would appreciate some guidance. I have replaced the short USB cable.

 

logfile-[20230309-19h39m04s074]-[5904]-2023-03-09.txt logfile-[20230309-19h39m12s172]-backgroundworker-[5684]-2023-03-09.txt

[srowlands]

Thanks everyone for your assistance. The problem was finally found to be the 12V DC to 7.4V DC converter.

It was the source all sorts of misleading behaviour in the camera itself, and the camera's interaction with BYE software.

Without an oscilloscope I cannot confirm, but I suspect the 7.4V DC output from the converter is not a clean DC and this was upsetting the camera.

I am now using battery power from the Canon battery pack LP-E8.

[astroman133]

Two possible causes come to mind.

1) you are shooting with a lens on the camera and the lens is trying to autofocus, but never succeeding, so it does not take a picture.

2) your anti-virus software is preventing the image from being downloaded.

So, remove the lens and take a test picture with the body cap in place, or when connected to a telescope and/or temporarily disable your anti-virus software.

[s3igell]

The 600D has a setting which needs to set to allow it to take an Image without a Lens (or without receiving an "In Focus" signal).

This setting is "C.Fn III: Others".

[admin]

That log file shows a .net error. Please re-install and make sure your computer is up-to-date, including .net 4.5.

2023-02-16 22:49:04,343 [Main] ERROR - Arithmetic operation resulted in an overflow.
2023-02-16 22:49:04,343 [Main] ERROR -    at DevExpress.Utils.AppearanceHelper.GetFontHashCodeCore(Font font)

If you really have connected your camera it means you have already gone past this error, in this case, please send that log file.

[srowlands]

Thanks Admin, but the fragments you quoted are not from the two log files I uploaded, so I am not sure what you mean. I will check my .NET 4.5 install though and I will check what @astroman133 and @s3igell have suggested.

[srowlands]

After considerable experimentation, I suspect my problem is with the power supply I am using to power the camera.

If I use the camera battery, everything seems to work OK.

When I use either of my two different brands of lithium powerpacks (12V) powering my 12V to 7.4V DC inverter, the lithium powerpacks power off after a time. This is now part of my ongoing investigation.

Thanks for the help. I will submit results of my testing in due course.

[astroman133]

Assuming that you are reducing 12V DC to 7.4V DC. You are not using an inverter which converts DC power to AC power. I think that your device is a DC regulator. It needs to provide the amperage required by the camera at the expected voltage.

[admin]

14 hours ago, srowlands said:

Thanks Admin, but the fragments you quoted are not from the two log files I uploaded, so I am not sure what you mean. I will check my .NET 4.5 install though and I will check what @astroman133 and @s3igell have suggested.

you're right, my bad.

[srowlands]

I eventually confirmed that the lithium power supply times out after 30sec if current draw (12V DC) is very low.

I have now fixed that but I now have a new problem.

The attached logs show that I took one exposure (RAW  + JPG) successfully. No lens fitted. Bulb (M) setting. Only the 600D camera connected to the USB.

I then added a second exposure to the plan, but the BYE just hung and one of the logs show:-

19:56:49  Imaging session started.
19:57:03  Imaging session cancelled
19:57:03  ERROR EDS_ERR_DEVICE_BUSY : EDSDK.EdsSendCommand(cameraRef, 4, 65539) 
19:57:06  Imaging session cancelled

I have attached the logs.

19:55:31  Licensed to srowlands
19:55:31  Processor Affinity
19:55:32  BackyardEOS 3.2.2 Premium Edition
19:55:39  Attempting to connect camera...
19:55:39  Canon drivers 'Canon\' initialized.
19:55:41  600D-T3i CONNECTED!
19:56:09  Imaging session started.
19:56:21  Imaging session completed successfully
19:56:23  LIGHT_2s_1600iso_20230314-19h56m11s470ms.CR2
19:56:23  LIGHT_2s_1600iso_20230314-19h56m11s470ms.jpg
19:56:49  Imaging session started.
19:57:03  Imaging session cancelled
19:57:03  ERROR EDS_ERR_DEVICE_BUSY : EDSDK.EdsSendCommand(cameraRef, 4, 65539) 
19:57:06  Imaging session cancelled

Any advice would be appreciated.

logfile-[20230314-19h55m23s404]-[11312]-2023-03-14.txt logfile-[20230314-19h55m30s650]-backgroundworker-[5764]-2023-03-14.txt

[astroman133]

I am a user, like yourself, and am not an expert at reading the logs.

The logs appear to support what you have said. During the first run, a single exposure is taken and both the RAW and JPG images are downloaded and processed. When an attempt is made to start another run, the camera fails and reports that it is busy.

I would suggest a couple of things. 1) BYE takes the images 1 at a time, so the fact that you changed the number of exposures from 1 to 2 before the failure is coincidental. 2) Simplify what you are trying to do by shooting RAW only. If I remember correctly, downloading RAW+JPG has caused issues with some models, but not for quite some time.

Try again and see if that makes any difference in your symptoms.

[s3igell]

Another element to check - Disable Long Exposure Noise Reduction (LENR).

While LENR is useful for single Long Exposures (it performs a Dark Exposure after each Light Exposure), this is less helpful / more detrimental for Deep Sky Multi-Exposure Shooting.  1) It doesn't leverage the Noise Reduction of Averaging Multiple Shots; and 2) it extends the Duration at which the Camera is BUSY after a "Normal Exposure" Shutter Action.

I don't believe this is actually the cause of your problem, else the 1st Image wouldn't have been Ready nor Downloaded while the Camera was still BUSY with the LENR Exposure.

[s3igell]

As Rick (astroman133) indicates, RAW+ JPEG is unnecessary for most Imaging Workflows.  With modern Operating Systems and Apps, all are readily capable of extracting the Embedded JPG Image from the RAW CR2 File.  And for actual Calibration and Stacking, only the RAW is wanted...

[admin]

With some camera model, taking RAW+JPG will cause issue. This is a behaviour more common with Nikon than Canon, but as mentioned above, try RAW only and see if it makes a difference.

Another thing this to try is to do a camera factory reset, this may fix it, especially if over the years you may have inadvertently changed a setting that may be causing this.

[srowlands]

I have been away on holidays.

I changed to RAW Only and it did not help. I usually use RAW only for astro work, but I had done some other work with the camera and had RAW + JPG set. My bad.

I will try a factory reset of the camera in a day or so when I get the chance. Also will examine the USB configuration on this port.

[astroman133]

The only historic issue with USB port configuration is related to Windows being configured to power down the port to extend battery life. That is unlikely to be causing your issue, although you should configure Windows to never power USB ports down to extend battery life.

[admin]

5 hours ago, srowlands said:

Thanks everyone for your assistance. The problem was finally found to be the 12V DC to 7.4V DC converter.

It was the source all sorts of misleading behaviour in the camera itself, and the camera's interaction with BYE software.

Without an oscilloscope I cannot confirm, but I suspect the 7.4V DC output from the converter is not a clean DC and this was upsetting the camera.

I am now using battery power from the Canon battery pack LP-E8.

Glad you made it work. Troubleshooting an issue where the root cause is power delivery is not an easy one to track down.