Date   

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

Ray Gralak
 

I agree that software should not have to run as admin. In the case of Voyager, that is where things are at.
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 instances are invoked. APCC gets around the problem by creating
separate virtual ports for regular and admin driver instances so two AP V2 drivers can be run simultaneously.

-Ray Gralak
Author of APCC (Astro-Physics Command Center): https://www.astro-physics.com/apcc-pro
Author of PEMPro V3: https://www.ccdware.com
Author of Astro-Physics V2 ASCOM Driver: https://www.siriusimaging.com/apdriver


-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Bill Long
Sent: Saturday, March 14, 2020 7:26 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] GTO CP3 connection problem via COM port in Windows 10

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

________________________________

From: main@ap-gto.groups.io <main@ap-gto.groups.io> on behalf of Ray Gralak <groups3@gralak.com>
Sent: Saturday, March 14, 2020 7:23 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

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.
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 administrative rights either. This
sounds like
some poor design decisions.

-Ray Gralak
Author of APCC (Astro-Physics Command Center):
https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.astro-physics.com%2Fapcc-
pro&amp;data=02%7C01%7C%7Ca4bd9792e1b74c61c18d08d7c887ee2f%7C84df9e7fe9f640afb435aaaaaaaaa
aaa%7C1%7C0%7C637198358442041913&amp;sdata=8vqWOMLqTW0cKxzD8xTQYsJJhw0qRzFS0tbe4sJw7s
A%3D&amp;reserved=0 <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.astro-
physics.com%2Fapcc-
pro&amp;data=02%7C01%7C%7Ca4bd9792e1b74c61c18d08d7c887ee2f%7C84df9e7fe9f640afb435aaaaaaaaa
aaa%7C1%7C0%7C637198358442041913&amp;sdata=8vqWOMLqTW0cKxzD8xTQYsJJhw0qRzFS0tbe4sJw7s
A%3D&amp;reserved=0>
Author of PEMPro V3:
https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ccdware.com&;data=02%7C01%
7C%7Ca4bd9792e1b74c61c18d08d7c887ee2f%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C63719
8358442051917&amp;sdata=CPBu3pUh9H22GyArs9ys3Xx6Le5KsLujRZi8ZOM1ekg%3D&amp;reserved=0
<https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ccdware.com&;data=02%7C01
%7C%7Ca4bd9792e1b74c61c18d08d7c887ee2f%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637
198358442051917&amp;sdata=CPBu3pUh9H22GyArs9ys3Xx6Le5KsLujRZi8ZOM1ekg%3D&amp;reserved=0>
Author of Astro-Physics V2 ASCOM Driver:
https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.siriusimaging.com%2Fapdriver&;
data=02%7C01%7C%7Ca4bd9792e1b74c61c18d08d7c887ee2f%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1
%7C0%7C637198358442051917&amp;sdata=gUtcJ2g%2B%2FRg6OvMtehafQbd%2Bn4vxIGVwLGp7OMPrqOg
%3D&amp;reserved=0
<https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.siriusimaging.com%2Fapdriver&am
p;data=02%7C01%7C%7Ca4bd9792e1b74c61c18d08d7c887ee2f%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7
C1%7C0%7C637198358442051917&amp;sdata=gUtcJ2g%2B%2FRg6OvMtehafQbd%2Bn4vxIGVwLGp7OMPrq
Og%3D&amp;reserved=0>


