No APCC. CPO3 Q firmware. I’ll have a look at the log... Gregg Visit my astronomy & astrophotography site www.greggsastronomy.com

Hi Gregg, Are you using APCC or any other software? What version of firmware and control box? Have you tried searching your driver log files for "Park"? If the mount is being sent a command to park

Hi I have run into an unusual problem.  I use MaximDL for image acquisition; it has a telescope pointing function which allows the user to take an image and then point to a specific location to

I can open the roof by pressing a wall button, but the bright sunlight makes it very difficult to read the keypad's display or see what's displayed on the computer monitor. I'll figure out

Hi Mike, Don’t understand the day test problem – why can’t youjust open the roof? I am guessing you aren’t fully “computer-remote” set up, sothe roof requires “manual” opening?

I am leery about slewing the scope with the roof closed. If I do something wrong, it could hit the roof tension cables. I will go out during the day tomorrow and see what happens with minor ACP

Ray, Thanks again. I posted a message about this on the DC-3 ACP forurm. Bob Denny may have some comments after the holidays. It may be possible for him to modify his code so that ACP shuts APCC

Mike, Why wait for nightfall to confirm this ASCOM start-upsituation ? If it isn’t raining, and you are available, this problem could beinvestigated even during the day. You don’t need a

Mike, OK, I'm guessing the CW UP message was shown previously because the mount hadn't been initialized yet. That's the control box type. When you connect the driver to your mount it will show the

[ap-gto] wrote: Now it doesn't show the message. I connected in ACP, which unparked the mount and started it tracking. No "CW up" message. GTO CP3. 2. I know you 5.20.08. 3. Please email me a

Stacey, I'm glad that fixed the problem! Auto-shutdown has been refined over time to seamlessly work with other applications. Others may have run into this issue much earlier and then seeing previous

Hi Mike, The counterweight position may be inaccurate if the mount has not yet been initialized and in a few other conditions with older mount firmware. So: 1. What version of mount firmware are you

OK! That seems to work with ACP. I set auto shutdown in APCC for 15 seconds. I modified ACP's ShutdownObs.js to disconnect from APCC as normal but to NOT shut down APCC. When ACP disconnects, APCC

Using the latest AP ASCOM driver, I notice that the window now displays "CW up" when that is not the case. I've never seen this before. I park my AP1200 with the OTA pointing due west at Dec 0, so

Hi Stacey, Well, then that's the reason why the virtual ports are not getting released. To fix the problem you must not let ACP terminate APCC! When the last client closes its connection to the

Hi Ray, ACP definitely termnates APCC in its "ShutdownObs.js" script. This is done by calling a fairly "cryptic" routine called "StopProcess". The full shutdown script is

Okay, but I want to understand *how* APCC is being closed down by APC because this is a clue as to why the ports are increasing. You said when you manually close APCC the virtual ports are released,

When ACP runs its "ShutdownObs.js" script, it parks the scope, closes the dome, warms the camera cooler and then closes all the software including Maxim-DL, FocusMax, and APCC.

Please explain how are you having ACP close APCC? -Ray Gralak Author of APCC (Astro-Physics Command Center): http://www.astro-physics.com/index.htm?products/accessories/software/apcc/apcc Author of

Hi Ray, Well there are strange things going on. It's rather frustrating. When it's working the virtual ports show up in device manager and they close when I manually exit APCC. However, they don't