Re: GTO CP3 connection problem via COM port in Windows 10


Bill Long
 

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 Web Dashboard UI have requirements on that, and a few others. 

Lets not derail the discussion though. It needs to run this way, and if everything else one needs runs as Admin it will work just fine. I have imaged for hundreds of hours with AP mounts, APCC, PHD2, SkyX, and Voyager all running as admin. 


From: main@ap-gto.groups.io <main@ap-gto.groups.io> on behalf of Ray Gralak <groups3@...>
Sent: Saturday, March 14, 2020 7:13 PM
To: main@ap-gto.groups.io <main@ap-gto.groups.io>
Subject: Re: [ap-gto] GTO CP3 connection problem via COM port in Windows 10
 
> There are good number of people I know of uses Voyager running as admin with A-P mounts and A-P V2
> ASCOM driver without issues like myself. Developer of Voyager said that Voyager must run as admin.

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 administrator to complete registration.

So what requires Voyager have to run as administrator? Certainly if it is just talking to an AP mount it does not need to run as administrator. Cameras neither, because other applications (e.g. SGPro and SkyX) do not need to run as administrator that access cameras, filter wheels, domes, weather stations, plate solvers, etc.

-Ray Gralak
Author of APCC (Astro-Physics Command Center): https://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.astro-physics.com%2Fapcc-pro&amp;data=02%7C01%7C%7C4754c20f8ce84ef9e50c08d7c8866c5a%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637198351972854681&amp;sdata=LJ%2FPZ1VVuCJVXgGUumw2B3PxVRvP47TwEzHEMCIl7HM%3D&amp;reserved=0
Author of PEMPro V3:  https://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ccdware.com&amp;data=02%7C01%7C%7C4754c20f8ce84ef9e50c08d7c8866c5a%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637198351972854681&amp;sdata=eEW7dcRsi8kNcrtHscBpIqPekW1%2FdsA3RpG1rmuri10%3D&amp;reserved=0
Author of Astro-Physics V2 ASCOM Driver: https://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.siriusimaging.com%2Fapdriver&amp;data=02%7C01%7C%7C4754c20f8ce84ef9e50c08d7c8866c5a%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637198351972854681&amp;sdata=T7o1GhnqdxuDxtrWKhFp%2F4Tl6gC6%2BGtoep%2FOI3HzTx0%3D&amp;reserved=0


> -----Original Message-----
> From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Peter Nagy
> Sent: Saturday, March 14, 2020 6:00 PM
> To: main@ap-gto.groups.io
> Subject: Re: [ap-gto] GTO CP3 connection problem via COM port in Windows 10
>
> There are good number of people I know of uses Voyager running as admin with A-P mounts and A-P V2
> ASCOM driver without issues like myself. Developer of Voyager said that Voyager must run as admin.
>
> I suggest Henry create a new thread at Voyager forum. There was a similar issue reported at Voyager forum and
> this is one example and hopefully this will fix it for you:
>
> https://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fforum.starkeeper.it%2Ft%2Fnew-problem-connecting-to-mach1gto-since-upgrading-windows-7-to-windows-&amp;data=02%7C01%7C%7C4754c20f8ce84ef9e50c08d7c8866c5a%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637198351972854681&amp;sdata=23mG1p9rVQFG72aCFvHrPA2FHCrrfjThsc5k8SvppdQ%3D&amp;reserved=0
> 10/1162/8
>
> Scroll down to about 9/13 as shown at right side. Here is one of the snippet:
>
> "A Teamviewer session with Leo has fixed all the problems! I am very grateful. For posterity, the problem with the
> web server is to do with the port. For some reason on my PC the port I need to use is 8081, not the default 80. Leo
> figured out the problem so its all working fine now!"
>
> Read the whole thread.
>
> Peter
>




Join main@ap-gto.groups.io to automatically receive all group messages.