-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Bill Long
Sent: Saturday, March 14, 2020 7:19 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] GTO CP3 connection problem via COM port in Windows 10

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@gralak.com>
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://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Feur04.safelinks.protection.outlook.com%2
F%3Furl%3Dhttps%253A%252F%252Fwww.astro-physics.com%252Fapcc-
&amp;data=02%7C01%7C%7Ca4bd9792e1b74c61c18d08d7c887ee2f%7C84df9e7fe9f640afb435aaaaaaaaaaaa
%7C1%7C0%7C637198358442051917&amp;sdata=W693ubnweW9ZrHgKCIWaplQvn8loBZSoh5DyjtAegkk%3D
&amp;reserved=0
<https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Feur04.safelinks.protection.outlook.com%
2F%3Furl%3Dhttps%253A%252F%252Fwww.astro-physics.com%252Fapcc-
&amp;data=02%7C01%7C%7Ca4bd9792e1b74c61c18d08d7c887ee2f%7C84df9e7fe9f640afb435aaaaaaaaaaaa
%7C1%7C0%7C637198358442051917&amp;sdata=W693ubnweW9ZrHgKCIWaplQvn8loBZSoh5DyjtAegkk%3D
&amp;reserved=0>
pro&amp;data=02%7C01%7C%7C4754c20f8ce84ef9e50c08d7c8866c5a%7C84df9e7fe9f640afb435aaaaaaaaaa
aa%7C1%7C0%7C637198351972854681&amp;sdata=LJ%2FPZ1VVuCJVXgGUumw2B3PxVRvP47TwEzHEMC
Il7HM%3D&amp;reserved=0
<https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Feur04.safelinks.protection.outlook.com%
2F%3Furl%3Dhttps%253A%252F%252Fwww.astro-
&amp;data=02%7C01%7C%7Ca4bd9792e1b74c61c18d08d7c887ee2f%7C84df9e7fe9f640afb435aaaaaaaaaaaa
%7C1%7C0%7C637198358442051917&amp;sdata=bLcbV8VTObboL1MMeRGSmi6wkHw1I9uXQ%2BXRJJyZ2
DQ%3D&amp;reserved=0
physics.com%2Fapcc-
pro&amp;data=02%7C01%7C%7C4754c20f8ce84ef9e50c08d7c8866c5a%7C84df9e7fe9f640afb435aaaaaaaaaa
aa%7C1%7C0%7C637198351972854681&amp;sdata=LJ%2FPZ1VVuCJVXgGUumw2B3PxVRvP47TwEzHEMC
Il7HM%3D&amp;reserved=0>
Author of PEMPro V3:
https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Feur04.safelinks.protection.outlook.com%2
F%3Furl%3Dhttps%253A%252F%252Fwww.ccdware.com%26amp%3Bdata%3D02%257C01%257&amp;data=0
2%7C01%7C%7Ca4bd9792e1b74c61c18d08d7c887ee2f%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0
%7C637198358442051917&amp;sdata=YVjNNQxHkmsZTPKGtNTP0IP1zqL1yD%2BU9PNBksy%2Fh74%3D&a
mp;reserved=0
<https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Feur04.safelinks.protection.outlook.com%
2F%3Furl%3Dhttps%253A%252F%252Fwww.ccdware.com%26amp%3Bdata%3D02%257C01%257&amp;data=
02%7C01%7C%7Ca4bd9792e1b74c61c18d08d7c887ee2f%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C
0%7C637198358442051917&amp;sdata=YVjNNQxHkmsZTPKGtNTP0IP1zqL1yD%2BU9PNBksy%2Fh74%3D&a
mp;reserved=0>
C%7C4754c20f8ce84ef9e50c08d7c8866c5a%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C6371983
51972854681&amp;sdata=eEW7dcRsi8kNcrtHscBpIqPekW1%2FdsA3RpG1rmuri10%3D&amp;reserved=0
<https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Feur04.safelinks.protection.outlook.com%
2F%3Furl%3Dhttps%253A%252F%252Fwww.ccdware.com%26amp%3Bdata%3D02%257C01%25&amp;data=0
2%7C01%7C%7Ca4bd9792e1b74c61c18d08d7c887ee2f%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0
%7C637198358442051917&amp;sdata=yoF4Vk9yksJuyUIeei8CMjmy%2F1CwPGa1NCfg0tvU1kM%3D&amp;res
erved=0
7C%7C4754c20f8ce84ef9e50c08d7c8866c5a%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637198
351972854681&amp;sdata=eEW7dcRsi8kNcrtHscBpIqPekW1%2FdsA3RpG1rmuri10%3D&amp;reserved=0>
Author of Astro-Physics V2 ASCOM Driver:
https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Feur04.safelinks.protection.outlook.com%2
F%3Furl%3Dhttps%253A%252F%252Fwww.siriusimaging.com%252Fapdriver%26amp&amp;data=02%7C01%7
C%7Ca4bd9792e1b74c61c18d08d7c887ee2f%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637198
358442051917&amp;sdata=IfwCaDswchXjYrGFxg14lTq4jjHh7yFEb93QAAJaDRI%3D&amp;reserved=0
<https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Feur04.safelinks.protection.outlook.com%
2F%3Furl%3Dhttps%253A%252F%252Fwww.siriusimaging.com%252Fapdriver%26amp&amp;data=02%7C01%
7C%7Ca4bd9792e1b74c61c18d08d7c887ee2f%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C63719
8358442051917&amp;sdata=IfwCaDswchXjYrGFxg14lTq4jjHh7yFEb93QAAJaDRI%3D&amp;reserved=0> ;
data=02%7C01%7C%7C4754c20f8ce84ef9e50c08d7c8866c5a%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1
%7C0%7C637198351972854681&amp;sdata=T7o1GhnqdxuDxtrWKhFp%2F4Tl6gC6%2BGtoep%2FOI3HzTx0%
3D&amp;reserved=0
<https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Feur04.safelinks.protection.outlook.com%
2F%3Furl%3Dhttps%253A%252F%252Fwww.siriusimaging.com%252Fapdriver%26amp&amp;data=02%7C01%
7C%7Ca4bd9792e1b74c61c18d08d7c887ee2f%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C63719
8358442051917&amp;sdata=IfwCaDswchXjYrGFxg14lTq4jjHh7yFEb93QAAJaDRI%3D&amp;reserved=0
;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://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Feur04.safelinks.protection.outlook.com%2
F%3Furl%3Dhttps%253A%252F%252Fforum.starkeeper.it%252Ft%252Fnew-problem-
&amp;data=02%7C01%7C%7Ca4bd9792e1b74c61c18d08d7c887ee2f%7C84df9e7fe9f640afb435aaaaaaaaaaaa
%7C1%7C0%7C637198358442051917&amp;sdata=dn5TcWBMjp03C5Xt198y0pZ50MjEI9kq8G%2FWIcReA4E%
3D&amp;reserved=0
<https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Feur04.safelinks.protection.outlook.com%
2F%3Furl%3Dhttps%253A%252F%252Fforum.starkeeper.it%252Ft%252Fnew-problem-
&amp;data=02%7C01%7C%7Ca4bd9792e1b74c61c18d08d7c887ee2f%7C84df9e7fe9f640afb435aaaaaaaaaaaa
%7C1%7C0%7C637198358442051917&amp;sdata=dn5TcWBMjp03C5Xt198y0pZ50MjEI9kq8G%2FWIcReA4E%
3D&amp;reserved=0>
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
<https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Feur04.safelinks.protection.outlook.com%
2F%3Furl%3Dhttps%253A%252F%252Fforum.starkeeper.it%252Ft%252Fnew-problem-
&amp;data=02%7C01%7C%7Ca4bd9792e1b74c61c18d08d7c887ee2f%7C84df9e7fe9f640afb435aaaaaaaaaaaa
%7C1%7C0%7C637198358442051917&amp;sdata=dn5TcWBMjp03C5Xt198y0pZ50MjEI9kq8G%2FWIcReA4E%
3D&amp;reserved=0
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









