Re: Mach2 Unguided testing continues
When the mount is in counterweight-up position and BYN triggers a dither, the mount first returns to counterweight-horizontal position to move the small increment,
When you are in counterweight up, the mount moves according to the safety protocol. There are two ways to move a mount.
First is to simply issue a timed move. Example: I want to move 15 arc sec, so I issue a command to move for 1 second at 1x sidereal. This will not rigger a safety move. The mount will instantly move to the correct point and not return to the counterweight down position.
Second is to issue a coordinate command move. Example: Move mount coordinate by 15 arc seconds. This will trigger a safety slew as you experienced.
The fact that 3rd party developers don't understand the difference and consequences causes them to use the wrong approach to dithering, and thus you end up with the extra wasted move. It is not the mount's fault, it is doing exactly what it should do.
From: Joseph Beyer <jcbeyer2001@...>
Sent: Thu, May 28, 2020 1:54 pm
Subject: Re: [ap-gto] Mach2 Unguided testing continues
I need to try out SGP direct dithering.
When direct dithering using BYN it works fine when the mount is in counterweight-down position. When the mount is in counterweight-up position and BYN triggers a dither, the mount first returns to counterweight-horizontal position to move the small increment, I assume is in the DEC axis, then returns to the imaging position. Clearly not an economy of motion. George says this is due to BYN not being able to work through the ASCOM V2 safety protocols. If I understood his message correctly SGP is able to use the V2 protocol. It should be able to move the several pixel distance without first moving the degrees of RA distance.
Hopefully SGP works more efficiently. I’d like to be able to keep the option to image without guiding in the counterweight-up position and direct dither. If not, the next best thing would be as Roland recommended leave PHD2 at an idle and just use it for dithering. It seems to work fine with the counterweights up.
On May 28, 2020, at 11:00 AM, uncarollo2 <chris1011@...> via groups.io <chris1011@...> wrote: