Re: [ap-gto] Re: Park 1 anomaly in all mounts


Jan 2, 2016

 


----------------------------

#72189 Jan 2, 2016

Correction of typo: I put the wrong date below for setting the time/date settings. Here is the correct procedure: First turn on power. Let the mount initialize normally with Autoconnect = Yes. If you are in Autoconnect = NO, enter the Location and then enter Resume From Park (don't Resume from Park1). Now go into the Setup menu, then Time/date menu. Change the date to 01/01/2015. Press the GoTo button, you should hear a beep, which means that the date changed successfully. If you don't hear the beep, go back and check the date again. Once you have the date set to 2015, verify you 3 park positions, starting with Park3, then Park2 and finally Park1. Sorry about this, and I hope I have not added to the confusion. Rolando   -----Original Message-----

From: chris1011@... [ap-gto] ap-gto@yahoogroups.com>

To: ap-gto ap-gto@yahoogroups.com>; ap-ug ap-ug@yahoogroups.com>

Sent: Sat, Jan 2, 2016 12:35 pm

Subject: [ap-gto] Park 1 anomaly in all mounts





Hello all mount users, If you are using Park1 please note, there is a problem now on the first day of 2016 starting the mount from Park1 position. There is a timing issue that has arisen with this first day of 2016. Resuming from Park 1 using the date of 1/1/2016 will cause the mount to go the wrong way and the scope will hit the pier if you send it to any object. The best option right now is to go into SETUP, go to the date/Time menu, change the date in the keypad to 01/01/2015. Meanwhile I will consult with our software engineer and try to determine what has happened with the new year date as far as calculating Park 1. The easiest procedure to avoid wrong move after startup from Park1 would be the following procedure: First turn on power. Let the mount initialize normally with Autoconnect = Yes. If you are in Autoconnect = NO, enter the Location and then enter Resume From Park (don't Resume from Park1). Now go into the Setup menu, then Time/date menu. Change the date to 01/01/2016. Press the GoTo button, you should hear a beep, which means that the date changed successfully. If you don't hear the beep, go back and check the date again. Once you have the date set to 2015, verify you 3 park positions, starting with Park3, then Park2 and finally Park1. With a date of 2016 in the keypad, for some reason it now calculates Park 1 to be on the East side of the mount. It works fine this way too, but now if you want to resume from Park1 in a new setup you would need to start the mount with scope on the East side (flipped over to the other side pointing North). Everything else will work fine, just this one park position has now flipped. I will try to determine where the timing issue is and let you all know how it can be fixed for the proper date. Roland Christen 



----------------------------

#72191 Jan 2, 2016

There should be no issue with software other than the keypad.  We traced it down to the fact that 2016 is a leap year. Apparently the keypad is off by one day in the meridian calculation, whereas the mount CP3 is calculating it correctly. So the 1 degree error is enough to cause Park 1 to be on the other side. This will be the case until March1 when the two will be in sync again.  We will do our best to fix the software bug as quickly as possible and make the version available for download. may take a couple of days. Rolando  -----Original Message-----

From: j.blazey@... [ap-gto] ap-gto@yahoogroups.com>

To: ap-gto ap-gto@yahoogroups.com>

Sent: Sat, Jan 2, 2016 1:34 pm

Subject: [ap-gto] Re: Park 1 anomaly in all mounts





Thanks for the heads up Roland. 

I drive the mount using TSX and park it with that sw's park command, which happens to be in the Park 1 position.  But on the telescope tab there is also the option to use the AP Park 1 command.  I'll see what happens tonight.

If I change the date will it still accurately slew to solar system objects?

Jeff


S
e
n
i
o
r
T
u
b
e
.
o
r
g