Mount Not Going To Park Position 3?

Tony Benjamin <tonybenjamin@...>
 

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 and hit Park to position 3 - but its about 10 degrees short of where it should be? Whats the best way to get it back to the correct Park position 3?


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

Bill Long
 

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


From: main@ap-gto.groups.io <main@ap-gto.groups.io> on behalf of Ray Gralak <groups3@...>
Sent: Saturday, March 14, 2020 7:23 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
 
> 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.

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 administrative rights either. This sounds like
some poor design decisions.

-Ray Gralak
Author of APCC (Astro-Physics Command Center): https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.astro-physics.com%2Fapcc-pro&amp;data=02%7C01%7C%7Ca4bd9792e1b74c61c18d08d7c887ee2f%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637198358442041913&amp;sdata=8vqWOMLqTW0cKxzD8xTQYsJJhw0qRzFS0tbe4sJw7sA%3D&amp;reserved=0
Author of PEMPro V3:  https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ccdware.com&amp;data=02%7C01%7C%7Ca4bd9792e1b74c61c18d08d7c887ee2f%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637198358442051917&amp;sdata=CPBu3pUh9H22GyArs9ys3Xx6Le5KsLujRZi8ZOM1ekg%3D&amp;reserved=0
Author of Astro-Physics V2 ASCOM Driver: https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.siriusimaging.com%2Fapdriver&amp;data=02%7C01%7C%7Ca4bd9792e1b74c61c18d08d7c887ee2f%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637198358442051917&amp;sdata=gUtcJ2g%2B%2FRg6OvMtehafQbd%2Bn4vxIGVwLGp7OMPrqOg%3D&amp;reserved=0


