Have downloaded the latest version of KStars (3.5., 64 bit. I can no longer capture bias frames, either as a Capture Preview or as part of a sequence. Lights, Darks, and Flats all work. I have tried capturing the bias frames at the fastest shutter on the camera (ASI6200MM) and at 1 second and it doesn't work either way.
Anyone else having this problem or have any advice?
I'm running Ekos on a Raspberry Pi running Stellarmate OS v1.7.0 (64 bit) which includes KStars 3.5.8.
By not working I mean that if I set up a sequence to take Bias frames and then start that sequence, in the Progress section of Capture Module next to the box that counts down the exposure time, all I get is the little spinner. No count down of exposure time and no frames marked as having been captured. I have checked the folder where the images are stored to verify that none were captured. IF I set up a new sequence with all the same parameters EXCEPT that I change the Type to Dark (or any other type), the sequence executes. I had not experienced this behavior prior to this most recent release.
Have looked at this some more and wanted to report that if I set up a Bias frame sequence as previously described and select the Start Sequence button, I get the behavior I described (just the spinner and no images captured). If I then select the Stop Sequence button, the sequence stops and the log shows "CCD capture aborted" as one would expect. If I then select the Start Sequence button again, the sequence starts and executes normally. Hope that helps.
I recently updated to everything latest (Stellarmate).
Did biases two times/nights. No issues.
Windows KStars client 3.5.8 Stable. Stellarmate OS v1.7.0 (32 bit) on RPI 4 4Gb.
-- Max S
ZWO AM5. RST-135. AZ-GTI. HEQ5. iOptron SkyTracker.
TPO RC6. FRA400. Rokinon 135 and other lenses.
ZWO ASI2600MC. D5500 modified with UVIR clip-in filter.
ZWO ASI120MM Mini x 2. ZWO 30F4 guider. Orion 50mm guider.
ZWO EAF x 2.
The following user(s) said Thank You: Jasem Mutlaq