APCC Tracking Corrections Not Working #APCC
dnakic@...
I did a 25 point Point Model Solve as I just purchased software (just got the software and doing a small model first). I was able to get Pointing to work effectively but the tracking is not working. When I turn on Tracking Correction, I see the stars streak. My AP1600GTO polar alignment and PEC was just completed recently with Pempro and tracks less than 1.5 arcsec of drift in 5min. I have the latest software for APCC, 1.8.1.1, ASCOM and drivers, MaximDL Pro, and TheSkyX Pro. Appreciate help on this matter.
|
|
Ray Gralak
The APCC tracking rate does not match the RA rate on the bottom (see screenshot below).
Something may have set an offset rate close to 1x sidereal in the ASCOM driver, which shows as a negative RA rate in arc-sec/secs in APCC status. Are you connected to some application via the ASCOM driver that might be setting a custom offset rate set in the ASCOM driver? (or did you set a rate there?)
-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 dnakic via groups.io > Sent: Monday, May 4, 2020 10:24 AM > To: main@ap-gto.groups.io > Subject: [ap-gto] APCC Tracking Corrections Not Working #APCC > > I did a 25 point Point Model Solve as I just purchased software (just got the software and doing a small model > first). I was able to get Pointing to work effectively but the tracking is not working. When I turn on Tracking > Correction, I see the stars streak. My AP1600GTO polar alignment and PEC was just completed recently with > Pempro and tracks less than 1.5 arcsec of drift in 5min. I have the latest software for APCC, 1.8.1.1, ASCOM > and drivers, MaximDL Pro, and TheSkyX Pro. Appreciate help on this matter. > > > Some screen captures: > > > > <blob:https://ap-gto.groups.io/bedb83f4-8c6e-44fe-b33a-289edd153480> > > > <blob:https://ap-gto.groups.io/a6f69ff7-ffef-42ec-b8ea-59dbcbe14e53> > > <blob:https://ap-gto.groups.io/a2142c12-4b41-40b5-909c-ca88c9f740d4> > > > 5sec image without guiding with Point Correction On and Tracking Correction Off > > > > <blob:https://ap-gto.groups.io/4bb3b6b4-9e2d-41d1-aef9-eb3dd9ed5a97> > > 5sec image without guiding with Point Correction On and Tracking Correction On > > > > <blob:https://ap-gto.groups.io/31edb270-de50-4b36-87f8-24d736048b3e> > > > |
|
dnakic@...
Ray, I did an experiment to understand the source of issue. When I run APCC and nothing else, including not having the ASCOM V2 I immediately get the -15.04056 vs the 4.48 in Tracking Correction. I don’t know of where I could introduce an offset. Open to suggestions of the source and how to resolve.
|
|
Ray Gralak
Are you by any chance using a GTOCP3?
toggle quoted message
Show quoted text
-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----- |
|
Ray Gralak
Hi Jerry,
I seem to have exactly the same issue. I have the latest V2 dirver, APPC version and a CTOCP4 controller. TheThe values in the Tracking rate correction are in units sidereal secs/hour (RA) and arc-sec/hour (Dec). These values do not include and offset rates that may have been sent via the ASCOM driver for tracking an object (comet/asteroid/planet/sun/moon/etc.). The values in the status bar are in arc-sec/sec for both RA and Dec, and *include* offset rates. So, the values won't match unless you do a conversion. In my screenshot the values were dramatically different even after the conversion, -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----- |
|