Hi alfredo, knro
I'm just an amateur astronomer so the programming/source code is way beyond me, but i'm happy to support with testing.
From the gphoto forum Marcus confirmed a basic single shot command line sequence that did work on my 60da which I copy below:-
On sun, Feb 08, 2015 at 06:52:24AM -0700, AWSBarker wrote:
> thanks Marcus,
> that does appear to work, below is a short edited summary. Seems like a lot
> of 'fails' and 'unknowns' to me but it did save the long exposure images, so
> many thanks.
> I'll feedback to a Kstars/EKOS/INDI group since i'm looking to be able to
> shot multiple long exposures which currently seems to cause problems.
> Tschuss, Andrew.
>
>
> gphoto2 --set-config eosremoterelease=Immediate --wait-event=41s
> --set-config eosremoterelease=Off --wait-event-and-download=2s
> Waiting for 41 seconds for events from camera. Press Ctrl-C to abort.
> UNKNOWN PTP Property d105 changed
> ...
> UNKNOWN PTP Property d1c7 changed
> UNKNOWN BulbExposureTime 0
> UNKNOWN unhandled EOS event StorageInfoChanged (size 12)
> UNKNOWN PTP Property d11b changed
> .....
> UNKNOWN PTP Property d1c7 changed
> UNKNOWN BulbExposureTime 40
>
> *** Error ***
> Failed to set new configuration value Off for configuration entry
> eosremoterelease.
> Waiting for 2 seconds for events from camera. Press Ctrl-C to abort.
> UNKNOWN PTP Property d1c7 changed
> UNKNOWN BulbExposureTime 41
> UNKNOWN PTP Property d1c7 changed
> UNKNOWN BulbExposureTime 42
The final is not "Off" but try "Release Full" or "None".
The BulbExposureTime should not be incrementing anymore and the image should
be downloaded.