Date   

Re: Fine tuning PHD2 settings for 1100 with Encoders #Guiding

Roland Christen
 

I don't see any screen shots

Roland



-----Original Message-----
From: Andrew J <andjones132@...>
To: main@ap-gto.groups.io
Sent: Fri, Oct 8, 2021 4:43 pm
Subject: Re: [ap-gto] Fine tuning PHD2 settings for 1100 with Encoders #Guiding

On Fri, Oct 8, 2021 at 01:39 PM, Roland Christen wrote:
ld let the mount track and record the tracking grap
Hi Roland.

Thank you for taking the time reply. I really appreciate the help. The main reason ordered the 1100 with Encoders is I was hoping my guiding would significantly improve and maybe even get to the point where could image without guiding at all.

I have change the delay to 2000ms. The 10s delay seemed like a bit long, but was willing to give it a try. 

Regarding, letting the mount track without guiding, I think that is pretty much what the PHD2 Guiding Assistant does (see screen shot). After letting it run for about 5 mins it reported a total RMS of around 0.23 arc-sec. It then recommend the MinMo of 0.20 for RA and 0.30 for DEC (never understood why these number need to be different). I tried bumping this up a bit during the night, but it didn't seem to help much.

I just was not sure if the results I was getting was just the best I should expect given my crappy skies here in Houston, or if I was just not fully dialed in. What always bugs me is to see my DEC axis jumping around. If I am polar aligned, which both PemPro and PHD2 say I am, then I would not expect much movement in my DEC, but it is jumping all over the place. I tried turning down the aggression as a lot of the gyrations look like over corrections. Maybe I just need to keep turning down the aggression in PHD to get rid of those spikes?

Andrew

--
Roland Christen
Astro-Physics


1600GTO notification

 

If you are interested in the 1600GTO mount and had signed up previously with the NotifyMe button, I urge you to check your emails periodically. We started our notification process on September 27.

 

The notification emails that we send out will have a deadline for you to contact us before we move on to the next person on the list.  Since the NotifyMe button only allows you to enter your email address, that is the only means that we have to contact you. Don’t miss your opportunity to order yours!

 

If you have not signed up, we invite you to do so. Just click the NotifyMe button for any of the 1600 webpages (1600GTO, 1600GTO-AE oar 1600GTO-AEL). You do not need to decide on encoders at the time you sign up and there is no obligation.

 

We plan to begin shipping these mounts shortly after the beginning of the new year.

 

Clear Skies,

Marj Christen

Astro-Physics

11250 Forest Hills Road

Machesney Park, IL 61115

Phone: 815-282-1513

www.astro-physics.com

 


Re: Fine tuning PHD2 settings for 1100 with Encoders #Guiding

Terry Martin
 

"the further north and near the leeward side of mountains, the worse the seeing"

Oh ya, I can attest to that!  I am so envious when I hear of people talk about 0.3 arc/sec better or total RMS guiding.

But luckily I have a Mach2 that saves the day.

Terry


Re: Fine tuning PHD2 settings for 1100 with Encoders #Guiding

 

Hi Andrew

can you please upload your guidelog for that session. I assume you followed the baseline guiding steps?

screen captures are interesting but aren't helpful for analysis

On Fri, Oct 8, 2021 at 2:43 PM Andrew J <andjones132@...> wrote:
On Fri, Oct 8, 2021 at 01:39 PM, Roland Christen wrote:
ld let the mount track and record the tracking grap
Hi Roland.

Thank you for taking the time reply. I really appreciate the help. The main reason ordered the 1100 with Encoders is I was hoping my guiding would significantly improve and maybe even get to the point where could image without guiding at all.

I have change the delay to 2000ms. The 10s delay seemed like a bit long, but was willing to give it a try. 

