> -----Original Message-----
> From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Greg Salyer
> Sent: Wednesday, May 20, 2020 7:54 AM
> To: main@ap-gto.groups.io
> Subject: Re: [ap-gto] APCC Pro 1.8.1.1 update #APCC
>
> Ray, when do you expect to have a fix?
>
> > On May 20, 2020, at 10:45 AM, Ray Gralak <groups3@...> wrote:
> >
> > Hi Bill,
> >
> > If you have a CP3 it's best that you stay with 1.8.0.9 until the next release. In 1.8.1.x a change was made to
> make the sign of the tracking rates consistent with what external programs expect, but it seems like it doesn't work
> with the CP3 because of an unexpected firmware difference between it and the CP4/5. Sorry, it wasn't discovered
> before 1.8.1.x was released. I usually don't have enough time to test with the CP3 under dark skies any more.
> >
> > -Ray Gralak
> > Author of APCC (Astro-Physics Command Center): https://www.astro-physics.com/apcc-pro
> > Author of PEMPro V3:  https://www.ccdware.com
> > Author of Astro-Physics V2 ASCOM Driver: https://www.siriusimaging.com/apdriver
> >
> >> -----Original Message-----
> >> From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Bill Conrad
> >> Sent: Tuesday, May 19, 2020 8:51 PM
> >> To: main@ap-gto.groups.io
> >> Subject: [ap-gto] APCC Pro 1.8.1.1 update #APCC
> >>
> >> I have been using APCC Pro 1.8.0.9 with V2 5.30.10 on a AP1600-CP3 mount. I have a pointing model and
> have
> >> been running with Enable Pointing Correction and Enable Tracking Correction. When I updated to APCC Pro
> >> 1.8.1.1 I had to turn off Enable Tracking Correction as the rates seemed wrong (could not track a star). Also, on
> >> pier flip I had to abort with the scope pointing way below the horizon, then got it to successfully park back to
> park 4.
> >> After restoring 1.8.0.9 everything worked properly as before. I don't currently have log files to post. Any help
> would
> >> be appreciated. Thanks.
> >>
> >
> >
> >
> >
>
>