Why would the geometry be different between shooting directly on the camera and shooting with Ekos? Does Ekos resize the geometry because if yes then that would be bad. However, in my experience it doesn’t do that.

Also, using a DSLR and saving the images as FITS is not to be recommended because it involves a conversion from CR2 (i.e. RAW data) to FITS which might (and very likely will) lead to data loss. Please try to always save the data in CR2 format to get the most out of the camera.


Wouter

IMO this would not solve the problem. A user could still enter a shutter speed unavailable in its camera or Ekos could still request the same when taking flats. Even with FORCE BULB = OFF Ekos would then resort to taking "B" exposures which must be prevented when the cam is in "M" mode.

My proposal is this: Use the "available shutter speeds list" that Ekos obtains from the camera anyway.

[2019-10-01T23:48:55.578 CEST DEBG ][ org.kde.kstars.indi] - Canon DSLR EOS 5D Mark II : "[DEBUG] 0: 30 "
[2019-10-01T23:48:55.578 CEST DEBG ][ org.kde.kstars.indi] - Canon DSLR EOS 5D Mark II : "[DEBUG] 1: 20 "
[2019-10-01T23:48:55.578 CEST DEBG ][ org.kde.kstars.indi] - Canon DSLR EOS 5D Mark II : "[DEBUG] 2: 15 "
[2019-10-01T23:48:55.578 CEST DEBG ][ org.kde.kstars.indi] - Canon DSLR EOS 5D Mark II : "[DEBUG] 3: 10 "
[2019-10-01T23:48:55.578 CEST DEBG ][ org.kde.kstars.indi] - Canon DSLR EOS 5D Mark II : "[DEBUG] 4: 8 "
[2019-10-01T23:48:55.578 CEST DEBG ][ org.kde.kstars.indi] - Canon DSLR EOS 5D Mark II : "[DEBUG] 5: 6 "
[2019-10-01T23:48:55.579 CEST DEBG ][ org.kde.kstars.indi] - Canon DSLR EOS 5D Mark II : "[DEBUG] 6: 4 "
[2019-10-01T23:48:55.579 CEST DEBG ][ org.kde.kstars.indi] - Canon DSLR EOS 5D Mark II : "[DEBUG] 7: 3 "
[2019-10-01T23:48:55.579 CEST DEBG ][ org.kde.kstars.indi] - Canon DSLR EOS 5D Mark II : "[DEBUG] 8: 2 "
[2019-10-01T23:48:55.579 CEST DEBG ][ org.kde.kstars.indi] - Canon DSLR EOS 5D Mark II : "[DEBUG] 9: 1.5 "
[2019-10-01T23:48:55.579 CEST DEBG ][ org.kde.kstars.indi] - Canon DSLR EOS 5D Mark II : "[DEBUG] 10: 1 "
[2019-10-01T23:48:55.579 CEST DEBG ][ org.kde.kstars.indi] - Canon DSLR EOS 5D Mark II : "[DEBUG] 11: 0.7 "
[2019-10-01T23:48:55.579 CEST DEBG ][ org.kde.kstars.indi] - Canon DSLR EOS 5D Mark II : "[DEBUG] 12: 0.5 "
[2019-10-01T23:48:55.579 CEST DEBG ][ org.kde.kstars.indi] - Canon DSLR EOS 5D Mark II : "[DEBUG] 13: 0.3 "
[2019-10-01T23:48:55.579 CEST DEBG ][ org.kde.kstars.indi] - Canon DSLR EOS 5D Mark II : "[DEBUG] 14: 1/4 "
[2019-10-01T23:48:55.579 CEST DEBG ][ org.kde.kstars.indi] - Canon DSLR EOS 5D Mark II : "[DEBUG] 15: 1/6 "
[2019-10-01T23:48:55.579 CEST DEBG ][ org.kde.kstars.indi] - Canon DSLR EOS 5D Mark II : "[DEBUG] 16: 1/8 "
[2019-10-01T23:48:55.579 CEST DEBG ][ org.kde.kstars.indi] - Canon DSLR EOS 5D Mark II : "[DEBUG] 17: 1/10 "
[2019-10-01T23:48:55.579 CEST DEBG ][ org.kde.kstars.indi] - Canon DSLR EOS 5D Mark II : "[DEBUG] 18: 1/15 "
[2019-10-01T23:48:55.579 CEST DEBG ][ org.kde.kstars.indi] - Canon DSLR EOS 5D Mark II : "[DEBUG] 19: 1/20 "
[2019-10-01T23:48:55.579 CEST DEBG ][ org.kde.kstars.indi] - Canon DSLR EOS 5D Mark II : "[DEBUG] 20: 1/30 "
[2019-10-01T23:48:55.579 CEST DEBG ][ org.kde.kstars.indi] - Canon DSLR EOS 5D Mark II : "[DEBUG] 21: 1/45 "
[2019-10-01T23:48:55.579 CEST DEBG ][ org.kde.kstars.indi] - Canon DSLR EOS 5D Mark II : "[DEBUG] 22: 1/60 "
[2019-10-01T23:48:55.579 CEST DEBG ][ org.kde.kstars.indi] - Canon DSLR EOS 5D Mark II : "[DEBUG] 23: 1/90 "
[2019-10-01T23:48:55.579 CEST DEBG ][ org.kde.kstars.indi] - Canon DSLR EOS 5D Mark II : "[DEBUG] 24: 1/125 "
[2019-10-01T23:48:55.579 CEST DEBG ][ org.kde.kstars.indi] - Canon DSLR EOS 5D Mark II : "[DEBUG] 25: 1/180 "
[2019-10-01T23:48:55.579 CEST DEBG ][ org.kde.kstars.indi] - Canon DSLR EOS 5D Mark II : "[DEBUG] 26: 1/250 "
[2019-10-01T23:48:55.579 CEST DEBG ][ org.kde.kstars.indi] - Canon DSLR EOS 5D Mark II : "[DEBUG] 27: 1/350 "
[2019-10-01T23:48:55.579 CEST DEBG ][ org.kde.kstars.indi] - Canon DSLR EOS 5D Mark II : "[DEBUG] 28: 1/500 "
[2019-10-01T23:48:55.579 CEST DEBG ][ org.kde.kstars.indi] - Canon DSLR EOS 5D Mark II : "[DEBUG] 29: 1/750 "
[2019-10-01T23:48:55.579 CEST DEBG ][ org.kde.kstars.indi] - Canon DSLR EOS 5D Mark II : "[DEBUG] * 30: 1/1000 "
[2019-10-01T23:48:55.579 CEST DEBG ][ org.kde.kstars.indi] - Canon DSLR EOS 5D Mark II : "[DEBUG] 31: 1/1500 "
[2019-10-01T23:48:55.579 CEST DEBG ][ org.kde.kstars.indi] - Canon DSLR EOS 5D Mark II : "[DEBUG] 32: 1/2000 "
[2019-10-01T23:48:55.579 CEST DEBG ][ org.kde.kstars.indi] - Canon DSLR EOS 5D Mark II : "[DEBUG] 33: 1/3000 "
[2019-10-01T23:48:55.579 CEST DEBG ][ org.kde.kstars.indi] - Canon DSLR EOS 5D Mark II : "[DEBUG] 34: 1/4000 "
[2019-10-01T23:48:55.579 CEST DEBG ][ org.kde.kstars.indi] - Canon DSLR EOS 5D Mark II : "[DEBUG] 35: 1/6000 "
[2019-10-01T23:48:55.580 CEST DEBG ][ org.kde.kstars.indi] - Canon DSLR EOS 5D Mark II : "[DEBUG] 36: 1/8000 "

