Date   

locked Re: #APCC APCC/APPM blocking issue with AP1100GTOAE #APCC

 

Dale that's a good point, and relevant to other plate solvers as well

There are many choices of star databases out there to solve from. picking the right one that matches your fov is important

On Sat, Sep 26, 2020 at 11:12 AM Dale Ghent <daleg@...> wrote:

If one is using ASTAP with long focal length telescopes, there is this *very* important tidbit in the ASTAP documentation:

        • For telescope with a small field of view <20 arcmin you could download the installer G18 up to magnitude 18 or a zipped G18 star database for manual install. at the program directory c:\program files\astap.  Remove the G17 files or force use of the G18 in ASTAP. tab alignment.

Excuse the broken English but what it basically means is that you need the larger G18 database instead of the smaller G17 star database if you're operating at a tight FoV, on the order of 20 arc minutes or less. Despite being only 1 magnitudes of difference, the G18 database is almost twice the size of the default G17 database and weighs in around 1GB in size. This means more stars for ASTAP to make quads against given a small FoV. Obviously telescopes with wider FoVs will contain more brighter stars in their images which is why the G17 database is adequate enough for most.

/dale

> On Sep 26, 2020, at 2:02 PM, Brian Valente <bvalente@...> wrote:
>
> >>> If the image area is smaller, for example because of a longer focal length, it may be more of a challenge.
>
> we're at 0.63"/pix and APPM+pinpoint has worked great
>
> When we do a sky model with around 270 points, we might get <5 failed plate solves
>
>
>
> On Sat, Sep 26, 2020 at 10:04 AM Ray Gralak <groups3@...> wrote:
> > Voyager uses ASTAP natively and it works like a champ. APPM doesn't solve repetitively enough for me to be
> > concerned about it.
>
> I don't even understand what that means?
>
> APPM does not natively plate solve. It uses an external plate solver. It simply reads the RA/Dec and other values from the solver,
> or intermediary app.
>
> For plate-solving I typically use PinPoint and all-sky backup to Astrometry.Net. I've done many thousands of plate solves. Maybe
> even hundreds of thousands. Unless there is a tree, clouds, or something else obscuring the sky, plate solves have been extremely
> reliable at the image scale I typically use (around 1.6 arc-sec/pixel). That said, PinPoint can have problems in areas of the sky
> where there are too many stars in the selected database, typically around the milkyway.
>
> If the image area is smaller, for example because of a longer focal length, it may be more of a challenge.
>
> -Ray Gralak
> Author of PEMPro
> Author of APCC (Astro-Physics Command Center): https://www.astro-physics.com/apcc-pro
> Author of Astro-Physics V2 ASCOM Driver: https://www.siriusimaging.com/apdriver
>
>
> > -----Original Message-----
> > From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Bill Long
> > Sent: Saturday, September 26, 2020 9:48 AM
> > To: Ray Gralak; main@ap-gto.groups.io
> > Subject: Re: [ap-gto] #APCC APCC/APPM blocking issue with AP1100GTOAE
> >
> > Voyager uses ASTAP natively and it works like a champ. APPM doesn't solve repetitively enough for me to be
> > concerned about it.
> >
> > ________________________________
> >
> > From: main@ap-gto.groups.io <main@ap-gto.groups.io> on behalf of Ray Gralak <groups3@...>
> > Sent: Saturday, September 26, 2020 9:26 AM
> > To: main@ap-gto.groups.io <main@ap-gto.groups.io>
> > Subject: Re: [ap-gto] #APCC APCC/APPM blocking issue with AP1100GTOAE
> >
> > >  It could be as simple as the fact that APPM is doing a large number of plate solves in a short period of time.
> >
> > I hope that's not true because it might make ASTAP a poor choice for plate solving.
> >
> > -Ray Gralak
> > Author of PEMPro
> > Author of APCC (Astro-Physics Command Center):
> > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.astro-physics.com%2Fapcc-
> > pro&amp;data=02%7C01%7C%7C5d031ac0f6f64c67c2a908d86238f03c%7C84df9e7fe9f640afb435aaaaaaaaaaaa
> > %7C1%7C0%7C637367343966191971&amp;sdata=L5NWYJiNctTmuNFXvB37zZINb6CJ57eCgg7MyuWklfw%3D&
> > amp;reserved=0 <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.astro-
> > physics.com%2Fapcc-
> > pro&amp;data=02%7C01%7C%7C5d031ac0f6f64c67c2a908d86238f03c%7C84df9e7fe9f640afb435aaaaaaaaaaaa
> > %7C1%7C0%7C637367343966191971&amp;sdata=L5NWYJiNctTmuNFXvB37zZINb6CJ57eCgg7MyuWklfw%3D&
> > amp;reserved=0>
> > Author of Astro-Physics V2 ASCOM Driver:
> > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.siriusimaging.com%2Fapdriver&amp;d
> > ata=02%7C01%7C%7C5d031ac0f6f64c67c2a908d86238f03c%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0
> > %7C637367343966191971&amp;sdata=L0AH7Z1UH%2FJv8TKH4hHT4xKWMZHMWDSKLJQbgVhwQsg%3D&am
> > p;reserved=0
> > <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.siriusimaging.com%2Fapdriver&amp;
> > data=02%7C01%7C%7C5d031ac0f6f64c67c2a908d86238f03c%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C
> > 0%7C637367343966191971&amp;sdata=L0AH7Z1UH%2FJv8TKH4hHT4xKWMZHMWDSKLJQbgVhwQsg%3D&a
> > mp;reserved=0>
> >
> >
> > > -----Original Message-----
> > > From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of W Hilmo
> > > Sent: Saturday, September 26, 2020 8:50 AM
> > > To: main@ap-gto.groups.io
> > > Subject: Re: [ap-gto] #APCC APCC/APPM blocking issue with AP1100GTOAE
> > >
> > > I agree.
> > >
> > > I suspect that it's an ASTAP problem, but something that APPM is doing is exposing it.  It could be as simple as
> > the
> > > fact that APPM is doing a large number of plate solves in a short period of time.  As I mentioned, I've not had time
> > > to do any investigation at all yet.
> > >
> > > -----Original Message-----
> > > From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of Ray Gralak
> > > Sent: Friday, September 25, 2020 6:52 PM
> > > To: main@ap-gto.groups.io
> > > Subject: Re: [ap-gto] #APCC APCC/APPM blocking issue with AP1100GTOAE
> > >
> > > > I switched to ASTAP for my plate solves with SGP and am seeing what is
> > > > probably the same issue described in the first post of this thread.
> > >
> > > APPM doesn't know which plate solver is in use when SGPro is used for plate solving. APPM operates the same
> > > way for all SGPro plate solvers because APPM uses the SGPro API for plate solving. Since PlateSolve2 doesn't
> > > seem to show the same problem, it seems likely that the problem is with how SGPro handles ASTAP.
> > >
> > > -Ray Gralak
> > > Author of PEMPro
> > > Author of APCC (Astro-Physics Command Center):
> > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.astro-physics.com%2Fapcc-
> > pro&amp;data=02%7C01%7C%7C5d031ac0f6f64c67c2a908d86238f03c%7C84df9e7fe9f640afb435aaaaaaaaaaaa
> > %7C1%7C0%7C637367343966191971&amp;sdata=L5NWYJiNctTmuNFXvB37zZINb6CJ57eCgg7MyuWklfw%3D&
> > amp;reserved=0 <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.astro-
> > physics.com%2Fapcc-
> > pro&amp;data=02%7C01%7C%7C5d031ac0f6f64c67c2a908d86238f03c%7C84df9e7fe9f640afb435aaaaaaaaaaaa
> > %7C1%7C0%7C637367343966191971&amp;sdata=L5NWYJiNctTmuNFXvB37zZINb6CJ57eCgg7MyuWklfw%3D&
> > amp;reserved=0>
> > > Author of Astro-Physics V2 ASCOM Driver:
> > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.siriusimaging.com%2Fapdriver&amp;d
> > ata=02%7C01%7C%7C5d031ac0f6f64c67c2a908d86238f03c%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0
> > %7C637367343966191971&amp;sdata=L0AH7Z1UH%2FJv8TKH4hHT4xKWMZHMWDSKLJQbgVhwQsg%3D&am
> > p;reserved=0
> > <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.siriusimaging.com%2Fapdriver&amp;
> > data=02%7C01%7C%7C5d031ac0f6f64c67c2a908d86238f03c%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C
> > 0%7C637367343966191971&amp;sdata=L0AH7Z1UH%2FJv8TKH4hHT4xKWMZHMWDSKLJQbgVhwQsg%3D&a
> > mp;reserved=0>
> > >
> > > > -----Original Message-----
> > > > From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf
> > > > Of W Hilmo
> > > > Sent: Friday, September 25, 2020 9:29 AM
> > > > To: main@ap-gto.groups.io
> > > > Subject: Re: [ap-gto] #APCC APCC/APPM blocking issue with AP1100GTOAE
> > > >
> > > > I switched to ASTAP for my plate solves with SGP and am seeing what is
> > > > probably the same issue described in the first post of this thread.
> > > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> >
> >
> >
> >
> >
> >
> >
> >
> >
>
>
>
>
>
>
>
>
> --
> Brian
>
>
>
> Brian Valente
> portfolio brianvalentephotography.com
>








