Hi Max,

3) Try collecting data for a model at a different time. : I am not sure what you mean on 3.

I meant, if it’s cloudy then try the mapping run another time when it’s less cloudy. :-) If the moon is out you may lose one or two points maximum, so it's really not that much of a factor. If the scope has a narrow field of view then the likelihood of a mapping point landing on the moon or very close to it is small.

If you doing a big model dense model it can take time especially with a slow dome. I get about 1 point per minute or less even when using the HA option.

A slow moving dome is problematic. Try increasing Dec spacing and reducing RA spacing. That might help improve speed in this case.

Is there a way cut and paste East and West models ?

No... and I would not advise trying that. It probably won't work well because it won't take into account the starting RA/Dec offsets of the initial reference plate solve.

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

From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Max Mirot via groups.io
Sent: Sunday, May 10, 2020 1:39 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] APPM feature requests

On Sun, May 10, 2020 at 11:15 AM, Ray Gralak wrote:
Hi Max,
1) Retry failed pointing image at the end of the APPM run.
Passing clouds and the Moon sometime affect more image than I like to see.
That's been on the "to do" list for some time, but A-P has to approve a new feature like this.
Paging Rolando . This is an easy call...
It has been low priority since the workarounds include:

1) Use the points you have.
2) Configure more points to start with to account for lost points.
3) Try collecting data for a model at a different time. : I am not sure what you mean on 3.
2)Someway to load prior pointing files.
You can do that already from APCC in the pointing model window.
3) Able to run and load East and West APPM indepentantly.
I would like to run east and west mapping on at another time or another night.
What's the use case? Usually you can plate solve 2-3 points per minute and start before it's dark enough to image. That should be enough for both pier sides.
If you doing a big model dense model it can take time especially with a slow dome. I get about 1 point per minute or less even when using the HA option.
A four point model will take all night.
I noticed that when I loaded the West model the East Values are preserved but there is no list or graph. Are East Values still active for pointing and tracking?
Is there a way cut and paste East and West models ?
Thanks
Max

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

-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Max Mirot via groups.io
Sent: Saturday, May 9, 2020 7:17 PM
To: main@ap-gto.groups.io
Subject: [ap-gto] APPM feature requests


I think these might be helpful to add.

1) Retry failed pointing image at the end of the APPM run.
Passing clouds and the Moon sometime affect more image than I like to see.

2)Someway to load prior pointing files.

3) Able to run and load East and West APPM indepentantly.
I would like to run east and west mapping on at another time or another night.

Thanks
Max

On Sun, May 10, 2020 at 11:15 AM, Ray Gralak wrote:

Hi Max,

1) Retry failed pointing image at the end of the APPM run.
Passing clouds and the Moon sometime affect more image than I like to see.

That's been on the "to do" list for some time, but A-P has to approve a new feature like this.

Paging Rolando .  This is an easy call...

It has been low priority since the workarounds include:

1) Use the points you have.
2) Configure more points to start with to account for lost points.
3) Try collecting data for a model at a different time. : I am not sure what you mean on 3.

2)Someway to load prior pointing files.

You can do that already from APCC in the pointing model window.

3) Able to run and load East and West APPM indepentantly.
I would like to run east and west mapping on at another time or another night.

What's the use case? Usually you can plate solve 2-3 points per minute and start before it's dark enough to image. That should be enough for both pier sides.

        If you doing a big model dense model it can take time especially with a slow dome.  I get about 1 point per minute or less even when using the HA option.
       A four point model will take all night.
        I noticed that when I loaded the West model the East Values are preserved but there is no list or graph.  Are East Values still active for pointing and tracking?
       Is there a way cut and paste East and West models ?
    Thanks
    Max
       

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

-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Max Mirot via groups.io
Sent: Saturday, May 9, 2020 7:17 PM
To: main@ap-gto.groups.io
Subject: [ap-gto] APPM feature requests


I think these might be helpful to add.

1) Retry failed pointing image at the end of the APPM run.
Passing clouds and the Moon sometime affect more image than I like to see.

2)Someway to load prior pointing files.

3) Able to run and load East and West APPM indepentantly.
I would like to run east and west mapping on at another time or another night.

Thanks
Max

Hi Max,

1) Retry failed pointing image at the end of the APPM run.
Passing clouds and the Moon sometime affect more image than I like to see.

