Re: APCC 184.108.40.206: strange behaviour when parking at Park1 position
toggle quoted messageShow quoted text
Our park positions are NOT some fixed position on the gearwheel. They are calculated RA and DEC positions to be a certain distance from the meridian. Any small time error in your computer clock will put them off by the amount of the error (i.e. 1 second of time = 15 arc seconds of park error).
The difference between Park1 and Park5 is only about 10 seconds of time error. Park1 points to the North horizon, as does Park5. If your clock advanced by 10 seconds it can very easily put the scope on the other side. It is most likely a small time error in your laptop or computer that you are using. If you use two computers to control the mount they can cause this kind of problem if one computer's time is slightly different (by 10 seconds) from the other. The keypad is a computer. Your laptop is a computer, etc.
My advice is to never use Park1 for any reason, especially not for parking at the end of a session. It is too close to the counterweight up position, and if your system starts tracking, then within 10 seconds you have tracked past the meridian and are essentially in "forbidden" territory. If you fall asleep the mount can very well continue tracking until the scope tracks into the pier, which could cause damage. Park 2 and Park3 will always work and won't change. Park 4 and Park5 are ok also because it would take 12 hours of tracking before counterweight up condition. With APCC you can also make your own custom Park wherever you like.
If it were up to me I would eliminate Park1 altogether, but I can hear the howls from people who are using it. Park5 is just as good in almost all cases.
From: Yves Laroche <yves.laroche@...>
Sent: Wed, Jun 17, 2020 10:26 am
Subject: Re: [ap-gto] APCC 220.127.116.11: strange behaviour when parking at Park1 position
This morning, the mount behaved the same as other night.
APCC was the only software connected, no ASCOM driver. I parked the mount to Park1 position and the mount slewed at the opposite direction. I decided to let the slew completed. The mount parked at Park5 position. I unparked the mount from that position (Last Parked Position) and park the mount to Park1. The mount slewed back to Park1 as it should.
There is a logic software problem in this version. Never see hat kind of behaviour before.
I'm using CP4 controller.
Le 17/06/20 00:18, Ray Gralak <groups3@...> a écrit :