Bug 475268 - Dome slaving doesn't work
Summary: Dome slaving doesn't work
Status: RESOLVED NOT A BUG
Alias: None
Product: kstars
Classification: Applications
Component: general (show other bugs)
Version: 3.6.7
Platform: Other macOS
: NOR normal
Target Milestone: ---
Assignee: Jasem Mutlaq
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-10-06 06:51 UTC by Jean-Claude
Modified: 2023-12-09 17:15 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments
Dome slaving (804.04 KB, application/pdf)
2023-10-06 06:51 UTC, Jean-Claude
Details
KStars366 (787.04 KB, application/pdf)
2023-10-06 08:42 UTC, Jean-Claude
Details
KStars367 (680.98 KB, application/pdf)
2023-10-06 08:43 UTC, Jean-Claude
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jean-Claude 2023-10-06 06:51:54 UTC
Created attachment 162109 [details]
Dome slaving

SUMMARY
***
Dome doesn't follow the scope
***


STEPS TO REPRODUCE
1. Unpark the scope in the scope panel
2. Enable slaving in the dome panel : dome should leave its park position and rotate to the scope position
3. 

OBSERVED RESULT
Dome doesn't move (see attachment)

EXPECTED RESULT
Using the SAME SETUP, Dome slaving works perfectly well with KStars 366 but not with KStars 367

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

ADDITIONAL INFORMATION
Comment 1 Jasem Mutlaq 2023-10-06 07:44:33 UTC
What is Hyperstar exactly? I tested with simulators and it works fine.
Comment 2 Jean-Claude 2023-10-06 08:42:28 UTC
Created attachment 162111 [details]
KStars366
Comment 3 Jean-Claude 2023-10-06 08:43:26 UTC
Created attachment 162112 [details]
KStars367
Comment 4 Jean-Claude 2023-10-06 08:47:59 UTC
I confirm the bug.
I added 2 additional attachments : KStars366 and KStars367
You can see from the log at the bottom of each screenshot that the dome is not slaved to the scope in 367 .
In the simulator everything works fine
Comment 5 Jean-Claude 2023-10-06 09:00:26 UTC
Hyperstar is a custom driver for the scope. I built 3 custom drivers for my 3 setups.
The bug I reported happens with all 3 drivers in KStars 367 but not in KStars366
Comment 6 Jasem Mutlaq 2023-12-05 09:42:53 UTC
You said there is no way to reproduce this with simulators? We need a way to reproduce this so we can work on a fix.
Comment 7 Jean-Claude 2023-12-05 09:48:59 UTC
Hi Jasem,
Please tell me what I could do to help. (a TeamViewer session ?)
Regards
Comment 8 Jasem Mutlaq 2023-12-05 09:50:29 UTC
Perhaps. Though can't debug MacOS, only Linux.
Comment 9 Jean-Claude 2023-12-05 09:55:59 UTC
The driver MaxDome has been perfectly working till version 3.6.6.
Somebody has changed the MaxDome driver code starting with version 3.6.7
Comment 10 Jasem Mutlaq 2023-12-05 10:03:41 UTC
INDI changes are not related to KStars or KDE, they are reported here: https://github.com/indilib/indi/issues
Comment 11 Jean-Claude 2023-12-08 15:09:39 UTC
Hi Jasem,
1/ I confirm again this bug : my dome (using the driver indi_maxdomeii version 1.4) can't be slaved anymore to my scope with KStars 3.6.7 and 3.6.8.
It's slaved perfectly with KStars 3.6.6.
2/ You told me that it was an INDI bug . Thus I posted a report on https://github.com/indilib/indi/issues/1974. It didn't receive any reply.
3/ I'm not a programmer but I tried something : I copied the files indi_maxdomeii and indi_maxdomeii.xml that I found in KStars 3.6.6 into KStars 3.6.8. But the bug didn't disappear.
4/ Please tell me who I shall contact or what test I could do to solve this problem
Regards
Comment 12 Jean-Claude 2023-12-09 10:13:52 UTC
Please mark this bug as "solved" because the dome is now slaved to the scope under KStars 3.6.8 !
What I did : to verify the INDI side of the bug, I ran my setup using the app IndiStarter ... and it worked : the dome was slaved to the scope !!
Then I went back to KStars 3.6.8  .... and it worked also !!
I don't know what went wrong before. Sorry.