toggle quoted messageShow quoted text
I understand that.
In this case, though, the user is not asking for help. He’s reached his own conclusion (which is contrary to your guidance for counterweight placement) and posted it. I don’t happen to agree with his post, and was curious to know if there was a more likely explanation that I could pass on.
I also understand that it might require more information than what’s in the thread over there.
On Dec 24, 2020, at 8:20 AM, Roland Christen via groups.io <chris1011@...> wrote:
Well, posting to CN won't fix things. If the poster contacts us, we can patch into his controller, see what version of software he has and the settings, and actually watch it do the tracking. I don't understand why people post problems on CN without first contacting the manufacturer.
From: W Hilmo <y.groups@...>
Sent: Thu, Dec 24, 2020 8:32 am
Subject: [ap-gto] Interesting Mach2 Behavior on Cloudy Nights
There are a couple of Mach2 threads on Cloudy Nights.
Last night, someone posted a couple of sample images here: https://www.cloudynights.com/topic/694300-mach2-waiting-list/?p=10752413
I would be interested in understanding what's happening with the image that shows the mount transcribing little loops while tracking. The author of the post says that changing the counterweight configuration to use higher weight, but farther down the shaft, corrected the problem. The author suggests that it's taking the encoders some time to correct tracking errors, but my experience with my AP1600AE suggests that the encoders are so fast, that it would be very hard to catch the corrections in an image like that.