I also have inconsistent polar alignment and thus PAA is quite useless for me at the moment because I have no idea what is the correct result and to which direction I have to make adjustments. My problem is that my results vary depending on which direction (east or west) I rotate telescope.
I use my primary scope for polar alignment and start the procedure from home position. For example yesterday I got following results when I rotated RA-axis 40 degrees:
Here some adjustments
I saved only a couple of results but in all PAA-tests results were similar: Az is quite repeatable regardless of slewing direction but Alt is quite random.
Do you have any ideas where the problem is? Could it be some mechanical issue?
I have a very weird problem with my OnStep (version 4.12, KStars 3.5.7, MacBook Pro) and I don't know is this related to OnStep or Indi-driver, but I think to ask first in Indi-forum. The problem exists every now and then, but I think that yesterday was first time, when I see it in the log-file.
The problem is that during tracking, OnStep starts slewing without any reason. I mean that I had slewed to target and aligned it and started capturing. After some time, OnStep starts slewing and the target moves out of camera.
Yesterday I was capturing M97 and the problem is very clear seen from attached log-file. I have take only couple of parts from the whole log.
As you can see, target coordinate (RA) was first 11:16:06. However, in some reason at time 2022-02-23T01:36:31.051 EET coordinate changed to 11:16:26 and mount status changed from tracking to slewing. At the end of the log file (time 2022-02-23T01:43:41.083 EET) mount status is again tracking and the target coordinate is 11:16:05 but the target is not anymore in the center of camera.
Has anyone noticed similar problem or have any idea what is wrong?
I tested last night beta3. With previous version (3.5.6) I had serial problems and KStars was very unstable and indidriver can crash anytime. I have MacBook Pro early 2011, Onstep 4.12 and ASI224MC.
This beta-version seems to be stable and scheduler ran whole night without problems. Only problem was connecting to indiserver. KStars crashed almost every time, when I tried to connect equipment. If I let indiserver running, connecting seems to work but starting indiserver seems crash Kstars.
Then there is something strange with Fitsviewer. I have disabled fitsviewer from settings because I don't want to see every single image using scheduler. In the version 3.5.6 I can still see the image using capture but that not happen with beta-version. I have to enable Fitsviewer to see preview image and the disable it before using scheduler.
Then there may be some issue with focus/polar alignment and with auto stretch. It seems that auto stretch is not enabled with those functions because my stars were dimmer than normally with same settings. But I'm not really sure about that.
Thank you for helping. I tried to figure out my software versions, but I can't find in which path indiserver is installed on Mac (I tried both directories /usr/bin and /usr/local/bin but can't find it). However Kstars is version 3.5.6 and I suppose that Indi is also newest version. Hope that latest version is available soon and it fixes my problems.
I have used OnStep via LX200 driver on my MacBook Pro (early 2011). Indi driver seems to be very unstable, it will crash every now and then. From last session, I saved two log files, where driver crashed similar way. It seems that "Child process 567 died". In the attachment is two log files.
Can anyone give me some advices, how can II have used OnStep via LX200 driver on my MacBook Pro (early 2011). Indi driver seems to be very unstable, it will crash every now and then. From last session, I saved two log files, where driver crashed similar way. It seems that "Child process 567 died". In the attachment is two log files.
Can anyone give me some advices, how can I get driver to be more stable?
I have exactly the same problem, mount not stopped when moving to the next position on the polar alignment. In the attachment is my log-file if it helps. Is there any suggestions how to fix this?