Re: Strange behaviour between CCDAP/APCC-AP Driver #APCC
toggle quoted messageShow quoted text
Park 1 is determined by time. It is set to approximately 5 hours 59 minutes 50 seconds past the meridian point. If the time in your CCDAP program is slightly different by 11 seconds or more, it will send the mount to 6hrs 00min 01 seconds past the meridian, which will of course set the scope on the east side of the pier.
Park1 is a problem because it is set at very nearly the flip point of the mount. So, if there is a slight time discrepancy between two applications, the mount may park the scope on the other side. Both positions are valid because both point the scope at the Northern/Southern horizon.
Park 2 and Park3 avoid this because both of those are 6 hours from the flip point. Park4 and 5 are also vulnerable to slight time discrepancies between various external apps. In order to be accurate, all apps used on the mount must have exactly the same time, down to 1 second.
From: Jos� Joaqu�n P�rez Guy <cotejardinero@...>
Sent: Wed, May 27, 2020 1:24 pm
Subject: Re: [ap-gto] Strange behaviour between CCDAP/APCC-AP Driver #APCC
Both, APCC and the driver has set the same position : Park 1
El mié., 27 de mayo de 2020 14:21, Ray Gralak <groups3@...> escribió:
I am not sure if this is the problem but CCDAP uses the ASCOM driver to park the mount so the ASCOM driver's park position will be used, not the park position set in APCC.