×

INDI Library v2.0.6 is Released (02 Feb 2024)

Bi-monthly release with minor bug fixes and improvements

capture: can't change exposure time after first exposure

  • Posts: 969
  • Thank you received: 94
Hi everyone
Canon700d
Set the exposure to 1.0s in capture and hit preview. The length of the exposure is now fixed at 1.0s in both capture and align no matter what exposure is set.
Any ideas?
TIA,
Steve
log: drive.google.com/open?id=1Bkh9NPZRIGLykv8gqwB_8vgpPzpvFxIg
Last edit: 5 years 6 months ago by alacant.
5 years 6 months ago #29019

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

I can't see the problem in the log, appears to be fine:
[2018-08-28T21:53:35.613 CEST INFO ][     org.kde.kstars.ekos.align] - "Capturing image..."
[2018-08-28T21:53:35.663 CEST INFO ][           org.kde.kstars.indi] - Canon DSLR EOS 700D 0 :  "[INFO] Starting 4 seconds exposure. "
[2018-08-28T21:53:41.770 CEST INFO ][           org.kde.kstars.indi] - Canon DSLR EOS 700D 0 :  "[INFO] Exposure done, downloading image... "
[2018-08-28T21:53:44.718 CEST INFO ][           org.kde.kstars.fits] - Loading FITS file  "/tmp/fitsuv1824"
[2018-08-28T21:53:45.771 CEST INFO ][     org.kde.kstars.ekos.align] - "Image received."
[2018-08-28T21:53:45.806 CEST INFO ][     org.kde.kstars.ekos.align] - "Solver iteration #1"
[2018-08-28T21:53:45.814 CEST INFO ][     org.kde.kstars.ekos.align] - "Starting solver..."

I also tried to replicate this on my 600D, which isn't too different from 700D, and it's also working fine.
5 years 6 months ago #29600

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

  • Posts: 1957
  • Thank you received: 420
I occasionally see this too with my 700D. Stopping Ekos and KStars and switching the 700D off and back on fixes it. No reboot needed. I haven’t been able to reproduce it nor to produce logs unfortunately.
5 years 6 months ago #29602

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

Any chance your camera power saving could be interfering with this? Try to disable power saving or at least increase inactivity timeout in your camera to 5+ minutes or something before it shuts itself.
5 years 6 months ago #29603

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

  • Posts: 969
  • Thank you received: 94
Hi
OK, here we are.
1s followed by 5s: fine. All subsequent exposures are correct.
1s followed by 4s: all subsequent exposures are 1s no matter what time is set.
Some sequences work, others don't.
TIA
5 years 6 months ago #29604
Attachments:

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

  • Posts: 1957
  • Thank you received: 420

The camera only started behaving like this recently. I am not sure if this was with KStars 2.9.8 or later but I am sure I didn’t change the power saving setting (nor any other for that matter) on the camera.
Last edit: 5 years 6 months ago by Wouter van Reeven.
5 years 6 months ago #29605

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

Ok, not sure what the problem is. If you can compile the driver, try this. In gphoto_ccd.cpp, go to line #498, you'll see this:
        if (isSimulation())
            isTemperatureSupported = false;
        else
            isTemperatureSupported = gphoto_supports_temperature(gphotodrv);

Replace all the above with this:
isTemperatureSupported = false;

Then edit gphoto_driver.cpp and remove all lines #852 to #920.

Then compile and sudo make install, and see if you see the problem.
Last edit: 5 years 6 months ago by Jasem Mutlaq.
5 years 6 months ago #29606

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

  • Posts: 969
  • Thank you received: 94
Edited and compiled...
As before:
1s then 4s: all subsequent exposures are 1s no matter what time is set
1s then 5s: all subsequent exposures as expected, 4s included
OR
the exposure ends (sound of shutter closing) but the frame is never downloaded.
TIA,
Steve
5 years 6 months ago #29609

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

  • Posts: 969
  • Thank you received: 94
Power saving is disabled. Thanks.
5 years 6 months ago #29610

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

Just tested here again with 1 --> 4 then --> 3 and it's fine.

So the driver, depending on the requested exposure time, either requests an exposure time from pre-defined value (Go to Main Control --> Presets) or uses BULB. If it can't find a value in the list, it switches to BULB mode then takes the exposure using a timer. I suspect that your camera has issues switching between these two modes. Try the following to always force BLOB mode. In gphoto_driver.cpp, line 1038, change:
int optimalExposureIndex = find_exposure_setting(gphoto, gphoto->exposure_widget, exptime_usec, true);

To:
int optimalExposureIndex = -1;

Recompile and test again.
5 years 6 months ago #29611

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

  • Posts: 969
  • Thank you received: 94
Hi. Yep, that fixed it. Thanks.
Dare I ask it be made an option? e.g. Always use BULB enable:disable

Otherwise, do I have to build indi-gphoto for each new build?
Thanks again and clear skies.
Last edit: 5 years 6 months ago by alacant.
5 years 6 months ago #29612

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

Yup will make that an option. Currently travelling so hopefully next week I will add it in.

Sent from my SM-G955F using Tapatalk
The following user(s) said Thank You: alacant
5 years 6 months ago #29650

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

Time to create page: 0.296 seconds