I just tested my 600D with and without mirror locking and it works just fine. There is something else going on with your camera. If you try gphoto2 from the command line, how do you images look?

Hi
Thanks for looking but this occurs across AMD64,RPI3 and UpCore running Fedora 28 ,Ubuntu Mate and Ubuntu.

It also occurs with both my Canon 100d camera's (one mod , one not mod) - not used or connected at the same time !

Even using the command line it does exactly the same - fails above 9.5 secs and repeats capture - "unspecified error" and failure to download. I will see if I still have the log.

This error is just like the one I had over a year ago,diff versions of GPhoto2 and OS, which caused me to go back to Windows.

The cable is only 40cm long and its a Lindy Cromo so shielded !

The only common theme here is the Canon 100d camera - which works 100% on Windows / Apt / BYEOS,

Did your test do long exposures of over 9.9secs (20,30secs) and did you repeat them 3 times one after the other ! And no repeat captures - hence images are over exposed !

What version of Gphoto2 and associated Lib files are you using on your system ?

get the following at the end when i fails :
63.917067 ptp_usb_getresp [usb.c:428] (0): PTP_OC 0x911c receiving resp failed: PTP Device Busy (0x2019)
63.917096 camera_unprepare_canon_eos_capture [config.c:450](0): 'ptp_canon_eos_resetuilock (params)' failed: PTP Device Busy (0x2019)
63.917136 ptp_usb_sendreq (2): Sending PTP_OC 0x1003 (Close session) request...
63.917160 gp_port_write (3): Writing 12 = 0xc bytes to port...
63.917265 gp_port_write (3): Wrote 12 = 0xc bytes to port: (hexdump of 12 bytes)
0000 0c 00 00 00 01 00 03 10-99 02 00 00 ............

63.917309 ptp_usb_getresp (2): Reading PTP_OC 0x1003 (Close session) response...
63.917332 gp_port_read (3): Reading 1024 = 0x400 bytes from port...
63.930826 gp_port_read (3): Read 12 = 0xc out of 1024 bytes from port: (hexdump of 12 bytes)
0000 0c 00 00 00 03 00 01 20-99 02 00 00 ....... ....