Regarding, letting the mount track without guiding, I think that is pretty much what the PHD2 Guiding Assistant does (see screen shot). After letting it run for about 5 mins it reported a total RMS of around 0.23 arc-sec. It then recommend the MinMo of 0.20 for RA and 0.30 for DEC (never understood why these number need to be different). I tried bumping this up a bit during the night, but it didn't seem to help much.

I just was not sure if the results I was getting was just the best I should expect given my crappy skies here in Houston, or if I was just not fully dialed in. What always bugs me is to see my DEC axis jumping around. If I am polar aligned, which both PemPro and PHD2 say I am, then I would not expect much movement in my DEC, but it is jumping all over the place. I tried turning down the aggression as a lot of the gyrations look like over corrections. Maybe I just need to keep turning down the aggression in PHD to get rid of those spikes?

Andrew



--
Brian 



Brian Valente


Re: Fine tuning PHD2 settings for 1100 with Encoders #Guiding

Andrew J
 

On Fri, Oct 8, 2021 at 01:39 PM, Roland Christen wrote:
ld let the mount track and record the tracking grap
Hi Roland.

Thank you for taking the time reply. I really appreciate the help. The main reason ordered the 1100 with Encoders is I was hoping my guiding would significantly improve and maybe even get to the point where could image without guiding at all.

I have change the delay to 2000ms. The 10s delay seemed like a bit long, but was willing to give it a try. 

Regarding, letting the mount track without guiding, I think that is pretty much what the PHD2 Guiding Assistant does (see screen shot). After letting it run for about 5 mins it reported a total RMS of around 0.23 arc-sec. It then recommend the MinMo of 0.20 for RA and 0.30 for DEC (never understood why these number need to be different). I tried bumping this up a bit during the night, but it didn't seem to help much.

I just was not sure if the results I was getting was just the best I should expect given my crappy skies here in Houston, or if I was just not fully dialed in. What always bugs me is to see my DEC axis jumping around. If I am polar aligned, which both PemPro and PHD2 say I am, then I would not expect much movement in my DEC, but it is jumping all over the place. I tried turning down the aggression as a lot of the gyrations look like over corrections. Maybe I just need to keep turning down the aggression in PHD to get rid of those spikes?

Andrew


Re: Fine tuning PHD2 settings for 1100 with Encoders #Guiding

Roland Christen
 

First I would let the mount track and record the tracking graph with corrections turned off. That will give you a baseline of the amount of natural sky scintillation (or seeing) that your site is experiencing. You cannot guide out seeing, so that will be the best you can do on that particular night. It depends on where your setup is located, of course - the further north and near the leeward side of mountains, the worse the seeing. The further south you are, and closer to the Gulf, the steadier the seeing will be.
You need to establish a baseline so that you don't have any unrealistic expectations about achieving a certain rms guiding error. Watching the Dec axis fluctuations over a 5 minute period is the best way to see that because the Dec motor will be sitting exactly still and any fluctuations or P-P value will be caused only by the atmosphere above. Of course you don't want to do this with the model running, and also you want to disregard any drift due to polar misalignment, atmospheric refraction, etc.

Set a 10 second "time lapse" between exposures
Second, I would cut my guide exposure to between 2 and 3 seconds and drop the 10 second delay down to 2 to 3 seconds.

Rolando

-----Original Message-----
From: Andrew J <andjones132@...>
To: main@ap-gto.groups.io
Sent: Fri, Oct 8, 2021 3:25 pm
Subject: [ap-gto] Fine tuning PHD2 settings for 1100 with Encoders #Guiding

We finally got a clear night and I was finally able to create a pointing model and attempt my first imaging run last night with my 1100GTO-AEL. I created about a 200 point model and setup PHD2 following some helpful advice from Brian Valente here on this forum back in July.
 
Here are my settings:
 
  • Used Guiding Assistant to set the RA/DEC MinMo by letting it run for about 5 mins
  • Set sidereal guide rate to 1x
  • Use 4 second guiding exposures
  • Set a 10 second "time lapse" between exposures
  • Use lowpass 2 algorithm on both RA and DEC
  • Set Medium aggressiveness (I used 65 for RA and 80 for DEC)
  • Don’t use backlash compensation