> -----Original Message-----
> From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Bill Long
> Sent: Saturday, March 14, 2020 7:19 PM
> To: main@ap-gto.groups.io
> Subject: Re: [ap-gto] GTO CP3 connection problem via COM port in Windows 10
>
> 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://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Feur04.safelinks.protection.outlook.com%2F%3Furl%3Dhttps%253A%252F%252Fwww.astro-physics.com%252Fapcc-&amp;data=02%7C01%7C%7Ca4bd9792e1b74c61c18d08d7c887ee2f%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637198358442051917&amp;sdata=W693ubnweW9ZrHgKCIWaplQvn8loBZSoh5DyjtAegkk%3D&amp;reserved=0
> pro&amp;data=02%7C01%7C%7C4754c20f8ce84ef9e50c08d7c8866c5a%7C84df9e7fe9f640afb435aaaaaaaaaa
> aa%7C1%7C0%7C637198351972854681&amp;sdata=LJ%2FPZ1VVuCJVXgGUumw2B3PxVRvP47TwEzHEMC
> Il7HM%3D&amp;reserved=0 <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Feur04.safelinks.protection.outlook.com%2F%3Furl%3Dhttps%253A%252F%252Fwww.astro-&amp;data=02%7C01%7C%7Ca4bd9792e1b74c61c18d08d7c887ee2f%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637198358442051917&amp;sdata=bLcbV8VTObboL1MMeRGSmi6wkHw1I9uXQ%2BXRJJyZ2DQ%3D&amp;reserved=0
> physics.com%2Fapcc-
> pro&amp;data=02%7C01%7C%7C4754c20f8ce84ef9e50c08d7c8866c5a%7C84df9e7fe9f640afb435aaaaaaaaaa
> aa%7C1%7C0%7C637198351972854681&amp;sdata=LJ%2FPZ1VVuCJVXgGUumw2B3PxVRvP47TwEzHEMC
> Il7HM%3D&amp;reserved=0>
> Author of PEMPro V3:
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Feur04.safelinks.protection.outlook.com%2F%3Furl%3Dhttps%253A%252F%252Fwww.ccdware.com%26amp%3Bdata%3D02%257C01%257&amp;data=02%7C01%7C%7Ca4bd9792e1b74c61c18d08d7c887ee2f%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637198358442051917&amp;sdata=YVjNNQxHkmsZTPKGtNTP0IP1zqL1yD%2BU9PNBksy%2Fh74%3D&amp;reserved=0
> C%7C4754c20f8ce84ef9e50c08d7c8866c5a%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C6371983
> 51972854681&amp;sdata=eEW7dcRsi8kNcrtHscBpIqPekW1%2FdsA3RpG1rmuri10%3D&amp;reserved=0
> <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Feur04.safelinks.protection.outlook.com%2F%3Furl%3Dhttps%253A%252F%252Fwww.ccdware.com%26amp%3Bdata%3D02%257C01%25&amp;data=02%7C01%7C%7Ca4bd9792e1b74c61c18d08d7c887ee2f%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637198358442051917&amp;sdata=yoF4Vk9yksJuyUIeei8CMjmy%2F1CwPGa1NCfg0tvU1kM%3D&amp;reserved=0
> 7C%7C4754c20f8ce84ef9e50c08d7c8866c5a%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637198
> 351972854681&amp;sdata=eEW7dcRsi8kNcrtHscBpIqPekW1%2FdsA3RpG1rmuri10%3D&amp;reserved=0>
> Author of Astro-Physics V2 ASCOM Driver:
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Feur04.safelinks.protection.outlook.com%2F%3Furl%3Dhttps%253A%252F%252Fwww.siriusimaging.com%252Fapdriver%26amp&amp;data=02%7C01%7C%7Ca4bd9792e1b74c61c18d08d7c887ee2f%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637198358442051917&amp;sdata=IfwCaDswchXjYrGFxg14lTq4jjHh7yFEb93QAAJaDRI%3D&amp;reserved=0;
> data=02%7C01%7C%7C4754c20f8ce84ef9e50c08d7c8866c5a%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1
> %7C0%7C637198351972854681&amp;sdata=T7o1GhnqdxuDxtrWKhFp%2F4Tl6gC6%2BGtoep%2FOI3HzTx0%
> 3D&amp;reserved=0
> <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Feur04.safelinks.protection.outlook.com%2F%3Furl%3Dhttps%253A%252F%252Fwww.siriusimaging.com%252Fapdriver%26amp&amp;data=02%7C01%7C%7Ca4bd9792e1b74c61c18d08d7c887ee2f%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637198358442051917&amp;sdata=IfwCaDswchXjYrGFxg14lTq4jjHh7yFEb93QAAJaDRI%3D&amp;reserved=0
> ;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://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Feur04.safelinks.protection.outlook.com%2F%3Furl%3Dhttps%253A%252F%252Fforum.starkeeper.it%252Ft%252Fnew-problem-&amp;data=02%7C01%7C%7Ca4bd9792e1b74c61c18d08d7c887ee2f%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637198358442051917&amp;sdata=dn5TcWBMjp03C5Xt198y0pZ50MjEI9kq8G%2FWIcReA4E%3D&amp;reserved=0
> 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
> <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Feur04.safelinks.protection.outlook.com%2F%3Furl%3Dhttps%253A%252F%252Fforum.starkeeper.it%252Ft%252Fnew-problem-&amp;data=02%7C01%7C%7Ca4bd9792e1b74c61c18d08d7c887ee2f%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637198358442051917&amp;sdata=dn5TcWBMjp03C5Xt198y0pZ50MjEI9kq8G%2FWIcReA4E%3D&amp;reserved=0
> 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
> >
>
>
>
>
>
>





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

