Date   

Re: Looking for GPS Device Recommendations for APCC

Mike Dodd
 

On 2/17/2022 12:24 PM, Dale Ghent wrote:
Why would you need to query the GPS for location more than once?
It's lot like your lat/long is going to change after getting your initial location :D
That was my question, too. Why not use a handheld GPS unit (or car GPS in Pedestrian mode), or even your cell phone to get the coordinates?
Once that's done, you can have NMEATime2 have the run of it to keep the clock in sync.
Yup. I use Dimension 4, but there are several good programs to query an Internet time server.

--- Mike


Re: Looking for GPS Device Recommendations for APCC

Dale Ghent
 

Why would you need to query the GPS for location more than once?

For APCC, it's used once - to get a location and to make a new Site entry from. It's lot like your lat/long is going to change after getting your initial location :D

Once that's done, you can have NMEATime2 have the run of it to keep the clock in sync.

On Feb 17, 2022, at 12:20, ap@... <ap@...> wrote:

Unless I'm mistaken though you cannot use the GPS for time and for APCC as a com port at the same time, as it will only present one COM port and whatever software sets the time will tie it up (or vice versa for APCC).

Though for $12 each you could always use two.


Also note that depending on the physical arrangement, nearby computers or other EMI sources, shielding by metal of the mount from a sky view, etc. may prevent these from working in practice. Some people use a USB extension to separate them, or a USB device with an external antenna which you can move further away. You won't know until you try.

The best software I found for time sync was not free, it was NMEATime2. It tried hard to work around the USB limitations; precise time cannot be found on a USB device because of timing issues, it requires "1PPS" which is a hardware signal to more precisely synchronize the receipt of the text string with the time. This gets you really close though. Not that you need precise time for DSO and planetary, maybe for satellite chasing.

One problem with all this is coordinating lat/long changes with "sites" in both APCC and your favorite session manager software, which probably needs to be done semi-manually.

Linwood



Re: Looking for GPS Device Recommendations for APCC

ap@CaptivePhotons.com
 

Unless I'm mistaken though you cannot use the GPS for time and for APCC as a com port at the same time, as it will only present one COM port and whatever software sets the time will tie it up (or vice versa for APCC). 

Though for $12 each you could always use two. 

Also note that depending on the physical arrangement, nearby computers or other EMI sources, shielding by metal of the mount from a sky view, etc. may prevent these from working in practice.  Some people use a USB extension to separate them, or a USB device with an external antenna which you can move further away.  You won't know until  you try. 

The best software I found for time sync was not free, it was NMEATime2.  It tried hard to work around the USB limitations; precise time cannot be found on a USB device because of timing issues, it requires "1PPS" which is a hardware signal to more precisely synchronize the receipt of the text string with the time. This gets you really close though.  Not that you need precise time for DSO and planetary, maybe for satellite chasing. 

One problem with all this is coordinating lat/long changes with "sites" in both APCC and your favorite session manager software, which probably needs to be done semi-manually. 

Linwood


Re: Looking for GPS Device Recommendations for APCC

Dale Ghent
 

The $10-$15 white USB GNSS sticks based on the ublox chips seem to work well in my experience. They can operate in one of two modes - exposing themselves as a serial port that spews forth NMEA sentences at the prescribed 4800bps data rate or, with a driver, integrated as a sensor in Windows. For these purposes, you will want the former, which means the thing is basically plug and play.

APCC will fetch location from a locked GPS, but for time syncing purposes you will want an app such as NMEAtime2.

On Feb 17, 2022, at 11:56, Ben Koltenbah <benjamin.e.c.koltenbah@...> wrote:

Greetings!

I would like to get a Windows PC-connected GPS device that is accessible by APCC (both Standard and Pro). I have found some inexpensive choices on Amazon as well as more expensive options, but before ordering, I thought I'd ask here if there are some particular and well-proven recommendations that are well-suited for establishing time and location through APCC for my Mach1GTO and 1100GTO mounts as well as general Windows applications.

Thanks!

Best Regards,
Ben


Re: Looking for GPS Device Recommendations for APCC

 

Hi Ben

a lot of folks (including myself) use the MGBox V2, which includes GPS among many other instruments

it's a lot more than GPS but the other instruments (temperature, pressure, etc.) can all feed APCC as well, very handy


Brian


On Thu, Feb 17, 2022 at 8:56 AM Ben Koltenbah <benjamin.e.c.koltenbah@...> wrote:
Greetings!

