Usually, this is fine but every now and then I noticed the scope does not park in position 4 exactly as it should (i.e., the RA axis is slightly off level).
All sky positions are calculated from the previous object that you did a Recal on. That includes park positions. If the last object that you Recal on is off by 1 degree when you pressed Recal, then every object that you go to including all park positions will also have that 1 degree error.
Your errant Recal could be the result of an error on your part or deliberate if you wanted to center a nebulous object and then did a recal on it. What you might think was the center might not be the center as defined in the database, so that throws off everything else following that move.
We are working on changing the way parks are generated so that they are not affected by errant recals or syncs. The software will be available for the CP4 and will be standard in the Mach2 CP5 controllers.
From: Bruce Donzanti <donza2735@...>
To: main <firstname.lastname@example.org>
Sent: Thu, Feb 13, 2020 5:42 am
Subject: [ap-gto] Erratic parking of the mount
In my permanent setup, I use SkySafari 6 Pro as my planetarium program to slew my AP1100 with no issues (connected to the GTOCP4 via RS232). It parks and unparks from position 4 with no issues. I also use PHD2 for guiding by linking it as required to the mount to my capture and live viewing software (SGPro or SharpCap) which are connected to mount via USB with no issues. However, I have had random problems with shutting down the system. I first park the scope using SkySafari 6 Pro and then close PHD2 followed by the capture software. Usually, this is fine but every now and then I noticed the scope does not park in position 4 exactly as it should (i.e., the RA axis is slightly off level). I can't seem to figure out what is the cause as it is very infrequent but annoying as it misaligns the scope for the next time I startup Skysafari 6 Pro to slew to an object (i.e., the mount is lost and I need to realign). Any thoughts as to what is going on? Is my shutdown sequence wrong?