Ray Gralak
 

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.
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 administrative rights either. This sounds like
some poor design decisions.

-Ray Gralak
Author of APCC (Astro-Physics Command Center): https://www.astro-physics.com/apcc-pro
Author of PEMPro V3: https://www.ccdware.com
Author of Astro-Physics V2 ASCOM Driver: https://www.siriusimaging.com/apdriver


-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Bill Long
Sent: Saturday, March 14, 2020 7:19 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] GTO CP3 connection problem via COM port in Windows 10

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@gralak.com>
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%7C84df9e7fe9f640afb435aaaaaaaaaa
aa%7C1%7C0%7C637198351972854681&amp;sdata=LJ%2FPZ1VVuCJVXgGUumw2B3PxVRvP47TwEzHEMC
Il7HM%3D&amp;reserved=0 <https://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.astro-
physics.com%2Fapcc-
pro&amp;data=02%7C01%7C%7C4754c20f8ce84ef9e50c08d7c8866c5a%7C84df9e7fe9f640afb435aaaaaaaaaa
aa%7C1%7C0%7C637198351972854681&amp;sdata=LJ%2FPZ1VVuCJVXgGUumw2B3PxVRvP47TwEzHEMC
Il7HM%3D&amp;reserved=0>
Author of PEMPro V3:
https://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ccdware.com&;data=02%7C01%7
C%7C4754c20f8ce84ef9e50c08d7c8866c5a%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C6371983
51972854681&amp;sdata=eEW7dcRsi8kNcrtHscBpIqPekW1%2FdsA3RpG1rmuri10%3D&amp;reserved=0
<https://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ccdware.com&;data=02%7C01%
7C%7C4754c20f8ce84ef9e50c08d7c8866c5a%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637198
351972854681&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&;
data=02%7C01%7C%7C4754c20f8ce84ef9e50c08d7c8866c5a%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1
%7C0%7C637198351972854681&amp;sdata=T7o1GhnqdxuDxtrWKhFp%2F4Tl6gC6%2BGtoep%2FOI3HzTx0%
3D&amp;reserved=0
<https://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.siriusimaging.com%2Fapdriver&
;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
<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





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
>





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

