Save To camera hang after first frame

[Lacni135]

Hi!
I'm using BackyardEOS 3.1.18 With a Canon 200D-SL2.
I was trying to do a timelapse by saving the image directly to the camera (to prevent the download time). I selected the option "Save To: Camera" as a result. The problem is that after the first image was taken, The software finished the first frame and stayed busy forever. The wheel was turning and the software was responding. My camera returned to its manual settings view on the liveView. I tried checking inside the log file but couldn't find any useful information to me. Normally i use "Save To: PC" and this works fine.

(I attached the logfile of the session)

Any ideas?
Thx in advance!

logfile-20200420-16h50m54s719-1560-2020-04-20.txt

[admin]

I've seen this before. The issue is related to the card write speed. When the command is issued to take the second picture, the camera is still busy writing the previous image to card. Adding the pause confirmed this.

Regards,

[admin]

Can you reproduce the error?

If yes try again, and then let the busy thingy last for at least 1 minute.  Kill the process in windows, and send me that log file.

Thank you.

[Lacni135]

Thank you for the answer,
I am able to reproduce the error consistently. Here is the new logfile following your instruction.

I also noticed that there was a background process of BYE still running (during the previous logfile when i shutdown the camera while the software was busy and then closed the software) if this is of any help whatsoever

logfile-20200420-17h40m43s380-408-2020-04-20.txt

[Lacni135]

Also, the problem only happens when i do more than 1 frame (1 frame only works fine).
The first image is also saved correctly to the SD card when the process is hangs and stays busy.

[admin]

if you put a 10 second pause between images does it work?

[Lacni135]

Alright so I tried with 10 sec, 5 sec and 2 sec pausing and they all work fine. Only with the 0 and 1 sec pausing the programs hang.

[s3igell]

Please consider performing a Factory Reset on the Camera, to ensure you haven't inadvertently selected a non-obvious setting which causes the Camera to ignore the USB Input for a second or two after each Image.

Realize that Canon does nothing to document What is occurring inside the Camera, nor which Settings either long existing or newly implemented will have specific impacts on the USB Interface.

 

[Lacni135]

I see. Is there any reason why a regular intervalometer doesn't have this problem? Difference between the intervalometer i/o compare to usb?

[astroman133]

The intervalometer is not talking to the camera though the Canon SDK, as BYE does. From your log file the "Camera BUSY" message is coming from the SDK. According to the log file (if I am reading it correctly) it only took 2 seconds to save the image to the card. Depending on the speed of the card, that is not excessive. Does your SD card meet the camera's minimum speed requirement?

Guylain, are you sure that BYE is handling the "Items transferred!" message as a trigger for issuing the next Take Picture command? While the log file appears to be truncated, it does not show the next command being issued.

[Lacni135]

I am using the Sandisk Extreme Pro 128GB  with "170MB/s".
I thought this would be enough.

*On the amazon page "Shot speeds up to 90MB/s*, transfer speeds up to 170MB/s"*

[astroman133]

With a read speed of 170 MB/s and write speed of 90 MB/s your card should be fast enough. I use a similar card (Sandisk Extreme Plus) in my T5i.

[s3igell]

2 hours ago, Lacni135 said:

I see. Is there any reason why a regular intervalometer doesn't have this problem? Difference between the intervalometer i/o compare to usb?

The Intervalometer uses the Old-School Shutter Port - which operates by Closing the Shutter Circuit to initiate the Exposure. Purely Electrical - No Intelligence or Programming involved.  This is not dependent upon any Communication between PC and USB Port and Camera, nor the usage of a Poorly Documented and Officially Unsupported Canon SDK.

[Lacni135]

So is there a way for BYE to get a confirmation that the picture as been saved to send the next command as soon as possible? In other word, letting BYE start the next image as fast as possible instead of putting a 2 second delay manually. Because right now the program just stops responding and you have to disconnect the camera or kill the process to be able to continue.

[admin]

1 hour ago, Lacni135 said:

So is there a way for BYE to get a confirmation that the picture as been saved to send the next command as soon as possible? In other word, letting BYE start the next image as fast as possible instead of putting a 2 second delay manually. Because right now the program just stops responding and you have to disconnect the camera or kill the process to be able to continue.

Not that I'm aware of, there are no events fired by the camera when the save is complete. It does not mean it's not possible. Without any SDK support from Canon and the lack of documentation does makes it difficult to confirm or not if this is something the SDK does expose or not.

Regards

[dkerber]

On 4/22/2020 at 10:39 AM, Lacni135 said:

I am using the Sandisk Extreme Pro 128GB  with "170MB/s".
I thought this would be enough.

*On the amazon page "Shot speeds up to 90MB/s*, transfer speeds up to 170MB/s"*

Considering that must be one of the fastest cards available, it should be! Even the one I use on my 1DX Mk II isn't quite that fast...

[Lacni135]

2 hours ago, admin said:

Not that I'm aware of, there are no events fired by the camera when the save is complete. It does not mean it's not possible. Without any SDK support from Canon and the lack of documentation does makes it difficult to confirm or not if this is something the SDK does expose or not.

Regards

All good, so i guess for now i will have to manually set the pausing time to prevent hanging.
Ps. I haven't read the documentation for this but is it possible to put decimal numbers for the pause?

[Lacni135]

9 minutes ago, dkerber said:

Considering that must be one of the fastest cards available, it should be! Even the one I use on my 1DX Mk II isn't quite that fast...

Thats what i thought but maybe there is some processing overhead or something taking more time... I'll also try reformating the SD card just to be sure.

[admin]

6 minutes ago, Lacni135 said:

All good, so i guess for now i will have to manually set the pausing time to prevent hanging.
Ps. I haven't read the documentation for this but is it possible to put decimal numbers for the pause?

ummm, no... it's whole seconds only

[Lacni135]

1 minute ago, admin said:

ummm, no... it's whole seconds only

No problem! I was just curious