×

INDI Library v2.0.7 is Released (01 Apr 2024)

Bi-monthly release with minor bug fixes and improvements

Canon 6D and AstroPi3 setup, exposure abort problem

  • Posts: 643
  • Thank you received: 62
Hi!

An attempt at summary of the abort exposure problem (not the focus module problem):

1. With setting "save to RAM", aborting an exposure leads to the camera being occupied, and not responding to subsequent capture attempts. This in turn stalls the whole process, scheduler not reporting it as error (at least not always) and therefor not (always) parking as it should.
(I am not totally sure about when aborting exposure could occur in a scheduled operation. I have at least one experience of it happening, due to failed autoguiding. Then autoguiding was resumed, but capture could not resume for 4 hours until I woke up).

2. With setting "save to SD-card", aborting leads to camera occupied for a few seconds, then subsequent capture works nicely. However, risk of SD-card filling up during the night.

Magnus
6 years 2 months ago #23102

Please Log in or Create an account to join the conversation.

  • Posts: 365
  • Thank you received: 32
Thanks for looking into it, you must be getting tired of these things at some point. ;)

The really consistent part for me was;
- Setting to save to RAM, works manually, but during the focus routine the second picture always fails as it reports to be busy.

Thanks, Vincent
6 years 2 months ago #23103

Please Log in or Create an account to join the conversation.

  • Posts: 643
  • Thank you received: 62
Hi!

Just had a chance to experiment a bit, before clouds gather here. I tested focusing, trying to reproduce the focus module issue of error messages about "cannot abort".

And I have two instances of the "Can not abort" issue. It does not happen every time for me, it seems more intermittent. Attached is a log file, where just at the end, there is one of these "Can not abort"-messages, and there should be another somewhat earlier on. I hope it is of any use.

Magnus
The following user(s) said Thank You: Vincent Groenewold
6 years 2 months ago #23114
Attachments:

Please Log in or Create an account to join the conversation.

  • Posts: 365
  • Thank you received: 32
So I tried a few more things and paid some closer attention. I'm setting the camera to save to RAM, the directory to my local Pictures folder on the Pi and destination is local only. That works, manually, as many times as I want within the direct INDI control panel. When I switch to Ekos and the focus module, I click autofocus, first picture is fine and location is local only, but I notice it changes the setting to client only for the second picture and it doesn't work anymore (busy) and I see on the camera itself it's been set into recording mode (whatever that means) and is waiting. It's very reproducable.

If I then go to the INDI panel, manually taking a picture also fails. I hit abort, go to the location setting and set it back to local and presto, it works again and saves the image to disk.

This is the log for the camera where I took the manual shots that worked, few posts above is a log of the failure;
 
6 years 2 months ago #23116
Attachments:

Please Log in or Create an account to join the conversation.

Autofocus always changed mode to CLIENT when it captures. If it was set to LOCAL before, it will fallback to it once capture is complete.

So with my 600D, I wasn't able to reproduce the problem when selecting "RAM" option. It just works in Capture & AutoFocus without any issues. At any rate, as a workaround, I added an option "SD Image", which has 2 options Save & Delete. It defaults to save. If you do not want your SD card to fill up, just select "Delete". This will make it use SD Card capture target, but deletes the file afterwards. Not sure if this will help with the problems above, so give it a try and let me know. Should be in PPA tomorrow.
The following user(s) said Thank You: Vincent Groenewold, Magnus Larsson
6 years 2 months ago #23131

Please Log in or Create an account to join the conversation.

  • Posts: 365
  • Thank you received: 32
So what is the exact difference between client and local when I'm running the INDI server and EKOS on the same machine? And why would that make it work in my case, does that make sense maybe if something is not set up right?

Thanks for testing, I'll try that option for sure, but SD card saving didn't work properly for me unfortunately. So will look into that as well.
6 years 2 months ago #23134

Please Log in or Create an account to join the conversation.

If you're running it on the SAME machine, don't use local!! Local is to be used when you are operating a remote INDI server AND you want to save the images on the remote INDI server. For example, if you running INDI server on a remote RPI3 and Ekos on your PC, and you want all the images to be saved on the RPI3, then you use "Local".
The following user(s) said Thank You: Vincent Groenewold
6 years 2 months ago #23135

Please Log in or Create an account to join the conversation.

  • Posts: 643
  • Thank you received: 62
Hi!

I'm going to test your new SD-card option today and get back with reports on that. But is it then correct that cannot reproduces the focus module "already exposing, cannot abort" problem? Could you make any sense of the logfile I posted?

Any ideas of what I could test to be any wiser about it? While the SD-card/RAM issue is easy to test during daytome, the focus requires a star ... but good to know what to do next time the coulds part.

Magnus
6 years 2 months ago #23159

Please Log in or Create an account to join the conversation.