Although my guiding was much better than I ever got with my Mach1, I still think there might be some room for improvement. Here is the graph that I had at the end of the session that was fairly representative of what I saw earlier in the night. I tried fumbling with the MinMo and Aggressive settings to try and smooth it out a bit, but was unable to get a better result. I would welcome any recommendation on how I can improve my settings or things to try.
 
Thanks in the advance for the help

Andrew J

--
Roland Christen
Astro-Physics


Fine tuning PHD2 settings for 1100 with Encoders #Guiding

Andrew J
 

We finally got a clear night and I was finally able to create a pointing model and attempt my first imaging run last night with my 1100GTO-AEL. I created about a 200 point model and setup PHD2 following some helpful advice from Brian Valente here on this forum back in July.

 

Here are my settings:

 

  • Used Guiding Assistant to set the RA/DEC MinMo by letting it run for about 5 mins
  • Set sidereal guide rate to 1x
  • Use 4 second guiding exposures
  • Set a 10 second "time lapse" between exposures
  • Use lowpass 2 algorithm on both RA and DEC
  • Set Medium aggressiveness (I used 65 for RA and 80 for DEC)
  • Don’t use backlash compensation


Although my guiding was much better than I ever got with my Mach1, I still think there might be some room for improvement. Here is the graph that I had at the end of the session that was fairly representative of what I saw earlier in the night. I tried fumbling with the MinMo and Aggressive settings to try and smooth it out a bit, but was unable to get a better result. I would welcome any recommendation on how I can improve my settings or things to try.

 

Thanks in the advance for the help

Andrew J


Re: APCC: RA limit reached while in Park 3? #APCC

Glenn
 

I thought I had configured the home and mount limits setting a while ago but have not checked it recently. Thank you for the suggestion. I will try that and report back.

Glenn


Re: Interesting Park using NINA

michael mccann
 

Hi
Yes actually I was trying to figure out what I was doing wrong to confuse the different applications. Wasn’t pointing the finger at software. I was wondering if I was activating software in right order. Last night was cloudy so I’ll try tonight.
Howard brought up taking flats, which on this maiden session I didn’t. So ‘safety park timer’ phrase was used. Which manual is that described in?

Cheers

On Oct 8, 2021, at 10:23, Howard Hedlund <howard@...> wrote:

Ray and Dale,

I honestly think we are starting down a rabbit hole here. It is my belief that Mr. McCann's safety park timer parked the mount while pointed at the zenith awaiting flats. After that, the issue was further compounded because the nature of that safety park was not understood.
There is no problem with how NINA is parking the mount.
There is no problem with how APCC is parking the mount.
There is no problem with how the driver is parking the mount.
While this discussion has been interesting, I honestly believe that the issue itself is little more than a misunderstanding of how things worked with the safety park timer.

Mag. 7 or Better Skies!

Howard Hedlund
Astro-Physics, Inc.
AP Phone: 815-282-1513
Direct Phone: 815-315-7015
www.astro-physics.com
Please include this e-mail with your response.

 Consider the environment before printing this e-mail.

-----Original Message-----
From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of Ray Gralak
Sent: Friday, October 8, 2021 8:41
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] Interesting Park using NINA

Hi Dale,

I honestly can't explain why there's a difference between an external
app such as NINA telling the driver to park, and the driver's own park button giving different results.
The only difference is that you can select a different park position from the driver's UI than the default. The actual park operations are handled identically.

-Ray

-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf
Of Dale Ghent
Sent: Thursday, October 7, 2021 2:09 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] Interesting Park using NINA


I honestly can't explain why there's a difference between an external
app such as NINA telling the driver to park, and the driver's own park
button giving different results. I would think that both interfaces run the same logic underneath. Perhaps Ray can shed some light on this mechanism.