--
Brian 



Brian Valente


locked Re: #APCC APCC/APPM blocking issue with AP1100GTOAE #APCC

Dale Ghent
 

If one is using ASTAP with long focal length telescopes, there is this *very* important tidbit in the ASTAP documentation:

• For telescope with a small field of view <20 arcmin you could download the installer G18 up to magnitude 18 or a zipped G18 star database for manual install. at the program directory c:\program files\astap. Remove the G17 files or force use of the G18 in ASTAP. tab alignment.

Excuse the broken English but what it basically means is that you need the larger G18 database instead of the smaller G17 star database if you're operating at a tight FoV, on the order of 20 arc minutes or less. Despite being only 1 magnitudes of difference, the G18 database is almost twice the size of the default G17 database and weighs in around 1GB in size. This means more stars for ASTAP to make quads against given a small FoV. Obviously telescopes with wider FoVs will contain more brighter stars in their images which is why the G17 database is adequate enough for most.

/dale

On Sep 26, 2020, at 2:02 PM, Brian Valente <bvalente@gmail.com> wrote:

If the image area is smaller, for example because of a longer focal length, it may be more of a challenge.
we're at 0.63"/pix and APPM+pinpoint has worked great

When we do a sky model with around 270 points, we might get <5 failed plate solves



On Sat, Sep 26, 2020 at 10:04 AM Ray Gralak <groups3@gralak.com> wrote:
Voyager uses ASTAP natively and it works like a champ. APPM doesn't solve repetitively enough for me to be
concerned about it.
I don't even understand what that means?

APPM does not natively plate solve. It uses an external plate solver. It simply reads the RA/Dec and other values from the solver,
or intermediary app.

For plate-solving I typically use PinPoint and all-sky backup to Astrometry.Net. I've done many thousands of plate solves. Maybe
even hundreds of thousands. Unless there is a tree, clouds, or something else obscuring the sky, plate solves have been extremely
reliable at the image scale I typically use (around 1.6 arc-sec/pixel). That said, PinPoint can have problems in areas of the sky
where there are too many stars in the selected database, typically around the milkyway.

If the image area is smaller, for example because of a longer focal length, it may be more of a challenge.

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


-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Bill Long
Sent: Saturday, September 26, 2020 9:48 AM
To: Ray Gralak; main@ap-gto.groups.io
Subject: Re: [ap-gto] #APCC APCC/APPM blocking issue with AP1100GTOAE

Voyager uses ASTAP natively and it works like a champ. APPM doesn't solve repetitively enough for me to be
concerned about it.

________________________________

From: main@ap-gto.groups.io <main@ap-gto.groups.io> on behalf of Ray Gralak <groups3@gralak.com>
Sent: Saturday, September 26, 2020 9:26 AM
To: main@ap-gto.groups.io <main@ap-gto.groups.io>
Subject: Re: [ap-gto] #APCC APCC/APPM blocking issue with AP1100GTOAE

It could be as simple as the fact that APPM is doing a large number of plate solves in a short period of time.
I hope that's not true because it might make ASTAP a poor choice for plate solving.

-Ray Gralak
Author of PEMPro
Author of APCC (Astro-Physics Command Center):
https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.astro-physics.com%2Fapcc-
pro&amp;data=02%7C01%7C%7C5d031ac0f6f64c67c2a908d86238f03c%7C84df9e7fe9f640afb435aaaaaaaaaaaa
%7C1%7C0%7C637367343966191971&amp;sdata=L5NWYJiNctTmuNFXvB37zZINb6CJ57eCgg7MyuWklfw%3D&
amp;reserved=0 <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.astro-
physics.com%2Fapcc-
pro&amp;data=02%7C01%7C%7C5d031ac0f6f64c67c2a908d86238f03c%7C84df9e7fe9f640afb435aaaaaaaaaaaa
%7C1%7C0%7C637367343966191971&amp;sdata=L5NWYJiNctTmuNFXvB37zZINb6CJ57eCgg7MyuWklfw%3D&
amp;reserved=0>
Author of Astro-Physics V2 ASCOM Driver:
https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.siriusimaging.com%2Fapdriver&;d
ata=02%7C01%7C%7C5d031ac0f6f64c67c2a908d86238f03c%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0
%7C637367343966191971&amp;sdata=L0AH7Z1UH%2FJv8TKH4hHT4xKWMZHMWDSKLJQbgVhwQsg%3D&am
p;reserved=0
<https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.siriusimaging.com%2Fapdriver&;
data=02%7C01%7C%7C5d031ac0f6f64c67c2a908d86238f03c%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C
0%7C637367343966191971&amp;sdata=L0AH7Z1UH%2FJv8TKH4hHT4xKWMZHMWDSKLJQbgVhwQsg%3D&a
mp;reserved=0>


-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of W Hilmo
Sent: Saturday, September 26, 2020 8:50 AM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] #APCC APCC/APPM blocking issue with AP1100GTOAE

I agree.

I suspect that it's an ASTAP problem, but something that APPM is doing is exposing it. It could be as simple as
the
fact that APPM is doing a large number of plate solves in a short period of time. As I mentioned, I've not had time
to do any investigation at all yet.

-----Original Message-----
From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of Ray Gralak
Sent: Friday, September 25, 2020 6:52 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] #APCC APCC/APPM blocking issue with AP1100GTOAE

I switched to ASTAP for my plate solves with SGP and am seeing what is
probably the same issue described in the first post of this thread.
APPM doesn't know which plate solver is in use when SGPro is used for plate solving. APPM operates the same
way for all SGPro plate solvers because APPM uses the SGPro API for plate solving. Since PlateSolve2 doesn't
seem to show the same problem, it seems likely that the problem is with how SGPro handles ASTAP.

