Aha! Time did recently change between the times we have been able to image here in the PNW (which is where Tony is at as well) I bet that is why.

Your logs show that you did not have an IP address set in the ASCOM driver. Try configuring the driver to be a GTOCP4 and to use the IP Address of the mount. Make sure to uncheck the APCC option in

Normally a mount will never do what you are describing, even if you have a power loss during a slew. But this situation can occur if during a session you did a recal on a wrong position. It can occur

No need to power cycle. Once there you are there. Rolando

Loosen the clutches and move it there manually. Then tighten the clutches and check all the other park positions. Rolando

Thank You Sir, Of course I picked the one point in the entire sky to Sync on - Regulus - that is below the peak of the one house that can hide some of my sky - so the plate solve failed. But figured

Hi Ray I do not use USB-serial converter. The PC has a physical serial port which is COM1 I have run device manager after boot. It reports COM1 as the only COM port and it is running properly. I have

The Ascom driver stopped connecting to my Mach1/ CTO4. I had to switch computers, but do not think that is the problem. I also installed the latest versions of APCC and Ascom. I am using an Ethernet

Well since you have APCC you can just do this: Tools > APPM Plate Solve and Sync Prior to that though, be sure you are not pointed at the pole. Just put in a random object you know exists into

Okay, Hi Bill, Next dumb question - do I just put coordinates into the GoTo/Recal page of APCC - or is that Recal button elsewhere?

Or -- point the mount at an object, center it, and RECAL. Problem solved.

Hi Peter, Thanks. I'll give that a go - I was hoping that there would be something more automated for this - but I guess having AE's would solve this issue?

I would say unlock the clutches of both axes, manually position the mount to Park 3, power cycle the mount if it's still powered up, then resume from Park 3 and go from there. Peter

Okay then... so every application used will likely need to be started as administrator. If not, there could be a conflict on the driver's COM port if both an admin and non-admin AP V2 driver

I think, the other day, I accidentally shutdown power to the mount while it was tracking and never got to "Park" it, as I normally do at Park position # (more or less North). I started it up tonight

I agree that software should not have to run as admin. In the case of Voyager, that is where things are at.

I suspected that. The developer has chosen a licensing scheme that requires administrative access. It is nothing to do with communication to astronomy equipment. Running a web UI/API does not require

Besides the philosophical discussion here -- which I agree with, these folks are right that Voyager needs to run as admin per the developer. The licensing portion of the software and the integrated

Henry, Did you try my instructions? This is a not a problem with the mount or AP software. This has to do with the COM port connection to the mount. Are you using a USB/serial converter? -Ray

Other ASCOM applications don't need to be run as administrator, and in fact should not need to be run as administrator. The only exception is that sometimes an application needs to run *once* as