I thin I must have been. Can't recall ever changing it from the default. But I guess I must have at some stage :-)

Paul, You wrote: There have been no changes in regards to communications to the mount. However, there is better error checking so communication errors are more readily logged. Have you always been

Dear astrophotographers, I would like to share with you some of the latest images from my remote observatory. This time I´m presenting two images of dark nebulae. The first one is Sandqvist 169 in

Will do. Thanks Ray. Is there any reason though that this has only become a problem since I updated APCC and the driver a few weeks ago? The older versions were rock solid in this regard.

Paul, You have a very long timeout configured (2000msec) which is causing problems for a reason I will need to ask to Howard about. Try switching to UDP and lowering the timeout to 300 msecs. Then

P.S. And after that, not only would it not unpark on the first attempt, but not at all in APCC. Eventually, after a few tries, I got it to unpark from the ASCOM driver.

Hi Ray, I don't know if this is a related problem, but just setting up now (yes, a clear sky in winter!), I had trouble connecting to the ASCOM driver. APCC started ok, connected to and initialised

Hi Ray, I've sent a zip of the APCC and ASCOM logs to your email - I assume it's the groups3@... one? Thanks, Paul

Hi Paul, Okay, but I cannot reproduce that scenario. It just doesn't happen for me. But, there is good news because there is no need for you to capture additional logs. I think you should already

Hi Ray, I'm positive I didn't use the driver or SGP for parking or unparking. Unless there's some park issued by SGP without my explicitly doing it. All I did was - start APCC - connected it to the

Hi Paul, Are you sure that you didn't park through the driver (or SGP)? Only parking through the driver causes this behavior. Unparking later, either through APCC or the driver, doesn't matter. -Ray

Interesting. It was solely with APCC. I never normally touch the ASCOM driver, Though it was connected (with SGP connected in turn to it). Paul

I would be surprised if you can reproduce the problem using APCC alone. I did finally reproduce the behavior you saw but only when parking/unparking using the ASCOM driver. The ASCOM driver is sending

Thanks for the advice Ray. I'll get the logs back to you. Will be a little while as I'll do it when I set up next - so depends on the next clear sky …. and it's winter in Australia at the moment :-(

Ggt0fek3dwaz GtaqEnvoyé depuis mon smartphone Samsung Galaxy.

Thank you Ray. I plan to first spend some time trying new timeout parameters. With Ethernet (TCP) set to 350ms and the (fallback) UART timeout set to 500ms. Kind regards, John

Luca, Okay, maybe I misunderstood your pictures... your last picture was "Screenshot 2019-06-08 06.47.15.png". At the bottom of APCC it says "unparked" yet the driver shows "Parked". Shutdown the

Thanks Howard, I have no doubt of your Mad AP Mount Skillz! 😉 I’m sure my situation is not all that common, so not surprising it wasn’t anticipated. It does appear Ray figured it out. I

Hi Ray, I connected directly to the mount via USB cable (not remote desktop). APCC did not unpark the mount and I am pretty sure it was not an issue of waiting for the status to change. I tried

Hi John, You can use the latest driver (v5.20.09) and latest mount CP4 firmware (VCP4-P01-13) with APCC v1.6. That said, there is nothing in v1.7 that is different from v1.6 in regards to serial or