That's been on the "to do" list for some time, but A-P has to approve a new feature like this.

It has been low priority since the workarounds include:

1) Use the points you have.
2) Configure more points to start with to account for lost points.
3) Try collecting data for a model at a different time.

2)Someway to load prior pointing files.

You can do that already from APCC in the pointing model window.

3) Able to run and load East and West APPM indepentantly.
I would like to run east and west mapping on at another time or another night.

What's the use case? Usually you can plate solve 2-3 points per minute and start before it's dark enough to image. That should be enough for both pier sides.

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

-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Max Mirot via groups.io
Sent: Saturday, May 9, 2020 7:17 PM
To: main@ap-gto.groups.io
Subject: [ap-gto] APPM feature requests


I think these might be helpful to add.

1) Retry failed pointing image at the end of the APPM run.
Passing clouds and the Moon sometime affect more image than I like to see.

2)Someway to load prior pointing files.

3) Able to run and load East and West APPM indepentantly.
I would like to run east and west mapping on at another time or another night.

Thanks
Max

Max

See section 5.17.2 in the APPC manual

Bryan

On Sun, May 10, 2020 at 09:39 AM, Max Mirot wrote:

missing

Is there a way to load a prior model 

I am missing how to accomplish this currently?

Max

I'm positive that if you send an e-mail to them they well tell you where you stand at this point.  I did that at the end of March when the stay at home order started and they got right back to me.
--
Dean Jacobsen
http://astrophoto.net/wp/ 
Image Gallery - http://astrophoto.net/wp/image-gallery/
Astrobin - https://www.astrobin.com/users/deanjacobsen/ 

Dean, I have no idea where I am on the list. Maybe soon they will be completed.  I'm really looking forward to that.
Thanks for the reply. 
Jerome

Hi
Good.  Glad you are inspecting.
I bought a losmandy polar scope for my losmandy g11 and it wouldn't fit. They were not helpful to fix it.
Glad it's in AP's hands.
How accurate are these things? I tried to align the reticle in my old losmandy and despite being super careful it cracked.
Tom

Jumping in here with a suggestion. Can it be a memory allocation used for processing that needs to be increased in the computer....what do you have now for computer memory? I know several programs use computer memory to swap out packets to speed math processing (i.e. high end video programs, Photo Shop). If a computer doesn't have access to sufficient memory it increases processing time greatly and perhaps that runs up against a time limit in PEMPRO.

Also, do you have other programs running at the same time in the background? Try shutting down all programs except for PEMPRO and see if that helps.
Bob

Ray,
Can you not use a subframe from the camera? For example I use TheSkyX and it does support subframes.
 Would this not work?
One only needs a small are of the sky for the polar alignment routines.
I will be out of luck. I have no view to the north and cannot use other solutions!
Tom

I think these might  be helpful to add.

1) Retry failed pointing image at the end of the APPM run.
Passing clouds and the Moon sometime affect more image than I like to see.

2)Someway to load prior pointing files.

3) Able to run and load East and West APPM indepentantly.
I would like to run east and west mapping on at  another time or another night.

Thanks
Max

I would say that one should never use the same sky model for different scopes. Differential flex will never be the
same and will throw off any model.

Agreed! Sorry, I forgot to address that part of Wayne's post.

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

-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of uncarollo2 <chris1011@aol.com> via
groups.io
Sent: Saturday, May 9, 2020 12:39 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] Strange Guiding Problem.

I would say that one should never use the same sky model for different scopes. Differential flex will never be the
same and will throw off any model.

Roland


-----Original Message-----
From: Ray Gralak <groups3@gralak.com>
To: main@ap-gto.groups.io
Sent: Sat, May 9, 2020 2:30 pm
Subject: Re: [ap-gto] Strange Guiding Problem.


Hi Wayne,

One data point: I was still using a sky model created with my refractor. I figured that was a bad idea, but I just
forgot to turn it off. Would that be an issue? Does modeling use tiny slew type commands for corrections? Any
ideas appreciated.

If you have tracking rate correction enabled then the telescope rate will be changed. There are no slews or micro-
slews issued.

However, make sure that pointing correction is also enabled or else it might appear that the scope is moving as
RA/Dec can slowly change because of the non-sidereal tracking rate.

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

