Joe I use CdC all the time with APCC and have not had issues as you describe. 1. Start APCC 2. Start CdC (Ver 4.0 Build 3575) 3. Click "Connect Telescope" Icon 4. Click Connect button and wait for all

Joe, The proper way to handle this case is to close the driver by double-clicking the driver's Client count box as explained in the help file. Or, if you want to run a script, you can force the

Ray, About your advice to close the app(s) first rather thanclosing APCC with an app still connected to the driver. I have run into a whale of a problem – maybe others mayhave found the

That is not at all the proper way to shut down APCC. Never kill a process as that can cause problems. If you have been killing APCC like that, then it's no wonder APCC kept having to use different

Hi Ray. So here's what I have done so far. I installed ASCOM, AP ASCOM Driver, and APCC Pro on a completely new installation of Win 10 on a test virtual machine, so there are no other applications

Hi Michael, I don't think that will help in this particular case, since his test doesn't use any ASCOM client applications (besides APCC). APCC will not trigger an auto-shutdown until an application

Sam, This is the way to test that it works: 1. Start APCC. 2. Click the button in APCC to start "AP Jog". AP Jog will start. 3. Click "Connect" in APJog. The driver should start. 4. Click

Hi Ray, Just an update. If I open task manager and kill the APCC process from task manager, it will shutdown APCC properly and the Driver exits as well. This is what I would expect to happen when

Sometimes Process Explorer can be helpful for finding out which process is utilizing resources: https://docs.microsoft.com/en-us/sysinternals/downloads/process-explorer I'm not sure

I'm not sure what to tell you. APCC is Shutdown but the driver doesn't seem to exit. I'll keep on looking into it, but if you have some suggestions on potential causes, let me know. Thanks. Sam

Sam, If that were true, then APCC would NOT automatically exit. An application needs to connect to the driver, then disconnect to trigger APCC's auto-shutdown. -Ray Gralak Author of APCC

Hi Ray. This is really strange because in my tests I am only running APCC and APC. There are no other applications that I have open. Is there any way to see what application is holding on to the

Hi Sam, Given what you say above this the problem is NOT the driver or APCC. APCC cannot close if the driver is still active. And, the driver cannot shut down unless all applications connected to

Hi Ray. Thanks for getting back to me. I tried updating to APCC Pro 1.6.0.3 without success. The COM ports remain. I noticed that for some reason the AP Ascom Driver remains open when exiting APCC

If you are doing one alignment per night and can rely on autoguiding instead of a corrected tracking rate (to reduce autoguider movements), you can certainly get away with doing that. Now, if you are

I quoted a better than 5 arc min pointing error since I was comfortable that the errors were no worse than that. I did not want to turn on the observatory and look at actual logs. For my setup (FOV 4

Hi Sam, First, if this is not a typo, please update to 1.6.0.3 :-) There is no difference in the virtual port drivers or shutdown logic in 1.6.x. Also, there is nothing different when disconnecting

Ok, thanks. That's what I needed to know. Rolando

Hi Rob, I use APCC regularly on an AP1200 mount and my RMS pointing error is under 0.8 arcmin from anywhere to anywhere in the sky, including after a flip and after startup (providing the PC time is

Reading the Pinpoint marketing speak under "Accuracy" at http://pinpoint.dc3.com/ It looks like for the one IAU site they reference they routinely get under 2 arc-seconds and