APCC Pro Beta and AP V2 ASCOM Driver Beta with an alternative to Eltima Virtual Ports


Ray Gralak
 

Hello all,

 

For those with issues with the Eltima virtual ports, here is a beta version of APCC and the AP V2 ASCOM driver that does not use the Eltima virtual ports.

 

Besides installing the beta versions of APCC and driver, the only thing that should be required is to configure the driver to use APCC Pro 1.9.4.1’s REST API, as shown in this screenshot:

(BTW, enabling the “IP Addr” checkbox will show the “APCC REST API” checkbox)

APV2-550-ConfigureAPCC-Rest

Download links:

 

AP V2 ASCOM Driver v5.50.00 (Beta)

https://www.gralak.com/apdriver/AstroPhysics_V2_Setup_BETA_5.50.00.exe

 

APCC Pro v1.9.4.1 (Beta)

https://www.apastrosoftware.com/apcc_download/APCC_Pro_Setup_BETA_1.9.4.1.exe

 

BTW, this version of APCC Pro also addresses the problem with retrieving GPS information from the latest MGBoxV2 ASCOM driver.

 

If you see any issues, please report them here.

 

-Ray


midmoastro
 

Thanks Ray
Todd


ap@CaptivePhotons.com
 

Thought I would give this a test run (it's great that COM ports are going away!).

 

I installed both, and cannot connect.  When I start APCC it prompts for privilege use (from a net command); that is new, and I am always leery of accepting unexpected privilege use, so I said no.

 

If I say "no" APCC opens and connects to the mount, and when I connect from NINA to ASCOM then ASCOM opens but ASCOM fails to connect to APCC.

 

Is this because I didn't let it run with privilege?   Is that required now?

 

To be clear:

                APCC, Advanced, API, Enable ReST is set and 60001.

                Ascom Driver Settings, IP Addres checked, APCC REST API checked, 127.0.0.1:60001

 

The issue seems to be APCC as netstat says when ASCOM is open. There is no 60001 listening when Ascom is not open, I would expect one from APCC.

 

[AstroPhysicsV2 Driver.exe]

  TCP    192.168.135.2:139      0.0.0.0:0              LISTENING

 

Same behavior firewall (Defender) on or off, no other AV or similar programs running.  Windows 10 Pro x 64 10.0.19044.

 

So… have to run with privilege?

 

Linwood

 

 

 

From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of Ray Gralak via groups.io
Sent: Wednesday, February 16, 2022 4:18 AM
To: main@ap-gto.groups.io
Subject: [ap-gto] APCC Pro Beta and AP V2 ASCOM Driver Beta with an alternative to Eltima Virtual Ports

 

Hello all,

 

For those with issues with the Eltima virtual ports, here is a beta version of APCC and the AP V2 ASCOM driver that does not use the Eltima virtual ports.

 

Besides installing the beta versions of APCC and driver, the only thing that should be required is to configure the driver to use APCC Pro 1.9.4.1’s REST API, as shown in this screenshot:

(BTW, enabling the “IP Addr” checkbox will show the “APCC REST API” checkbox)

APV2-550-ConfigureAPCC-Rest

Download links:

 

AP V2 ASCOM Driver v5.50.00 (Beta)

https://www.gralak.com/apdriver/AstroPhysics_V2_Setup_BETA_5.50.00.exe

 

APCC Pro v1.9.4.1 (Beta)

https://www.apastrosoftware.com/apcc_download/APCC_Pro_Setup_BETA_1.9.4.1.exe

 

BTW, this version of APCC Pro also addresses the problem with retrieving GPS information from the latest MGBoxV2 ASCOM driver.

 

If you see any issues, please report them here.

 

-Ray


ap@CaptivePhotons.com
 

I realized after writing this that the UAC prompt would tell me the command, and it was harmless but was to create an ACL on the 60001 port, so I allowed it to run.  On subsequent APCC runs it does not prompt, so it appears it is necessary to run it once allowing privilege.

 

However, having done that, I still cannot connect to the mount.  I just tried this:

 

Started APCC (no priv prompt).

 

Ran Setup Telescope (i.e. ASCOM setup), it opens, and shows IP/REST as expected, but if I hit "Check Port" it says "Mount not found".  However at that moment if I do a netstat I do see not only the listener but communications established.

 

C:\Windows\system32>netstat -abn | find "60001"

  TCP    0.0.0.0:60001          0.0.0.0:0              LISTENING

  TCP    127.0.0.1:55895        127.0.0.1:60001        ESTABLISHED

  TCP    127.0.0.1:60001        127.0.0.1:55895        ESTABLISHED

  TCP    [::]:60001             [::]:0                 LISTENING

 

But the check port does not work -- this is with nothing else running but APCC (which is connected to the mount via IP) and the setup driver.

 

 

From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of ap@... via groups.io
Sent: Wednesday, February 16, 2022 1:01 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] APCC Pro Beta and AP V2 ASCOM Driver Beta with an alternative to Eltima Virtual Ports

 