But given a correct PC and mount time and a reasonable lat/long,
parking should always be successful and fine assuming your mount is
properly aligned, something that can be done with a single plate
solve. Time zones aren't going to have a bearing on the mount's internal clock. Like your PC, the system clock actually runs in UTC time, with whatever timezone you have configured applied to it for purposes of display.

What I bet *might* be happening in your case is that you have the
keypad connected to your mount and it's not set for an EXT auto
connect. So when your mount is powering on, the time that's configured
in the keypad is immediately getting applied to the CP when the keypad
initializes it. This could possibly explain some mount/PC time
mismatch or wonkiness. With the Sync Time options I pointed out before, you can set the keypad to EXT in its autoconnect setting which will allow the ASCOM driver to initialize the mount when it connects.

On Oct 7, 2021, at 16:50, michael mccann via groups.io <mmccawsprojects@...> wrote:
You know that might be. I’m living in New Mexico, but so close to
Arizona my computer always tell me my
time is an hour earlier. I’m out in the countryside where I get my
time from cell/data and not a regular network. I thought I had
corrected this problem on my computer because I set the display time
for mountain time zone, but when you look at all the settings it shows that it thinks it’s in Pacific time zone. I tried several times to change it. Software comes back says that I don’t have permission to, and yet I’m the administrator.

So finalizing the park is best from AP ASCOM.

















Re: Interesting Park using NINA

Howard Hedlund
 

Ray and Dale,

I honestly think we are starting down a rabbit hole here. It is my belief that Mr. McCann's safety park timer parked the mount while pointed at the zenith awaiting flats. After that, the issue was further compounded because the nature of that safety park was not understood.
There is no problem with how NINA is parking the mount.
There is no problem with how APCC is parking the mount.
There is no problem with how the driver is parking the mount.
While this discussion has been interesting, I honestly believe that the issue itself is little more than a misunderstanding of how things worked with the safety park timer.

Mag. 7 or Better Skies!

Howard Hedlund
Astro-Physics, Inc.
AP Phone: 815-282-1513
Direct Phone: 815-315-7015
www.astro-physics.com
Please include this e-mail with your response.

 Consider the environment before printing this e-mail.

-----Original Message-----
From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of Ray Gralak
Sent: Friday, October 8, 2021 8:41
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] Interesting Park using NINA

Hi Dale,

I honestly can't explain why there's a difference between an external
app such as NINA telling the driver to park, and the driver's own park button giving different results.
The only difference is that you can select a different park position from the driver's UI than the default. The actual park operations are handled identically.

-Ray

-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf
Of Dale Ghent
Sent: Thursday, October 7, 2021 2:09 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] Interesting Park using NINA


I honestly can't explain why there's a difference between an external
app such as NINA telling the driver to park, and the driver's own park
button giving different results. I would think that both interfaces run the same logic underneath. Perhaps Ray can shed some light on this mechanism.

But given a correct PC and mount time and a reasonable lat/long,
parking should always be successful and fine assuming your mount is
properly aligned, something that can be done with a single plate
solve. Time zones aren't going to have a bearing on the mount's internal clock. Like your PC, the system clock actually runs in UTC time, with whatever timezone you have configured applied to it for purposes of display.

What I bet *might* be happening in your case is that you have the
keypad connected to your mount and it's not set for an EXT auto
connect. So when your mount is powering on, the time that's configured
in the keypad is immediately getting applied to the CP when the keypad
initializes it. This could possibly explain some mount/PC time
mismatch or wonkiness. With the Sync Time options I pointed out before, you can set the keypad to EXT in its autoconnect setting which will allow the ASCOM driver to initialize the mount when it connects.

On Oct 7, 2021, at 16:50, michael mccann via groups.io <mmccawsprojects@...> wrote:

You know that might be. I’m living in New Mexico, but so close to
Arizona my computer always tell me my
time is an hour earlier. I’m out in the countryside where I get my
time from cell/data and not a regular network. I thought I had
corrected this problem on my computer because I set the display time
for mountain time zone, but when you look at all the settings it shows that it thinks it’s in Pacific time zone. I tried several times to change it. Software comes back says that I don’t have permission to, and yet I’m the administrator.

So finalizing the park is best from AP ASCOM.







Re: APCC: RA limit reached while in Park 3? #APCC

Howard Hedlund
 

I agree with Ray's next step.  Try reconfiguring Home and Limits as shown.  If a problem persists, let's set up a time where I can help you while you are at the mount.


Re: Seeking CP3 Control Box with V2 Chip

Howard Hedlund
 

Periodic error is a mechanical characteristic of a worm screw gear.  A PE curve is simply a measurement of that error.  It's validity for making corrections is entirely dependent on the synchrony between the worm's actual physical rotational position and the position address in the GTOCPx.  This is often referred to as its phase.  The worm screw is not indexed.  The GTOCPx can only assume that this synchrony is maintained and is correct.  It cannot ascertain that positional or phase value afresh.  This is where the difficulty arises in swapping control boxes.
It does not matter if the axis is moved or kept perfectly still.
It does not matter that the old curve was saved and reloaded into the new box.
There is currently no way to re-establish the proper phase when you swap boxes (...or when you move the gears by hand without the servo, or when you do anything else to break the phase synchrony.)    
This will soon be a problem of the past.  There will be a solution using the AP SerialUtility.jar.  I believe that all we need at this point is for me to get the time to write up instructions and do a little more testing. 


Re: Seeking CP3 Control Box with V2 Chip

Roland Christen
 

Thank you George Smile

Rolando



-----Original Message-----
From: George <george@...>
To: main@ap-gto.groups.io <main@ap-gto.groups.io>
Sent: Fri, Oct 8, 2021 10:12 am
Subject: Re: [ap-gto] Seeking CP3 Control Box with V2 Chip

It’s on our Tech Support page:
 
Regards,
 
George
 
George Whitney
Astro-Physics, Inc.
Phone:  815-222-6538 (direct line)
Phone:  815-282-1513 (office)
Email:  george@...
 
From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of Roland Christen via groups.io
Sent: Friday, October 8, 2021 10:08 AM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] Seeking CP3 Control Box with V2 Chip
 
 
How well you are polar aligned seems verry critical.
Polar alignment is not critical at all. There are two check boxes that nulls out any drift caused by polar mis-alignment. Even if you don't use that feature, the final calculation of the periodic error curve removes any drift.
 
I did once post a step by step procedure on the old user group. I'm not sure if it was archived. It explained what each of the steps do and how best to use the various settings to make a well corrected curve. Maybe someone on this group saved it and can bring it back to life?
 
Rolando
 
 
-----Original Message-----
From: David Diaz <night.skywatcher@...>
To: main@ap-gto.groups.io
Sent: Fri, Oct 8, 2021 8:30 am
Subject: Re: [ap-gto] Seeking CP3 Control Box with V2 Chip
On Wed, Oct 6, 2021 at 05:55 PM, Roland Christen wrote:
 
 
That said, doing a Pempro run is actually fun, and the more you do it, the easier it becomes.
 
Roland-- 
Roland Christen
Astro-Physics
Is there a “PemPro curve creation for dummies” resource anywhere?

Looks rather intimidating..

How well you are polar aligned seems verry critical.

Thx
DD

--
Roland Christen
Astro-Physics

--
Roland Christen
Astro-Physics


Re: Seeking CP3 Control Box with V2 Chip

George
 

It’s on our Tech Support page:

https://astro-physics.info/tech_support/mounts/making-pe-curve.pdf

 

Regards,

 

George

 

George Whitney

Astro-Physics, Inc.

Phone:  815-222-6538 (direct line)

