toggle quoted messageShow quoted text
From: email@example.com [mailto:firstname.lastname@example.org] On Behalf Of Yves Laroche
Sent: Tuesday, June 16, 2020 6:20 PM
Subject: Re: [ap-gto] APCC 220.127.116.11: strange behaviour when parking at Park1 position
The meridian delay set to "0" appeared at 03h16
The park message appeared at 03h28
There is a 12 minutes difference between both.
Le 16/06/20 18:36, Ray Gralak <groups3@...> a écrit :
[Edited Message Follows]
[Reason: Removed leading "Also" in first paragraph, which I forgot to remove when I moved the
paragraph to the top.]
APCC can force the mount into a counterweight-up position first which, depending on the start position,
might make it seem like it's going the wrong way.
If you don't think that's the case, then find in your APCC log where the park started. The meridian delay
should be set to "0" before the park is issued by APCC, except if there is a multipart slew. Search for
"meridian" to find places where it can get set.
Author of APCC (Astro-Physics Command Center): https://www.astro-physics.com/apcc-pro
Author of PEMPro V3: https://www.ccdware.com
Author of Astro-Physics V2 ASCOM Driver: https://www.siriusimaging.com/apdriver
> -----Original Message-----
> From: email@example.com [mailto:firstname.lastname@example.org] On Behalf Of Yves Laroche
> Sent: Tuesday, June 16, 2020 1:20 PM
> To: email@example.com
> Subject: [ap-gto] APCC 18.104.22.168: strange behaviour when parking at Park1 position
> Hi Ray,
> This morning at the end of my imaging session I parked the mount at Park1 position as usual but the
> was slewing at the opposite direction (Park4 or Park5). I stopped the slew and re-initiate the Park1
> and the mount went back to the Park1 position as it should. By chance my system is not completely
> automated else it can be a serious problem. At that time, the ASCOM driver was disconnected.
> I will sent you the logs on request.
> Best regards,