Thought I would give this a test run (it's great that COM ports are going away!).

 

I installed both, and cannot connect.  When I start APCC it prompts for privilege use (from a net command); that is new, and I am always leery of accepting unexpected privilege use, so I said no.

 

If I say "no" APCC opens and connects to the mount, and when I connect from NINA to ASCOM then ASCOM opens but ASCOM fails to connect to APCC.

 

Is this because I didn't let it run with privilege?   Is that required now?

 

To be clear:

                APCC, Advanced, API, Enable ReST is set and 60001.

                Ascom Driver Settings, IP Addres checked, APCC REST API checked, 127.0.0.1:60001

 

The issue seems to be APCC as netstat says when ASCOM is open. There is no 60001 listening when Ascom is not open, I would expect one from APCC.

 

[AstroPhysicsV2 Driver.exe]

  TCP    192.168.135.2:139      0.0.0.0:0              LISTENING

 

Same behavior firewall (Defender) on or off, no other AV or similar programs running.  Windows 10 Pro x 64 10.0.19044.

 

So… have to run with privilege?

 

Linwood

 

 

 

From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of Ray Gralak via groups.io
Sent: Wednesday, February 16, 2022 4:18 AM
To: main@ap-gto.groups.io
Subject: [ap-gto] APCC Pro Beta and AP V2 ASCOM Driver Beta with an alternative to Eltima Virtual Ports

 

Hello all,

 

For those with issues with the Eltima virtual ports, here is a beta version of APCC and the AP V2 ASCOM driver that does not use the Eltima virtual ports.

 

Besides installing the beta versions of APCC and driver, the only thing that should be required is to configure the driver to use APCC Pro 1.9.4.1’s REST API, as shown in this screenshot:

(BTW, enabling the “IP Addr” checkbox will show the “APCC REST API” checkbox)

APV2-550-ConfigureAPCC-Rest

Download links:

 

AP V2 ASCOM Driver v5.50.00 (Beta)

https://www.gralak.com/apdriver/AstroPhysics_V2_Setup_BETA_5.50.00.exe

 

APCC Pro v1.9.4.1 (Beta)

https://www.apastrosoftware.com/apcc_download/APCC_Pro_Setup_BETA_1.9.4.1.exe

 

BTW, this version of APCC Pro also addresses the problem with retrieving GPS information from the latest MGBoxV2 ASCOM driver.

 

If you see any issues, please report them here.

 

-Ray


Larry Phillips
 

Ray, I just wanted to report success. I was limited on what I could do here on the rainy afternoon in Tucson, but I could successfully connect and reparked the mount to Park 3.  Win 10 computer upgraded to Win 11 via MS upgrade system.

Larry


Ray Gralak
 

In APCC's Advanced Settings, check if the REST API is enabled:

 

 

-Ray

 

> -----Original Message-----

> From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of ap@...

> Sent: Wednesday, February 16, 2022 10:22 AM

> To: main@ap-gto.groups.io

> Subject: Re: [ap-gto] APCC Pro Beta and AP V2 ASCOM Driver Beta with an alternative to Eltima Virtual Ports

>

> I realized after writing this that the UAC prompt would tell me the command, and it was harmless but was to

> create an ACL on the 60001 port, so I allowed it to run.  On subsequent APCC runs it does not prompt, so it

> appears it is necessary to run it once allowing privilege.

>

>

>

> However, having done that, I still cannot connect to the mount.  I just tried this:

>

>

>

> Started APCC (no priv prompt).

>

>

>

> Ran Setup Telescope (i.e. ASCOM setup), it opens, and shows IP/REST as expected, but if I hit "Check Port"

> it says "Mount not found".  However at that moment if I do a netstat I do see not only the listener but

> communications established.

>

>

>

> C:\Windows\system32>netstat -abn | find "60001"

>

>   TCP    0.0.0.0:60001          0.0.0.0:0              LISTENING

>

>   TCP    127.0.0.1:55895        127.0.0.1:60001        ESTABLISHED

>

>   TCP    127.0.0.1:60001        127.0.0.1:55895        ESTABLISHED

>

>   TCP    [::]:60001             [::]:0                 LISTENING

>

>

>

> But the check port does not work -- this is with nothing else running but APCC (which is connected to the

> mount via IP) and the setup driver.

>

>

>

>

>

>

>

> From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of ap@... via

> groups.io

> Sent: Wednesday, February 16, 2022 1:01 PM

> To: main@ap-gto.groups.io

> Subject: Re: [ap-gto] APCC Pro Beta and AP V2 ASCOM Driver Beta with an alternative to Eltima Virtual Ports

>

>

>

> Thought I would give this a test run (it's great that COM ports are going away!).

>

>

>

> I installed both, and cannot connect.  When I start APCC it prompts for privilege use (from a net command);

> that is new, and I am always leery of accepting unexpected privilege use, so I said no.

>

>

>

> If I say "no" APCC opens and connects to the mount, and when I connect from NINA to ASCOM then ASCOM

> opens but ASCOM fails to connect to APCC.

>

>

>

> Is this because I didn't let it run with privilege?   Is that required now?

>

>

>

> To be clear:

>

>                 APCC, Advanced, API, Enable ReST is set and 60001.

>

>                 Ascom Driver Settings, IP Addres checked, APCC REST API checked, 127.0.0.1:60001

>

>

>

> The issue seems to be APCC as netstat says when ASCOM is open. There is no 60001 listening when Ascom

> is not open, I would expect one from APCC.

>

>

>

> [AstroPhysicsV2 Driver.exe]

>

>   TCP    192.168.135.2:139      0.0.0.0:0              LISTENING

>

>

>

> Same behavior firewall (Defender) on or off, no other AV or similar programs running.  Windows 10 Pro x 64

> 10.0.19044.

>

>

>

> So… have to run with privilege?

>

>

>

> Linwood

>

>

>

>

>

>

>

> From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of Ray Gralak via groups.io

> Sent: Wednesday, February 16, 2022 4:18 AM

> To: main@ap-gto.groups.io

> Subject: [ap-gto] APCC Pro Beta and AP V2 ASCOM Driver Beta with an alternative to Eltima Virtual Ports

>

>

>

> Hello all,

>

>

>

> For those with issues with the Eltima virtual ports, here is a beta version of APCC and the AP V2 ASCOM

> driver that does not use the Eltima virtual ports.

>

>

>

> Besides installing the beta versions of APCC and driver, the only thing that should be required is to configure

> the driver to use APCC Pro 1.9.4.1’s REST API, as shown in this screenshot:

>

> (BTW, enabling the “IP Addr” checkbox will show the “APCC REST API” checkbox)

>

> APV2-550-ConfigureAPCC-Rest

>

> Download links:

>

>

>

> AP V2 ASCOM Driver v5.50.00 (Beta)

>

> https://www.gralak.com/apdriver/AstroPhysics_V2_Setup_BETA_5.50.00.exe

>

>

>

> APCC Pro v1.9.4.1 (Beta)

>

> https://www.apastrosoftware.com/apcc_download/APCC_Pro_Setup_BETA_1.9.4.1.exe

>

>

>

> BTW, this version of APCC Pro also addresses the problem with retrieving GPS information from the latest

> MGBoxV2 ASCOM driver.

>

>

>

> If you see any issues, please report them here.

>

>

>

> -Ray

>


ap@CaptivePhotons.com
 

Yes.  As mentioned below.  😊

 

And it opened the port, as netstat shows.


Though on mine there is a "Third party Applications" shown between Advanced Settings and API, and I have it set to NINA.

 

 

From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of Ray Gralak via groups.io
Sent: Wednesday, February 16, 2022 8:55 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] APCC Pro Beta and AP V2 ASCOM Driver Beta with an alternative to Eltima Virtual Ports

 

In APCC's Advanced Settings, check if the REST API is enabled:

 

 

-Ray

 

> -----Original Message-----

> From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of ap@...

> Sent: Wednesday, February 16, 2022 10:22 AM

> To: main@ap-gto.groups.io

> Subject: Re: [ap-gto] APCC Pro Beta and AP V2 ASCOM Driver Beta with an alternative to Eltima Virtual Ports

>

> I realized after writing this that the UAC prompt would tell me the command, and it was harmless but was to

> create an ACL on the 60001 port, so I allowed it to run.  On subsequent APCC runs it does not prompt, so it

> appears it is necessary to run it once allowing privilege.

>

>

>

> However, having done that, I still cannot connect to the mount.  I just tried this:

>

>

>

> Started APCC (no priv prompt).

>

>

>

> Ran Setup Telescope (i.e. ASCOM setup), it opens, and shows IP/REST as expected, but if I hit "Check Port"

> it says "Mount not found".  However at that moment if I do a netstat I do see not only the listener but

> communications established.

>

>

>

> C:\Windows\system32>netstat -abn | find "60001"

>

>   TCP    0.0.0.0:60001          0.0.0.0:0              LISTENING

>

>   TCP    127.0.0.1:55895        127.0.0.1:60001        ESTABLISHED

>

>   TCP    127.0.0.1:60001        127.0.0.1:55895        ESTABLISHED

>

>   TCP    [::]:60001             [::]:0                 LISTENING

>

>

>

> But the check port does not work -- this is with nothing else running but APCC (which is connected to the

> mount via IP) and the setup driver.

>

>

>

>

>

>

>

> From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of ap@... via

> groups.io

> Sent: Wednesday, February 16, 2022 1:01 PM

> To: main@ap-gto.groups.io

> Subject: Re: [ap-gto] APCC Pro Beta and AP V2 ASCOM Driver Beta with an alternative to Eltima Virtual Ports

>

>

>

> Thought I would give this a test run (it's great that COM ports are going away!).

>

>

>

> I installed both, and cannot connect.  When I start APCC it prompts for privilege use (from a net command);

> that is new, and I am always leery of accepting unexpected privilege use, so I said no.

>

>

>

> If I say "no" APCC opens and connects to the mount, and when I connect from NINA to ASCOM then ASCOM

> opens but ASCOM fails to connect to APCC.

>

>

>

> Is this because I didn't let it run with privilege?   Is that required now?

>

>

>

> To be clear:

>

>                 APCC, Advanced, API, Enable ReST is set and 60001.

>

>                 Ascom Driver Settings, IP Addres checked, APCC REST API checked, 127.0.0.1:60001

>

>

>

> The issue seems to be APCC as netstat says when ASCOM is open. There is no 60001 listening when Ascom

> is not open, I would expect one from APCC.

>

>

>

> [AstroPhysicsV2 Driver.exe]

>

>   TCP    192.168.135.2:139      0.0.0.0:0              LISTENING

>

>

>

> Same behavior firewall (Defender) on or off, no other AV or similar programs running.  Windows 10 Pro x 64

> 10.0.19044.

>

>

>

> So… have to run with privilege?

>

>

>

> Linwood

>

>

>

>

>

>

>

> From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of Ray Gralak via groups.io

> Sent: Wednesday, February 16, 2022 4:18 AM

> To: main@ap-gto.groups.io

> Subject: [ap-gto] APCC Pro Beta and AP V2 ASCOM Driver Beta with an alternative to Eltima Virtual Ports

>

>

>

> Hello all,

>

>

>

> For those with issues with the Eltima virtual ports, here is a beta version of APCC and the AP V2 ASCOM

> driver that does not use the Eltima virtual ports.

>

>

>

> Besides installing the beta versions of APCC and driver, the only thing that should be required is to configure

> the driver to use APCC Pro 1.9.4.1’s REST API, as shown in this screenshot:

>

> (BTW, enabling the “IP Addr” checkbox will show the “APCC REST API” checkbox)

>

> APV2-550-ConfigureAPCC-Rest

>

> Download links:

>

>

>

> AP V2 ASCOM Driver v5.50.00 (Beta)

>

> https://www.gralak.com/apdriver/AstroPhysics_V2_Setup_BETA_5.50.00.exe

>

>

>

> APCC Pro v1.9.4.1 (Beta)

>

> https://www.apastrosoftware.com/apcc_download/APCC_Pro_Setup_BETA_1.9.4.1.exe

>

>

>

> BTW, this version of APCC Pro also addresses the problem with retrieving GPS information from the latest

> MGBoxV2 ASCOM driver.

>

>

>

> If you see any issues, please report them here.

>

>

>

> -Ray

>


Ray Gralak
 

Unfortunately, the port was probably blocked by Windows when you denied the request for access.

 

-Ray

 

From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of ap@...
Sent: Wednesday, February 16, 2022 6:00 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] APCC Pro Beta and AP V2 ASCOM Driver Beta with an alternative to Eltima Virtual Ports

 

Yes.  As mentioned below.  😊

 

And it opened the port, as netstat shows.


Though on mine there is a "Third party Applications" shown between Advanced Settings and API, and I have it set to NINA.

 

 

From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of Ray Gralak via groups.io
Sent: Wednesday, February 16, 2022 8:55 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] APCC Pro Beta and AP V2 ASCOM Driver Beta with an alternative to Eltima Virtual Ports

 

