×

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

Bi-monthly release with minor bug fixes and improvements

Read More...

(SOLVED)DSLR exposure time

  • Posts: 173
  • Thank you received: 19

(SOLVED)DSLR exposure time was created by Jon

I have noticed a problem when taking exposures with my Canon T1i. The shutter releases immediately upon pressing the start sequence button, then there is an approximate 5 sec. delay before the exposure countdown begins, the shutter then closes when the countdown reaches 0. This obviously results in an exposure that is ~ 5 secs. longer than it should be. I am using an Odroid C2 as the indi server and have reproduced this in several clients including a VM kubuntu 15.10, full desktop Kubuntu 16.04 and a Pixinsight client on Windows. If I have a setting that is incorrect, I apologize but I have looked and cannot see anything different about my setup.

I reproduced this by taking a couple of 2 sec. exposures to demonstrate. The log file is attached.....


File Attachment:

File Name: indi_gphot..._log.zip
File Size:6 KB





--Jon
Last edit: 7 years 9 months ago by Jon. Reason: Mark Solved
7 years 9 months ago #9232
Attachments:

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

  • Posts: 173
  • Thank you received: 19

Replied by Jon on topic DSLR exposure time

Repeated this using the camera connected locally and with command line to gphoto2. The problem is still there. Must be something in the gphoto driver....
Here's the output from the following issued command:
gphoto2 --set-config bulb=1 --wait-event=5s --set-config bulb=0 --wait-event-and-download=2s  
 
*** Error ***              
PTP Device Busy
Waiting for 5 seconds for events from camera. Press Ctrl-C to abort.
UNKNOWN PTP Property d11b changed
UNKNOWN PTP Property d11c changed
UNKNOWN PTP Property d120 changed
UNKNOWN PTP Property d122 changed
UNKNOWN PTP Property d105 changed
UNKNOWN PTP Property d108 changed
UNKNOWN PTP Property d106 changed
UNKNOWN PTP Property d107 changed
UNKNOWN PTP Property d109 changed
UNKNOWN PTP Property d10b changed
UNKNOWN PTP Property d10c changed
UNKNOWN PTP Property d10d changed
UNKNOWN PTP Property d10e changed
UNKNOWN PTP Property d10f changed
UNKNOWN PTP Property d11b changed
UNKNOWN PTP Property d114 changed
UNKNOWN PTP Property d116 changed
UNKNOWN PTP Property d119 changed
UNKNOWN PTP Property d110 changed
UNKNOWN PTP Property d101 changed
UNKNOWN PTP Property d102 changed
UNKNOWN PTP Property d103 changed
UNKNOWN PTP Property d104 changed
UNKNOWN PTP Property d11d changed
UNKNOWN PTP Property d111 changed
UNKNOWN PTP Property d112 changed
UNKNOWN PTP Property d113 changed
UNKNOWN PTP Property d11c changed
UNKNOWN PTP Property d11f changed
UNKNOWN PTP Property d11e changed
UNKNOWN PTP Property d1aa changed
UNKNOWN PTP Property d120 changed
UNKNOWN PTP Property d122 changed
UNKNOWN PTP Property d150 changed
UNKNOWN PTP Property d151 changed
UNKNOWN PTP Property d152 changed
UNKNOWN PTP Property d153 changed
UNKNOWN PTP Property d154 changed
UNKNOWN PTP Property d155 changed
UNKNOWN PTP Property d160 changed
UNKNOWN PTP Property d161 changed
UNKNOWN PTP Property d162 changed
UNKNOWN PTP Property d1a0 changed
UNKNOWN PTP Property d1a1 changed
UNKNOWN PTP Property d1a8 changed
UNKNOWN PTP Property d1a7 changed
UNKNOWN PTP Property d1ab changed
UNKNOWN PTP Property d1b0 changed
UNKNOWN PTP Property d1b1 changed
UNKNOWN PTP Property d1b2 changed
UNKNOWN PTP Property d1b3 changed
UNKNOWN PTP Property d1b4 changed
UNKNOWN PTP Property d1b5 changed
UNKNOWN PTP Property d1a9 changed
UNKNOWN PTP Property d145 changed
UNKNOWN PTP Property d1ac changed
UNKNOWN PTP Property d1d9 changed
UNKNOWN PTP Property d1ba changed
UNKNOWN PTP Property d1bb changed
UNKNOWN PTP Property d1bc changed
UNKNOWN PTP Property d1d4 changed
UNKNOWN PTP Property d1b8 changed
UNKNOWN PTP Property d1d3 changed
UNKNOWN PTP Property d1d8 changed
UNKNOWN PTP Property d1b7 changed
UNKNOWN PTP Property d1da changed
UNKNOWN PTP Property d1db changed
UNKNOWN PTP Property d1dc changed
UNKNOWN PTP Property d1df changed
UNKNOWN PTP Property d1bd changed
UNKNOWN PTP Property d1d3 changed
UNKNOWN PTP Property d115 changed
UNKNOWN PTP Property d1d0 changed
UNKNOWN PTP Property d1d1 changed
UNKNOWN PTP Property d1af changed
UNKNOWN PTP Property d11b changed
UNKNOWN PTP Property d11c changed
UNKNOWN PTP Property d11b changed
UNKNOWN PTP Property d11b changed
UNKNOWN PTP Property d11c changed
UNKNOWN PTP Property d11b changed
UNKNOWN PTP Property d11c changed
UNKNOWN PTP Property d11b changed
UNKNOWN PTP Property d103 changed
UNKNOWN PTP Property d102 changed
UNKNOWN Camera Status 1
UNKNOWN PTP Property d11b changed
UNKNOWN BulbExposureTime 0
UNKNOWN BulbExposureTime 1
UNKNOWN BulbExposureTime 2
UNKNOWN BulbExposureTime 3
UNKNOWN BulbExposureTime 4
UNKNOWN BulbExposureTime 5
UNKNOWN BulbExposureTime 6
UNKNOWN BulbExposureTime 7
UNKNOWN BulbExposureTime 8
UNKNOWN BulbExposureTime 9
 