Maybe use artificial star for day-time? I wasn't able to get any unjustified "aborts" in my testing today. Will try later with my observatory.
6 years 2 months ago #23171

Please Log in or Create an account to join the conversation.

  • Posts: 643
  • Thank you received: 62
Hi!

The new feature, Delete from SD-card, seems to work nicely here. Pictures are taken and immediately deleted. And the problem with hanging on abort is solved in this way. with the camera set to save on SD-card and delete from SD-card, I can abort exposures and then almost immediately capture again. Nice!!

The focus problem however, is still here. The error message I get is not about "busy" but "GPhoto driver is already exposing. Can not abort".And when this happens, the camera just takes a quick snapshot - even though I have it set to 5 secs, it just snaps a picture, as it it was less then 1 sec, and then gives this error msg. And then stalls - nothing more happens until I intervene manually. Attached is a log file where this happens in the end. It is very intermittent, I could focus a number of times before it happened tonight - but then there it is.

Hope this is useful.

Magnus
6 years 2 months ago #23181
Attachments:

Please Log in or Create an account to join the conversation.

  • Posts: 365
  • Thank you received: 32
I may have mixed some words up, but that's exactly what happens to my camera. Still exposing indeed and with this super fast shot being taken. For me it is very consistent though, always fails after the first shot. I didn't test the new version yet, but I suspect it still happens than.
Last edit: 6 years 2 months ago by Vincent Groenewold.
6 years 2 months ago #23185

Please Log in or Create an account to join the conversation.