In APCC's Advanced Settings, check if the REST API is enabled:

 

 

-Ray

 

> -----Original Message-----

> From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of ap@...

> Sent: Wednesday, February 16, 2022 10:22 AM

> To: main@ap-gto.groups.io

> Subject: Re: [ap-gto] APCC Pro Beta and AP V2 ASCOM Driver Beta with an alternative to Eltima Virtual Ports

>

> I realized after writing this that the UAC prompt would tell me the command, and it was harmless but was to

> create an ACL on the 60001 port, so I allowed it to run.  On subsequent APCC runs it does not prompt, so it

> appears it is necessary to run it once allowing privilege.

>

>

>

> However, having done that, I still cannot connect to the mount.  I just tried this:

>

>

>

> Started APCC (no priv prompt).

>

>

>

> Ran Setup Telescope (i.e. ASCOM setup), it opens, and shows IP/REST as expected, but if I hit "Check Port"

> it says "Mount not found".  However at that moment if I do a netstat I do see not only the listener but

> communications established.

>

>

>

> C:\Windows\system32>netstat -abn | find "60001"

>

>   TCP    0.0.0.0:60001          0.0.0.0:0              LISTENING

>

>   TCP    127.0.0.1:55895        127.0.0.1:60001        ESTABLISHED

>

>   TCP    127.0.0.1:60001        127.0.0.1:55895        ESTABLISHED

>

>   TCP    [::]:60001             [::]:0                 LISTENING

>

>

>

> But the check port does not work -- this is with nothing else running but APCC (which is connected to the

> mount via IP) and the setup driver.

>

>

>

>

>

>

>

> From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of ap@... via

> groups.io

> Sent: Wednesday, February 16, 2022 1:01 PM

> To: main@ap-gto.groups.io

> Subject: Re: [ap-gto] APCC Pro Beta and AP V2 ASCOM Driver Beta with an alternative to Eltima Virtual Ports

>

>

>

> Thought I would give this a test run (it's great that COM ports are going away!).

>

>

>

> I installed both, and cannot connect.  When I start APCC it prompts for privilege use (from a net command);

> that is new, and I am always leery of accepting unexpected privilege use, so I said no.

>

>

>

> If I say "no" APCC opens and connects to the mount, and when I connect from NINA to ASCOM then ASCOM

> opens but ASCOM fails to connect to APCC.

>

>

>

> Is this because I didn't let it run with privilege?   Is that required now?

>

>

>

> To be clear:

>

>                 APCC, Advanced, API, Enable ReST is set and 60001.

>

>                 Ascom Driver Settings, IP Addres checked, APCC REST API checked, 127.0.0.1:60001

>

>

>

> The issue seems to be APCC as netstat says when ASCOM is open. There is no 60001 listening when Ascom

> is not open, I would expect one from APCC.

>

>

>

> [AstroPhysicsV2 Driver.exe]

>

>   TCP    192.168.135.2:139      0.0.0.0:0              LISTENING

>

>

>

> Same behavior firewall (Defender) on or off, no other AV or similar programs running.  Windows 10 Pro x 64

> 10.0.19044.

>

>

>

> So… have to run with privilege?

>

>

>

> Linwood

>

>

>

>

>

>

>

> From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of Ray Gralak via groups.io

> Sent: Wednesday, February 16, 2022 4:18 AM

> To: main@ap-gto.groups.io

> Subject: [ap-gto] APCC Pro Beta and AP V2 ASCOM Driver Beta with an alternative to Eltima Virtual Ports

>

>

>

> Hello all,

>

>

>

> For those with issues with the Eltima virtual ports, here is a beta version of APCC and the AP V2 ASCOM

> driver that does not use the Eltima virtual ports.

>

>

>

> Besides installing the beta versions of APCC and driver, the only thing that should be required is to configure

> the driver to use APCC Pro 1.9.4.1’s REST API, as shown in this screenshot:

>

> (BTW, enabling the “IP Addr” checkbox will show the “APCC REST API” checkbox)

>

> APV2-550-ConfigureAPCC-Rest

>

> Download links:

>

>

>

> AP V2 ASCOM Driver v5.50.00 (Beta)

>

> https://www.gralak.com/apdriver/AstroPhysics_V2_Setup_BETA_5.50.00.exe

>

>

>

> APCC Pro v1.9.4.1 (Beta)

>

> https://www.apastrosoftware.com/apcc_download/APCC_Pro_Setup_BETA_1.9.4.1.exe

>

>

>

> BTW, this version of APCC Pro also addresses the problem with retrieving GPS information from the latest

> MGBoxV2 ASCOM driver.

>

>

>

> If you see any issues, please report them here.

>

>

>

> -Ray

>


ap@CaptivePhotons.com
 

I included (below) the netstat showing the port open and communications established.

 

Besides, it's a high port, I would not anticipate a permission problem accessing it.  But… it is open.

 

I can't do it right now as it is outside imaging, but should I remove/re-install or…. ?

 

 

From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of Ray Gralak via groups.io
Sent: Wednesday, February 16, 2022 9:04 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] APCC Pro Beta and AP V2 ASCOM Driver Beta with an alternative to Eltima Virtual Ports

 

Unfortunately, the port was probably blocked by Windows when you denied the request for access.

 

-Ray

 

From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of ap@...
Sent: Wednesday, February 16, 2022 6:00 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] APCC Pro Beta and AP V2 ASCOM Driver Beta with an alternative to Eltima Virtual Ports

 

Yes.  As mentioned below.  😊

 

And it opened the port, as netstat shows.


Though on mine there is a "Third party Applications" shown between Advanced Settings and API, and I have it set to NINA.

 

 

From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of Ray Gralak via groups.io
Sent: Wednesday, February 16, 2022 8:55 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] APCC Pro Beta and AP V2 ASCOM Driver Beta with an alternative to Eltima Virtual Ports

 

In APCC's Advanced Settings, check if the REST API is enabled:

 

 

-Ray

 

> -----Original Message-----

> From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of ap@...

> Sent: Wednesday, February 16, 2022 10:22 AM

> To: main@ap-gto.groups.io

> Subject: Re: [ap-gto] APCC Pro Beta and AP V2 ASCOM Driver Beta with an alternative to Eltima Virtual Ports

>

> I realized after writing this that the UAC prompt would tell me the command, and it was harmless but was to

> create an ACL on the 60001 port, so I allowed it to run.  On subsequent APCC runs it does not prompt, so it

> appears it is necessary to run it once allowing privilege.

>

>

>

> However, having done that, I still cannot connect to the mount.  I just tried this:

>

>

>

> Started APCC (no priv prompt).

>

>

>

> Ran Setup Telescope (i.e. ASCOM setup), it opens, and shows IP/REST as expected, but if I hit "Check Port"

> it says "Mount not found".  However at that moment if I do a netstat I do see not only the listener but

> communications established.

>

>

>

> C:\Windows\system32>netstat -abn | find "60001"

>

>   TCP    0.0.0.0:60001          0.0.0.0:0              LISTENING

>

>   TCP    127.0.0.1:55895        127.0.0.1:60001        ESTABLISHED

>

>   TCP    127.0.0.1:60001        127.0.0.1:55895        ESTABLISHED

>

>   TCP    [::]:60001             [::]:0                 LISTENING

>

>

>

> But the check port does not work -- this is with nothing else running but APCC (which is connected to the

> mount via IP) and the setup driver.

>

>

>

>

>

>