Ray Gralak
 

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 Gralak
Author of APCC (Astro-Physics Command Center): https://www.astro-physics.com/apcc-pro
Author of PEMPro V3: https://www.ccdware.com
Author of Astro-Physics V2 ASCOM Driver: https://www.siriusimaging.com/apdriver

-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Henry Kwok
Sent: Saturday, March 14, 2020 6:48 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] GTO CP3 connection problem via COM port in Windows 10

Hi Ray and Peter,

Voyager must run in administrator mode.

The person on the Voyager forum is me. Leo has fixed most of the problem for me. As it turns out, most of the
problem was due to the upgrade process from Windows 7 to Windows 10. I have since done a clean install of
Windows 10, and after Leo tweaked the settings everything is working 99% of the time now.

The only exception is the problem I described above i.e. the driver will not connect to the mount on the first attempt
after a reboot, but will connect subsequently without changing any settings between the 1st and 2nd attempts.
Therefore I know it has nothin to do with COM port selection. It is almost as if it needs one attempt to wake up
something (hardware or software I am not sure).

The problem does not appear limited to Voyager as it will also happen with APJog (which I set to administrator
mode) as well, therefore I think it is a problem with hardware-driver interaction and I have elected to post here
rather than on the Voyager forum.

Cheers

Henry


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

Ray Gralak
 

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://www.astro-physics.com/apcc-pro
Author of PEMPro V3: https://www.ccdware.com
Author of Astro-Physics V2 ASCOM Driver: https://www.siriusimaging.com/apdriver


-----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://forum.starkeeper.it/t/new-problem-connecting-to-mach1gto-since-upgrading-windows-7-to-windows-
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


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

Bill Long
 

I recently bought a used Mach 1 with CP3 V2, and I cannot reproduce this issue on Windows 10. 


From: main@ap-gto.groups.io <main@ap-gto.groups.io> on behalf of Henry Kwok <henry.ck.kwok@...>
Sent: Saturday, March 14, 2020 6:48 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
 
Hi Ray and Peter,

Voyager must run in administrator mode.

The person on the Voyager forum is me. Leo has fixed most of the problem for me. As it turns out, most of the problem was due to the upgrade process from Windows 7 to Windows 10. I have since done a clean install of Windows 10, and after Leo tweaked the settings everything is working 99% of the time now.

The only exception is the problem I described above i.e. the driver will not connect to the mount on the first attempt after a reboot, but will connect subsequently without changing any settings between the 1st and 2nd attempts. Therefore I know it has nothin to do with COM port selection. It is almost as if it needs one attempt to wake up something (hardware or software I am not sure).

The problem does not appear limited to Voyager as it will also happen with APJog (which I set to administrator mode) as well, therefore I think it is a problem with hardware-driver interaction and I have elected to post here rather than on the Voyager forum. 

Cheers

Henry


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

Henry Kwok
 

Hi Ray and Peter,

Voyager must run in administrator mode.

The person on the Voyager forum is me. Leo has fixed most of the problem for me. As it turns out, most of the problem was due to the upgrade process from Windows 7 to Windows 10. I have since done a clean install of Windows 10, and after Leo tweaked the settings everything is working 99% of the time now.