Phone:  815-282-1513 (office)

Email:  george@...

 

From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of Roland Christen via groups.io
Sent: Friday, October 8, 2021 10:08 AM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] Seeking CP3 Control Box with V2 Chip

 

 

How well you are polar aligned seems verry critical.

Polar alignment is not critical at all. There are two check boxes that nulls out any drift caused by polar mis-alignment. Even if you don't use that feature, the final calculation of the periodic error curve removes any drift.

 

I did once post a step by step procedure on the old user group. I'm not sure if it was archived. It explained what each of the steps do and how best to use the various settings to make a well corrected curve. Maybe someone on this group saved it and can bring it back to life?

 

Rolando

 

 

-----Original Message-----
From: David Diaz <night.skywatcher@...>
To: main@ap-gto.groups.io
Sent: Fri, Oct 8, 2021 8:30 am
Subject: Re: [ap-gto] Seeking CP3 Control Box with V2 Chip

On Wed, Oct 6, 2021 at 05:55 PM, Roland Christen wrote:

 

 

That said, doing a Pempro run is actually fun, and the more you do it, the easier it becomes.

 

Roland-- 

Roland Christen
Astro-Physics

Is there a “PemPro curve creation for dummies” resource anywhere?

Looks rather intimidating..

How well you are polar aligned seems verry critical.

Thx
DD


--
Roland Christen
Astro-Physics


Re: Seeking CP3 Control Box with V2 Chip

Roland Christen
 


How well you are polar aligned seems verry critical.
Polar alignment is not critical at all. There are two check boxes that nulls out any drift caused by polar mis-alignment. Even if you don't use that feature, the final calculation of the periodic error curve removes any drift.

I did once post a step by step procedure on the old user group. I'm not sure if it was archived. It explained what each of the steps do and how best to use the various settings to make a well corrected curve. Maybe someone on this group saved it and can bring it back to life?

Rolando


-----Original Message-----
From: David Diaz <night.skywatcher@...>
To: main@ap-gto.groups.io
Sent: Fri, Oct 8, 2021 8:30 am
Subject: Re: [ap-gto] Seeking CP3 Control Box with V2 Chip

On Wed, Oct 6, 2021 at 05:55 PM, Roland Christen wrote:
 
 
That said, doing a Pempro run is actually fun, and the more you do it, the easier it becomes.
 
Roland-- 
Roland Christen
Astro-Physics
Is there a “PemPro curve creation for dummies” resource anywhere?

Looks rather intimidating..

How well you are polar aligned seems verry critical.

Thx
DD

--
Roland Christen
Astro-Physics


Re: Seeking CP3 Control Box with V2 Chip

Ray Gralak
 

Hi David,

Is there a “PemPro curve creation for dummies” resource anywhere?
There is a specific section in PEMPro's help file for Astro-Physics mounts. Here is the same information online:

https://www.siriusimaging.com/Help/PEMProV3/index.html?astrophysicsgtocp3.html

How well you are polar aligned seems verry critical.
It depends. PEMPro will subtract drift, but polar alignment has to be good enough that the star PEMPro monitors doesn't drift off the camera sensor over the period of time it collects data (usually 5-6 worm cycles, or 30-40 minutes). So, the required polar alignment accuracy depends on the sensor size and focal length of the telescope, and thus I would say polar alignment should be accurate within 15-20 arc-minutes.

-Ray



-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of David Diaz
Sent: Friday, October 8, 2021 6:30 AM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] Seeking CP3 Control Box with V2 Chip

On Wed, Oct 6, 2021 at 05:55 PM, Roland Christen wrote:




That said, doing a Pempro run is actually fun, and the more you do it, the easier it becomes.

Roland--
Roland Christen
Astro-Physics

Is there a “PemPro curve creation for dummies” resource anywhere?

Looks rather intimidating..

How well you are polar aligned seems verry critical.

Thx
DD


Re: Seeking CP3 Control Box with V2 Chip