>

> From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of ap@... via

> groups.io

> Sent: Wednesday, February 16, 2022 1:01 PM

> To: main@ap-gto.groups.io

> Subject: Re: [ap-gto] APCC Pro Beta and AP V2 ASCOM Driver Beta with an alternative to Eltima Virtual Ports

>

>

>

> Thought I would give this a test run (it's great that COM ports are going away!).

>

>

>

> I installed both, and cannot connect.  When I start APCC it prompts for privilege use (from a net command);

> that is new, and I am always leery of accepting unexpected privilege use, so I said no.

>

>

>

> If I say "no" APCC opens and connects to the mount, and when I connect from NINA to ASCOM then ASCOM

> opens but ASCOM fails to connect to APCC.

>

>

>

> Is this because I didn't let it run with privilege?   Is that required now?

>

>

>

> To be clear:

>

>                 APCC, Advanced, API, Enable ReST is set and 60001.

>

>                 Ascom Driver Settings, IP Addres checked, APCC REST API checked, 127.0.0.1:60001

>

>

>

> The issue seems to be APCC as netstat says when ASCOM is open. There is no 60001 listening when Ascom

> is not open, I would expect one from APCC.

>

>

>

> [AstroPhysicsV2 Driver.exe]

>

>   TCP    192.168.135.2:139      0.0.0.0:0              LISTENING

>

>

>

> Same behavior firewall (Defender) on or off, no other AV or similar programs running.  Windows 10 Pro x 64

> 10.0.19044.

>

>

>

> So… have to run with privilege?

>

>

>

> Linwood

>

>

>

>

>

>

>

> From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of Ray Gralak via groups.io

> Sent: Wednesday, February 16, 2022 4:18 AM

> To: main@ap-gto.groups.io

> Subject: [ap-gto] APCC Pro Beta and AP V2 ASCOM Driver Beta with an alternative to Eltima Virtual Ports

>

>

>

> Hello all,

>

>

>

> For those with issues with the Eltima virtual ports, here is a beta version of APCC and the AP V2 ASCOM

> driver that does not use the Eltima virtual ports.

>

>

>

> Besides installing the beta versions of APCC and driver, the only thing that should be required is to configure

> the driver to use APCC Pro 1.9.4.1’s REST API, as shown in this screenshot:

>

> (BTW, enabling the “IP Addr” checkbox will show the “APCC REST API” checkbox)

>

> APV2-550-ConfigureAPCC-Rest

>

> Download links:

>

>

>

> AP V2 ASCOM Driver v5.50.00 (Beta)

>

> https://www.gralak.com/apdriver/AstroPhysics_V2_Setup_BETA_5.50.00.exe

>

>

>

> APCC Pro v1.9.4.1 (Beta)

>

> https://www.apastrosoftware.com/apcc_download/APCC_Pro_Setup_BETA_1.9.4.1.exe

>

>

>

> BTW, this version of APCC Pro also addresses the problem with retrieving GPS information from the latest

> MGBoxV2 ASCOM driver.

>

>

>

> If you see any issues, please report them here.

>

>

>

> -Ray

>


ap@CaptivePhotons.com
 

PS. After I figured out what the netsh request was, I did allow it, so that was done.

 

 

From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of ap@... via groups.io
Sent: Wednesday, February 16, 2022 9:07 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] APCC Pro Beta and AP V2 ASCOM Driver Beta with an alternative to Eltima Virtual Ports

 

I included (below) the netstat showing the port open and communications established.

 

Besides, it's a high port, I would not anticipate a permission problem accessing it.  But… it is open.

 

I can't do it right now as it is outside imaging, but should I remove/re-install or…. ?

 

 

From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of Ray Gralak via groups.io
Sent: Wednesday, February 16, 2022 9:04 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] APCC Pro Beta and AP V2 ASCOM Driver Beta with an alternative to Eltima Virtual Ports

 

Unfortunately, the port was probably blocked by Windows when you denied the request for access.

 

-Ray

 

From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of ap@...
Sent: Wednesday, February 16, 2022 6:00 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] APCC Pro Beta and AP V2 ASCOM Driver Beta with an alternative to Eltima Virtual Ports

 

Yes.  As mentioned below.  😊

 

And it opened the port, as netstat shows.


Though on mine there is a "Third party Applications" shown between Advanced Settings and API, and I have it set to NINA.

 

 

From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of Ray Gralak via groups.io
Sent: Wednesday, February 16, 2022 8:55 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] APCC Pro Beta and AP V2 ASCOM Driver Beta with an alternative to Eltima Virtual Ports

 

In APCC's Advanced Settings, check if the REST API is enabled:

 

 

-Ray

 

> -----Original Message-----

> From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of ap@...

> Sent: Wednesday, February 16, 2022 10:22 AM

> To: main@ap-gto.groups.io

> Subject: Re: [ap-gto] APCC Pro Beta and AP V2 ASCOM Driver Beta with an alternative to Eltima Virtual Ports

>

> I realized after writing this that the UAC prompt would tell me the command, and it was harmless but was to

> create an ACL on the 60001 port, so I allowed it to run.  On subsequent APCC runs it does not prompt, so it

> appears it is necessary to run it once allowing privilege.

>

>

>

> However, having done that, I still cannot connect to the mount.  I just tried this:

>

>

>

> Started APCC (no priv prompt).

>

>

>

> Ran Setup Telescope (i.e. ASCOM setup), it opens, and shows IP/REST as expected, but if I hit "Check Port"

> it says "Mount not found".  However at that moment if I do a netstat I do see not only the listener but

> communications established.

>

>

>

> C:\Windows\system32>netstat -abn | find "60001"

>

>   TCP    0.0.0.0:60001          0.0.0.0:0              LISTENING

>

>   TCP    127.0.0.1:55895        127.0.0.1:60001        ESTABLISHED

>

>   TCP    127.0.0.1:60001        127.0.0.1:55895        ESTABLISHED

>

>   TCP    [::]:60001             [::]:0                 LISTENING

>

>

>

> But the check port does not work -- this is with nothing else running but APCC (which is connected to the

> mount via IP) and the setup driver.

>

>

>

>

>

>

>

> From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of ap@... via

> groups.io

> Sent: Wednesday, February 16, 2022 1:01 PM

> To: main@ap-gto.groups.io

> Subject: Re: [ap-gto] APCC Pro Beta and AP V2 ASCOM Driver Beta with an alternative to Eltima Virtual Ports

>

>

>

> Thought I would give this a test run (it's great that COM ports are going away!).

>

>

>

> I installed both, and cannot connect.  When I start APCC it prompts for privilege use (from a net command);

> that is new, and I am always leery of accepting unexpected privilege use, so I said no.

>

>

>

> If I say "no" APCC opens and connects to the mount, and when I connect from NINA to ASCOM then ASCOM

> opens but ASCOM fails to connect to APCC.

>

>

>

> Is this because I didn't let it run with privilege?   Is that required now?

>

>

>

> To be clear:

>

>                 APCC, Advanced, API, Enable ReST is set and 60001.

>

>                 Ascom Driver Settings, IP Addres checked, APCC REST API checked, 127.0.0.1:60001

>

>

>

> The issue seems to be APCC as netstat says when ASCOM is open. There is no 60001 listening when Ascom

> is not open, I would expect one from APCC.

>

>

>

> [AstroPhysicsV2 Driver.exe]

>

>   TCP    192.168.135.2:139      0.0.0.0:0              LISTENING

>

>

>

> Same behavior firewall (Defender) on or off, no other AV or similar programs running.  Windows 10 Pro x 64

> 10.0.19044.

>

>

>

> So… have to run with privilege?

>

>

>

> Linwood

>

>

>

>

>

>

>

> From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of Ray Gralak via groups.io

> Sent: Wednesday, February 16, 2022 4:18 AM

> To: main@ap-gto.groups.io

> Subject: [ap-gto] APCC Pro Beta and AP V2 ASCOM Driver Beta with an alternative to Eltima Virtual Ports

>

>

>

> Hello all,

>

>

>

> For those with issues with the Eltima virtual ports, here is a beta version of APCC and the AP V2 ASCOM

> driver that does not use the Eltima virtual ports.

>

>

>

> Besides installing the beta versions of APCC and driver, the only thing that should be required is to configure

> the driver to use APCC Pro 1.9.4.1’s REST API, as shown in this screenshot:

>

> (BTW, enabling the “IP Addr” checkbox will show the “APCC REST API” checkbox)

>

> APV2-550-ConfigureAPCC-Rest

>

> Download links:

>

>

>

> AP V2 ASCOM Driver v5.50.00 (Beta)

>

> https://www.gralak.com/apdriver/AstroPhysics_V2_Setup_BETA_5.50.00.exe

>

>

>

> APCC Pro v1.9.4.1 (Beta)

>

> https://www.apastrosoftware.com/apcc_download/APCC_Pro_Setup_BETA_1.9.4.1.exe

>

>

>

> BTW, this version of APCC Pro also addresses the problem with retrieving GPS information from the latest

> MGBoxV2 ASCOM driver.

>

>

>

> If you see any issues, please report them here.

>

>

>

> -Ray

>


Ray Gralak
 

I’m confused… are you able to get the driver to communicate via REST?

 

-Ray

 

From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of ap@...
Sent: Wednesday, February 16, 2022 6:09 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] APCC Pro Beta and AP V2 ASCOM Driver Beta with an alternative to Eltima Virtual Ports

 

