Thank you very much, Ray!
toggle quoted messageShow quoted text
On Jan 22, 2021, at 8:38 PM, Ray Gralak via groups.io <email@example.com> wrote:
Thank you for the logs. This was an unusual case in that there happened to be a race condition between the horizon limit being reached and the update of the RA/Dec tracking rates because the pointing model was active. I have created a new APCC Pro release, v220.127.116.11, which should prevent this from happening in the future. This issue only affects APCC Pro.
In case "check for update" is not working in APCC Pro, here is the direct download link:
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: firstname.lastname@example.org [mailto:email@example.com] On Behalf Of Luca Marinelli
Sent: Friday, January 22, 2021 3:19 AM
Subject: Re: [ap-gto] Mach2 tracking below custom horizon
[Edited Message Follows]
So I went through the SGP log and the application was sitting idly not sending any commands to AP ASCOM
driver after the end of the APPM run. As I said, I was not running a sequence, only using SGP for camera control
and plate solving.
Ray, I copied the APPC and AP ASCOM logs in my Dropbox if you want to take a look, but I am quite certain this
had nothing to do with an errant request from a client.
APPC/AP ASCOM logs: https://www.dropbox.com/s/bh3l6k5sut40hfi/ApccZip-Luca_Marinelli-2021-01-22-
SGP log: https://www.dropbox.com/s/o3gdtid7curwcys/sg_logfile_20210120175716.log?dl=0
The APPM run ended at 7:47pm 1/20/2021 near the Western horizon.