-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Wayne Hixson via groups.io
Sent: Saturday, May 9, 2020 8:26 AM
To: main@ap-gto.groups.io
Subject: [ap-gto] Strange Guiding Problem.

Good morning! Took my new 12. f/6.7 iDK for a spin on the Mach2 and crashed into a wall - metaphorically
speaking. I was using a QSI 690 with OAG and Voyager software. I created a new profile in PHD2 based on the
new telescope Guiding calibration told me that DEC and RA weren't 'orthogonal' I think it was and guiding would
be poor and it was - well over 1.5" which is twice what I was getting with a refractor. I had settling criteria of 1.4"
and it took forever to reach that. Once I got a 300 second sub started, it would never finish as "PHD2 detected a
slew and stopped guiding". voyager would then stop the image and try to get things going again, just never
happened successfully. I was dead tired at that time (about 3 am) and knew I was in no state to try to figure

things

out. This is my first large SCT, always been a refractor guy, so issues are new to me and thought I'd ask for
HELLLP!!! What might cause a micro slew in the middle of an image? What's different in guiding a big scope

that I

need to know in troubleshooting?

One data point: I was still using a sky model created with my refractor. I figured that was a bad idea, but I just
forgot to turn it off. Would that be an issue? Does modeling use tiny slew type commands for corrections? Any
ideas appreciated.

Wayne

Hi Wayne,

One data point: I was still using a sky model created with my refractor. I figured that was a bad idea, but I just
forgot to turn it off. Would that be an issue? Does modeling use tiny slew type commands for corrections? Any
ideas appreciated.

If you have tracking rate correction enabled then the telescope rate will be changed. There are no slews or micro-slews issued.

However, make sure that pointing correction is also enabled or else it might appear that the scope is moving as RA/Dec can slowly change because of the non-sidereal tracking rate.

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

-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Wayne Hixson via groups.io
Sent: Saturday, May 9, 2020 8:26 AM
To: main@ap-gto.groups.io
Subject: [ap-gto] Strange Guiding Problem.

Good morning! Took my new 12. f/6.7 iDK for a spin on the Mach2 and crashed into a wall - metaphorically
speaking. I was using a QSI 690 with OAG and Voyager software. I created a new profile in PHD2 based on the
new telescope Guiding calibration told me that DEC and RA weren't 'orthogonal' I think it was and guiding would
be poor and it was - well over 1.5" which is twice what I was getting with a refractor. I had settling criteria of 1.4"
and it took forever to reach that. Once I got a 300 second sub started, it would never finish as "PHD2 detected a
slew and stopped guiding". voyager would then stop the image and try to get things going again, just never
happened successfully. I was dead tired at that time (about 3 am) and knew I was in no state to try to figure things
out. This is my first large SCT, always been a refractor guy, so issues are new to me and thought I'd ask for
HELLLP!!! What might cause a micro slew in the middle of an image? What's different in guiding a big scope that I
need to know in troubleshooting?

One data point: I was still using a sky model created with my refractor. I figured that was a bad idea, but I just
forgot to turn it off. Would that be an issue? Does modeling use tiny slew type commands for corrections? Any
ideas appreciated.

Wayne

Ok just sent to your aol.com email

Hi Benoit,

No issues with ccdstack (which is written in C#) and full res frames
from the 6200 . I do load multiple frames and register/process and
other fun activities

I am sure it's because CCDStack is running as a 64-bit application.

Building PEMPro as a 64-bit executable is non-trivial because a few of the components in PEMPro are legacy 32-bit ActiveX or C++ DLLs. Also, not all ASCOM drivers are 64-bit or activeX servers which will make a 64-bit version potentially less compatible.

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

-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Benoit Schillings
Sent: Saturday, May 9, 2020 10:27 AM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] PEMPro on ASI6200 & QHY600

No issues with ccdstack (which is written in C#) and full res frames
from the 6200 . I do load multiple frames and register/process and
other fun activities

-- benoit

On Sat, May 9, 2020 at 7:11 AM Tom Blahovici <tom.va2fsq@videotron.ca> wrote:

I'm planning for that camera as well. Is CCDInspector having the same issue?

Some other options...use video memory. Compile for 64bit. Allow subframes.
Swap images to a disk file. (Ram disk would work).
This camera is going to be extremely popular.
Tom