PS. After I figured out what the netsh request was, I did allow it, so that was done.

 

 

From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of ap@... via groups.io
Sent: Wednesday, February 16, 2022 9:07 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] APCC Pro Beta and AP V2 ASCOM Driver Beta with an alternative to Eltima Virtual Ports

 

I included (below) the netstat showing the port open and communications established.

 

Besides, it's a high port, I would not anticipate a permission problem accessing it.  But… it is open.

 

I can't do it right now as it is outside imaging, but should I remove/re-install or…. ?

 

 

From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of Ray Gralak via groups.io
Sent: Wednesday, February 16, 2022 9:04 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] APCC Pro Beta and AP V2 ASCOM Driver Beta with an alternative to Eltima Virtual Ports

 

Unfortunately, the port was probably blocked by Windows when you denied the request for access.

 

-Ray

 

From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of ap@...
Sent: Wednesday, February 16, 2022 6:00 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] APCC Pro Beta and AP V2 ASCOM Driver Beta with an alternative to Eltima Virtual Ports

 

Yes.  As mentioned below.  😊

 

And it opened the port, as netstat shows.


Though on mine there is a "Third party Applications" shown between Advanced Settings and API, and I have it set to NINA.

 

 

From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of Ray Gralak via groups.io
Sent: Wednesday, February 16, 2022 8:55 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] APCC Pro Beta and AP V2 ASCOM Driver Beta with an alternative to Eltima Virtual Ports

 

In APCC's Advanced Settings, check if the REST API is enabled:

 

 

-Ray

 

> -----Original Message-----

> From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of ap@...

> Sent: Wednesday, February 16, 2022 10:22 AM

> To: main@ap-gto.groups.io

> Subject: Re: [ap-gto] APCC Pro Beta and AP V2 ASCOM Driver Beta with an alternative to Eltima Virtual Ports

>

> I realized after writing this that the UAC prompt would tell me the command, and it was harmless but was to

> create an ACL on the 60001 port, so I allowed it to run.  On subsequent APCC runs it does not prompt, so it

> appears it is necessary to run it once allowing privilege.

>

>

>

> However, having done that, I still cannot connect to the mount.  I just tried this:

>

>

>

> Started APCC (no priv prompt).

>

>

>

> Ran Setup Telescope (i.e. ASCOM setup), it opens, and shows IP/REST as expected, but if I hit "Check Port"

> it says "Mount not found".  However at that moment if I do a netstat I do see not only the listener but

> communications established.

>

>

>

> C:\Windows\system32>netstat -abn | find "60001"

>

>   TCP    0.0.0.0:60001          0.0.0.0:0              LISTENING

>

>   TCP    127.0.0.1:55895        127.0.0.1:60001        ESTABLISHED

>

>   TCP    127.0.0.1:60001        127.0.0.1:55895        ESTABLISHED

>

>   TCP    [::]:60001             [::]:0                 LISTENING

>

>

>

> But the check port does not work -- this is with nothing else running but APCC (which is connected to the

> mount via IP) and the setup driver.

>

>

>

>

>

>

>

> From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of ap@... via

> groups.io

> Sent: Wednesday, February 16, 2022 1:01 PM

> To: main@ap-gto.groups.io

> Subject: Re: [ap-gto] APCC Pro Beta and AP V2 ASCOM Driver Beta with an alternative to Eltima Virtual Ports

>

>

>

> Thought I would give this a test run (it's great that COM ports are going away!).

>

>

>

> I installed both, and cannot connect.  When I start APCC it prompts for privilege use (from a net command);

> that is new, and I am always leery of accepting unexpected privilege use, so I said no.

>

>

>

> If I say "no" APCC opens and connects to the mount, and when I connect from NINA to ASCOM then ASCOM

> opens but ASCOM fails to connect to APCC.

>

>

>

> Is this because I didn't let it run with privilege?   Is that required now?

>

>

>

> To be clear:

>

>                 APCC, Advanced, API, Enable ReST is set and 60001.

>

>                 Ascom Driver Settings, IP Addres checked, APCC REST API checked, 127.0.0.1:60001

>

>

>

> The issue seems to be APCC as netstat says when ASCOM is open. There is no 60001 listening when Ascom

> is not open, I would expect one from APCC.

>

>

>

> [AstroPhysicsV2 Driver.exe]

>

>   TCP    192.168.135.2:139      0.0.0.0:0              LISTENING

>

>

>

> Same behavior firewall (Defender) on or off, no other AV or similar programs running.  Windows 10 Pro x 64

> 10.0.19044.

>

>

>

> So… have to run with privilege?

>

>

>

> Linwood

>

>

>

>

>

>

>

> From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of Ray Gralak via groups.io

> Sent: Wednesday, February 16, 2022 4:18 AM

> To: main@ap-gto.groups.io

> Subject: [ap-gto] APCC Pro Beta and AP V2 ASCOM Driver Beta with an alternative to Eltima Virtual Ports

>

>

>

> Hello all,

>

>

>

> For those with issues with the Eltima virtual ports, here is a beta version of APCC and the AP V2 ASCOM

> driver that does not use the Eltima virtual ports.

>

>

>

> Besides installing the beta versions of APCC and driver, the only thing that should be required is to configure

> the driver to use APCC Pro 1.9.4.1’s REST API, as shown in this screenshot:

>

> (BTW, enabling the “IP Addr” checkbox will show the “APCC REST API” checkbox)

>

> APV2-550-ConfigureAPCC-Rest

>

> Download links:

>

>

>

> AP V2 ASCOM Driver v5.50.00 (Beta)

>

> https://www.gralak.com/apdriver/AstroPhysics_V2_Setup_BETA_5.50.00.exe

>

>

>

> APCC Pro v1.9.4.1 (Beta)

>

> https://www.apastrosoftware.com/apcc_download/APCC_Pro_Setup_BETA_1.9.4.1.exe

>

>

>

> BTW, this version of APCC Pro also addresses the problem with retrieving GPS information from the latest

> MGBoxV2 ASCOM driver.

>

>

>

> If you see any issues, please report them here.

>

>

>

> -Ray

>


ap@CaptivePhotons.com
 

In terms of what the driver thinks it cannot see the mount.

 

But when it connects, I can see (via netstat -anb) that it has an established TCP connection to 127.0.0.1:60001, so at the TCP level it appears to connect.

 

The Check Port button fails (I sent that in a screen shot of both screens, APCC and ASCOM).

 

It is as though it can connect but doesn't like what it sees.  I can get a sniffer capture of it if that helps, a bit latter; I am trying to adjust out some tilt now and am almost there so do not want to interrupt it at the moment.   Waiting for a patch of clouds to pass.   (This is using COM ports again).

 

 

 

From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of Ray Gralak via groups.io
Sent: Wednesday, February 16, 2022 9:13 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] APCC Pro Beta and AP V2 ASCOM Driver Beta with an alternative to Eltima Virtual Ports

 

I’m confused… are you able to get the driver to communicate via REST?

 

-Ray

 

From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of ap@...
Sent: Wednesday, February 16, 2022 6:09 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] APCC Pro Beta and AP V2 ASCOM Driver Beta with an alternative to Eltima Virtual Ports

 

PS. After I figured out what the netsh request was, I did allow it, so that was done.

 

 

From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of ap@... via groups.io
Sent: Wednesday, February 16, 2022 9:07 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] APCC Pro Beta and AP V2 ASCOM Driver Beta with an alternative to Eltima Virtual Ports

 

I included (below) the netstat showing the port open and communications established.

 