Catherine Hyde
 

Hi Chris. I just upgraded to the CP4 box, so I do in fact have a 3 lying around, and yes it does have the upgraded V2 chip and running 4.19.3 firmware. I was going to sell it on Astromart but hadn't yet. 


Re: Interesting Park using NINA

Ray Gralak
 

Hi Dale,

I honestly can't explain why there's a difference between an external app such as NINA telling the driver to
park, and the driver's own park button giving different results.
The only difference is that you can select a different park position from the driver's UI than the default. The actual park operations are handled identically.

-Ray

-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Dale Ghent
Sent: Thursday, October 7, 2021 2:09 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] Interesting Park using NINA


I honestly can't explain why there's a difference between an external app such as NINA telling the driver to
park, and the driver's own park button giving different results. I would think that both interfaces run the same
logic underneath. Perhaps Ray can shed some light on this mechanism.

But given a correct PC and mount time and a reasonable lat/long, parking should always be successful and
fine assuming your mount is properly aligned, something that can be done with a single plate solve. Time
zones aren't going to have a bearing on the mount's internal clock. Like your PC, the system clock actually
runs in UTC time, with whatever timezone you have configured applied to it for purposes of display.

What I bet *might* be happening in your case is that you have the keypad connected to your mount and it's
not set for an EXT auto connect. So when your mount is powering on, the time that's configured in the keypad
is immediately getting applied to the CP when the keypad initializes it. This could possibly explain some
mount/PC time mismatch or wonkiness. With the Sync Time options I pointed out before, you can set the
keypad to EXT in its autoconnect setting which will allow the ASCOM driver to initialize the mount when it
connects.

On Oct 7, 2021, at 16:50, michael mccann via groups.io <mmccawsprojects@...> wrote:

You know that might be. I’m living in New Mexico, but so close to Arizona my computer always tell me my
time is an hour earlier. I’m out in the countryside where I get my time from cell/data and not a regular network. I
thought I had corrected this problem on my computer because I set the display time for mountain time zone,
but when you look at all the settings it shows that it thinks it’s in Pacific time zone. I tried several times to
change it. Software comes back says that I don’t have permission to, and yet I’m the administrator.

So finalizing the park is best from AP ASCOM.







Re: APCC: RA limit reached while in Park 3? #APCC

Ray Gralak
 

Hi Glenn,

 

> Does anyone know what might be causing this?

Have you tried reconfiguring Home and mount limits on APCC Homing/Limits tab?

 

 

 

-Ray

 

From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Glenn
Sent: Thursday, October 7, 2021 10:21 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] APCC: RA limit reached while in Park 3? #APCC

 

Howard, thank you for speaking to me on the phone today. 

For the benefit of others, I will repeat what you told me to do to attempt to solve the problem. 

  1. Park the mount (I used Park 3)
  2. Reconfigure the V2 driver to not use the APCC virtual port. I changed it back to the IP address used by my Ethernet configuration. 
  3. Configure the driver to Unpark from Park 3 and unpark the mount. 

After doing this, the mount unparked and responded to commands normally. 

I then reconfigured the driver for use with APCC Pro and tried to connect to the mount. I got this error, which is what has appeared since the beginning. 



I don't even have to connect to the driver to get this error. It appears as soon as I connect to the mount. 

Does anyone know what might be causing this?

Thank you,

Glenn


Re: Seeking CP3 Control Box with V2 Chip

David Diaz <night.skywatcher@...>
 

On Wed, Oct 6, 2021 at 05:55 PM, Roland Christen wrote:
 
 
That said, doing a Pempro run is actually fun, and the more you do it, the easier it becomes.
 
Roland-- 
Roland Christen
Astro-Physics
Is there a “PemPro curve creation for dummies” resource anywhere?

Looks rather intimidating..

How well you are polar aligned seems verry critical.

Thx
DD

4881 - 4900 of 86825