Come and join our community. Expand your network and get to know new people!
Thanks all! Just please try to this the updated KStars tonight and see if the issue with binning is gone.
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. Just wonderful!
gpsd is not killed and is blocking the port. You can use other port to overcome this with option -S
gpsd -b -n -N -D 4 -S 12947 /dev/ttyAMA0
another screenshot, with more messages
So Alfred WAS right!
The binning introduced a division by 3, resulting in % not equal 0.
Good eye, Alfred!!
You're welcome, Radek!
Somehow, I did have an enlightened weekend.
I am sure that will change again, come Monday...
this is what I am getting...
first I entered the line as suggested, and received a couple of error messages
then checked systemctl status gpsd
Kill gpsd and run in a terminal with -N option (plus all options from config file) i.e.
gpsd -b -n -N -D 4 /dev/ttyAMA0
to be honest, I do not really understand what it means
I have been trying to find the logs, and checked a couple of websites to get my head around, including looking into syslog files, but got lost.
If I run "cgps", this is what I am getting - any other ideas on what I could try?
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
Good news everyone!
I found and fixed the issue. First of all, not all frames are valid.
ZWO specifically states that Width % 8 must be always zero. So if your frame dimension violates that, it gets "corrected" by the driver. For height, it's Height %2 = 0
But the actual problem was in Ekos. Ekos sets binning first _then_ sets the frame. However, if the frame dimensions are the _same_, then nothing is set. When the frame are "auto corrected" by the driver, this is not reflected in Ekos when the binning changes. At any rate, please compile or use both indi-asi nightly driver and kstars nightly and report back if this fixes the issue.
I still have a second SD card with an image. I'll check that.
Changing the password, time zone, language and the host name, updating KStars, installing chromium browser, teamviewer and removing firefox were the only modifications I have done.
I'll expected it to be the host name and used the one I changed it to, I'll just want to make sure I didn't miss something.
It will take me a while. So thank you for your help in advance.