Have a look at the diagram. The DR is expressed in numbers of bits. The maximum is 14 which is why a 14 bit ADC is used and the maximum bit depth of the images is 14. The fact that the numbers get scaled to 16 bits is just what the driver does. So the discussion didn’t go sideways at all. And yes, I know what DR means and how it is determined. All I am saying is that this is how the characteristics of the sensor are published by ZWO.
In what way did the discussion go sideways?
With purely 14 bit data, a given pixel could have a value of, say, 1000 in one image and 1001 in another picture. The average between the two is 1000.5 which cannot be represented by an integer. By multiplying the values by 4, the first value becomes 4000 and the second 4004 with a average of 4002 which can be represented by an integer. The advantage of converting the data to 16 bit this way is that a more natural representation of intensity differences can be achieved when compared to pure 14 bit data.
The diagrams on the product page show that the maximum dynamic range (DR) is 14 so with a 16 bit ADC the DNs indeed are multiples of 4.
Yes, Celestron mounts need this.
Astro123 post=70286 wrote: Should I have bothered doing the initial 2 star Nexstar alignment at the beginning ?
Can you show a screenshot of the Ekos configuration screen?
Astro123 post=70286 wrote: Why does EKOS think my two cameras are the same when I go to the guide section ?
Probably Ekos expects the focal length and pixel size of the guide cam and not of the main imaging cam.
Astro123 post=70286 wrote: Why does the RA calibration fail ( backlash ? ? can you change the settings to make it more aggressive , or is there a problem with the Celestron Driver)
Guiding is not tracking!!!!
Astro123 post=70286 wrote: The guide section in EKOS does not say its guiding , BUT the mount section does say its tracking , is it getting this information form the mount ( Nexstar).
I use an ASI6200MM with a Raspberry Pi 4 with 4 Gb and if I switch off the FITS viewer, KStars runs all night without crashing. If KStars doesn't run on an RPi then why would it run on a mini PC? Also, why isn't KStars able to use more than 2 Gb of memory? Are you running a 64 bit Ubuntu on the RPi? Finally, yes the Pi is laggy for me to but not nearly as much as on the mini PC.
All, see this thread here:
The topic starter is not using a Raspberry Pi.
Yes it is confusing. But the link I posted literally is the first hit I get when I search on Google. Have you tried that at least?
Also, with RPi it is really easy to set up a virtual frame buffer with the correct dimensions. With any other device, like the mini PC you're using, it is exceedingly hard. You'll need to set up Xorg to use a frame buffer and then an .xinitrc again with a frame buffer to get this working. I have been using a mini PC for about two years and in the end I gave up because a Raspberry Pi 4 with 4 Gb just performs better. Even with the virtual frame buffer and using a wired network, there were a lot of hick ups in the virtual display and things like plate solving just didn't perform very well. I had to wait for over a minute for a solution to come and with an RPi it is about 2 seconds. Not kidding!!!
My advice: use the mini PC for something else and get you a Raspberry Pi 4. That works and it works really well. There are scripts that can help you to install Ubuntu and KStars and they work. If you don't know Linux very well then a mini PC is just too hard. I have been using Linux for over 20 years and found it hard to configure my mini PC. Just my $0.02
You can search for all of this on internet yourself, right?
Or .... make sure that your user logs in automatically and make sure that VNC is an application that gets started automatically when your user logs in. For both you can search online how to do that. It depends on the login manager and the desktop that you are using.
You may want to do
sudo apt-get update
sudo apt-get dist-upgrade
and then try the
sudo apt-get install
What version of Ubuntu? 32 bit or 64 bit?
It probably is related to what Jasem wrote. I used a 5 slot EFW before ad probably didn't erase the XML file.
Ekos does have this. For each job in the scheduler you can specify a specific start time: