https://bugs.kde.org/show_bug.cgi?id=423012
TallFurryMan <eric.dejouha...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Version Fixed In| |v3.4.3
Status|REPORTED |RESOLVED
Latest Commit| |https://invent.kde.org/educ
| |ation/kstars/-/commit/11130
| |020b83497e98efaf5ace4fc8922
| |83abf652
Resolution|--- |FIXED
--- Comment #1 from TallFurryMan <eric.dejouha...@gmail.com> ---
This is worked around by
https://invent.kde.org/education/kstars/-/commit/11130020b83497e98efaf5ace4fc892283abf652.
If PHD2 fails connecting to the guide camera at first, it will often succeed at
the second attempt. Test test_ekos_guide waits long enough to accept one
failing attempt, although it is unclear what makes PHD2 fail to connect. There
are very rare cases where PHD2 fails to connect twice, and test fails.
In a real-life situation, there is nothing much Ekos can do about a failing
guide camera, as most of the time the INDI Profile will *not* contain that
sensor. If the camera is working properly, PHD2 will successfully connect at
some point.
If the Guide Module is used independently, failure to connect will cause the
module to remain unconnected (in terms of devices, not in terms of PHD2
connection).
If the Guide Module is used through the Scheduler Module, Scheduler will
attempt to connect multiple times, increasing the chance PHD2 connects.
--
You are receiving this mail because:
You are watching all bug changes.
