toggle quoted messageShow quoted text
If you correctly initialized the mount with the keypad, then APCC just sends coordinates to the mount. If mount goes in the wrong direction, that implies the keypad initialization was incorrect.
What happens if you let APCC initialize the mount with the keypad not connected? For this test to mean something you must make sure APCC was synched to the mount the last time the mount was powered off.
To make sure you are sending accurate RA/Dec coordinates, you can use a planetarium program to invoke mount slews.
Author of PEMPro
Author of APCC (Astro-Physics Command Center): https://www.astro-physics.com/apcc-pro
Author of Astro-Physics V2 ASCOM Driver: https://www.siriusimaging.com/apdriver
From: email@example.com [mailto:firstname.lastname@example.org] On Behalf Of John
Sent: Wednesday, December 23, 2020 6:54 PM
Subject: Re: [ap-gto] Initial GoTo In APCC Pro Cause Nose or Tail Dive
Just looking at this time zone business. The keypad takes a positive values for the time zone (8 in my case). As a W
was entered earlier to indicate that we are West of the prime
meridian. I think there's another W in there now (the other W being for Winter).. APCC takes either a positive or
negative value for the offset.
I just powered up the mount again with just the keypad (by itself) connected to the gtocp5. The keypad has auto
connect = yes, so it is initializing the mount. The laptop and apcc are not connected
The mount unparks and starts tracking. The initial goto (using just the keypad) works just fine
The only issue I'm seeing (if it is an issue), is in apcc. The only way I can get the initial goto to work in apcc, is by
pressing the 'find home' button first and then execute the goto,
which is no big deal, thanks!