Besides, it's a high port, I would not anticipate a permission problem accessing it.  But… it is open.

 

I can't do it right now as it is outside imaging, but should I remove/re-install or…. ?

 

 

From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of Ray Gralak via groups.io
Sent: Wednesday, February 16, 2022 9:04 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] APCC Pro Beta and AP V2 ASCOM Driver Beta with an alternative to Eltima Virtual Ports

 

Unfortunately, the port was probably blocked by Windows when you denied the request for access.

 

-Ray

 

From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of ap@...
Sent: Wednesday, February 16, 2022 6:00 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] APCC Pro Beta and AP V2 ASCOM Driver Beta with an alternative to Eltima Virtual Ports

 

Yes.  As mentioned below.  😊

 

And it opened the port, as netstat shows.


Though on mine there is a "Third party Applications" shown between Advanced Settings and API, and I have it set to NINA.

 

 

From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of Ray Gralak via groups.io
Sent: Wednesday, February 16, 2022 8:55 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] APCC Pro Beta and AP V2 ASCOM Driver Beta with an alternative to Eltima Virtual Ports

 

In APCC's Advanced Settings, check if the REST API is enabled:

 

 

-Ray

 

> -----Original Message-----

> From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of ap@...

> Sent: Wednesday, February 16, 2022 10:22 AM

> To: main@ap-gto.groups.io

> Subject: Re: [ap-gto] APCC Pro Beta and AP V2 ASCOM Driver Beta with an alternative to Eltima Virtual Ports

>

> I realized after writing this that the UAC prompt would tell me the command, and it was harmless but was to

> create an ACL on the 60001 port, so I allowed it to run.  On subsequent APCC runs it does not prompt, so it

> appears it is necessary to run it once allowing privilege.

>

>

>

> However, having done that, I still cannot connect to the mount.  I just tried this:

>

>

>

> Started APCC (no priv prompt).

>

>

>

> Ran Setup Telescope (i.e. ASCOM setup), it opens, and shows IP/REST as expected, but if I hit "Check Port"

> it says "Mount not found".  However at that moment if I do a netstat I do see not only the listener but

> communications established.

>

>

>

> C:\Windows\system32>netstat -abn | find "60001"

>

>   TCP    0.0.0.0:60001          0.0.0.0:0              LISTENING

>

>   TCP    127.0.0.1:55895        127.0.0.1:60001        ESTABLISHED

>

>   TCP    127.0.0.1:60001        127.0.0.1:55895        ESTABLISHED

>

>   TCP    [::]:60001             [::]:0                 LISTENING

>

>

>

> But the check port does not work -- this is with nothing else running but APCC (which is connected to the

> mount via IP) and the setup driver.

>

>

>

>

>

>

>

> From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of ap@... via

> groups.io

> Sent: Wednesday, February 16, 2022 1:01 PM

> To: main@ap-gto.groups.io

> Subject: Re: [ap-gto] APCC Pro Beta and AP V2 ASCOM Driver Beta with an alternative to Eltima Virtual Ports

>

>

>

> Thought I would give this a test run (it's great that COM ports are going away!).

>

>

>

> I installed both, and cannot connect.  When I start APCC it prompts for privilege use (from a net command);

> that is new, and I am always leery of accepting unexpected privilege use, so I said no.

>

>

>

> If I say "no" APCC opens and connects to the mount, and when I connect from NINA to ASCOM then ASCOM

> opens but ASCOM fails to connect to APCC.

>

>

>

> Is this because I didn't let it run with privilege?   Is that required now?

>

>

>

> To be clear:

>

>                 APCC, Advanced, API, Enable ReST is set and 60001.

>

>                 Ascom Driver Settings, IP Addres checked, APCC REST API checked, 127.0.0.1:60001

>

>

>

> The issue seems to be APCC as netstat says when ASCOM is open. There is no 60001 listening when Ascom

> is not open, I would expect one from APCC.

>

>

>

> [AstroPhysicsV2 Driver.exe]

>

>   TCP    192.168.135.2:139      0.0.0.0:0              LISTENING

>

>

>

> Same behavior firewall (Defender) on or off, no other AV or similar programs running.  Windows 10 Pro x 64

> 10.0.19044.

>

>

>

> So… have to run with privilege?

>

>

>

> Linwood

>

>

>

>

>

>

>

> From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of Ray Gralak via groups.io

> Sent: Wednesday, February 16, 2022 4:18 AM

> To: main@ap-gto.groups.io

> Subject: [ap-gto] APCC Pro Beta and AP V2 ASCOM Driver Beta with an alternative to Eltima Virtual Ports

>

>

>

> Hello all,

>

>

>

> For those with issues with the Eltima virtual ports, here is a beta version of APCC and the AP V2 ASCOM

> driver that does not use the Eltima virtual ports.

>

>

>

> Besides installing the beta versions of APCC and driver, the only thing that should be required is to configure

> the driver to use APCC Pro 1.9.4.1’s REST API, as shown in this screenshot:

>

> (BTW, enabling the “IP Addr” checkbox will show the “APCC REST API” checkbox)

>

> APV2-550-ConfigureAPCC-Rest

>

> Download links:

>

>

>

> AP V2 ASCOM Driver v5.50.00 (Beta)

>

> https://www.gralak.com/apdriver/AstroPhysics_V2_Setup_BETA_5.50.00.exe

>

>

>

> APCC Pro v1.9.4.1 (Beta)

>

> https://www.apastrosoftware.com/apcc_download/APCC_Pro_Setup_BETA_1.9.4.1.exe

>

>

>

> BTW, this version of APCC Pro also addresses the problem with retrieving GPS information from the latest

> MGBoxV2 ASCOM driver.

>

>

>

> If you see any issues, please report them here.

>

>

>

> -Ray

>


Ray Gralak
 

That port 60001 gets created does not mean that traffic can flow. You may have to change windows firewall settings, or an anti-virus software firewall rule.

 

-Ray

 

 

From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of ap@...
Sent: Wednesday, February 16, 2022 6:18 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] APCC Pro Beta and AP V2 ASCOM Driver Beta with an alternative to Eltima Virtual Ports

 

In terms of what the driver thinks it cannot see the mount.

 

But when it connects, I can see (via netstat -anb) that it has an established TCP connection to 127.0.0.1:60001, so at the TCP level it appears to connect.

 

The Check Port button fails (I sent that in a screen shot of both screens, APCC and ASCOM).

 

It is as though it can connect but doesn't like what it sees.  I can get a sniffer capture of it if that helps, a bit latter; I am trying to adjust out some tilt now and am almost there so do not want to interrupt it at the moment.   Waiting for a patch of clouds to pass.   (This is using COM ports again).

 

 

 

From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of Ray Gralak via groups.io
Sent: Wednesday, February 16, 2022 9:13 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] APCC Pro Beta and AP V2 ASCOM Driver Beta with an alternative to Eltima Virtual Ports

 

I’m confused… are you able to get the driver to communicate via REST?

 

-Ray

 

From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of ap@...
Sent: Wednesday, February 16, 2022 6:09 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] APCC Pro Beta and AP V2 ASCOM Driver Beta with an alternative to Eltima Virtual Ports

 

PS. After I figured out what the netsh request was, I did allow it, so that was done.

 

 

From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of ap@... via groups.io
Sent: Wednesday, February 16, 2022 9:07 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] APCC Pro Beta and AP V2 ASCOM Driver Beta with an alternative to Eltima Virtual Ports

 

I included (below) the netstat showing the port open and communications established.

 

Besides, it's a high port, I would not anticipate a permission problem accessing it.  But… it is open.

 

I can't do it right now as it is outside imaging, but should I remove/re-install or…. ?

 

 

From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of Ray Gralak via groups.io
Sent: Wednesday, February 16, 2022 9:04 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] APCC Pro Beta and AP V2 ASCOM Driver Beta with an alternative to Eltima Virtual Ports

 

Unfortunately, the port was probably blocked by Windows when you denied the request for access.

 

-Ray

 

From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of ap@...
Sent: Wednesday, February 16, 2022 6:00 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] APCC Pro Beta and AP V2 ASCOM Driver Beta with an alternative to Eltima Virtual Ports

 

Yes.  As mentioned below.  😊

 

And it opened the port, as netstat shows.


Though on mine there is a "Third party Applications" shown between Advanced Settings and API, and I have it set to NINA.

 

 

From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of Ray Gralak via groups.io
Sent: Wednesday, February 16, 2022 8:55 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] APCC Pro Beta and AP V2 ASCOM Driver Beta with an alternative to Eltima Virtual Ports

 