*** Error ***              
PTP Device Busy
Waiting for 2 seconds for events from camera. Press Ctrl-C to abort.
UNKNOWN PTP Property d102 changed
Saving file as capt0000.cr2                                                    
UNKNOWN PTP Property d103 changed
UNKNOWN Camera Status 0

--Jon
Last edit: 7 years 9 months ago by Jon. Reason: Added ouput
7 years 9 months ago #9244

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

  • Posts: 173
  • Thank you received: 19

Replied by Jon on topic DSLR exposure time

The following command works nicely:
gphoto2 --wait-event=3s --set-config eosremoterelease=2 --wait-event=5s --set-config eosremoterelease=4 --wait-event-and-download=5s

It seems as though the --wait-event command might be missing......I also tried a wait-event=2s and it works but it's tight.

--Jon
7 years 9 months ago #9245

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

  • Posts: 173
  • Thank you received: 19

Replied by Jon on topic DSLR exposure time

Ran updates this morning and the problem still exists. Is anyone else experiencing this problem when using gphoto-ccd? I am unable to take any flats due to this issue.

--Jon
7 years 9 months ago #9249

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

Replied by Jasem Mutlaq on topic DSLR exposure time

Submit debug logs from INDI Gphoto driver. Turn them on before you connect. Why is the first wait even necessary at all, what event are you waiting for? Connection with the camera?
Last edit: 7 years 9 months ago by Jasem Mutlaq.
7 years 9 months ago #9263

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

  • Posts: 173
  • Thank you received: 19

Replied by Jon on topic DSLR exposure time

In answer to that question, I really don't know! I am only trying to use the command line to debug against the log file I submitted. Didn't have this issue a couple weeks ago when I was taking the test flats for you. This started about a week ago so something changed but I don't know what. It's definitely not my camera as it is working in some other commercial packages as it should. Debug log was submitted with the original post, or so I thought.
--Jon
7 years 9 months ago #9267

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

Replied by Jasem Mutlaq on topic DSLR exposure time

Ok looking at your log it seems your camera also has the bulb widget which is then used to take bulb exposure, but apparently this is not working for you. I changed the code so that it prefer eosremoterelease over bulb if found. Try tomorrow.
The following user(s) said Thank You: Jon
7 years 9 months ago #9287

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

  • Posts: 173
  • Thank you received: 19

Replied by Jon on topic DSLR exposure time

OK Thanks for that... I have been experimenting all day with the following code trying different values from the enum for the regular bulb widget but nothing I did worked. I'll try updating tomorrow.
else if (gphoto->bulb_widget)
        {
            DEBUGFDEVICE(device, INDI::Logger::DBG_DEBUG,"Using internal bulb widget:%s",gphoto->bulb_widget->name);
 
            // Check if the internal bulb widget is eosremoterelease, and if yes, set it accordingly
            if(strcmp(gphoto->bulb_widget->name, "eosremoterelease") == 0 )
            {
                gphoto_set_widget_num(gphoto, gphoto->bulb_widget, EOS_PRESS_FULL); //600D eosremoterelease PRESS FULL
            }
             //Otherwise use the regular bulb widget
            else
            {
                    gphoto_set_widget_num(gphoto, gphoto->bulb_widget, EOS_PRESS_FULL);
            }
        }

Thanks...........

--Jon
7 years 9 months ago #9291

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

  • Posts: 173
  • Thank you received: 19

Replied by Jon on topic (SOLVED)DSLR exposure time

Couldn't wait.....Downloaded and compiled and it is working!! Thank you very much!

--Jon
Last edit: 7 years 9 months ago by Jon. Reason: Mark Solved
7 years 9 months ago #9292

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

Time to create page: 0.233 seconds