I took my very first steps today without any mount or telescope, just my tripod and my Canon 7D (135 lens) pointing to the moon, trying to get full moon pictures.

I wanted to try different exposure times with ISO fixed set to 100, mode set to bulb, manually focused. I tried FITS and Native-format, both in parallel.

From what I see, it seems, that Ekos is setting wrong exposure times. I could not yet figure out a pattern, but that is what comes out, when I compare the meta data of the native files (CR2) with the settings made:

Filename -> exposure in metadata
Moon_Light_0.010_secs_2018-06-25T22-28-46_002 -> 1/10
Moon_Light_0.020_secs_2018-06-25T22-29-25_001 -> 1/10
Moon_Light_0.100_secs_2018-06-25T22-30-10_001 -> 1/10 (correct)
Moon_Light_0.500_secs_2018-06-25T22-30-31_002 -> 1/10
Moon_Light_1_secs_2018-06-25T22-31-15_002 -> 1/10
Moon_Light_1.500_secs_2018-06-25T22-35-52_001 -> 1
Moon_Light_2_secs_2018-06-25T22-32-46_002 -> 1
Moon_Light_10_secs_2018-06-25T22-32-14_001 -> 9
Moon_Light_11_secs_2018-06-25T22-35-22_001 -> 10

I am pretty sure, I am missing something here and would really appreciate your help.

Thanks in advance

Amin

Is it possible, that BULB mode on the Canon DSLR is not really suitable for short exposure times?

Should I rather set the DSLR to a fix exposure time and set the same exposure time in the Ekos capture plugin

I can confirm there is something wrong with <1s exposures using a Canon 5D Mk2.

Thanks for the confirmation, really helped a newbie. Do you use a workaround?

I normally would not use <1s exposures in astro photography and I assume that's why the bug hasn't been reported before. I tried mirror lock (which did cause trouble in the past) enabled and disabled but both settings deliver the same bogus results.

I wanted to use <1 s exposures to get the moon fully with the DSLR, I will try around some more maybe tomorrow and report back.

I see. You could set exposure time manually and use mirror lock and delayed shutter release (Selbstauslöser) to preventt jitter. Or, you could set aperture such that 1/10s (whichh seems to work in your case) is well suited. In any event it would be nice to help Jasem hunt this bug down.

BTW, I just noticed your >1s exposures are affected, too. That reminds me of problems we had in the past. Do you have the latest INDI/EKOS installed? I believe exposures of >=1s do work correctly here.

I am running KStars and Ekos on a Mac. KStars is version 2.9.6 and the canon driver 2.2. I could not find the Ekos version.

@Herrhausen: Are these the right versions? Or is there a newer one available?

I am still having difficulties with the exposure times.

I tried to set them fix on my DSLR in Tv mode which works fine, just the setting in the FITS files is obviously taken from the info in INDI, so that might vary.

I am especially wondering for the BIAS-Frames, as they should be taken with the shortest possible exposure as far as I know. That would be 1/8000s for my DSLR, but if Ekos can't work with these short exposure rates and I always need to set it manually on the camera, is that really the intended way of working?

I have no idea about Mac versions, sorry.