Bug 396072 - Guiding timing out
Summary: Guiding timing out
Status: RESOLVED FIXED
Alias: None
Product: kstars
Classification: Applications
Component: general (show other bugs)
Version: 2.9.6
Platform: Other Microsoft Windows
: NOR normal
Target Milestone: ---
Assignee: Jasem Mutlaq
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2018-07-02 01:32 UTC by Niels Looije
Modified: 2020-12-14 18:19 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments
log guiding error (77.26 KB, text/plain)
2018-07-13 23:15 UTC, Niels Looije
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Niels Looije 2018-07-02 01:32:01 UTC
While trying out the guiding module, if i press "Guide" it gives me the following message:

2018-07-02T03:25:35 GUIDE_RA: Scope cannot reach the start point after 35 iterations. Possible mount or backlash problems...
2018-07-02T03:22:56 RA drifting reverse...
2018-07-02T03:22:25 RA drifting forward...
2018-07-02T03:22:25 Calibration started.

Guiding does not seem to start. What does this error mean and how do i fix it?
Comment 1 Jasem Mutlaq 2018-07-02 05:34:50 UTC
It's issues with your mount. What mount are you using? Enable INDI+Guide logging in Ekos and then attach the log.
Comment 2 Niels Looije 2018-07-13 23:15:08 UTC
Created attachment 113923 [details]
log guiding error

Uploaded a recent log of the guiding error.

During calibration the image is shifting east and west slightly so communication with the mount seems ok. Also i control the telescop from KStars with no problems.
Comment 3 Niels Looije 2018-07-19 18:51:40 UTC
I forgot to add, i am connecting to a LX90 GPS mount using the LX90 INDI mount driver.

Any ideas?
Comment 4 Niels Looije 2018-07-28 12:04:58 UTC
I would like to see some feedback on this issue.
Is there anything else i can provide in terms of info, logs etc?
Comment 5 Andrew Crouthamel 2018-09-28 03:07:42 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 set the bug status 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 6 Niels Looije 2018-09-29 08:23:49 UTC
If more info needed from my side please let me know, i still want to have this resolved.