-Ray Gralak
Author of PEMPro
Author of APCC (Astro-Physics Command Center):
https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.astro-physics.com%2Fapcc-
pro&amp;data=02%7C01%7C%7C5d031ac0f6f64c67c2a908d86238f03c%7C84df9e7fe9f640afb435aaaaaaaaaaaa
%7C1%7C0%7C637367343966191971&amp;sdata=L5NWYJiNctTmuNFXvB37zZINb6CJ57eCgg7MyuWklfw%3D&
amp;reserved=0 <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.astro-
physics.com%2Fapcc-
pro&amp;data=02%7C01%7C%7C5d031ac0f6f64c67c2a908d86238f03c%7C84df9e7fe9f640afb435aaaaaaaaaaaa
%7C1%7C0%7C637367343966191971&amp;sdata=L5NWYJiNctTmuNFXvB37zZINb6CJ57eCgg7MyuWklfw%3D&
amp;reserved=0>
Author of Astro-Physics V2 ASCOM Driver:
https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.siriusimaging.com%2Fapdriver&;d
ata=02%7C01%7C%7C5d031ac0f6f64c67c2a908d86238f03c%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0
%7C637367343966191971&amp;sdata=L0AH7Z1UH%2FJv8TKH4hHT4xKWMZHMWDSKLJQbgVhwQsg%3D&am
p;reserved=0
<https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.siriusimaging.com%2Fapdriver&;
data=02%7C01%7C%7C5d031ac0f6f64c67c2a908d86238f03c%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C
0%7C637367343966191971&amp;sdata=L0AH7Z1UH%2FJv8TKH4hHT4xKWMZHMWDSKLJQbgVhwQsg%3D&a
mp;reserved=0>

-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf
Of W Hilmo
Sent: Friday, September 25, 2020 9:29 AM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] #APCC APCC/APPM blocking issue with AP1100GTOAE

I switched to ASTAP for my plate solves with SGP and am seeing what is
probably the same issue described in the first post of this thread.
























--
Brian



Brian Valente
portfolio brianvalentephotography.com


locked Re: #APCC APCC/APPM blocking issue with AP1100GTOAE #APCC

 

>>> If the image area is smaller, for example because of a longer focal length, it may be more of a challenge.

we're at 0.63"/pix and APPM+pinpoint has worked great

When we do a sky model with around 270 points, we might get <5 failed plate solves



On Sat, Sep 26, 2020 at 10:04 AM Ray Gralak <groups3@...> wrote:
> Voyager uses ASTAP natively and it works like a champ. APPM doesn't solve repetitively enough for me to be
> concerned about it.

I don't even understand what that means?

APPM does not natively plate solve. It uses an external plate solver. It simply reads the RA/Dec and other values from the solver,
or intermediary app.

For plate-solving I typically use PinPoint and all-sky backup to Astrometry.Net. I've done many thousands of plate solves. Maybe
even hundreds of thousands. Unless there is a tree, clouds, or something else obscuring the sky, plate solves have been extremely
reliable at the image scale I typically use (around 1.6 arc-sec/pixel). That said, PinPoint can have problems in areas of the sky
where there are too many stars in the selected database, typically around the milkyway.

If the image area is smaller, for example because of a longer focal length, it may be more of a challenge.

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


> -----Original Message-----
> From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Bill Long
> Sent: Saturday, September 26, 2020 9:48 AM
> To: Ray Gralak; main@ap-gto.groups.io
> Subject: Re: [ap-gto] #APCC APCC/APPM blocking issue with AP1100GTOAE
>
> Voyager uses ASTAP natively and it works like a champ. APPM doesn't solve repetitively enough for me to be
> concerned about it.
>
> ________________________________
>
> From: main@ap-gto.groups.io <main@ap-gto.groups.io> on behalf of Ray Gralak <groups3@...>
> Sent: Saturday, September 26, 2020 9:26 AM
> To: main@ap-gto.groups.io <main@ap-gto.groups.io>
> Subject: Re: [ap-gto] #APCC APCC/APPM blocking issue with AP1100GTOAE
>
> >  It could be as simple as the fact that APPM is doing a large number of plate solves in a short period of time.
>
> I hope that's not true because it might make ASTAP a poor choice for plate solving.
>
> -Ray Gralak
> Author of PEMPro
> Author of APCC (Astro-Physics Command Center):
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.astro-physics.com%2Fapcc-
> pro&amp;data=02%7C01%7C%7C5d031ac0f6f64c67c2a908d86238f03c%7C84df9e7fe9f640afb435aaaaaaaaaaaa
> %7C1%7C0%7C637367343966191971&amp;sdata=L5NWYJiNctTmuNFXvB37zZINb6CJ57eCgg7MyuWklfw%3D&
> amp;reserved=0 <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.astro-
> physics.com%2Fapcc-
> pro&amp;data=02%7C01%7C%7C5d031ac0f6f64c67c2a908d86238f03c%7C84df9e7fe9f640afb435aaaaaaaaaaaa
> %7C1%7C0%7C637367343966191971&amp;sdata=L5NWYJiNctTmuNFXvB37zZINb6CJ57eCgg7MyuWklfw%3D&
> amp;reserved=0>
> Author of Astro-Physics V2 ASCOM Driver:
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.siriusimaging.com%2Fapdriver&amp;d
> ata=02%7C01%7C%7C5d031ac0f6f64c67c2a908d86238f03c%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0
> %7C637367343966191971&amp;sdata=L0AH7Z1UH%2FJv8TKH4hHT4xKWMZHMWDSKLJQbgVhwQsg%3D&am
> p;reserved=0
> <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.siriusimaging.com%2Fapdriver&amp;
> data=02%7C01%7C%7C5d031ac0f6f64c67c2a908d86238f03c%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C
> 0%7C637367343966191971&amp;sdata=L0AH7Z1UH%2FJv8TKH4hHT4xKWMZHMWDSKLJQbgVhwQsg%3D&a
> mp;reserved=0>
>
>
> > -----Original Message-----
> > From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of W Hilmo
> > Sent: Saturday, September 26, 2020 8:50 AM
> > To: main@ap-gto.groups.io
> > Subject: Re: [ap-gto] #APCC APCC/APPM blocking issue with AP1100GTOAE
> >
> > I agree.
> >
> > I suspect that it's an ASTAP problem, but something that APPM is doing is exposing it.  It could be as simple as
> the
> > fact that APPM is doing a large number of plate solves in a short period of time.  As I mentioned, I've not had time
> > to do any investigation at all yet.
> >
> > -----Original Message-----
> > From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of Ray Gralak
> > Sent: Friday, September 25, 2020 6:52 PM
> > To: main@ap-gto.groups.io
> > Subject: Re: [ap-gto] #APCC APCC/APPM blocking issue with AP1100GTOAE
> >
> > > I switched to ASTAP for my plate solves with SGP and am seeing what is
> > > probably the same issue described in the first post of this thread.
> >
> > APPM doesn't know which plate solver is in use when SGPro is used for plate solving. APPM operates the same
> > way for all SGPro plate solvers because APPM uses the SGPro API for plate solving. Since PlateSolve2 doesn't
> > seem to show the same problem, it seems likely that the problem is with how SGPro handles ASTAP.
> >
> > -Ray Gralak
> > Author of PEMPro
> > Author of APCC (Astro-Physics Command Center):
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.astro-physics.com%2Fapcc-
> pro&amp;data=02%7C01%7C%7C5d031ac0f6f64c67c2a908d86238f03c%7C84df9e7fe9f640afb435aaaaaaaaaaaa
> %7C1%7C0%7C637367343966191971&amp;sdata=L5NWYJiNctTmuNFXvB37zZINb6CJ57eCgg7MyuWklfw%3D&
> amp;reserved=0 <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.astro-
> physics.com%2Fapcc-
> pro&amp;data=02%7C01%7C%7C5d031ac0f6f64c67c2a908d86238f03c%7C84df9e7fe9f640afb435aaaaaaaaaaaa
> %7C1%7C0%7C637367343966191971&amp;sdata=L5NWYJiNctTmuNFXvB37zZINb6CJ57eCgg7MyuWklfw%3D&
> amp;reserved=0>
> > Author of Astro-Physics V2 ASCOM Driver:
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.siriusimaging.com%2Fapdriver&amp;d
> ata=02%7C01%7C%7C5d031ac0f6f64c67c2a908d86238f03c%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0
> %7C637367343966191971&amp;sdata=L0AH7Z1UH%2FJv8TKH4hHT4xKWMZHMWDSKLJQbgVhwQsg%3D&am
> p;reserved=0
> <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.siriusimaging.com%2Fapdriver&amp;
> data=02%7C01%7C%7C5d031ac0f6f64c67c2a908d86238f03c%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C
> 0%7C637367343966191971&amp;sdata=L0AH7Z1UH%2FJv8TKH4hHT4xKWMZHMWDSKLJQbgVhwQsg%3D&a
> mp;reserved=0>
> >
> > > -----Original Message-----
> > > From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf
> > > Of W Hilmo
> > > Sent: Friday, September 25, 2020 9:29 AM
> > > To: main@ap-gto.groups.io
> > > Subject: Re: [ap-gto] #APCC APCC/APPM blocking issue with AP1100GTOAE
> > >
> > > I switched to ASTAP for my plate solves with SGP and am seeing what is
> > > probably the same issue described in the first post of this thread.
> > >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
>
>
>
>
>
>
>
>
>