The only exception is the problem I described above i.e. the driver will not connect to the mount on the first attempt after a reboot, but will connect subsequently without changing any settings between the 1st and 2nd attempts. Therefore I know it has nothin to do with COM port selection. It is almost as if it needs one attempt to wake up something (hardware or software I am not sure).

The problem does not appear limited to Voyager as it will also happen with APJog (which I set to administrator mode) as well, therefore I think it is a problem with hardware-driver interaction and I have elected to post here rather than on the Voyager forum. 

Cheers

Henry


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

Peter Nagy
 

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://forum.starkeeper.it/t/new-problem-connecting-to-mach1gto-since-upgrading-windows-7-to-windows-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


Re: Keypad Upgrade for Using Mach2

Robert Berta
 
Edited

Terri Zittritsch You can run Sky Safari on Windows 10 platform.....I do. You have to first install a free program called XePlayer which creates an Android partition on your computer. After that you can run any Android app from your Windows platform. You need to install the PlayStore and any of your favorite Android aps also including an Android file reader so you can see the files you save, etc. The files you install are in the Android partition so can't be seen or read with a regular Windows file reader. I have Sky Safari Pro latest version and I connect to my AP 900 and AP 1100 mounts for control of the telescope mounts from SS. I also use it with a Celestron fork mount and an Ioptron MiniTower Pro for field use and public outreach. I have both a CP3 for the 900 and CP4 for the 1100.  Astro Physics still hasn't quite figured out the wireless on the CP4 (it suffers from drop outs) but with a SkyFi I can wirelessly control the mounts from my Windows 10 computer as well as a Samsung tablet and Samsung cell phone.  The latest SkyFi units are very robust and can be used a long way from the mount. The only thing missing on Sky Safari is that you can only park and unpark from Park 4....Sky Safari knows about that and plans to offer more park positions in the future. Not a big deal though.....I initialize with the hand control and than connect with Sky Safari.  I park in position 3 and restore from that due to the setup in my observing setup so don't use park 4.


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

Ray Gralak
 

Hi Henry,

Before connecting the driver open Windows Device Manager and find the COM port(s) that are present on your system. Then open the AP V2 Driver ASCOM Setup. The driver does not automatically discover which port the mount is using so you must select the proper COM port. Select each port and click "Check Port" until you locate the port. Then close the window. The driver should now connect

Also, do not run Voyager or any other ASCOM client as administrator. It should not be required to run any ASCOM client applications as administrator as that may cause a second instance of the driver to start if you also have another application connected.

If you still have problems with take notice of the COM port the driver is trying to connect with to make sure it matches the COM port the mount is connected to. If you are using a USB/serial converter sometimes they try to allocate a new COM port every time they run or after booting. If you have one that does that then try updating its device driver. If that doesn't help try a different USB/serial converter, or if you have a desktop get a serial port add in card.

-Ray Gralak
Author of APCC (Astro-Physics Command Center): https://www.astro-physics.com/apcc-pro
Author of PEMPro V3: https://www.ccdware.com
Author of Astro-Physics V2 ASCOM Driver: https://www.siriusimaging.com/apdriver

-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Henry Kwok
Sent: Saturday, March 14, 2020 12:51 PM
To: main@ap-gto.groups.io
Subject: [ap-gto] GTO CP3 connection problem via COM port in Windows 10

Hi Ray (or anyone else who can help):

Since I have upgraded to Windows 10 (from Windows 7) I have a problem connecting to the mount via COM port
using ASCOM.
Basically the first attempt at connecting to the mount after a fresh boot up of the machine will always fail.
However, if I try again the second time it will work.

For example, I normally start APJog, then click connect. It will launch the mount ASCOM driver window, but it will
fail to detect the mount.
To solve the problem I will have to click connect again (which does nothing), then click disconnect (so to close the
mount driver window), then click connect again and then everything will work fine from there.

I have also tried to connect to the mount from Voyager - and I see the same problem (i.e. first attempt at connecting
to the mount after a fresh boot will fail).

This is a fatal issue, but more a nuisance.

I have noticed this problem since upgrading to Windows 10. Windows device manager does not report any error.

