El Corazon, now you killed me with this reply

So the problem is exactly opposite to what I have thought! I have been using this Atik 460EX for over 3 years and it always imaged at 2750px x 2200 px. This geometry was always like that in FITS header and actual FITS data. I haven't used any other software than KStars/Ekos & INDI ever since so I never compared it to any other source. Having said that I would bet Atik 460EX chip resolution was 2750px x 2200 px
Recently the atik driver maintained by Peter Polakovič has been replaced by Jasem and the new driver was included in regular updates as a 3rdparty driver. I have updated my systems and noticed that I cannot calibrate new light frames with dark and bias frames library, which I maintain for myself. I noticed that the resolution of the new images is 2749px x 2199 px. I took it as a bug in the new driver BUT the actual issue is that it is the old driver that was wrong with the image geometry!
The native resolution of Atik 460EX is 2749px x 2199 px. Period.
This solves the issue!

PS. I'm happy you enlightened me. However I will miss these lacking pixels... They sit in hundred of my images. I wish I knew where they came from

You're welcome, Radek!

Somehow, I did have an enlightened weekend.

I am sure that will change again, come Monday...

)

Cheers

Jo

So Alfred WAS right!

The binning introduced a division by 3, resulting in % not equal 0.

Good eye, Alfred!!

I'm glad to hear I - for once - might have contributed something helpful. As a non-coder I always feel like being somewhat retarded here. Anyway, I hope we successfully hunted down this bug. BTW, I've used Ekos 3 nights in a row and other than some missing pixels I have not experienced any issues. Simply wonderful!

Thanks Alfred and everyone who contributed to this thread!

Please try to test this change in the updated KStars tonight and see if the issue with binning is gone.

Will test as soon as possible, but the weather forecast here for the next 10 days shows only clouds....

Thanks for fixing this so promptly, Jasem!

I don't want to proclaim victory too early but I tested the latest code indoor and the results are perfect. I was focusing in 2x2, shot a few 1x1bin frames from the queue, solved in 2x2 and again shot a few 1x1bin frames. They all were of the correct dimension. I expect the same results in the night sky. Many thanks for sorting this out!

Hi,

I wanted to tell you that this issue was solved. I did test it the night after the driver was fixed. And indeed no more missing rows of pixels in the first frame after a change of binning. But the last few nights I have been really struggeling with the ASI drivers. I get loads of crashed asi drivers messages, mostly when trying binning 4x4, 3x3 and also 2x2. If I refrain from binning and stay on 1x1 all is fine. The images taken when binning 3x3 and 4x4 look very strange, there are slanting bands in the image. Mostly after one image is taken it crashes the asi driver.

I use an ASI294MC.

Yesterday also the ASI385 crashed the driver, this was after guiding fine for some 20 to 30 minutes. This is new, I did not have this before yesterdays update to the nightly builds.

I will post Logs later today, I can not reach them at the moment. But I wanted to let you know. Maybe there's more users affected?

FYI I tested binning on a laptop with sharpcap. Nu issues with binning there, so it's not the camera (I guess).

I agree with you that that problem was solved. All downloaded images now have the correct dimensions in my last two tests.

I also agree that there is (probably) a problem with binning 4x4, I saw a similar distorted image, but did not investigate further at this time, since everything was working fine with 3x3 binning.

But the much bigger problem is this:

indilib.org/forum/ekos/4670-solver-fails...scheduler.html#35492

Whatever changes were made have now completely killed the scheduler. Because, if the alignment module can no longer capture an image, it obviously cannot align and if it cannot align you can't use the scheduler, unless you are into collecting images from random sections of the sky.

Here are the logs from 2 nights ago. Although I am not certain what all the lines mean, it is very clear that something is very wrong when half the log consists of warnings that something "failed for trixel 32"

www.dropbox.com/sh/jsu99h7geo6sgss/AACUm...76w67XR5ETf5gUa?dl=0

This concerns the KStars version (nightly) Jasem refers to in his post 35159.

Jo

PS: To reemphasize: The problem with the alignment module not capturing an image occurs ONLY in the scheduler. If the alignment module is used outside the scheduler, it works fine. So only users who have tried using the scheduler will likely have experienced this bug.

I think it is better to start a new topic: ASI294Pro Binning issue 3x3 and 4x4, so I did please look for it.

I have been OK with this finding for last couple of weeks.... However my FITS files from Atik 460EX are showing 2750x2200 geometry (+1 in x and y).
Anybody facing this issue again?