Thank you, I believe I found and fixed the issue. Should be in the next KStars nightly.

Would that be build #1584 (Jul 8, 2022 5:24:00 PM)?

I just tried build version Build: 2022-07-08T17:50:38Z. Log attached.
It also fails.

It was a simple test using just the INDI screen after homing to zero degrees.

1, I set the raw angle to 10 degrees. It worked.
2. I set the raw angle to 15 degrees. It worked.
3. I set the raw angle to 5 degrees. It worked (it reversed to 5 degrees).
4.. I then set the raw angle to 350 degrees. It should have gone back to zero, then continued counterclockwise to 350.
But as soon as it reached zero - it threw an error:

[WARNING] Bogus motor position received: 258086. Syncing rotator to 0 "

It then continued counterclockwise but did not stop at 350. In fact, as soon as it crossed the zero, the degree indicator read around 250 degrees.,
But it didn't then go clockwise to 350, instead it just kept moving counterclockwise further away from 350 until I aborted it.

My latest test shows it's not that simple. It goes forwards and back correctly without any problem.
It's when it crosses the zero (and perhaps the 180) degree point that errors pop up.
(I posted the latest test that shows the error is when reaching zero).

Peter

Ok I found the issue and should be fixed in v1.4 of the driver. Should be in nightly tomorrow.

Thanks Jasem! I just tested it in daytime, and it works great. I will test the alignment module with a "load and slew" and verify that I works in the real world. But I think you nailed it. Thanks again!

Also - I checked and it no longer goes past 180 and wraps up my cables. I tested 170 degrees, and then after it git there I entered 195. It reversed back around perfectly the other direction. No more wrap.

Ok, testing at night using the solver failed to sync my camera with a saved image.
I homed the rotator toe start. The raw angle was zero.
Then I plate solved the sky successfully near my target. I saw updates to the rotator position angle.
Then I loaded a previous image of this target, and with LOAD AND SLEW.
EKOS zeroed in on the target, and gave the command:

2022-07-10T22:36:28 Setting position angle to 117.743 degrees E of N...
2022-07-10T22:39:09 Rotator reached target position angle.

But it actually went to a position angle of 78.01

The resulting image was way off, yet EKOS gave the thumbs up:

2022-07-10T22:39:53 Target is within acceptable range. Astrometric solver is successful.
2022-07-10T22:39:53 Target is within 00° 00' 04" degrees of solution coordinates.

Is there some kind of initial option I must do in order to have EKOS and the Nightcrawler syncs up?


Something is not right.

I just tried to follow your rotator instruction video, and I am not getting what you did.

I set the target Position Angle to 117. I then went into the capture module and did a 20 second exposure,
EKOS said it was setting the rotator to 117 degrees, but that did not happen. Instead, the rotator went right past a position angle of 117 and stoped at 151.
Then EKOS said it was at 117 (it was not) and captured the image.

Logs?

Jasem, is there a particular sequence of activities that you would like me to test while logging?
My concern is that what EKOS displays during the alignment, and what is actually happening are not the same. The rotation between the two images (saved vs current) are completely different, while EKOS thinks they are aligned.

That's why I need logs. Need to see what Alignment module thinks the PA is for the image and what the rotator reports.

It may be a few days. We have large thunderstorms coming in today that will last for several nights.
PS: Did I read that you also have the Nightcrawler? Is yours working fine? Perhaps mine is faulty?