my laptop cover a couple days ago.
On Fri, Dec 8, 2017 at 8:56 PM, 'Ray Gralak (Groups)' email@example.com
[ap-gto] <firstname.lastname@example.org> wrote:
You gave me a time frame of where to look in the logs and the only thing
relevant is that somehow the mount was parked by something other than APCC
and that caused the problem with APPM. So, it doesn't appear to be a
software error. At least not an APCC/APPM/AP driver software error.
If you don't know what else you were running at that time that could have
caused this then you probably will need to work with A-P to find the reason
why the mount parked.
Author of APCC (Astro-Physics Command Center):
Author of PEMPro: http://www.ccdware.com
Author of Astro-Physics V2 ASCOM Driver: http://www.gralak.com/apdriver
Author of PulseGuide: http://www.pulseguide.com
Author of Sigma: http://www.gralak.com/sigma
-----Original Message-----the COM port read errors. I started APPM
From: email@example.com [mailto:firstname.lastname@example.org]
Sent: Friday, December 8, 2017 3:09 PM
Subject: RE: [ap-gto] Trouble with APPM
I dug through the log file and found some interesting things, including
runs a couple of different times and it looks like there are some unsafeslews logged. I have the horizon and
meridian limits set with the actions when these limits are set to "warnonly".
Here is a Dropbox link to the excerpt:
[Non-text portions of this message have been removed]