--
Brian 



Brian Valente


locked Re: #APCC APCC/APPM blocking issue with AP1100GTOAE #APCC

Bill Long
 

I never said APPM natively solves. I was saying it doesn't need to solve frequently enough for me to be concerned about ASTAP.


From: main@ap-gto.groups.io <main@ap-gto.groups.io> on behalf of Ray Gralak <groups3@...>
Sent: Saturday, September 26, 2020 10:04 AM
To: main@ap-gto.groups.io <main@ap-gto.groups.io>
Subject: Re: [ap-gto] #APCC APCC/APPM blocking issue with AP1100GTOAE
 
> Voyager uses ASTAP natively and it works like a champ. APPM doesn't solve repetitively enough for me to be
> concerned about it.

I don't even understand what that means?

APPM does not natively plate solve. It uses an external plate solver. It simply reads the RA/Dec and other values from the solver,
or intermediary app.

For plate-solving I typically use PinPoint and all-sky backup to Astrometry.Net. I've done many thousands of plate solves. Maybe
even hundreds of thousands. Unless there is a tree, clouds, or something else obscuring the sky, plate solves have been extremely
reliable at the image scale I typically use (around 1.6 arc-sec/pixel). That said, PinPoint can have problems in areas of the sky
where there are too many stars in the selected database, typically around the milkyway.

If the image area is smaller, for example because of a longer focal length, it may be more of a challenge.

-Ray Gralak
Author of PEMPro
Author of APCC (Astro-Physics Command Center): https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.astro-physics.com%2Fapcc-pro&amp;data=02%7C01%7C%7Cfd6b7446b6dc43767ff008d8623e4d81%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637367367004625483&amp;sdata=EKSA7MUuJDqcoDekyEMjE8INqIh5GVSoZwH0hSPz9lE%3D&amp;reserved=0
Author of Astro-Physics V2 ASCOM Driver: https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.siriusimaging.com%2Fapdriver&amp;data=02%7C01%7C%7Cfd6b7446b6dc43767ff008d8623e4d81%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637367367004625483&amp;sdata=o5MMFwdXea6TScC7O0BQ3kwCw7E8tL17gFCDPSaO3oc%3D&amp;reserved=0


> -----Original Message-----
> From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Bill Long
> Sent: Saturday, September 26, 2020 9:48 AM
> To: Ray Gralak; main@ap-gto.groups.io
> Subject: Re: [ap-gto] #APCC APCC/APPM blocking issue with AP1100GTOAE
>
> Voyager uses ASTAP natively and it works like a champ. APPM doesn't solve repetitively enough for me to be
> concerned about it.
>
> ________________________________
>
> From: main@ap-gto.groups.io <main@ap-gto.groups.io> on behalf of Ray Gralak <groups3@...>
> Sent: Saturday, September 26, 2020 9:26 AM
> To: main@ap-gto.groups.io <main@ap-gto.groups.io>
> Subject: Re: [ap-gto] #APCC APCC/APPM blocking issue with AP1100GTOAE
>
> >  It could be as simple as the fact that APPM is doing a large number of plate solves in a short period of time.
>
> I hope that's not true because it might make ASTAP a poor choice for plate solving.
>
> -Ray Gralak
> Author of PEMPro
> Author of APCC (Astro-Physics Command Center):
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.astro-physics.com%2Fapcc-
> pro&amp;data=02%7C01%7C%7C5d031ac0f6f64c67c2a908d86238f03c%7C84df9e7fe9f640afb435aaaaaaaaaaaa
> %7C1%7C0%7C637367343966191971&amp;sdata=L5NWYJiNctTmuNFXvB37zZINb6CJ57eCgg7MyuWklfw%3D&
> amp;reserved=0 <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.astro-
> physics.com%2Fapcc-
> pro&amp;data=02%7C01%7C%7C5d031ac0f6f64c67c2a908d86238f03c%7C84df9e7fe9f640afb435aaaaaaaaaaaa
> %7C1%7C0%7C637367343966191971&amp;sdata=L5NWYJiNctTmuNFXvB37zZINb6CJ57eCgg7MyuWklfw%3D&
> amp;reserved=0>
> Author of Astro-Physics V2 ASCOM Driver:
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.siriusimaging.com%2Fapdriver&amp;d
> ata=02%7C01%7C%7C5d031ac0f6f64c67c2a908d86238f03c%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0
> %7C637367343966191971&amp;sdata=L0AH7Z1UH%2FJv8TKH4hHT4xKWMZHMWDSKLJQbgVhwQsg%3D&am
> p;reserved=0
> <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.siriusimaging.com%2Fapdriver&amp;
> data=02%7C01%7C%7C5d031ac0f6f64c67c2a908d86238f03c%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C
> 0%7C637367343966191971&amp;sdata=L0AH7Z1UH%2FJv8TKH4hHT4xKWMZHMWDSKLJQbgVhwQsg%3D&a
> mp;reserved=0>
>
>
> > -----Original Message-----
> > From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of W Hilmo
> > Sent: Saturday, September 26, 2020 8:50 AM
> > To: main@ap-gto.groups.io
> > Subject: Re: [ap-gto] #APCC APCC/APPM blocking issue with AP1100GTOAE
> >
> > I agree.
> >
> > I suspect that it's an ASTAP problem, but something that APPM is doing is exposing it.  It could be as simple as
> the
> > fact that APPM is doing a large number of plate solves in a short period of time.  As I mentioned, I've not had time
> > to do any investigation at all yet.
> >
> > -----Original Message-----
> > From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of Ray Gralak
> > Sent: Friday, September 25, 2020 6:52 PM
> > To: main@ap-gto.groups.io
> > Subject: Re: [ap-gto] #APCC APCC/APPM blocking issue with AP1100GTOAE
> >
> > > I switched to ASTAP for my plate solves with SGP and am seeing what is
> > > probably the same issue described in the first post of this thread.
> >
> > APPM doesn't know which plate solver is in use when SGPro is used for plate solving. APPM operates the same
> > way for all SGPro plate solvers because APPM uses the SGPro API for plate solving. Since PlateSolve2 doesn't
> > seem to show the same problem, it seems likely that the problem is with how SGPro handles ASTAP.
> >
> > -Ray Gralak
> > Author of PEMPro
> > Author of APCC (Astro-Physics Command Center):
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.astro-physics.com%2Fapcc-
> pro&amp;data=02%7C01%7C%7C5d031ac0f6f64c67c2a908d86238f03c%7C84df9e7fe9f640afb435aaaaaaaaaaaa
> %7C1%7C0%7C637367343966191971&amp;sdata=L5NWYJiNctTmuNFXvB37zZINb6CJ57eCgg7MyuWklfw%3D&
> amp;reserved=0 <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.astro-
> physics.com%2Fapcc-
> pro&amp;data=02%7C01%7C%7C5d031ac0f6f64c67c2a908d86238f03c%7C84df9e7fe9f640afb435aaaaaaaaaaaa
> %7C1%7C0%7C637367343966191971&amp;sdata=L5NWYJiNctTmuNFXvB37zZINb6CJ57eCgg7MyuWklfw%3D&
> amp;reserved=0>
> > Author of Astro-Physics V2 ASCOM Driver:
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.siriusimaging.com%2Fapdriver&amp;d
> ata=02%7C01%7C%7C5d031ac0f6f64c67c2a908d86238f03c%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0
> %7C637367343966191971&amp;sdata=L0AH7Z1UH%2FJv8TKH4hHT4xKWMZHMWDSKLJQbgVhwQsg%3D&am
> p;reserved=0
> <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.siriusimaging.com%2Fapdriver&amp;
> data=02%7C01%7C%7C5d031ac0f6f64c67c2a908d86238f03c%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C
> 0%7C637367343966191971&amp;sdata=L0AH7Z1UH%2FJv8TKH4hHT4xKWMZHMWDSKLJQbgVhwQsg%3D&a
> mp;reserved=0>
> >
> > > -----Original Message-----
> > > From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf
> > > Of W Hilmo
> > > Sent: Friday, September 25, 2020 9:29 AM
> > > To: main@ap-gto.groups.io
> > > Subject: Re: [ap-gto] #APCC APCC/APPM blocking issue with AP1100GTOAE
> > >
> > > I switched to ASTAP for my plate solves with SGP and am seeing what is
> > > probably the same issue described in the first post of this thread.
> > >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
>
>
>
>
>
>
>
>
>







