Hi Linwood, I have confirmed that the move buttons seem to work correctly in SkyX build 13150. -Ray

Hi Andy, Did you try NINA's move buttons again with a lower tracking speed? -Ray

Yes, a great description Roland and thanks. Now if the encoders are engaged, do they also respond similarly to vibrations induced when manually focusing? Curious. Jeff

Chris White wrote: I've been flipping a coin about going with a Mach2 or an 1100GTO (Non-AE) for a while now, and the coin has not landed yet. Since I dont expect to get a really big scope (Happy

Great description Roland. Thank you. I've been flipping a coin about going with a Mach2 or an 1100GTO (Non-AE) for a while now, and the coin has not landed yet. Since I dont expect to get a really

Is the mount level in the north-south axis and the altitude adjuster backed all the way out? Trying to understand if it is that you’ve run out of range of movement or if the axis is stuck with a gap

Hi Andy, Yes, that is correct. However, because of the speed of the mount, the final stopped position would probably be in a slightly counterweight-up position. -Ray

Here are my most recent APCC and Driver logs. Not sure if this adds anything to the discussion but here they are.

I have always found that our encoder mounts track more accurately than the same mount with encoders turned off. Theoretically both guiding and the use of a precision encoder can track a precise point

Ray said: That is very possible. I was in a bit of a panic when I couldn't stop it, and it was 3 rooms away from me. So thinking out loud -- if it was moving slower and I disconnected, it would

Linwood, It looks like you disconnected APCC before the mount could reach the limit. -Ray

Indeed there wasn't, not quite sure how I managed that. My apologies. Try this one: https://drive.google.com/file/d/1DsmnAnzYuQTG4H7PgemtZgPg7vQmIbUo/view?usp=sharing

There is no APCC log -Ray

Use the APCC log zipper and post your ASCOM and APCC logs and the time at which this occurred. They were in the first note with the steps to reproduce. Here’s the link again:

Use the APCC log zipper and post your ASCOM and APCC logs and the time at which this occurred. -Ray

Ray wrote: > >But it got "stuck" and just kept going even when TSX and then APCC was disconnected. > It didn't get "stuck". The mount did what it was commanded to do by TSX. > The TSX bug

The behavior seems the same I reported last year with my Mach2. Will try to go back to see the details if helpful

Correct. As below.

If the mount doesn't get a "stop slew" command, it will continue to slew until it hits one of the limits. If no limits were set, then the last limit occurs at the meridian when the scope is completely

It didn't get "stuck". The mount did what it was commanded to do by TSX. The TSX bug is that it does not restore the tracking rate to sidereal when the move button is released in TSX. -Ray