https://bugs.kde.org/show_bug.cgi?id=412280
Bug ID: 412280
Summary: Comparing X2 dome driver (TheSkyX) and indi dome
driver (KStars)
Product: kstars
Version: 3.3.6
Platform: Other
OS: macOS
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: ---
SUMMARY
I spent quite a time trying to understand and solve the dome / telescope
synchronisation with KStars, while I found no problem with TheSkyX.
In both cases I used the same dome parameters :
- Home + Park azimuth = 73.00°
- Ticks per turn = 714
- Autosync threshold (deg.) 0.50°
- Radius (m) 1.150 m
- Shutter width (m) 0.600 m
- N displacement (m) 0.060 m
- E displacement (m) 0.020 m
- Up displacement (m) -0.217 m
- OTA offset (m) 0.405 m
However while I met a perfect and reproducible match between the dome aperture
and the scope azimuth with TheSkyX, this was not the case with KStars.
To be more precise, the match was good in the North, East and West. In the
South the match was never satisfactory : the scope pointed to near one edge of
the dome aperture.
I think that the culprit is a missing "debounce time" parameter in KStars.
Having the possibility to adjust a debounce time is important especially when
the number of ticks corresponding to a complete dome rotation is important (in
my case 714 ticks for a 360° dome rotation).
In TheSkyX the Rotation sensor debounce time can be adjusted between 20ms and
240ms :
I choose 40ms for my setup.
STEPS TO REPRODUCE
1.
2.
3.
OBSERVED RESULT
The match in the South is rarely satisfactory.
EXPECTED RESULT
Could we introduce such a debounce time in KStars
SOFTWARE/OS VERSIONS
Windows:
macOS: 10.14
Linux/KDE Plasma:
(available in About System)
KDE Plasma Version:
KDE Frameworks Version:
Qt Version:
ADDITIONAL INFORMATION
--
You are receiving this mail because:
You are watching all bug changes.
