I installed a Sirius dome in my backyard. Only the dome rotation is controlled by a MaxDome II controller board. The shutters are controlled manually.
This situation occurs when the observatory is local (not remote).
However this situation is not taken into account by the MaxDome II indi driver (indi_maxdomeii) because there are only two buttons : "Open" and "Close" buttons.
This results in a lot of errors :
[2019-10-29T09:56:50.630 CET DEBG ][ org.kde.kstars.indi] - MaxDome II : "Shutter error "
I suggest that a "Manual" button should be added to the MaxDome II indi Control Panel to avoid this error.
I'm probably missing something but the buttons "Linear" and "Log" are inoperant in the KStars FITS Viewer / Histogram.
They have no effect since the beginning (KStars v. 3.0.0)
With KStars 3.3.3 I couldn't take bias, darks and flats
Thanks for the link, Rob.
I already had a shot in the past , but - sad to say - it's not for my level.
I'll keep being VERY satisfied with the dmg.
I realised that it was Wolfgang's work after I posted my reply.
Yes I would love to build KStars for myself but for this I need some help. And you are welcome !
I'm using the driver indi_maxdomeii version 1.3
I would be happy to help you for the tests and we could do it whenever it suits you
Here is my address jcjesior at free.fr
Demystifying is the word. Thank you.
Another bug appears if I click on the shutter "Opening" button : the dome turns more than 360°, with no way to abort the motion.
My system has a manual shutter, not a motorised one. A checkbox should be included to take into account this possibility. In fact a motorised shutter is useful for remote observatories or for a fully automatic operation of a local observatory.
No crashing for me on macOS Mojave.
Rob, you've done a beautiful work on the Observatory Panel. Thank you.
I found a small bug : if I enter in the field "Absolute position the dome should move" the angle of the home sensor (say 73°), the dome turns 73° + 360° instead of turning only 73°.
It works as expected if I enter another value .
The astrometry seems to work OK. I will test it more carefully to-night.
You describe precisely what I experienced.
I just checked the debug options for both drivers and will attach the logs as soon as the problem occurs another time.
Thank you Jasem. I should have though of that by myself !
This is an old bug : the indi_skysafari and indi_sqm_weather drivers use a lot of CPU power from unknown reasons.
The attached screenshot shows that the % CPU goes to nearly 100%.
Quitting and reconnecting the drivers solves the problem.
In the INDI Control Panel :
- Click SkySafari / Options / Debug / Enable
- the debug settings appear briefly and disappear
It is not possible to enable the debugging
KStars v. 3.3.1 running on macOS