BTW, Voyager always run in administrator mode. I have set APJog to run as administrator as well, because if I
don't and try to run Voyager after APJog the mount will not connect.

Is there some setting I am missing?

Thanks


Re: Mach2

Terri Zittritsch
 

Hi Jerome, I like it very much.  Very solid.   I also purchased spikes for the feet as I wasn't sure how the swiveling foot pads will work.     Given I purchased the center extension, I probably didn't need the extendable legs.   Everything fits together nicely.  Comes with a nice case.


More AP900 Goodness - Caroline's Rose

Dean Jacobsen
 

I'm still restoring my Astrobin gallery after the loss of everyone's pictures.  Sometimes I find an old image that I think I can do better on now.

This is NGC 7789 aka Caroline's Rose from September 2018 with the FSQ-106 at f/5. 

https://www.astrobin.com/full/365581/C/

The low resolution images don't do this open cluster justice so this one has been posted as a 100% resolution image.  Click on the "Full resolution" button in the upper right corner.

I love the smattering of red giants in this one.

Equipment and exposure details are listed on the "Technical card" page.
--
Dean Jacobsen
http://astrophoto.net/wp/ 
Image Gallery - http://astrophoto.net/wp/image-gallery/
Astrobin - https://www.astrobin.com/users/deanjacobsen/ 


GTO CP3 connection problem via COM port in Windows 10

Henry Kwok
 

Hi Ray (or anyone else who can help):

Since I have upgraded to Windows 10 (from Windows 7) I have a problem connecting to the mount via COM port using ASCOM.
Basically the first attempt at connecting to the mount after a fresh boot up of the machine will always fail.
However, if I try again the second time it will work.

For example, I normally start APJog, then click connect. It will launch the mount ASCOM driver window, but it will fail to detect the mount.
To solve the problem I will have to click connect again (which does nothing), then click disconnect (so to close the mount driver window), then click connect again and then everything will work fine from there.

I have also tried to connect to the mount from Voyager - and I see the same problem (i.e. first attempt at connecting to the mount after a fresh boot will fail).

This is a fatal issue, but more a nuisance.

I have noticed this problem since upgrading to Windows 10. Windows device manager does not report any error.

BTW, Voyager always run in administrator mode. I have set APJog to run as administrator as well, because if I don't and try to run Voyager after APJog the mount will not connect.

Is there some setting I am missing?

Thanks


Re: Mach2

 

Nice!  I'm really looking forward to getting mine.  
Is that a T-Pod 130 tripod?  I've been thinking of eventually getting a 110.  How do you like it?  
Jerome


Re: Mach2

Cheng-Yang Tan
 

Very nice! My colleague received his as well. I’m sure I’ll get to see it in person very soon.

On Saturday, March 14, 2020, 12:59 PM, Harley Davidson <astrocnc@...> wrote:

Very nice!!!

tony

On 3/14/2020 1:08 PM, Terri Zittritsch wrote:


Re: Mach2

Harley Davidson
 

Very nice!!!

tony

On 3/14/2020 1:08 PM, Terri Zittritsch wrote:

I’ve gotten several personal messages asking me to post pictures.   Here you go:
https://drive.google.com/file/d/1yldIol7IwBtdcCPXYaQDLo21BOGmGIq1/view?usp=drivesdk

https://drive.google.com/file/d/15911KnglxkSsxn_Bguba9E1VCbesTxhd/view?usp=drivesdk

T



Re: Keypad Upgrade for Using Mach2

Wayne Hixson
 

A question I have is exactly where model corrections for guiding and pointing are applied? In the software or in the GTOCP5 itself?

Wayne


On Mar 14, 2020, at 9:43 AM, Dominique Durand via Groups.Io <dom33.durand@...> wrote:

Terri, And yes, almost everything can work together, current users make it a permanent experience and I am sure that the Mach2 encoder system makes this even more secure. It's good to already have the Mach2 manual ... I would like to already have this version even if it may not be the final one.Good continuation in your discovery of the extended possibilities of Mach2 and APCC-Pro.


Mach2

Terri Zittritsch
 

10721 - 10740 of 79702