I would like to get a Windows PC-connected GPS device that is accessible by APCC (both Standard and Pro).  I have found some inexpensive choices on Amazon as well as more expensive options, but before ordering, I thought I'd ask here if there are some particular and well-proven recommendations that are well-suited for establishing time and location through APCC for my Mach1GTO and 1100GTO mounts as well as general Windows applications.

Thanks!

Best Regards,
Ben



--
Brian 



Brian Valente


Looking for GPS Device Recommendations for APCC

Ben Koltenbah
 

Greetings!

I would like to get a Windows PC-connected GPS device that is accessible by APCC (both Standard and Pro).  I have found some inexpensive choices on Amazon as well as more expensive options, but before ordering, I thought I'd ask here if there are some particular and well-proven recommendations that are well-suited for establishing time and location through APCC for my Mach1GTO and 1100GTO mounts as well as general Windows applications.

Thanks!

Best Regards,
Ben


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

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


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

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


Re: [NINA] Astro-Physics Tools 0.4

alain.prette@...
 

Excellent work .. i'll test when i get my camera (dead) ..

Alain


Re: [NINA] Astro-Physics Tools 0.4

Ray Gralak
 

Thanks Dale, for your hard work on this!

-Ray

-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Dale Ghent
Sent: Wednesday, February 16, 2022 11:32 PM
To: main@ap-gto.groups.io
Subject: [ap-gto] [NINA] Astro-Physics Tools 0.4


Hi all,

After a bit of a holiday break, followed by a definitely not-boring time at the day job, I was finally able to
return to some coding and have a small (but perhaps big to some) update to my Astro-Physics Tools plugin
for NINA 2.0.

The major change with version 0.4.0.0 is in the way that the plugin's settings are saved. Instead of using the
traditional Windows app settings method, which left you with settings that were the same no matter which
NINA profile you were using, the plugin's settings are now saved in the active NINA profile itself. This will allow
you to have settings that are specific to each profile you might have. This is useful in case you use multiple
setups on your A-P mount(s) that are different enough that you might want some varying model creation
settings or whatnot. Your existing settings are converted into the profile-based storage automatically.

Another change is that my original plugin, Utilities for Astro-Physics Mounts, is now considered unsupported
and has been removed from the NINA plugin manager listing. Astro-Physics Tools is its replacement and will
continue to be developed. U4APM was a good first cut that proved out the idea of a sequencer integrating
with an external modeling app. With Ray's work bringing the API in 1.9 to fruition, U4APM is no longer needed
and I'll see it off in a viking funeral.

I've updated the plugin's documentation, including adding some diagrams that I hope will further explain how
declination arc are laid out. It may be found here: https://daleghent.com/astro-physics-tools

This release requires NINA 2.0 beta build 45. Full change log here: https://github.com/daleghent/nina-astro-
physics-tools/blob/main/CHANGELOG.md

/dale


[NINA] Astro-Physics Tools 0.4

Dale Ghent
 

Hi all,

After a bit of a holiday break, followed by a definitely not-boring time at the day job, I was finally able to return to some coding and have a small (but perhaps big to some) update to my Astro-Physics Tools plugin for NINA 2.0.

The major change with version 0.4.0.0 is in the way that the plugin's settings are saved. Instead of using the traditional Windows app settings method, which left you with settings that were the same no matter which NINA profile you were using, the plugin's settings are now saved in the active NINA profile itself. This will allow you to have settings that are specific to each profile you might have. This is useful in case you use multiple setups on your A-P mount(s) that are different enough that you might want some varying model creation settings or whatnot. Your existing settings are converted into the profile-based storage automatically.

Another change is that my original plugin, Utilities for Astro-Physics Mounts, is now considered unsupported and has been removed from the NINA plugin manager listing. Astro-Physics Tools is its replacement and will continue to be developed. U4APM was a good first cut that proved out the idea of a sequencer integrating with an external modeling app. With Ray's work bringing the API in 1.9 to fruition, U4APM is no longer needed and I'll see it off in a viking funeral.

I've updated the plugin's documentation, including adding some diagrams that I hope will further explain how declination arc are laid out. It may be found here: https://daleghent.com/astro-physics-tools

This release requires NINA 2.0 beta build 45. Full change log here: https://github.com/daleghent/nina-astro-physics-tools/blob/main/CHANGELOG.md

/dale


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

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




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

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


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

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

>


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

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

>


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

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

>


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

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

>


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

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

>


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

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

>


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

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

>

3921 - 3940 of 88912