Hi,

Seems this started when ASTAP solver was introduced. Used to work without problems on earlier versions.

When you define 'remote solving' (and astrometry enabled on the remote indi server, and connected, and yes astromtry.net is installed on that server) Ekos always gives an error when starting the solver. See attached image.

If you keep the setting remote, and restart Kstars all solver options are greyed on the Windows Version . The linux (X86) version just crashes when you hit the solver tab. Only way to get it working again is to manually edit kstars.rc and change the solvertype to 0.



Kstars version 3.3.8
Tested from Windows and Ununtu 18 to different indi servers (Raspberry, Ubuntu)


Paul

same situation here - win-kstars 3.3.8 - previous versions worked. need solution as the teleskop does not always has inet connection

Stefan

I use "Offline" and not remote. I wonder what the difference is. Mine works.

where is that "offline"? I have ASTAP, Asto.net and a selector online or remote (which then asks for astro binaries)

Windows does not work with astrometry.net in offline mode, as the Software does not run on Windows, you have to use the mimic software ANSVR to do that..

Actually it does run. Enable Microsofts WSL (included in W10) choose /install Ubuntu as the os in WSL and install astrometry.net . Then it runs without problems and can be launched as a command (see also the astap documentation)

But that is not the subject of this thread. Point is the solver installed on a remote indi server does no longer work, (But nobody seems to care) and crashes kstars. (but many other things as well)

Paul

the point is, 3.3.8 does not use the indi_astrometry driver to utilize a distant astrometry installation for "offline" solving. I went back to 3.3.4 all all is fine - sorry to say but 3.3.8 does not run well

I just tested today and it works, at least on simulators. Connected to remote system with astrometry driver and it solved fine. I will try it today with my observatory. Also, indi_astrometry is not required locally per se, it needs to running on the remote target.

Maybe I was unprecise. What I tried to say was. in 3.3.4 you could by putting "astrometry" in "AUXsetting" use your own solver on your INDI server instead of a client-local or internet solver. in 3.3.8 this ability seemed to have dissapeared as Astro-remote does not work. Will be happy to wait for your results, maybe it's just the fool I am

Well, all I can say is that mine works fine under the same and correct conditions...