In APCC's Advanced Settings, check if the REST API is enabled:

 

 

-Ray

 

> -----Original Message-----

> From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of ap@...

> Sent: Wednesday, February 16, 2022 10:22 AM

> To: main@ap-gto.groups.io

> Subject: Re: [ap-gto] APCC Pro Beta and AP V2 ASCOM Driver Beta with an alternative to Eltima Virtual Ports

>

> I realized after writing this that the UAC prompt would tell me the command, and it was harmless but was to

> create an ACL on the 60001 port, so I allowed it to run.  On subsequent APCC runs it does not prompt, so it

> appears it is necessary to run it once allowing privilege.

>

>

>

> However, having done that, I still cannot connect to the mount.  I just tried this:

>

>

>

> Started APCC (no priv prompt).

>

>

>

> Ran Setup Telescope (i.e. ASCOM setup), it opens, and shows IP/REST as expected, but if I hit "Check Port"

> it says "Mount not found".  However at that moment if I do a netstat I do see not only the listener but

> communications established.

>

>

>

> C:\Windows\system32>netstat -abn | find "60001"

>

>   TCP    0.0.0.0:60001          0.0.0.0:0              LISTENING

>

>   TCP    127.0.0.1:55895        127.0.0.1:60001        ESTABLISHED

>

>   TCP    127.0.0.1:60001        127.0.0.1:55895        ESTABLISHED

>

>   TCP    [::]:60001             [::]:0                 LISTENING

>

>

>

> But the check port does not work -- this is with nothing else running but APCC (which is connected to the

> mount via IP) and the setup driver.

>

>

>

>

>

>

>

> From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of ap@... via

> groups.io

> Sent: Wednesday, February 16, 2022 1:01 PM

> To: main@ap-gto.groups.io

> Subject: Re: [ap-gto] APCC Pro Beta and AP V2 ASCOM Driver Beta with an alternative to Eltima Virtual Ports

>

>

>

> Thought I would give this a test run (it's great that COM ports are going away!).

>

>

>

> I installed both, and cannot connect.  When I start APCC it prompts for privilege use (from a net command);

> that is new, and I am always leery of accepting unexpected privilege use, so I said no.

>

>

>

> If I say "no" APCC opens and connects to the mount, and when I connect from NINA to ASCOM then ASCOM

> opens but ASCOM fails to connect to APCC.

>

>

>

> Is this because I didn't let it run with privilege?   Is that required now?

>

>

>

> To be clear:

>

>                 APCC, Advanced, API, Enable ReST is set and 60001.

>

>                 Ascom Driver Settings, IP Addres checked, APCC REST API checked, 127.0.0.1:60001

>

>

>

> The issue seems to be APCC as netstat says when ASCOM is open. There is no 60001 listening when Ascom

> is not open, I would expect one from APCC.

>

>

>

> [AstroPhysicsV2 Driver.exe]

>

>   TCP    192.168.135.2:139      0.0.0.0:0              LISTENING

>

>

>

> Same behavior firewall (Defender) on or off, no other AV or similar programs running.  Windows 10 Pro x 64

> 10.0.19044.

>

>

>

> So… have to run with privilege?

>

>

>

> Linwood

>

>

>

>

>

>

>

> From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of Ray Gralak via groups.io

> Sent: Wednesday, February 16, 2022 4:18 AM

> To: main@ap-gto.groups.io

> Subject: [ap-gto] APCC Pro Beta and AP V2 ASCOM Driver Beta with an alternative to Eltima Virtual Ports

>

>

>

> Hello all,

>

>

>

> For those with issues with the Eltima virtual ports, here is a beta version of APCC and the AP V2 ASCOM

> driver that does not use the Eltima virtual ports.

>

>

>

> Besides installing the beta versions of APCC and driver, the only thing that should be required is to configure

> the driver to use APCC Pro 1.9.4.1’s REST API, as shown in this screenshot:

>

> (BTW, enabling the “IP Addr” checkbox will show the “APCC REST API” checkbox)

>

> APV2-550-ConfigureAPCC-Rest

>

> Download links:

>

>

>

> AP V2 ASCOM Driver v5.50.00 (Beta)

>

> https://www.gralak.com/apdriver/AstroPhysics_V2_Setup_BETA_5.50.00.exe

>

>

>

> APCC Pro v1.9.4.1 (Beta)

>

> https://www.apastrosoftware.com/apcc_download/APCC_Pro_Setup_BETA_1.9.4.1.exe

>

>

>

> BTW, this version of APCC Pro also addresses the problem with retrieving GPS information from the latest

> MGBoxV2 ASCOM driver.

>

>

>

> If you see any issues, please report them here.

>

>

>

> -Ray

>


ap@CaptivePhotons.com
 

I wrote you already that I turned the firewall completely off and had the same behavior, as well as have no other AV software on the machine (nor any other security software).

 

A bit later I will set this all up again and send details again, they must have been lost in space somewhere.

 

More to follow.

 

Linwood

 

 

From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of Ray Gralak via groups.io
Sent: Wednesday, February 16, 2022 9:20 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] APCC Pro Beta and AP V2 ASCOM Driver Beta with an alternative to Eltima Virtual Ports

 

That port 60001 gets created does not mean that traffic can flow. You may have to change windows firewall settings, or an anti-virus software firewall rule.

 

-Ray

 

 

From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of ap@...
Sent: Wednesday, February 16, 2022 6:18 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] APCC Pro Beta and AP V2 ASCOM Driver Beta with an alternative to Eltima Virtual Ports

 

In terms of what the driver thinks it cannot see the mount.

 

But when it connects, I can see (via netstat -anb) that it has an established TCP connection to 127.0.0.1:60001, so at the TCP level it appears to connect.

 

The Check Port button fails (I sent that in a screen shot of both screens, APCC and ASCOM).

 

It is as though it can connect but doesn't like what it sees.  I can get a sniffer capture of it if that helps, a bit latter; I am trying to adjust out some tilt now and am almost there so do not want to interrupt it at the moment.   Waiting for a patch of clouds to pass.   (This is using COM ports again).

 

 

 

From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of Ray Gralak via groups.io
Sent: Wednesday, February 16, 2022 9:13 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] APCC Pro Beta and AP V2 ASCOM Driver Beta with an alternative to Eltima Virtual Ports

 

I’m confused… are you able to get the driver to communicate via REST?

 

-Ray

 

From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of ap@...
Sent: Wednesday, February 16, 2022 6:09 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] APCC Pro Beta and AP V2 ASCOM Driver Beta with an alternative to Eltima Virtual Ports

 

PS. After I figured out what the netsh request was, I did allow it, so that was done.

 

 

From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of ap@... via groups.io
Sent: Wednesday, February 16, 2022 9:07 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] APCC Pro Beta and AP V2 ASCOM Driver Beta with an alternative to Eltima Virtual Ports

 

I included (below) the netstat showing the port open and communications established.

 

Besides, it's a high port, I would not anticipate a permission problem accessing it.  But… it is open.

 

I can't do it right now as it is outside imaging, but should I remove/re-install or…. ?

 

 

From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of Ray Gralak via groups.io
Sent: Wednesday, February 16, 2022 9:04 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] APCC Pro Beta and AP V2 ASCOM Driver Beta with an alternative to Eltima Virtual Ports

 

Unfortunately, the port was probably blocked by Windows when you denied the request for access.

 

-Ray

 

From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of ap@...
Sent: Wednesday, February 16, 2022 6:00 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] APCC Pro Beta and AP V2 ASCOM Driver Beta with an alternative to Eltima Virtual Ports

 

Yes.  As mentioned below.  😊

 

And it opened the port, as netstat shows.


Though on mine there is a "Third party Applications" shown between Advanced Settings and API, and I have it set to NINA.

 

 

From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of Ray Gralak via groups.io
Sent: Wednesday, February 16, 2022 8:55 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] APCC Pro Beta and AP V2 ASCOM Driver Beta with an alternative to Eltima Virtual Ports

 

In APCC's Advanced Settings, check if the REST API is enabled:

 

 

-Ray

 

> -----Original Message-----

> From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of ap@...

> Sent: Wednesday, February 16, 2022 10:22 AM

> To: main@ap-gto.groups.io

> Subject: Re: [ap-gto] APCC Pro Beta and AP V2 ASCOM Driver Beta with an alternative to Eltima Virtual Ports

>

> I realized after writing this that the UAC prompt would tell me the command, and it was harmless but was to

