Once again, thank you knro.
I took the time to carefully read the entire page you sent me and all this thing regarding the "force bulb" for longer exposures and manual for exposures less than a second caught my attention. So I've tried to capture a 10" long picture and got success. The camera was on "M" and "force bulb" was set to be active on Ekos. This whole time I was trying shorter exposures.
That's a good thing!
But then I tried to take a fast exposure like 1/100". The camera was on "M" and "force bulb" as set to be off on Ekos. I've set the exposure time to be 0.01, which is a predefined shutter speed on this particular model (1/100). But just changing this (force bulb to off and exposure time to 0.01) made it fail again.
That's the complete log of actions, with the successful 10" exposure, and the failed 1/100" exposure after (on top):
2020-08-18T23:17:39: [ERROR] Failed to expose.
2020-08-18T23:17:39: [ERROR] Error downloading image from camera: Directory not found
2020-08-18T23:17:36: [INFO] Starting 0.01 seconds exposure (+3 seconds mirror lock).
2020-08-18T23:17:23: [INFO] Starting 0.01 seconds exposure (+3 seconds mirror lock).
2020-08-18T23:17:23: [ERROR] Failed to expose.
2020-08-18T23:17:23: [ERROR] Error downloading image from camera: Directory not found
2020-08-18T23:17:19: [INFO] Starting 0.01 seconds exposure (+3 seconds mirror lock).
2020-08-18T23:16:57: [INFO] Force BULB is disabled. Exposures shall utilize camera predefined exposures time first before attempting BULB.
2020-08-18T23:16:26: [INFO] Starting 10.3 seconds exposure (+3 seconds mirror lock).
2020-08-18T23:16:19: [INFO] Force BULB is enabled. All expsures shall be captured in BULB mode except for subsecond captures.So as you can see the 10" (actually for some reason that I don't know it's 10.3") works right away. BULB mode enabled. Then I disable bulb (as I'm going to perform a short exposure) and proceed to test the 0.01" exposure, which fails triggering a retry from Ekos.
I then tried the 0.01" exposure with "force bulb" enabled, just for curiosity. But it also failed:
2020-08-18T23:23:08: [ERROR] Failed to expose.
2020-08-18T23:22:54: [INFO] Starting 0.01 seconds exposure (+3 seconds mirror lock).
2020-08-18T23:22:54: [ERROR] Failed to expose.
2020-08-18T23:22:41: [INFO] Starting 0.01 seconds exposure (+3 seconds mirror lock).
2020-08-18T23:22:40: [ERROR] Failed to expose.
2020-08-18T23:22:26: [INFO] Starting 0.01 seconds exposure (+3 seconds mirror lock).
2020-08-18T23:22:19: [INFO] Force BULB is enabled. All expsures shall be captured in BULB mode except for subsecond captures.So in other words, only long exposures with "force bulb" enabled are working for me at this moment. Any idea?
Now regarding this gphoto2 command, I logged on the Pi's SSH and with the INDI server stooped I executed it, took around 2 minutes to finish:
$ gphoto2 --debug --debug-logfile=gphoto.txt --capture-image-and-download
ERROR: Could not capture image.
ERROR: Could not capture.The complete log is here: gist.github.com/fschuindt/d2a5f3b0fab08d873716d21dd4a5c2ab
It's a huge file, more than 14k lines.
Side note I had to install gphoto2 in order to run this command, it was't installed before. But I think that makes sense since I believe I'm using a DSLR-specific driver instead of the gphoto driver, right?
I think that's it. Any tips/clues/ideas?
Thank you all for the support!
Read More...