Coming from an operating mode of mostly using the mount with hand controller in a setup on the patio and
occasional use of the AP Ascom driver to connect autoguiding, is the use model of APCC going to 'undo' useful
things that I have gotten used to in the past? Or introducing 'unnecessary' complications for my use model?

In general APCC was designed to be transparent to ASCOM and client ASCOM applications. However, in order to completely answer your question you will need to describe your "use model".

-Ray Gralak
Author of APCC (Astro-Physics Command Center): http://www.astro-physics.com/index.htm?products/accessories/software/apcc/apcc
Author of PEMPro V3: https://www.ccdware.com
Author of Astro-Physics V2 ASCOM Driver: https://www.siriusimaging.com/apdriver

-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of drgert1 via Groups.Io
Sent: Sunday, November 10, 2019 8:02 PM
To: main@ap-gto.groups.io
Subject: [ap-gto] APCC for ISS Tracking

Hello All,

I am just getting started installing APCC and reading through the extensive documentation. Actually my initial (only)
interest to use APCC for is to track ISS. Reading through the docs I am impressed / worried about all the other
things that APCC does / 'takes over' and I am getting concerned if deploying APCC is the right decision.

Coming from an operating mode of mostly using the mount with hand controller in a setup on the patio and
occasional use of the AP Ascom driver to connect autoguiding, is the use model of APCC going to 'undo' useful
things that I have gotten used to in the past? Or introducing 'unnecessary' complications for my use model?

Thanks & Clear Skies,
Gert