> create an ACL on the 60001 port, so I allowed it to run.  On subsequent APCC runs it does not prompt, so it

> appears it is necessary to run it once allowing privilege.

>

>

>

> However, having done that, I still cannot connect to the mount.  I just tried this:

>

>

>

> Started APCC (no priv prompt).

>

>

>

> Ran Setup Telescope (i.e. ASCOM setup), it opens, and shows IP/REST as expected, but if I hit "Check Port"

> it says "Mount not found".  However at that moment if I do a netstat I do see not only the listener but

> communications established.

>

>

>

> C:\Windows\system32>netstat -abn | find "60001"

>

>   TCP    0.0.0.0:60001          0.0.0.0:0              LISTENING

>

>   TCP    127.0.0.1:55895        127.0.0.1:60001        ESTABLISHED

>

>   TCP    127.0.0.1:60001        127.0.0.1:55895        ESTABLISHED

>

>   TCP    [::]:60001             [::]:0                 LISTENING

>

>

>

> But the check port does not work -- this is with nothing else running but APCC (which is connected to the

> mount via IP) and the setup driver.

>

>

>

>

>

>

>

> From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of ap@... via

> groups.io

> Sent: Wednesday, February 16, 2022 1:01 PM

> To: main@ap-gto.groups.io

> Subject: Re: [ap-gto] APCC Pro Beta and AP V2 ASCOM Driver Beta with an alternative to Eltima Virtual Ports

>

>

>

> Thought I would give this a test run (it's great that COM ports are going away!).

>

>

>

> I installed both, and cannot connect.  When I start APCC it prompts for privilege use (from a net command);

> that is new, and I am always leery of accepting unexpected privilege use, so I said no.

>

>

>

> If I say "no" APCC opens and connects to the mount, and when I connect from NINA to ASCOM then ASCOM

> opens but ASCOM fails to connect to APCC.

>

>

>

> Is this because I didn't let it run with privilege?   Is that required now?

>

>

>

> To be clear:

>

>                 APCC, Advanced, API, Enable ReST is set and 60001.

>

>                 Ascom Driver Settings, IP Addres checked, APCC REST API checked, 127.0.0.1:60001

>

>

>

> The issue seems to be APCC as netstat says when ASCOM is open. There is no 60001 listening when Ascom

> is not open, I would expect one from APCC.

>

>

>

> [AstroPhysicsV2 Driver.exe]

>

>   TCP    192.168.135.2:139      0.0.0.0:0              LISTENING

>

>

>

> Same behavior firewall (Defender) on or off, no other AV or similar programs running.  Windows 10 Pro x 64

> 10.0.19044.

>

>

>

> So… have to run with privilege?

>

>

>

> Linwood

>

>

>

>

>

>

>

> From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of Ray Gralak via groups.io

> Sent: Wednesday, February 16, 2022 4:18 AM

> To: main@ap-gto.groups.io

> Subject: [ap-gto] APCC Pro Beta and AP V2 ASCOM Driver Beta with an alternative to Eltima Virtual Ports

>

>

>

> Hello all,

>

>

>

> For those with issues with the Eltima virtual ports, here is a beta version of APCC and the AP V2 ASCOM

> driver that does not use the Eltima virtual ports.

>

>

>

> Besides installing the beta versions of APCC and driver, the only thing that should be required is to configure

> the driver to use APCC Pro 1.9.4.1’s REST API, as shown in this screenshot:

>

> (BTW, enabling the “IP Addr” checkbox will show the “APCC REST API” checkbox)

>

> APV2-550-ConfigureAPCC-Rest

>

> Download links:

>

>

>

> AP V2 ASCOM Driver v5.50.00 (Beta)

>

> https://www.gralak.com/apdriver/AstroPhysics_V2_Setup_BETA_5.50.00.exe

>

>

>

> APCC Pro v1.9.4.1 (Beta)

>

> https://www.apastrosoftware.com/apcc_download/APCC_Pro_Setup_BETA_1.9.4.1.exe

>

>

>

> BTW, this version of APCC Pro also addresses the problem with retrieving GPS information from the latest

> MGBoxV2 ASCOM driver.

>

>

>

> If you see any issues, please report them here.

>

>

>

> -Ray

>


ap@CaptivePhotons.com
 
Edited

(Sorry, somehow this sent before i was ready). 

OK, fresh attempt.

Reboot.
Firewall off (Defender), no other AV or security software running.
Setup telescope (ASCOM setup): 
    IP Addr checked, REST API (auto checked), 127.0.0:60001
    OK (long pause, but no error)
Open APCC: 
   Go to virtual ports, delete Com 21
   Settings, Advanced, confirm API shows REST enabled, port 60001
   Just to be safe, exit APCC
Open APCC: 
   Run netstat and confirm port 60001 is in listening state (IPv4 and IPv6) 
Open ASCom setup: 
Open wireshark and capture for port 60001
Hit check port == says "mount not found" 
  
Wireshark shows: 

POST /api/mount/sendcmd HTTP/1.1

Connection: Keep-Alive

Content-Type: application/json; Charset=UTF-8

Accept: */*

User-Agent: Mozilla/4.0 (compatible; Win32; WinHttp.WinHttpRequest.5)

Content-Length: 20

Host: 127.0.0.1:60001

 

{ "Command": ":U#"}
HTTP/1.1 404 Not Found


There's a continual flow of these, with 404 errors coming from APCC to ASCOM.

The mount is connected to APCC via TCP and appears happy, sitting there parked, but I can control it fine as usual. 

I'm open to suggestions if I am doing something incorrectly, but they appear to be talking, just not happy with what they are saying to each other. 

Linwood


Ray Gralak
 

I am able to reproduce the problem. For some reason, the REST routes are gone after packaging APCC with the DLLs it uses. I haven't found the cause yet but people should still use the new APCC version to get GPS info from the latest MGBoxV2 server.

-Ray

-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of ap@...
Sent: Wednesday, February 16, 2022 7:19 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] APCC Pro Beta and AP V2 ASCOM Driver Beta with an alternative to Eltima Virtual Ports

[Edited Message Follows]

(Sorry, somehow this sent before i was ready).

OK, fresh attempt.



Reboot.
Firewall off (Defender), no other AV or security software running.
Setup telescope (ASCOM setup):
IP Addr checked, REST API (auto checked), 127.0.0:60001
OK (long pause, but no error)
Open APCC:
Go to virtual ports, delete Com 21
Settings, Advanced, confirm API shows REST enabled, port 60001
Just to be safe, exit APCC
Open APCC:
Run netstat and confirm port 60001 is in listening state (IPv4 and IPv6)
Open ASCom setup:
Open wireshark and capture for port 60001
Hit check port == says "mount not found"

Wireshark shows:



POST /api/mount/sendcmd HTTP/1.1

Connection: Keep-Alive

Content-Type: application/json; Charset=UTF-8

Accept: */*

User-Agent: Mozilla/4.0 (compatible; Win32; WinHttp.WinHttpRequest.5)

Content-Length: 20

Host: 127.0.0.1:60001



{ "Command": ":U#"}
HTTP/1.1 404 Not Found


There's a continual flow of these, with 404 errors coming from APCC to ASCOM.

The mount is connected to APCC via TCP and appears happy, sitting there parked, but I can control it fine as
usual.

I'm open to suggestions if I am doing something incorrectly, but they appear to be talking, just not happy with
what they are saying to each other.

Linwood




Ray Gralak
 

Here's and update which fixes the REST API endpoint issue in APCC. No changes were required to the driver:

APCC Pro v1.9.4.1 (Beta)
https://www.apastrosoftware.com/apcc_download/APCC_Pro_Setup_BETA_1.9.4.1a.exe

I also updated the original installer at the old link in case anyone downloads from that link before seeing this post.

-Ray


ap@CaptivePhotons.com
 

On Thu, Feb 17, 2022 at 02:21 AM, Ray Gralak wrote:
I am able to reproduce the problem. For some reason, the REST routes are gone after packaging APCC with the DLLs it uses. I haven't found the cause yet but people should still use the new APCC version to get GPS info from the latest MGBoxV2 server.
Thanks for hanging in there, I was starting to feel like Rod Serling was going to start talking soon.  :) 

I saw your subsequent note, and downloaded, I it now connects and sees the mount. 

Thank you. 

Linwood


Larry Phillips
 

Ray, should all of us who installed the previous beta which appears to work, also install this version?  Do we need to uninstall the previous beta?

Larry