I just tested the Pentax DSLR driver.
For the logging I selected Ekos Capture and FITS and the CCD-driver (See log attached).

I created one sequence of 2 shots with exposure 2s/2s delay and started with ISO 3200. Next I deleted the sequence and just changed the ISO back to ISO 100.

The viewer shows the frame at ISO 3200 and does not change the ISO while the sequence has ISO 100. I am pushing the start sequence button rather than the Preview button. The result is that the viewer pops up and allows me to invert colors, save or close. The behaviour is totally under control if selecting the FITS format. Frames get saved properly. Also the communication of new parameters for a new sequence seems to work well with the FITS format. Issues reported before were probably due to the native format viewer.

The log shows only ISO 100 as being selected, there is no ISO 3200 there at all. I'll check this with Canon later today.

If you want I will check again this evening. I was first running tests with one line of 2 exposures in the sequence list. I deleted the line and put a new one with another ISO value and the ISO did not change on the DSLR. Another test was running two identical lines with only the ISO value that was different. I do not remember whether I run the tests with the FITS format or the Native format. I have the impression that performance is better with FITS than with native. Do not put too much time in it now. I will come back this evening with verified tests and provide the logs.

Just one additional question. Which signal starts and stops logging? Is it the "Connect" signal?

Here follows the result of my verified test.
The gphoto2 version gives the following result:
This version of gphoto2 is using the following software versions and options:
gphoto2 2.5.9 gcc, popt(m), exif, no cdk, aa, jpeg, readline
libgphoto2 2.5.16.1 all camlibs, gcc, ltdl, EXIF
libgphoto2_port 0.12.0 iolibs: disk ptpip serial usb1 usbdiskdirect usbscsi, gcc, ltdl, USB, serial without locking

I used the Pentax DSLR driver
After reboot and launch of kstars I launched indi and connected the DSLR.
I created a first sequences 2 times a 2s exp, 0s delay with FITS format ISO 100 followed by a sequence with 2 frames with 2s exp and 0s delay again with fits format and ISO 800.

I started both sequences and it all went well except after the 3rd frame the ISO value went temporarelly 1600 before again returning to 800.

Find attached the log

Yes this is very weird.. I just tried to replicate it with Canon 600D, but it took all sequences with different ISOs fine without any glitches.. not sure what's going on there.

I just thought I would add some confusion...

I think the fits viewer is got some buffering problems. I was playing with the preview again because I wasn't understanding what was happening with the histogram display. So I was going from one ISO to another and frankly I couldn't corroborate what I was seeing with the settings. Also, I got the impression, looking at the histogram, that the fits viewer was adding two, even three captures together. Finally I closed the viewer and did a couple more previews and things appeared to be. This isn't a feature is it?

See in images two and three histogram peaks. This is because I left the fits viewer open and I went through 3 exposure settings.

I was not yet there, but indeed I do not understand the view in the FITS viewer. If I take 2 frames, I expect that I get twice the same view but that is not the case. The intensity seems to change from one to the next frame. The viewer is not adding I think but need to look closer into it.
In the meantime in order to analyse the issue I reconnected my ZWO camera that worked fine months ago. Now I can launch the driver and start a sequence but it loops without end and without vizualising the frame. I do not understand what is happening. I use the FITS format. From the other side, I thought something was wong with my camera but under windows it works fine. I tried to take a log but did not succeed.

I think it was just not syncing the GUI while visible. Can you check.. close the histogram, take a photo, then open it up, is it updated now? If yes, then problem should be fixed in next version. If not, then the problem is elsewhere.

I took a sequence of 2 frames exposure of 1s delay 2s FITS format.
The first frame is vizualised in the FITS viewer. I looked at the statistics and found a mean of 525.
For the second frame the colors change and the mean becomes 12.581. The two frames are saved and I have attached them.

Hi,
I resumed after a few days testing of my K5. In the production version the GPhoto DSLR driver works fine but the PENTAX DSLR driver not.
The frame visualized in the FITS viewer is a line with width 277 and height 2. In the CCD tab of EKOS Size is limited to 277x2.
Could this be corrected?
The issue with the old frames showing up in the FITS viewer is still not solved I have the impression.

Thanks for the help!

Stefan

That's the weird things. It never happen on my K5IIs til now. Hmmmm......

Hi,
After a few months inactivity I resumed again working with my PENTAX K-5.
Indiserver with EQMod mount, ZWO AS120MC works perfectly.
PENTAX DSLR is still a big problem. What worked months ago with GPHOTO DSLR does not even work anymore today neither with the PENTAX DSLR driver.
I get really hopeless.
I use KSTARS 2.9.7 Build 2018-08-03T18:03:22Z 6:2.9.7+201808030814~ubuntu18.04.1
KDE Frameworks 5.44.0
Qt 5.9.5 (built against 5.9.5)
The xcb windowing system
Indi-full cersion 1.7.4~201808031039~ubuntu18.04.1
I am using stable upgrading
GHPOTO2 Version 2.5.15-2
In EKOS it is impossible to set W and H of the frame higher than 3000x3264
I launched the GPHOTO DSLR via the device manager but EKOS asked to shutdown the running one before launching a new one.
When taking a sequence of pictures I get and automatic and prompt Abort and the message "KStars detected INDI driver indi_gphoto_ccd crashed. Please check INDI server log in the Device Manager."

The Camera is on Bulb mode and USB MSC.

Could someone report back whar should work and what not today?
I tried the PENTAX DSLR driver and that also blocks.

I went back to Entangle controlling my PENTAX K-5 and that works fine when changing the ISO but no effect can be seen if the exposure time is doubled.

Thanks for the help,

Stefan