locked Re: #APCC APCC/APPM blocking issue with AP1100GTOAE #APCC

Ray Gralak
 

Voyager uses ASTAP natively and it works like a champ. APPM doesn't solve repetitively enough for me to be
concerned about it.
I don't even understand what that means?

APPM does not natively plate solve. It uses an external plate solver. It simply reads the RA/Dec and other values from the solver,
or intermediary app.

For plate-solving I typically use PinPoint and all-sky backup to Astrometry.Net. I've done many thousands of plate solves. Maybe
even hundreds of thousands. Unless there is a tree, clouds, or something else obscuring the sky, plate solves have been extremely
reliable at the image scale I typically use (around 1.6 arc-sec/pixel). That said, PinPoint can have problems in areas of the sky
where there are too many stars in the selected database, typically around the milkyway.

If the image area is smaller, for example because of a longer focal length, it may be more of a challenge.

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


-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Bill Long
Sent: Saturday, September 26, 2020 9:48 AM
To: Ray Gralak; main@ap-gto.groups.io
Subject: Re: [ap-gto] #APCC APCC/APPM blocking issue with AP1100GTOAE

Voyager uses ASTAP natively and it works like a champ. APPM doesn't solve repetitively enough for me to be
concerned about it.

________________________________

From: main@ap-gto.groups.io <main@ap-gto.groups.io> on behalf of Ray Gralak <groups3@gralak.com>
Sent: Saturday, September 26, 2020 9:26 AM
To: main@ap-gto.groups.io <main@ap-gto.groups.io>
Subject: Re: [ap-gto] #APCC APCC/APPM blocking issue with AP1100GTOAE

It could be as simple as the fact that APPM is doing a large number of plate solves in a short period of time.
I hope that's not true because it might make ASTAP a poor choice for plate solving.

-Ray Gralak
Author of PEMPro
Author of APCC (Astro-Physics Command Center):
https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.astro-physics.com%2Fapcc-
pro&amp;data=02%7C01%7C%7C5d031ac0f6f64c67c2a908d86238f03c%7C84df9e7fe9f640afb435aaaaaaaaaaaa
%7C1%7C0%7C637367343966191971&amp;sdata=L5NWYJiNctTmuNFXvB37zZINb6CJ57eCgg7MyuWklfw%3D&
amp;reserved=0 <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.astro-
physics.com%2Fapcc-
pro&amp;data=02%7C01%7C%7C5d031ac0f6f64c67c2a908d86238f03c%7C84df9e7fe9f640afb435aaaaaaaaaaaa
%7C1%7C0%7C637367343966191971&amp;sdata=L5NWYJiNctTmuNFXvB37zZINb6CJ57eCgg7MyuWklfw%3D&
amp;reserved=0>
Author of Astro-Physics V2 ASCOM Driver:
https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.siriusimaging.com%2Fapdriver&;d
ata=02%7C01%7C%7C5d031ac0f6f64c67c2a908d86238f03c%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0
%7C637367343966191971&amp;sdata=L0AH7Z1UH%2FJv8TKH4hHT4xKWMZHMWDSKLJQbgVhwQsg%3D&am
p;reserved=0
<https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.siriusimaging.com%2Fapdriver&;
data=02%7C01%7C%7C5d031ac0f6f64c67c2a908d86238f03c%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C
0%7C637367343966191971&amp;sdata=L0AH7Z1UH%2FJv8TKH4hHT4xKWMZHMWDSKLJQbgVhwQsg%3D&a
mp;reserved=0>


-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of W Hilmo
Sent: Saturday, September 26, 2020 8:50 AM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] #APCC APCC/APPM blocking issue with AP1100GTOAE

I agree.

I suspect that it's an ASTAP problem, but something that APPM is doing is exposing it. It could be as simple as
the
fact that APPM is doing a large number of plate solves in a short period of time. As I mentioned, I've not had time
to do any investigation at all yet.

-----Original Message-----
From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of Ray Gralak
Sent: Friday, September 25, 2020 6:52 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] #APCC APCC/APPM blocking issue with AP1100GTOAE

I switched to ASTAP for my plate solves with SGP and am seeing what is
probably the same issue described in the first post of this thread.
APPM doesn't know which plate solver is in use when SGPro is used for plate solving. APPM operates the same
way for all SGPro plate solvers because APPM uses the SGPro API for plate solving. Since PlateSolve2 doesn't
seem to show the same problem, it seems likely that the problem is with how SGPro handles ASTAP.

-Ray Gralak
Author of PEMPro
Author of APCC (Astro-Physics Command Center):
https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.astro-physics.com%2Fapcc-
pro&amp;data=02%7C01%7C%7C5d031ac0f6f64c67c2a908d86238f03c%7C84df9e7fe9f640afb435aaaaaaaaaaaa
%7C1%7C0%7C637367343966191971&amp;sdata=L5NWYJiNctTmuNFXvB37zZINb6CJ57eCgg7MyuWklfw%3D&
amp;reserved=0 <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.astro-
physics.com%2Fapcc-
pro&amp;data=02%7C01%7C%7C5d031ac0f6f64c67c2a908d86238f03c%7C84df9e7fe9f640afb435aaaaaaaaaaaa
%7C1%7C0%7C637367343966191971&amp;sdata=L5NWYJiNctTmuNFXvB37zZINb6CJ57eCgg7MyuWklfw%3D&
amp;reserved=0>
Author of Astro-Physics V2 ASCOM Driver:
https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.siriusimaging.com%2Fapdriver&;d
ata=02%7C01%7C%7C5d031ac0f6f64c67c2a908d86238f03c%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0
%7C637367343966191971&amp;sdata=L0AH7Z1UH%2FJv8TKH4hHT4xKWMZHMWDSKLJQbgVhwQsg%3D&am
p;reserved=0
<https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.siriusimaging.com%2Fapdriver&;
data=02%7C01%7C%7C5d031ac0f6f64c67c2a908d86238f03c%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C
0%7C637367343966191971&amp;sdata=L0AH7Z1UH%2FJv8TKH4hHT4xKWMZHMWDSKLJQbgVhwQsg%3D&a
mp;reserved=0>

-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf
Of W Hilmo
Sent: Friday, September 25, 2020 9:29 AM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] #APCC APCC/APPM blocking issue with AP1100GTOAE

I switched to ASTAP for my plate solves with SGP and am seeing what is
probably the same issue described in the first post of this thread.


















locked Re: #APCC APCC/APPM blocking issue with AP1100GTOAE #APCC

Bill Long
 

Voyager uses ASTAP natively and it works like a champ. APPM doesn't solve repetitively enough for me to be concerned about it. 


