Bug 445059 - Mount goto not working with current build
Summary: Mount goto not working with current build
Status: RESOLVED FIXED
Alias: None
Product: kstars
Classification: Applications
Component: general (show other bugs)
Version: 3.5.5
Platform: Compiled Sources Linux
: NOR critical
Target Milestone: ---
Assignee: Jasem Mutlaq
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-11-06 04:40 UTC by Paul
Modified: 2021-11-07 07:21 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Log showing some errors (25.97 KB, text/plain)
2021-11-06 04:40 UTC, Paul
Details
attachment-16546-0.html (3.18 KB, text/html)
2021-11-06 10:22 UTC, Paul
Details
attachment-25492-0.html (3.27 KB, text/html)
2021-11-07 04:51 UTC, Paul
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Paul 2021-11-06 04:40:44 UTC
Created attachment 143267 [details]
Log showing some errors

SUMMARY
I have a Losmandy G11 and running Raspberry Pi OS 32bit.
I can control the mount using the virtual buttons and park and unpark but the goto has stopped working.
It was fine until I decided to do a build.

STEPS TO REPRODUCE
1. Build latest kstars from source
2. Start kstars and connect devices
3. Select an object
4. Select slew button

OBSERVED RESULT
No mount movement

EXPECTED RESULT
Mount slews to object

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
Comment 1 Jasem Mutlaq 2021-11-06 09:59:10 UTC
Thanks for the log, according to it:

Losmandy Gemini :  "[ERROR] Slew failed (6).

So mount responded with error (6) and didn't want to slew. Can you check what this error is? maybe some limits were set in the mount or something else? This is not a KStars issue.
Comment 2 Paul 2021-11-06 10:22:32 UTC
Created attachment 143274 [details]
attachment-16546-0.html

James,

I’ll have another look, it only started after I did a new build.

Maybe try an old build.

Paul




> On 6 Nov 2021, at 8:59:10 pm, Jasem Mutlaq <bugzilla_noreply@kde.org> wrote:
> 
> https://bugs.kde.org/show_bug.cgi?id=445059
> 
> Jasem Mutlaq <mutlaqja@ikarustech.com> changed:
> 
>           What    |Removed                     |Added
> ----------------------------------------------------------------------------
>             Status|REPORTED                    |RESOLVED
>         Resolution|---                         |NOT A BUG
> 
> --- Comment #1 from Jasem Mutlaq <mutlaqja@ikarustech.com> ---
> Thanks for the log, according to it:
> 
> Losmandy Gemini :  "[ERROR] Slew failed (6).
> 
> So mount responded with error (6) and didn't want to slew. Can you check what
> this error is? maybe some limits were set in the mount or something else? This
> is not a KStars issue.
> 
> -- 
> You are receiving this mail because:
> You reported the bug.
Comment 3 Paul 2021-11-07 04:51:09 UTC
Created attachment 143304 [details]
attachment-25492-0.html

James,

I booted up today and it appears to be working.

I commanded the telescope to look at the Sun and it went straight to it - without the usual prompt warning me about pointing at the Sun.

Paul




> On 6 Nov 2021, at 8:59:10 pm, Jasem Mutlaq <bugzilla_noreply@kde.org> wrote:
> 
> https://bugs.kde.org/show_bug.cgi?id=445059
> 
> Jasem Mutlaq <mutlaqja@ikarustech.com> changed:
> 
>           What    |Removed                     |Added
> ----------------------------------------------------------------------------
>             Status|REPORTED                    |RESOLVED
>         Resolution|---                         |NOT A BUG
> 
> --- Comment #1 from Jasem Mutlaq <mutlaqja@ikarustech.com> ---
> Thanks for the log, according to it:
> 
> Losmandy Gemini :  "[ERROR] Slew failed (6).
> 
> So mount responded with error (6) and didn't want to slew. Can you check what
> this error is? maybe some limits were set in the mount or something else? This
> is not a KStars issue.
> 
> -- 
> You are receiving this mail because:
> You reported the bug.
Comment 4 Paul 2021-11-07 07:21:23 UTC
Problem appears to have been an issue with the mount that went away after a reboot.