| Summary: | Dome slaving doesn't work | ||
|---|---|---|---|
| Product: | [Applications] kstars | Reporter: | Jean-Claude <jcjesior> |
| Component: | general | Assignee: | Jasem Mutlaq <mutlaqja> |
| Status: | RESOLVED NOT A BUG | ||
| Severity: | normal | ||
| Priority: | NOR | ||
| Version: | 3.6.7 | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | macOS | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
Dome slaving
KStars366 KStars367 |
||
What is Hyperstar exactly? I tested with simulators and it works fine. Created attachment 162111 [details]
KStars366
Created attachment 162112 [details]
KStars367
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 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 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. Hi Jasem, Please tell me what I could do to help. (a TeamViewer session ?) Regards Perhaps. Though can't debug MacOS, only Linux. 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 INDI changes are not related to KStars or KDE, they are reported here: https://github.com/indilib/indi/issues 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 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. |
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