It seems as though the autoguider commands are being interpreted as user initiated slews.
Yes, autoguider commands are essentially user initiated moves which cause the mount to go to a new coordinate every time a move command is issued. This is universal and applies to every mount ever made, whether AP mount or other brands. They will all do the same.
From: Michael Dolenga via groups.io <giroditalia@...>
To: email@example.com <firstname.lastname@example.org>
Sent: Sat, Jul 18, 2020 9:31 am
Subject: [ap-gto] Mount coordinates change while autoguiding
I've noticed that my 900GTO's coordinates, as reported by ASCOM (latest version of the driver) change over a session where I am autoguiding. This occurs whether using MaximDL or NINA/PhD. In both cases, I am configured to send autoguider commands via the ASCOM driver rather than a separate ST4 cable.
This confounds automated meridian flips because the mount "thinks" it is pointed somewhere other than where it actually is. Often, the difference is too slight to be significance, but sometimes not.
As an example, last night I was doing 30 minute shots of the Crescent Nebula. Over one hour, as reported by the RA/DEC fields written into the FITS header, I saw a difference of 6 minutes, 4 seconds in RA and 1 minute 7 seconds in DEC.
If I leave the mount running with no autoguider connected at all, RA and DEC remain constant, as I would expect.
Is this expected behavior or am I possibly missing some configuration option? It seems as though the autoguider commands are being interpreted as user initiated slews.