Stefan Nonneman replied to the topic 'Pentax K-5 capture failed' in the forum. 6 years ago

The Pentax K-5 firmware version is 1.16 (last version).
This morning, when updating and upgrading I saw that indi-gphoto was upgraded.
In order to be sure that the issues were not caused by some settings I changed myself, I reset all settings to factory settings.
When starting the indiserver a warning is shown: [WARNING] Shutter speed widget does not have any valid data (count=0).
The driver name is GPhoto CCD and the Exec is indi_pentax_ccd, version 2.3, interface 10.
I saved a series of capturing sequences in a file for upload when starting.
After uploading the saved sequences and the first start, all sequences go quickly to status complete. The indi_pentax_ccd process continues running.
Resetting the status to Idle for all lines and starting the list of sequences changes the status of the first sequence to "in progress", beside expose an indicator starts turning and the message window opens and informs that the indi_pentax_ccd driver crashed. The indi_pentax_ccd process on the linux machine was initially in a status Sl+ meaning S=uninterruptible sleep, l=is multithreaded and +=is in the foreground process group. After the message that the driver crashed theprocess status was S+ so the multi-threading disappeared.
The driver log did not revealed any issue.
In the KSTARS log the following error appears: INDI Server: "2018-08-05T08:36:36: Driver indi_pentax_ccd: indi_pentax_ccd dispatch error: Property CCD_ABORT_EXPOSURE is not defined in Pentax DSLR K5D 0." from which I deduce that it is not possible to abort the exposure in the PENTAX K5D0. In any case when starting the exposure I would expect the countdown to start and the indicator starts turning.
When disconnecting and reconnecting (without stopping and restarting the indi server) the status of the indi_pentax_ccd process becomes again multi-threaded. Restarting the sequence puts the first sequence again in "in progress" status, the driver does not crash but the linux process is again not multi-threaded anymore, just as the driver would crash but this is not reported.
Remark that after that the driver crashed, the DSLR does not remain blocked. When restarting the indiserver and reconnecting the DSLR the exposure button of the DSLR does not respond when pushing it. The DSLR seems to be under full control of EKOS.

Read More...