Looking at the logs:
[2018-02-10T19:16:46.694 CET INFO ][     org.kde.kstars.ekos.focus] - "Capturing image..."
[2018-02-10T19:16:50.141 CET DEBG ][           org.kde.kstars.indi] - Canon DSLR EOS 1000D : "[DEBUG] read_libraw: raw_width: 3948 top_margin 18 left_margin 42 first_visible_pixel 71106 "
[2018-02-10T19:16:50.141 CET DEBG ][           org.kde.kstars.indi] - Canon DSLR EOS 1000D : "[DEBUG] read_libraw: rawdata.sizes.width: 3906 rawdata.sizes.height 2602 memsize 20326824 bayer_pattern RGGB "
[2018-02-10T19:16:50.141 CET DEBG ][           org.kde.kstars.indi] - Canon DSLR EOS 1000D : "[DEBUG] read_libraw: memsize (20326824) naxis (2) w (3906) h (2602) bpp (16) pattern (RGGB) "
[2018-02-10T19:16:50.142 CET DEBG ][           org.kde.kstars.indi] - Canon DSLR EOS 1000D : "[DEBUG] Subframing... "
[2018-02-10T19:16:50.142 CET DEBG ][           org.kde.kstars.indi] - Canon DSLR EOS 1000D : "[DEBUG] Uploading file. Ext: fits, Size: 77760, sendImage? Yes, saveImage? No "
[2018-02-10T19:16:50.166 CET INFO ][           org.kde.kstars.fits] - Loading FITS file  "/tmp/fitsZK1365"
[2018-02-10T19:16:50.168 CET INFO ][     org.kde.kstars.ekos.focus] - "Image received."
[2018-02-10T19:16:50.173 CET DEBG ][     org.kde.kstars.ekos.focus] - Focus newFITS # 1 : Current HFR  2.52203
[2018-02-10T19:16:50.174 CET DEBG ][     org.kde.kstars.ekos.focus] - Frame is subframed. X: 2 Y: 44 W: 192 H: 192 binX: 1 binY: 1
[2018-02-10T19:16:50.174 CET INFO ][     org.kde.kstars.ekos.focus] - "Capturing image..."
[2018-02-10T19:16:50.175 CET DEBG ][           org.kde.kstars.indi] - Canon DSLR EOS 1000D : "[DEBUG] Upload complete "
[2018-02-10T19:16:50.175 CET DEBG ][           org.kde.kstars.indi] - Canon DSLR EOS 1000D : "[DEBUG] Aborting exposure... "
[2018-02-10T19:16:50.175 CET DEBG ][           org.kde.kstars.indi] - Canon DSLR EOS 1000D : "[DEBUG] Closing shutter "
[2018-02-10T19:16:50.178 CET DEBG ][           org.kde.kstars.indi] - Canon DSLR EOS 1000D : "[DEBUG] Using widget:bulb "
[2018-02-10T19:16:50.178 CET DEBG ][           org.kde.kstars.indi] - Canon DSLR EOS 1000D : "[DEBUG] Setting toggle widget bulb: 0 "
[2018-02-10T19:16:50.178 CET DEBG ][           org.kde.kstars.indi] - Canon DSLR EOS 1000D : "[DEBUG] Setting new configuration OK. "
[2018-02-10T19:16:50.178 CET DEBG ][           org.kde.kstars.indi] - Canon DSLR EOS 1000D : "[DEBUG] Exposure aborted. "
[2018-02-10T19:16:50.179 CET DEBG ][           org.kde.kstars.indi] - Canon DSLR EOS 1000D : "[DEBUG] Requested CCD Frame is (  0,  0) (3906 x 2602) "
[2018-02-10T19:16:50.179 CET DEBG ][           org.kde.kstars.indi] - Canon DSLR EOS 1000D : "[DEBUG] Starting exposure (exptime: 3 secs, mirror lock: 0) "
[2018-02-10T19:16:50.179 CET DEBG ][           org.kde.kstars.indi] - Canon DSLR EOS 1000D : "[DEBUG]   Mutex locked "
[2018-02-10T19:16:50.179 CET DEBG ][           org.kde.kstars.indi] - Canon DSLR EOS 1000D : "[DEBUG] Setting radio/menu widget iso: 4 (800) "
[2018-02-10T19:16:50.179 CET DEBG ][           org.kde.kstars.indi] - Canon DSLR EOS 1000D : "[DEBUG] Setting new configuration OK. "
[2018-02-10T19:16:50.179 CET DEBG ][           org.kde.kstars.indi] - Canon DSLR EOS 1000D : "[DEBUG] Setting radio/menu widget imageformat: 7 (RAW) "
[2018-02-10T19:16:50.185 CET WARN ][        org.kde.knotifications] - Audio notification requested, but sound file from notifyrc file was not found, aborting audio notification
[2018-02-10T19:16:50.185 CET DEBG ][           org.kde.kstars.indi] - Canon DSLR EOS 1000D : "[DEBUG] Setting new configuration OK. "
[2018-02-10T19:16:50.185 CET DEBG ][           org.kde.kstars.indi] - Canon DSLR EOS 1000D : "[DEBUG] Using internal bulb widget:bulb "
[2018-02-10T19:16:50.185 CET DEBG ][           org.kde.kstars.indi] - Canon DSLR EOS 1000D : "[DEBUG] Setting toggle widget bulb: 1 "
[2018-02-10T19:16:50.442 CET DEBG ][           org.kde.kstars.indi] - Canon DSLR EOS 1000D : "[DEBUG] Setting new configuration OK. "
[2018-02-10T19:16:50.442 CET DEBG ][           org.kde.kstars.indi] - Canon DSLR EOS 1000D : "[DEBUG] Exposure started "
[2018-02-10T19:16:50.444 CET INFO ][           org.kde.kstars.indi] - Canon DSLR EOS 1000D :  "[INFO] Starting 3 sec exposure "
[2018-02-10T19:16:50.444 CET DEBG ][           org.kde.kstars.indi] - Canon DSLR EOS 1000D : "[DEBUG] Time left: 3000 "
[2018-02-10T19:16:50.444 CET DEBG ][           org.kde.kstars.indi] - Canon DSLR EOS 1000D : "[DEBUG] Requested CCD Frame is (  2, 44) (192 x 192) "
[2018-02-10T19:16:50.444 CET DEBG ][           org.kde.kstars.indi] - Canon DSLR EOS 1000D : "[DEBUG] Aborting exposure... "
[2018-02-10T19:16:50.444 CET DEBG ][           org.kde.kstars.indi] - Canon DSLR EOS 1000D : "[DEBUG] Closing shutter "
[2018-02-10T19:16:50.444 CET DEBG ][           org.kde.kstars.indi] - Canon DSLR EOS 1000D : "[DEBUG] Using widget:bulb "
[2018-02-10T19:16:50.444 CET DEBG ][           org.kde.kstars.indi] - Canon DSLR EOS 1000D : "[DEBUG] Setting toggle widget bulb: 0 "
[2018-02-10T19:16:50.444 CET DEBG ][           org.kde.kstars.indi] - Canon DSLR EOS 1000D : "[DEBUG] Setting new configuration OK. "
[2018-02-10T19:16:50.444 CET DEBG ][           org.kde.kstars.indi] - Canon DSLR EOS 1000D : "[DEBUG] Exposure aborted. "
[2018-02-10T19:16:50.446 CET INFO ][           org.kde.kstars.indi] - Canon DSLR EOS 1000D :  "[ERROR] GPhoto driver is already exposing. Can not abort. "

"Aborting Expsoure" is never supposed to be called above... so something is causing this and I don't know what it is. Can you post a screenshot of your Focus Module? Also, something you can try to change the "Settle" value to 2 seconds to or something and see if that somewhat helps. But I'd like to get to the cause of the "Abort" command since I couldn't reproduce it here with 600D nor with my observatory setup.
6 years 2 months ago #23212

Please Log in or Create an account to join the conversation.

Time to create page: 0.371 seconds