From: main@ap-gto.groups.io <main@ap-gto.groups.io> on behalf of Ray Gralak <groups3@...>
Sent: Saturday, September 26, 2020 9:26 AM
To: main@ap-gto.groups.io <main@ap-gto.groups.io>
Subject: Re: [ap-gto] #APCC APCC/APPM blocking issue with AP1100GTOAE
 
>  It could be as simple as the fact that APPM is doing a large number of plate solves in a short period of time.

I hope that's not true because it might make ASTAP a poor choice for plate solving.

-Ray Gralak
Author of PEMPro
Author of APCC (Astro-Physics Command Center): https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.astro-physics.com%2Fapcc-pro&amp;data=02%7C01%7C%7C5d031ac0f6f64c67c2a908d86238f03c%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637367343966191971&amp;sdata=L5NWYJiNctTmuNFXvB37zZINb6CJ57eCgg7MyuWklfw%3D&amp;reserved=0
Author of Astro-Physics V2 ASCOM Driver: https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.siriusimaging.com%2Fapdriver&amp;data=02%7C01%7C%7C5d031ac0f6f64c67c2a908d86238f03c%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637367343966191971&amp;sdata=L0AH7Z1UH%2FJv8TKH4hHT4xKWMZHMWDSKLJQbgVhwQsg%3D&amp;reserved=0


> -----Original Message-----
> From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of W Hilmo
> Sent: Saturday, September 26, 2020 8:50 AM
> To: main@ap-gto.groups.io
> Subject: Re: [ap-gto] #APCC APCC/APPM blocking issue with AP1100GTOAE
>
> I agree.
>
> I suspect that it's an ASTAP problem, but something that APPM is doing is exposing it.  It could be as simple as the
> fact that APPM is doing a large number of plate solves in a short period of time.  As I mentioned, I've not had time
> to do any investigation at all yet.
>
> -----Original Message-----
> From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of Ray Gralak
> Sent: Friday, September 25, 2020 6:52 PM
> To: main@ap-gto.groups.io
> Subject: Re: [ap-gto] #APCC APCC/APPM blocking issue with AP1100GTOAE
>
> > I switched to ASTAP for my plate solves with SGP and am seeing what is
> > probably the same issue described in the first post of this thread.
>
> APPM doesn’t know which plate solver is in use when SGPro is used for plate solving. APPM operates the same
> way for all SGPro plate solvers because APPM uses the SGPro API for plate solving. Since PlateSolve2 doesn’t
> seem to show the same problem, it seems likely that the problem is with how SGPro handles ASTAP.
>
> -Ray Gralak
> Author of PEMPro
> Author of APCC (Astro-Physics Command Center): https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.astro-physics.com%2Fapcc-pro&amp;data=02%7C01%7C%7C5d031ac0f6f64c67c2a908d86238f03c%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637367343966191971&amp;sdata=L5NWYJiNctTmuNFXvB37zZINb6CJ57eCgg7MyuWklfw%3D&amp;reserved=0
> Author of Astro-Physics V2 ASCOM Driver: https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.siriusimaging.com%2Fapdriver&amp;data=02%7C01%7C%7C5d031ac0f6f64c67c2a908d86238f03c%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637367343966191971&amp;sdata=L0AH7Z1UH%2FJv8TKH4hHT4xKWMZHMWDSKLJQbgVhwQsg%3D&amp;reserved=0
>
> > -----Original Message-----
> > From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf
> > Of W Hilmo
> > Sent: Friday, September 25, 2020 9:29 AM
> > To: main@ap-gto.groups.io
> > Subject: Re: [ap-gto] #APCC APCC/APPM blocking issue with AP1100GTOAE
> >
> > I switched to ASTAP for my plate solves with SGP and am seeing what is
> > probably the same issue described in the first post of this thread.
> >
>
>
>
>
>
>
>
>
>
>
>
>








locked Re: #APCC APCC/APPM blocking issue with AP1100GTOAE #APCC

Ray Gralak
 

It could be as simple as the fact that APPM is doing a large number of plate solves in a short period of time.
I hope that's not true because it might make ASTAP a poor choice for plate solving.

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


-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of W Hilmo
Sent: Saturday, September 26, 2020 8:50 AM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] #APCC APCC/APPM blocking issue with AP1100GTOAE

I agree.

I suspect that it's an ASTAP problem, but something that APPM is doing is exposing it. It could be as simple as the
fact that APPM is doing a large number of plate solves in a short period of time. As I mentioned, I've not had time
to do any investigation at all yet.

-----Original Message-----
From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of Ray Gralak
Sent: Friday, September 25, 2020 6:52 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] #APCC APCC/APPM blocking issue with AP1100GTOAE

I switched to ASTAP for my plate solves with SGP and am seeing what is
probably the same issue described in the first post of this thread.
APPM doesn’t know which plate solver is in use when SGPro is used for plate solving. APPM operates the same
way for all SGPro plate solvers because APPM uses the SGPro API for plate solving. Since PlateSolve2 doesn’t
seem to show the same problem, it seems likely that the problem is with how SGPro handles ASTAP.

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

-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf
Of W Hilmo
Sent: Friday, September 25, 2020 9:29 AM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] #APCC APCC/APPM blocking issue with AP1100GTOAE

I switched to ASTAP for my plate solves with SGP and am seeing what is
probably the same issue described in the first post of this thread.











Re: APCC, ASTAp, SPG & Astrometry.net #APCC

Ray Gralak
 

Can a Plate Solve tool like ASTAP or Astrometry.net be of any use for increased pointing or tracking ability by itself
or in conjunction with APCC Standard?
You can use a plate solver with some external applications to do run-time local RECALs and recentering.

That is different from what APCC Pro does (pointing and tracking rate modeling).

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


-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of John A. Sillasen
Sent: Friday, September 25, 2020 9:39 PM
To: main@ap-gto.groups.io
Subject: [ap-gto] APCC, ASTAp, SPG & Astrometry.net #APCC

Strictly opinion gathering post. I've not used a Plate Solving tool, or an automation tool for that matter. I have APCC
Standard Edition since its initial release in fact. Can't say I've used it other that to see that it works.

Can a Plate Solve tool like ASTAP or Astrometry.net be of any use for increased pointing or tracking ability by itself
or in conjunction with APCC Standard?

As APPM is part of APCC Pro, is Plate Solving needed?

Better than wool gathering, I'm information and opinion gathering.

Thank you for your thoughts,

John Sillasen


Re: Cannot set new meridian delay

Ray Gralak
 

Steve,

The problem seems to start with Cartes du Ciel. I usually start (and finish) a session with SharpCap. The delay
input works fine with only SharpCap connected. Then I bring up CDC. That immediately causes the problem. The
only way to fix it seems to be the workarounds described above. So it isn't an urgent problem, and I'm not sure
where the problem actually is, but CDC seems to hose the input mechanism.
It's unlikely that there is anything in the AP V2 driver causing this. It is likely a problem with Cartes du Ciel not implementing rules of COM interop correctly. Both CDC and PHD2, which are both C++ applications, have been known to break one of the COM interop rules (only access the COM interop server on the same thread that the COM interop connection was created).

Applications written in .Net (like SGpro, PEMPro, etc.) do not have this issue because .Net automatically funnels all requests into the thread on which the COM interop object was created.

To solve the problem either the client application (CdC) needs to be fixed, or COM interop replaced with something else. For example, a new driver without using COM interop (non-ASCOM).

Unfortunately, ASCOM and Alpaca both have design flaws, so I am hoping that a new framework will be accepted in the future.

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

-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Steven Panish
Sent: Saturday, September 26, 2020 8:48 AM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] Cannot set new meridian delay

I've got a workaround! Sorry for the delay - unpleasant medical procedure. Not sure what a modal window is but
the other window open was the Cartes du Ciel Alpaca dialog box. Which may be relevant, see below.

