Understood yet the mount was in the Park 4, my normal park position, after an all-night imaging run. ACP was attempting to execute the park command and shutdown the observatory. I have yet to move the

I just noticed the same issue, the box to show the latest available version of APCC Pro is blank (and I made sure that APCC Pro is in the list of applications allowed by the windows firewall). Also

Ray, I’ll make the change to asynchronous park for tonight’s imaging run, and test the CloseSpecialRoof script to see if it behaves better with that setting. Thanks for the tip. -Craig

Craig, You should switch to asynchronous parks. -Ray Gralak Author of PEMPro Author of APCC (Astro-Physics Command Center): https://www.astro-physics.com/apcc-pro Author of Astro-Physics V2 ASCOM

Hi Ray, I connect to my mount using the serial port. I am not currently configured for asynchronous parks. -Craig

Steve, This is not a problem in APCC. It looks like a network error. The command to park the mount did not reach the mount for some reason: 0366449 2021-01-10 06:28:32.100: Debug, Command

Craig, I do have the special close script but that’s only used in weather events and I’ve seldom had that problem but it could have the two times I’ve seen this as both time it did rain

I just checked the driver and I am set for Asynchronous parks (checked). That part about resending I've proven when I see this condition and the mount is in the park position and issued the park

The likely case is one of those ASCOM applications is sending something to cause the mount to not complete the park operation while parking. Are you both using Asynchronous parks in the AP V2

Steve, It could be that what I mentioned in my previous post: one of the ASCOM applications might have sent a command around the time the park operation was about to complete, putting APCC in an

Hi Ray, I am for this session with version 1.8.8.13 of APCC and I see the follow-up fixes are not displayed? Does this correct for the same?

This should do it https://www.dropbox.com/s/v8y72py2yi58xoz/ApccZip-Steven_Reilly-2021-01-10-1 20444.zip?dl=0 -Steve

I’ve had this problem from time to time at my observatory. When it happens for me, the scope is left not tracking, pointing up, and ACP Expert reports waiting for the mount to park. If I send the

Thanks Ray, I do indeed stand corrected. But then why is the option to unpark active? That’s confusing. -Steve

Go ahead and post the link, but I may not get time to review it until later today. For APCC to get into this state, something (an ASCOM client application?) might have stopped mount tracking in the

Steve, > Have another look at the screen shot and APCC. Does APCC not have Unpark as > being Active choice and Park greyed out (inactive)? That's not the park status. See this portion of your

Dominique I suspect that unpowered usb3 hub at the computer is your problem. All hubs in the chain need to be powered. Don Anderson

Ray, I do have the zipped log file if that is of any help. It's the usual files and just the log file for that period and 12.4MBs. I can upload to Dropbox if you want it. -Steve

Michael Try running your set up with an external USB cable using your existing Startech hub. If your rig runs reliably at the low temperatures, you can pretty much zero in on cabling within the mount

That hub should work fine at 47F but those specs are just a general average. Your particular hub may not work reliably at those temps. The problem could also be running power cables along side data