Before taking any picture Ekos should check whether the camera is set to "M" mode. If so, Ekos should avoid all shutter speeds hat are not in the list (also reject all other shutter speeds entered by the user manually). Ekos should offer all valid shutter speeds either by way of a pulldown menu in the CCD TAB's "Exposure:" field and/or by clicking the UP and DOWN arrows next to it. This of course requires Ekos to allow deviation from the desired ADU to some extent when taking flats.

All cameras with a separate "B" mode would benefit massively from this modification. But other cameras would benefit to some extent, too since Ekos would no longer obtain inaccurately timed "B" exposures for fast shutter speeds when falling back to "B" mode. IMO 1/2000s cannot be timed by countdown. Even in a camera without separate "B" mode, requesting a 1/1400s (just an example) exposure would - as it is now - result in an inaccurately exposed frame.

The fallback to "B" mode is what should be prevented. With "B/M cameras" like the 5D it results in malfunction. With all other cameras it results in inaccurately timed exposures (at high shutter speeds).

In my experience, it does!

Ahh ok I was aware of that thread but only fleetingly read it.

So, why not use CR2 files? As I pointed out, that prevents one image conversion (from CR2 to FITS) which will prevent any possible (i.e. very likely) data loss.


Wouter

Thats not a problem since i use the raw files from the CF Card anyway, when i am working with the DSLR.


Gesendet von iPhone mit Tapatalk

Working with CR2 lights, flats and darks prevents conversion problems, no doubt about that!

Well, I think I just stuck to the standard without further thought. :-/ With CR2 files, is all the information that is normally stored in the FITS header, stored in a CR2 header, too? Maybe we should discuss this privately since it is unrelated to the OP's issues.

Hello Jasem

Will the fix be available soon? I couldn't take flats at all tonight. Kstars closed each time. Even if a took a flat without the preview, when I opened it in Fits Viewer it still crashed.

David

You can find the Windows nightly releases here: binary-factory.kde.org/job/KStars_Nightly_win64/

Ok I just committed changes to force the exposure to be aligned with the DSLR preset exposures. Can you please test?

Sure, will do today.