It seems that either resetting the delay from the handbox (v2.17 I think) - or just bringing up that window - fixes it. I
did that with no apps open. Also after exiting all ASCOM control via applications, then bringing up PulseGuide and
setting a delay there makes the meridan delay numeric entry work thereafter when I bring up Sharpcap.

The problem seems to start with Cartes du Ciel. I usually start (and finish) a session with SharpCap. The delay
input works fine with only SharpCap connected. Then I bring up CDC. That immediately causes the problem. The
only way to fix it seems to be the workarounds described above. So it isn't an urgent problem, and I'm not sure
where the problem actually is, but CDC seems to hose the input mechanism.

Steve


On Thu, Sep 24, 2020 at 11:02 PM Ray Gralak <groups3@gralak.com> wrote:


Sorry, MODAL dialog box. There is no APCC involved.

That means no part of the main application will be responsive until you close the MODAL dialog box.

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


> -----Original Message-----
> From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Steven Panish
> Sent: Thursday, September 24, 2020 7:56 PM
> To: main@ap-gto.groups.io
> Subject: Re: [ap-gto] Cannot set new meridian delay
>
> Hi Ray,
>
> Thanks for the input. I'm not using APCC so there is no modeling dialog box open. I've tried both with and
without
> the plus sign, and zero, but nothing takes. It's stuck on 2. I'll try resetting from the handbox. This is the
first time
> I've used a meridian delay with the new driver, didn't have an issue with the older version. Don't remember
what
> that was, sorry. Otherwise, everything is working as far as I can tell. That was the delay I wanted and I
used it for a
> couple nights. I'll report back after trying to clear it with the handbox. I'd have done it the other night but
I've literally
> forgotten where that is in the handbox interface.
>
> Steve
>
> On Thu, Sep 24, 2020 at 9:32 AM Ray Gralak <groups3@gralak.com> wrote:
>
>
> Hi Steve,
>
>
>
> > But now I can't clear the +2 setting!
>
>
>
> Just to be clear, the driver does not accept a "+" before a number. The background of the control will
turn
> blue to indicate wrong input, and the "Set Meridian Delay" button will become disabled. Here is a
screenshot of this:
>
>
>
>
>
>
>
> If the problem is not the “+” sign, it also could be the mount is not responding or a model dialog box is
present
> somewhere that you need to dismiss.
>
>
>
> -Ray Gralak
>
> Author of PEMPro
>
> Author of APCC (Astro-Physics Command Center): https://www.astro-physics.com/apcc-pro
>
> Author of Astro-Physics V2 ASCOM Driver: https://www.siriusimaging.com/apdriver
>
>
>
> > -----Original Message-----
>
> > From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Steven Panish
>
> > Sent: Wednesday, September 23, 2020 7:14 PM
>
> > To: main@ap-gto.groups.io
>
> > Subject: [ap-gto] Cannot set new meridian delay
>
> >
>
> > Hi All,
>
> >
>
> > Using a 1200 with CP3, V2 chip, ASCOM V2 driver 5.30.10 with multiple apps running (SharpCap
does the
>
> > initialization, PHD2, Cartes du Ciel, Stellarium). A couple nights ago I set a +2 meridian delay using
the
> driver
>
> > interface. The delay works properly. But now I can't clear the +2 setting! The button to disable the
delay
> turns it off
>
> > as it should, but I want to enter a different delay and the interface won't take it, the +2 just stays
there.
> Same
>
> > behavior if the delay is enabled or disabled. I have not tried to use the handbox to reset it, but I want
to be
> able to
>
> > do it from the driver interface in any case. I looked (quickly) at the log and to my inexpert eye there
was no
>
> > command issued that looked like a time change or meridian delay.
>
> >
>
> > Has anyone seen this behavior and (I hope) made it go away?
>
> >
>
> > thanks,
>
> >
>
> > Steve
>
>
>
>
>
>
>
>









locked Re: #APCC APCC/APPM blocking issue with AP1100GTOAE #APCC

Eric Dreher
 

I agree completely.  I own SGP, but no longer use it, so I vote for autonomous use of ASTAP.


locked Re: #APCC APCC/APPM blocking issue with AP1100GTOAE #APCC

Bill Long
 

Would be great if APPM could skip SGP and just solve directly with ASTAP.


From: main@ap-gto.groups.io <main@ap-gto.groups.io> on behalf of W Hilmo <y.groups@...>
Sent: Saturday, September 26, 2020 8:50 AM
To: main@ap-gto.groups.io <main@ap-gto.groups.io>
Subject: Re: [ap-gto] #APCC APCC/APPM blocking issue with AP1100GTOAE
 
I agree.

I suspect that it's an ASTAP problem, but something that APPM is doing is exposing it.  It could be as simple as the fact that APPM is doing a large number of plate solves in a short period of time.  As I mentioned, I've not had time to do any investigation at all yet.

-----Original Message-----
From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of Ray Gralak
Sent: Friday, September 25, 2020 6:52 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] #APCC APCC/APPM blocking issue with AP1100GTOAE

> I switched to ASTAP for my plate solves with SGP and am seeing what is
> probably the same issue described in the first post of this thread.

APPM doesn’t know which plate solver is in use when SGPro is used for plate solving. APPM operates the same way for all SGPro plate solvers because APPM uses the SGPro API for plate solving. Since PlateSolve2 doesn’t seem to show the same problem, it seems likely that the problem is with how SGPro handles ASTAP.

-Ray Gralak
Author of PEMPro
Author of APCC (Astro-Physics Command Center): https://eur06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.astro-physics.com%2Fapcc-pro&amp;data=02%7C01%7C%7Cc0911257129c43bc474e08d86233f127%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637367322508133626&amp;sdata=fEmlNk9Az%2BuewiSGBmqcnyyTa%2BXxNnk%2FOf3DNNwJi0s%3D&amp;reserved=0
Author of Astro-Physics V2 ASCOM Driver: https://eur06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.siriusimaging.com%2Fapdriver&amp;data=02%7C01%7C%7Cc0911257129c43bc474e08d86233f127%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637367322508133626&amp;sdata=dCQL9p5E%2BX36633%2F%2BTTbYG380LKXz98P9zCpD4w4wl0%3D&amp;reserved=0

> -----Original Message-----
> From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf
> Of W Hilmo
> Sent: Friday, September 25, 2020 9:29 AM
> To: main@ap-gto.groups.io
> Subject: Re: [ap-gto] #APCC APCC/APPM blocking issue with AP1100GTOAE
>
> I switched to ASTAP for my plate solves with SGP and am seeing what is
> probably the same issue described in the first post of this thread.
>















locked Re: #APCC APCC/APPM blocking issue with AP1100GTOAE #APCC

W Hilmo
 

I agree.

I suspect that it's an ASTAP problem, but something that APPM is doing is exposing it. It could be as simple as the fact that APPM is doing a large number of plate solves in a short period of time. As I mentioned, I've not had time to do any investigation at all yet.

-----Original Message-----
From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of Ray Gralak
Sent: Friday, September 25, 2020 6:52 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] #APCC APCC/APPM blocking issue with AP1100GTOAE

I switched to ASTAP for my plate solves with SGP and am seeing what is
probably the same issue described in the first post of this thread.
APPM doesn’t know which plate solver is in use when SGPro is used for plate solving. APPM operates the same way for all SGPro plate solvers because APPM uses the SGPro API for plate solving. Since PlateSolve2 doesn’t seem to show the same problem, it seems likely that the problem is with how SGPro handles ASTAP.

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

-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf
Of W Hilmo
Sent: Friday, September 25, 2020 9:29 AM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] #APCC APCC/APPM blocking issue with AP1100GTOAE

I switched to ASTAP for my plate solves with SGP and am seeing what is
probably the same issue described in the first post of this thread.


Re: Cannot set new meridian delay

Steven Panish
 

