The main difference is ... the GUI and the tools it interface with.
I wanted a single window GUI with task oriented tabs easy to use on the dark with a small netbook screen, and very quick to do simple task.
But a GUI is very upon personal preference like a car bodywork.
About tools interface, it currently use PHD2 for autoguiding, astrometry.net or Elbrus for astrometry (yes Elbrus work fine with wine and solve a field very quickly).
And Cartes du Ciel is used to display the solved images or send target coordinates.
Again all of this is subject to personal preference.
And finally it can run natively on Windows to connect to a INDI server running on a Raspberry for example, or use local ASCOM devices but this is not the subject here.
I enjoy kstars and ekos. But a more task oriented GUI, as you commented, is very welcome. If only it could run on a raspberry pi 2 and access it with vnc to control everything from my 6.4 mobile phone... Just dreaming, sorry.
A raspberry version is possible, I not use one at the moment but I already compile Cartes du Ciel using a qemu virtual machine.
I try to compile the program and make a deb on the file section, but untested because the emulator is way to slow to run a X11 application.
Oleg, this is awesome!
I have just given it a try on my Raspberry Pi it works perfectly. At first glance it might be used as a on-device main control interface (using RPi LCD).
I will seriously consider CCDciel for my Astroberry project. Seems to be perfect GUI for on-device INDI control.
Are you planning to support Lin_guider besides PHD? The latter has known performance issues when running on Raspberry so Lin_guider support would be very useful.
Thanks for nice piece of astro software!
| Orion CT8 | Askar FRA 400 | NEQ6 (hypermod) | Atik 460EX | ASI 1600 | ASI 120MM | Atik EFW2