63.931010 gp_port_close (2): Closing port...
63.932171 _close_async_interrupts (2): canceling transfer 0:0x55083df0 (status 0)
63.932267 _close_async_interrupts (2): canceling transfer 1:0x55080358 (status 0)
63.932305 _close_async_interrupts (2): canceling transfer 2:0x55080530 (status 0)
63.932341 _close_async_interrupts (2): canceling transfer 3:0x55080708 (status 0)
63.932376 _close_async_interrupts (2): canceling transfer 4:0x550808e0 (status 0)
63.932411 _close_async_interrupts (2): canceling transfer 5:0x55080ab8 (status 0)
63.932446 _close_async_interrupts (2): canceling transfer 6:0x55072a30 (status 0)
63.932481 _close_async_interrupts (2): canceling transfer 7:0x55072c08 (status 0)
63.932515 _close_async_interrupts (2): canceling transfer 8:0x55072de0 (status 0)
63.932550 _close_async_interrupts (2): canceling transfer 9:0x55072fb8 (status 0)
63.932585 _close_async_interrupts (2): checking: transfer 0:0x55083df0 status 0
63.932611 _close_async_interrupts (2): checking: transfer 1:0x55080358 status 0
63.932635 _close_async_interrupts (2): checking: transfer 2:0x55080530 status 0
63.932658 _close_async_interrupts (2): checking: transfer 3:0x55080708 status 0
63.932682 _close_async_interrupts (2): checking: transfer 4:0x550808e0 status 0
63.932706 _close_async_interrupts (2): checking: transfer 5:0x55080ab8 status 0
63.932730 _close_async_interrupts (2): checking: transfer 6:0x55072a30 status 0
63.932754 _close_async_interrupts (2): checking: transfer 7:0x55072c08 status 0
63.932778 _close_async_interrupts (2): checking: transfer 8:0x55072de0 status 0
63.932801 _close_async_interrupts (2): checking: transfer 9:0x55072fb8 status 0
63.932855 _cb_irq (2): 0x55083df0 with status 3
63.932890 _cb_irq (2): 0x55080358 with status 3
63.932922 _cb_irq (2): 0x55080530 with status 3
63.932953 _cb_irq (2): 0x55080708 with status 3
63.932984 _cb_irq (2): 0x550808e0 with status 3
63.933014 _cb_irq (2): 0x55080ab8 with status 3
63.933045 _cb_irq (2): 0x55072a30 with status 3
63.933078 _cb_irq (2): 0x55072c08 with status 3
63.933109 _cb_irq (2): 0x55072de0 with status 3
63.933139 _cb_irq (2): 0x55072fb8 with status 3
63.935317 gp_filesystem_reset (2): resetting filesystem
63.935386 gp_filesystem_lru_clear (2): Clearing fscache LRU list...
63.935409 gp_filesystem_lru_clear (2): fscache LRU list already empty
63.935434 delete_all_folders (2): Internally deleting all folders from '/'...
63.935458 lookup_folder (2): Lookup folder '/'...
63.935482 lookup_folder (2): Found! / is 0x55064b30
63.935506 recurse_delete_folder (2): Recurse delete folder 0x55064b30//
63.935529 gp_port_free (2): Freeing port...
63.935549 gp_port_close (2): Closing port...
63.936353 gp_filesystem_reset (2): resetting filesystem
63.936418 gp_filesystem_lru_clear (2): Clearing fscache LRU list...
63.936437 gp_filesystem_lru_clear (2): fscache LRU list already empty
63.936460 delete_all_folders (2): Internally deleting all folders from '/'...
63.936484 lookup_folder (2): Lookup folder '/'...
63.936562 lookup_folder (2): Found! / is 0x55064b30
63.936585 recurse_delete_folder (2): Recurse delete folder 0x55064b30//

Ok thanks for the help but I am going to abandon my Indi project till next year. I need to be able to trust whats going on and DSLR on Indi with my Canon 100d is playing ball. Good luck with your project - clear skies

I submitted a change now that *might* fix this issue, it should be available in INDI Nightly PPA later on.

Just tried it after changing to nightly and install/update - no difference same error

One question do you use LAN or Wifi for your connections - I use Wifi (connected by Realvnc)?

Something else I have noticed since 2.5 now getting double click of lens shutter and or Mirror Lock - but they arn't he correct number of seconds - e.g. 2 secs mirror lock last click noise maybe 5-10secs after image is displayed.

Also black images are starting to appear if you change ISO settings or exposure length.

Is this with v2.5 of INDI Gphoto driver?

Yep - Indi Devices reports v2.5 for the Indi Canon dslr driver which I presume is the same thing as Indi Gphoto driver as its a Sym Link.

Before the upgrade it showed v2.4.

I have ( i think) found the problem, I know I was going to ignore it until next year but the weather has been bad for Astro so I did some more testing/digging.

The problem appears to be Noise Reduction setting in my Canon 100d - I have it on and my APT works no problem however this causes no end of weird things in Indi/Ekos which I believe is a timing problem caused by NR.

If I switch NR off on the camera Indi / Ekos works for both FITS and Native no matter what expo time I set (well 60 ,30,20,10,6 secs all work ! )

I found this for a Nikon camera and thought I wonder github.com/gphoto/libgphoto2/issues/94 - well it looks like thats it.

I still have to do live field testing but that looks to be good step forward

P.S. I like the new Icon for Live Viewing !!!!

Thanks, I'll make sure to add this note to the GPhoto driver documentatoin.

ok just did a field test - using rpi3 stand alone and Rpi3 as server and PC running Kstars/ Platesolving - on both DSLR behaved 100%.

Please can the Scheduler be fixed - LOL