I've got a workaround!  Sorry for the delay - unpleasant medical procedure.  Not sure what a modal window is but the other window open was the Cartes du Ciel Alpaca dialog box.  Which may be relevant, see below.

It seems that either resetting the delay from the handbox (v2.17 I think) - or just bringing up that window - fixes it.  I did that with no apps open.   Also after exiting all ASCOM control via applications, then bringing up PulseGuide and setting a delay there makes the meridan delay numeric entry work thereafter when I bring up Sharpcap.  

The problem seems to start with Cartes du Ciel.  I usually start (and finish) a session with SharpCap.  The delay input works fine with only SharpCap connected.  Then I bring up CDC.  That immediately causes the problem.  The only way to fix it seems to be the workarounds described above.  So it isn't an urgent problem, and I'm not sure where the problem actually is, but CDC seems to hose the input mechanism.

Steve


On Thu, Sep 24, 2020 at 11:02 PM Ray Gralak <groups3@...> wrote:
Sorry, MODAL dialog box. There is no APCC involved.

That means no part of the main application will be responsive until you close the MODAL dialog box.

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


> -----Original Message-----
> From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Steven Panish
> Sent: Thursday, September 24, 2020 7:56 PM
> To: main@ap-gto.groups.io
> Subject: Re: [ap-gto] Cannot set new meridian delay
>
> Hi Ray,
>
> Thanks for the input.  I'm not using APCC so there is no modeling dialog box open.  I've tried both with and without
> the  plus sign, and zero, but nothing takes.  It's stuck on 2.  I'll try resetting from the handbox.  This is the first time
> I've used a meridian delay with the new driver, didn't have an issue with the older version.  Don't remember what
> that was, sorry.  Otherwise, everything is working as far as I can tell.  That was the delay I wanted and I used it for a
> couple nights.  I'll report back after trying to clear it with the handbox.  I'd have done it the other night but I've literally
> forgotten where that is in the handbox interface.
>
> Steve
>
> On Thu, Sep 24, 2020 at 9:32 AM Ray Gralak <groups3@...> wrote:
>
>
>       Hi Steve,
>
>
>
>       > But now I can't clear the +2 setting!
>
>
>
>       Just to be clear, the driver does not accept a "+" before a number. The background of the control will turn
> blue to indicate wrong input, and the "Set Meridian Delay" button will become disabled. Here is a screenshot of this:
>
>
>
>
>
>
>
>       If the problem is not the “+” sign, it also could be the mount is not responding or a model dialog box is present
> somewhere that you need to dismiss.
>
>
>
>       -Ray Gralak
>
>       Author of PEMPro
>
>       Author of APCC (Astro-Physics Command Center): https://www.astro-physics.com/apcc-pro
>
>       Author of Astro-Physics V2 ASCOM Driver: https://www.siriusimaging.com/apdriver
>
>
>
>       > -----Original Message-----
>
>       > From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Steven Panish
>
>       > Sent: Wednesday, September 23, 2020 7:14 PM
>
>       > To: main@ap-gto.groups.io
>
>       > Subject: [ap-gto] Cannot set new meridian delay
>
>       >
>
>       > Hi All,
>
>       >
>
>       > Using a 1200 with CP3, V2 chip, ASCOM V2 driver 5.30.10 with multiple apps running (SharpCap does the
>
>       > initialization, PHD2, Cartes du Ciel, Stellarium).  A couple nights ago I set a +2 meridian delay using the
> driver
>
>       > interface.  The delay works properly.  But now I can't clear the +2 setting!  The button to disable the delay
> turns it off
>
>       > as it should, but I want to enter a different delay and the interface won't take it, the +2 just stays there.
> Same
>
>       > behavior if the delay is enabled or disabled.  I have not tried to use the handbox to reset it, but I want to be
> able to
>
>       > do it from the driver interface in any case.  I looked (quickly) at the log and to my inexpert eye there was no
>
>       > command issued that looked like a time change or meridian delay.
>
>       >
>
>       > Has anyone seen this behavior and (I hope) made it go away?
>
>       >
>
>       > thanks,
>
>       >
>
>       > Steve
>
>
>
>
>
>
>
>







Re: APCC, ASTAp, SPG & Astrometry.net #APCC

Worsel
 
Edited

John:

I have used plate solving for some time as a means to point the FOV precisely at the desired target.

Last year, I upgrade to APCC-Pro in order to implement pointing and tracking model with the goal of longer un-guided images.  APPC-Pro is required for building the models in APPM.  APPM does NOT execute actual plate solving; rather it relies on third party tools.

From the Overview section of APPM
----
APPM, or Astro-Physics Point Mapper, is a tool that collects data points across the sky of the telescope's actual pointing position versus the targeted slew position. The difference between the actual and targeted positions is the pointing error. By systematically capturing the pointing errors throughout a set of points in the sky a pointing (correction) and tracking rate (correction) models can be created.APPM can map points on both hemispheres (East and West) and also in counterweight up positions.

Note that the process of mapping points does not make APPM "modeling software". The modeling software component is in APCC Pro, which uses the pointing data to create the actual pointing and tracking rate models.
----

For details, see Section XIV in the APPC-Pro Help doc https://www.astro-physics.info/tech_support/software/apcc/apcc-pro.pdf


Re: APCC, ASTAp, SPG & Astrometry.net #APCC

KHursh
 

I do not have APCC Pro (yet), but I do use plate solving as part of my imaging suite. I use NINA and SG Pro and plate solving is used to accurately frame my image VERY quickly (in the case of ASTAP). Bottom line: it is a tool for pointing only. APCC and APPM are tools for tracking and use the plate solving tool to accurately tell the mount where it is in the sky.


APCC, ASTAp, SPG & Astrometry.net #APCC

John A. Sillasen
 

Strictly opinion gathering post.  I've not used a Plate Solving tool, or an automation tool for that matter. I have APCC Standard Edition since its  initial release in fact. Can't say I've used it other that to see that it works. 

Can a Plate Solve tool like ASTAP or Astrometry.net be of any use for increased pointing or tracking ability by itself or in conjunction with APCC Standard?

As APPM is part of APCC Pro, is Plate Solving needed?

Better than wool gathering,  I'm information and opinion gathering.

Thank you for your thoughts, 

John Sillasen 


locked Re: #APCC APCC/APPM blocking issue with AP1100GTOAE #APCC

Ray Gralak
 

I switched to ASTAP for my plate solves with SGP and am seeing what is probably the same issue described in the
first post of this thread.
APPM doesn’t know which plate solver is in use when SGPro is used for plate solving. APPM operates the same way for all SGPro plate solvers because APPM uses the SGPro API for plate solving. Since PlateSolve2 doesn’t seem to show the same problem, it seems likely that the problem is with how SGPro handles ASTAP.

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

-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of W Hilmo
Sent: Friday, September 25, 2020 9:29 AM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] #APCC APCC/APPM blocking issue with AP1100GTOAE

I switched to ASTAP for my plate solves with SGP and am seeing what is probably the same issue described in the
first post of this thread.


locked Re: #APCC APCC/APPM blocking issue with AP1100GTOAE #APCC

Worsel
 

On the APPM Measurement tab, there is a "Slew Settle Time".  The default is 3s.

Bryan


locked Re: #APCC APCC/APPM blocking issue with AP1100GTOAE #APCC

Bill Long
 

http://www.hnsky.org/astap.htm



From: main@ap-gto.groups.io <main@ap-gto.groups.io> on behalf of CurtisC via groups.io <calypte@...>
Sent: Friday, September 25, 2020 1:52 PM
To: main@ap-gto.groups.io <main@ap-gto.groups.io>
Subject: Re: [ap-gto] #APCC APCC/APPM blocking issue with AP1100GTOAE
 
I've probably missed a post.  What is ASTAP?


locked Re: #APCC APCC/APPM blocking issue with AP1100GTOAE #APCC

CurtisC
 

I've probably missed a post.  What is ASTAP?

10821 - 10840 of 84253