Bug 450979

Summary: EKOS: Remote Astrometry not working
Product: [Applications] kstars Reporter: matthias.will
Component: generalAssignee: Jasem Mutlaq <mutlaqja>
Status: RESOLVED NOT A BUG    
Severity: normal    
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: unspecified   
OS: Unspecified   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: Windows Log
Kubuntu Log

Description matthias.will 2022-02-28 20:09:54 UTC
Created attachment 147199 [details]
Windows Log

SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols.
See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***


STEPS TO REPRODUCE
1. Install INDI Server together mit astrometry.net and a bunch of Index Files on another machine. Start INDI with Telescope Simulator Driver, CCD-Simulator Driver and Astrometry Driver
2. In EKOS create a Profile using Mount with Telescope Simulator, CCD with CCD-Simulator and AUX 1 with Astrometry Driver
3. Connect the Profile and got to Solver Control
4. Set Solver Mode to Remote
5. Set Solver Action to Slew to Target or Sync then under Solver Control press Button Capture & Solve

OBSERVED RESULT
- Output "Cannot set solver to remote. The Ekos equipment profile must include the astrometry Auxiliary driver."
- Endless Spinner Next to Solver Control Button named Stop

EXPECTED RESULT
Finish solving process

SOFTWARE/OS VERSIONS
Tested Clients: Windows 10 with Kstars 3.5.7 and 3.5.8; Kubuntu 20.04 with Kstars 3.5.8 (bleeding)
Tested Server: Ubuntu Server 20.04.04 (aarch64) with INDI Server 1.9.5 and astrometry.net 0.78

ADDITIONAL INFORMATION
Comment 1 matthias.will 2022-02-28 20:16:08 UTC
Created attachment 147200 [details]
Kubuntu Log
Comment 2 Jasem Mutlaq 2022-03-02 17:16:04 UTC
Logs looks OK, I cannot reproduce the issue. Try to solve a big further away from the poles. Increase gain to 90 and exposure to 3-4 seconds.
Comment 3 Jasem Mutlaq 2022-03-14 09:36:19 UTC
Tried this again just now and it's detected just fine and the remote solver works OK.
Comment 4 Bug Janitor Service 2022-03-29 04:35:29 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 5 matthias.will 2022-03-30 22:10:59 UTC
Updated every system so far. Fact is that the log tells me that solving works fine and is completed but the spinner rotates without ending. Using online astrometry works fine: the spinner is becoming a check mark and the 1 is showing up in the cross section. I found some forum entries talking about the same problem:

https://www.indilib.org/forum/ekos/7005-remote-astrometry/54204.html
https://www.indilib.org/forum/ekos/4334-remote-solver-does-not-work-with-kstars-3-0-0-on-windows/33084.html

So i understand that it is hard to debug something you can't reproduce. Maybe you could at least tell me the where  << [org.kde.kstars.indi] - Astrometry :  "[INFO] Solver complete. " >> is gererated, so i can see if i could find something odd in the code that could cause the trouble.

Thanks for your time and patience.
Comment 6 Bug Janitor Service 2022-04-14 04:34:45 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 7 matthias.will 2022-04-22 19:39:17 UTC
After I upgraded my INDI server to Ubuntu 22.10, I had to reinstall INDI and it turns out that there had been an issue with the server and not with EKOS. Everything works fine now. So I have to apologize but also to thank you for checking this. Hopefully somebody will use this so she/he can decide to reinstall the server in the first place.