ASCOM Driver Beta - v5.20.04


Ray Gralak
 

Hello all,

Here is new beta version of the AP V2 ASCOM driver. If you see any problems please report them here or to me via private email.

https://www.gralak.com/apdriver/AstroPhysics_V2_Setup_5.20.04.exe

Changes since v5.20.02:

V5.20.04 - 2018-Oct-01 Beta - Ray Gralak
-------------------------------------------------------------------
- IMPROVEMENT - Park/Unpark positions will not change because of the new Park 5 position.
- Update documentation for various features, including Time synchronization options.
- Change wording of sync time during initialization.
- BUG FIX - Change RA/DEC AxisRates from 0-5, to -5-5 degrees/sec.

V5.20.03 - 2018-Sep-24 Beta - Ray Gralak
-------------------------------------------------------------------
- NEW FEATURE - Added Park 5
- BUG FIX - Dec MoveAxis was always setting Rate=0
- Removed extra "PEC" label from the Handbox
- When Encoder tracking is enabled on encoder-equipped mounts, disable PEM Enable/Disable buttons, and hide PEM Record button


-Ray Gralak
Author of APCC (Astro-Physics Command Center): http://www.astro-physics.com/index.htm?products/accessories/software/apcc/apcc
Author of PEMPro V3: https://www.ccdware.com
Author of Astro-Physics V2 ASCOM Driver: https://www.siriusimaging.com/apdriver


Guillaume Richard
 

Ray

I downloaded, installed and tested 5.20.04. I am happy to report MoveAxis works perfectly in declination. The rate exactly as expected per the ASCOM standard. 


The rates min/max also look good:
Can move axis RA Dec Rotator? True True False
Axis rates 0-RA Max: 5.0
Axis rates 0-RA Min: -5.0
Axis rates 1-DEC Max: 5.0
Axis rates 1-DEC Min: -5.0

When initiating a Move Axis and asking the mount to report on its position every second I get the expected values as long as the rate is below 2.5 deg/s:

Moving about axis 0-RA at 2 degree per second, RA in hours:
2018-10-01 22:03:40.445000 RA: 20.0 Dec: 20.0
2018-10-01 22:03:41.501000 RA: 20.07575 Dec: 20.0
2018-10-01 22:03:42.525000 RA: 20.2602222222 Dec: 20.0
2018-10-01 22:03:43.581000 RA: 20.41225 Dec: 20.0
2018-10-01 22:03:44.605000 RA: 20.41225 Dec: 20.0
2018-10-01 22:03:45.628000 RA: 20.5658611111 Dec: 20.0
2018-10-01 22:03:46.652000 RA: 20.7080277778 Dec: 20.0
2018-10-01 22:03:47.676000 RA: 20.8595833333 Dec: 20.0
2018-10-01 22:03:48.700000 RA: 21.0107777778 Dec: 20.0
2018-10-01 22:03:49.724000 RA: 21.1626944444 Dec: 20.0

Moving about axis 1-DEC at 2 degree per second, dec in Degrees:
2018-10-01 22:03:50.859000 RA: 21.1626944444 Dec: 20.0
2018-10-01 22:03:51.883000 RA: 21.3888055556 Dec: 20.0594444444
2018-10-01 22:03:52.907000 RA: 21.4156111111 Dec: 22.3841666667
2018-10-01 22:03:53.931000 RA: 21.4156111111 Dec: 24.9680555556
2018-10-01 22:03:54.955000 RA: 21.4156111111 Dec: 27.2133333333
2018-10-01 22:03:55.979000 RA: 21.4156111111 Dec: 27.2133333333
2018-10-01 22:03:57.034000 RA: 21.4156111111 Dec: 30.6233333333
2018-10-01 22:03:58.058000 RA: 21.4156111111 Dec: 32.9413888889
2018-10-01 22:03:59.082000 RA: 21.4156111111 Dec: 35.2194444444
2018-10-01 22:04:00.106000 RA: 21.4156111111 Dec: 37.4975

Just for curiosity, I also noticed the maximum speed in Dec is about 2.5 degrees per second, not 5 degrees per second.
Above 2.5 degrees per second the mount accepts the command but does not seem capable of maintaining the rate.
Not sure if it is built in or if I should increase the power supplied to the mount (I supply 12.7 volt stabilized and at full speed consume up to 0.4A). Here is the log when asking for 4.5 degres per second in declination, with the mount lagging:
 
Moving about axis 1-DEC at 4.5 degree per second and reporting every second:
2018-10-01 22:15:24.159000 RA: 20.1761111111 Dec: 20.0
2018-10-01 22:15:25.183000 RA: 20.1761388889 Dec: 21.7266666667
2018-10-01 22:15:26.207000 RA: 20.1761388889 Dec: 24.6155555556
2018-10-01 22:15:27.230000 RA: 20.1761388889 Dec: 27.5552777778
2018-10-01 22:15:28.254000 RA: 20.1761388889 Dec: 30.1691666667
2018-10-01 22:15:29.278000 RA: 20.1761388889 Dec: 32.9783333333
2018-10-01 22:15:30.302000 RA: 20.1761388889 Dec: 35.8330555556
2018-10-01 22:15:31.326000 RA: 20.1761388889 Dec: 38.6861111111

Anyways, for my purpose 2.5 degres/s solves the problem.

Thanks for providing the new driver.

Guillaume Richard


Ray Gralak
 

Hi Richard,

Thanks for the feedback!

As for the 2.5 degrees/second, there may be an internal limit set in the mount's firmware for the commands that set the tracking rate. I know the limit is 2.5 degrees/sec for the 3600GTO but I think you said you have a 1100GTO, correct?

BTW, have you tried 3 or 4 degrees/second? I recall at one time there was a limit of 1000x (a little over 4 deg/sec) but I thought that was changed to 1200x. If it hasn't changed I will adjust the rate range in the next driver build.

-Ray Gralak
Author of APCC (Astro-Physics Command Center): http://www.astro-physics.com/index.htm?products/accessories/software/apcc/apcc
Author of PEMPro V3: https://www.ccdware.com
Author of Astro-Physics V2 ASCOM Driver: https://www.siriusimaging.com/apdriver

-----Original Message-----
From: ap-gto@yahoogroups.com [mailto:ap-gto@yahoogroups.com]
Sent: Monday, October 1, 2018 8:32 PM
To: ap-gto@yahoogroups.com
Subject: [ap-gto] Re: ASCOM Driver Beta - v5.20.04



Ray

I downloaded, installed and tested 5.20.04. I am happy to report MoveAxis works perfectly in declination. The rate
exactly as expected per the ASCOM standard.




The rates min/max also look good:
Can move axis RA Dec Rotator? True True False
Axis rates 0-RA Max: 5.0
Axis rates 0-RA Min: -5.0
Axis rates 1-DEC Max: 5.0
Axis rates 1-DEC Min: -5.0

When initiating a Move Axis and asking the mount to report on its position every second I get the expected values as
long as the rate is below 2.5 deg/s:

Moving about axis 0-RA at 2 degree per second, RA in hours:
2018-10-01 22:03:40.445000 RA: 20.0 Dec: 20.0
2018-10-01 22:03:41.501000 RA: 20.07575 Dec: 20.0
2018-10-01 22:03:42.525000 RA: 20.2602222222 Dec: 20.0
2018-10-01 22:03:43.581000 RA: 20.41225 Dec: 20.0
2018-10-01 22:03:44.605000 RA: 20.41225 Dec: 20.0
2018-10-01 22:03:45.628000 RA: 20.5658611111 Dec: 20.0
2018-10-01 22:03:46.652000 RA: 20.7080277778 Dec: 20.0
2018-10-01 22:03:47.676000 RA: 20.8595833333 Dec: 20.0
2018-10-01 22:03:48.700000 RA: 21.0107777778 Dec: 20.0
2018-10-01 22:03:49.724000 RA: 21.1626944444 Dec: 20.0

Moving about axis 1-DEC at 2 degree per second, dec in Degrees:
2018-10-01 22:03:50.859000 RA: 21.1626944444 Dec: 20.0
2018-10-01 22:03:51.883000 RA: 21.3888055556 Dec: 20.0594444444
2018-10-01 22:03:52.907000 RA: 21.4156111111 Dec: 22.3841666667
2018-10-01 22 :03:53.931000 RA: 21.4156111111 Dec: 24.9680555556
2018-10-01 22:03:54.955000 RA: 21.4156111111 Dec: 27.2133333333
2018-10-01 22:03:55.979000 RA: 21.4156111111 Dec: 27.2133333333
2018-10-01 22:03:57.034000 RA: 21.4156111111 Dec: 30.6233333333
2018-10-01 22:03:58.058000 RA: 21.4156111111 Dec: 32.9413888889
2018-10-01 22:03:59.082000 RA: 21.4156111111 Dec: 35.2194444444
2018-10-01 22:04:00.106000 RA: 21.4156111111 Dec: 37.4975

Just for curiosity, I also noticed the maximum speed in Dec is about 2.5 degrees per second, not 5 degrees per
second.
Above 2.5 degrees per second the mount accepts the command but does not seem capable of maintaining the rate.
Not sure if it is built in or if I should increase the power supplied to the mount (I supply 12.7 volt stabilized and at full
speed consume up to 0.4A). Here is the log when asking for 4.5 degres per second in declination, with the mount
lagging:

Moving about axis 1-DEC at 4.5 degree per second and reporting every second:
2018-10-01 22:15:24.159000 RA: 20.1761111111 Dec: 20.0
2018-10-01 22:15:25.183000 RA: 20.1761388889 Dec: 21.7266666667
2018-10-01 22:15:26.207000 RA: 20.1761388889 Dec: 24.6155555556
2018-10-01 22:15:27.230000 RA: 20.1761388889 Dec: 27.5552777778
2018-10-01 22:15:28.254000 RA: 20.1761388889 Dec: 30.1691666667
2018-10-01 22:15:29.278000 RA: 20.1761388889 Dec: 32.9783333333
2018-10-01 22:15:30.302000 RA: 20.1761388889 Dec: 35.8330555556
2018-10-01 22:15:31.326000 RA: 20.1761388889 Dec: 38.6861111111

Anyways, for my purpose 2.5 degres/s solves the problem.

Thanks for providing the new driver.

Guillaume Richard



Bill Long
 

What is park 5?
From: ap-gto@... on behalf of 'Ray Gralak (Groups)' groups3@... [ap-gto]
Sent: Monday, October 1, 2018 6:27:15 PM
To: ap-gto@...
Subject: [ap-gto] ASCOM Driver Beta - v5.20.04
 
 

Hello all,

Here is new beta version of the AP V2 ASCOM driver. If you see any problems please report them here or to me via private email.

https://www.gralak.com/apdriver/AstroPhysics_V2_Setup_5.20.04.exe

Changes since v5.20.02:

V5.20.04 - 2018-Oct-01 Beta - Ray Gralak
----------------------------------------------------------
- IMPROVEMENT - Park/Unpark positions will not change because of the new Park 5 position.
- Update documentation for various features, including Time synchronization options.
- Change wording of sync time during initialization.
- BUG FIX - Change RA/DEC AxisRates from 0-5, to -5-5 degrees/sec.

V5.20.03 - 2018-Sep-24 Beta - Ray Gralak
----------------------------------------------------------
- NEW FEATURE - Added Park 5
- BUG FIX - Dec MoveAxis was always setting Rate=0
- Removed extra "PEC" label from the Handbox
- When Encoder tracking is enabled on encoder-equipped mounts, disable PEM Enable/Disable buttons, and hide PEM Record button

-Ray Gralak
Author of APCC (Astro-Physics Command Center): http://www.astro-physics.com/index.htm?products/accessories/software/apcc/apcc
Author of PEMPro V3: https://www.ccdware.com
Author of Astro-Physics V2 ASCOM Driver: https://www.siriusimaging.com/apdriver


George
 

Similar to Park 4, but with scope pointing north.

 

Regards,

 

George

 

George Whitney

Astro-Physics, Inc.

Phone:  815-282-1513

Email:  george@...

 

From: ap-gto@... [mailto:ap-gto@...]
Sent: Monday, October 01, 2018 11:03 PM
To: ap-gto@...
Subject: Re: [ap-gto] ASCOM Driver Beta - v5.20.04

 

 

What is park 5?


From: ap-gto@... on behalf of 'Ray Gralak (Groups)' groups3@... [ap-gto]
Sent: Monday, October 1, 2018 6:27:15 PM
To: ap-gto@...
Subject: [ap-gto] ASCOM Driver Beta - v5.20.04

 

 

Hello all,

Here is new beta version of the AP V2 ASCOM driver. If you see any problems please report them here or to me via private email.

https://www.gralak.com/apdriver/AstroPhysics_V2_Setup_5.20.04.exe

Changes since v5.20.02:

V5.20.04 - 2018-Oct-01 Beta - Ray Gralak
----------------------------------------------------------
- IMPROVEMENT - Park/Unpark positions will not change because of the new Park 5 position.
- Update documentation for various features, including Time synchronization options.
- Change wording of sync time during initialization.
- BUG FIX - Change RA/DEC AxisRates from 0-5, to -5-5 degrees/sec.

V5.20.03 - 2018-Sep-24 Beta - Ray Gralak
----------------------------------------------------------
- NEW FEATURE - Added Park 5
- BUG FIX - Dec MoveAxis was always setting Rate=0
- Removed extra "PEC" label from the Handbox
- When Encoder tracking is enabled on encoder-equipped mounts, disable PEM Enable/Disable buttons, and hide PEM Record button

-Ray Gralak
Author of APCC (Astro-Physics Command Center): http://www.astro-physics.com/index.htm?products/accessories/software/apcc/apcc
Author of PEMPro V3: https://www.ccdware.com
Author of Astro-Physics V2 ASCOM Driver: https://www.siriusimaging.com/apdriver


topboxman
 

Good. I would prefer that over Park 1.

Peter


---In ap-gto@..., <george@...> wrote :

Similar to Park 4, but with scope pointing north.

 

Regards,

 

George

 

George Whitney

Astro-Physics, Inc.

Phone:  815-282-1513

Email:  george@...

 

From: ap-gto@... [mailto:ap-gto@...]
Sent: Monday, October 01, 2018 11:03 PM
To: ap-gto@...
Subject: Re: [ap-gto] ASCOM Driver Beta - v5.20.04

 

 

What is park 5?


From: ap-gto@... <ap-gto@...> on behalf of 'Ray Gralak (Groups)' groups3@... [ap-gto] <ap-gto@...>
Sent: Monday, October 1, 2018 6:27:15 PM
To: ap-gto@...
Subject: [ap-gto] ASCOM Driver Beta - v5.20.04

 

 

Hello all,

Here is new beta version of the AP V2 ASCOM driver. If you see any problems please report them here or to me via private email.

https://www.gralak.com/apdriver/AstroPhysics_V2_Setup_5.20.04.exe

Changes since v5.20.02:

V5.20.04 - 2018-Oct-01 Beta - Ray Gralak
----------------------------------------------------------
- IMPROVEMENT - Park/Unpark positions will not change because of the new Park 5 position.
- Update documentation for various features, including Time synchronization options.
- Change wording of sync time during initialization.
- BUG FIX - Change RA/DEC AxisRates from 0-5, to -5-5 degrees/sec.

V5.20.03 - 2018-Sep-24 Beta - Ray Gralak
----------------------------------------------------------
- NEW FEATURE - Added Park 5
- BUG FIX - Dec MoveAxis was always setting Rate=0
- Removed extra "PEC" label from the Handbox
- When Encoder tracking is enabled on encoder-equipped mounts, disable PEM Enable/Disable buttons, and hide PEM Record button

-Ray Gralak
Author of APCC (Astro-Physics Command Center): http://www.astro-physics.com/index.htm?products/accessories/software/apcc/apcc
Author of PEMPro V3: https://www.ccdware.com
Author of Astro-Physics V2 ASCOM Driver: https://www.siriusimaging.com/apdriver


topboxman
 

Dang!! I should have drank coffee first before making the post.

I meant I prefer Park 5 over Park 4.

Peter


---In ap-gto@..., <pnagy@...> wrote :

Good. I would prefer that over Park 1.

Peter


---In ap-gto@..., <george@...> wrote :

Similar to Park 4, but with scope pointing north.

 

Regards,

 

George

 

George Whitney

Astro-Physics, Inc.

Phone:  815-282-1513

Email:  george@...

 

From: ap-gto@... [mailto:ap-gto@...]
Sent: Monday, October 01, 2018 11:03 PM
To: ap-gto@...
Subject: Re: [ap-gto] ASCOM Driver Beta - v5.20.04

 

 

What is park 5?


From: ap-gto@... <ap-gto@...> on behalf of 'Ray Gralak (Groups)' groups3@... [ap-gto] <ap-gto@...>
Sent: Monday, October 1, 2018 6:27:15 PM
To: ap-gto@...
Subject: [ap-gto] ASCOM Driver Beta - v5.20.04

 

 

Hello all,

Here is new beta version of the AP V2 ASCOM driver. If you see any problems please report them here or to me via private email.

https://www.gralak.com/apdriver/AstroPhysics_V2_Setup_5.20.04.exe

Changes since v5.20.02:

V5.20.04 - 2018-Oct-01 Beta - Ray Gralak
----------------------------------------------------------
- IMPROVEMENT - Park/Unpark positions will not change because of the new Park 5 position.
- Update documentation for various features, including Time synchronization options.
- Change wording of sync time during initialization.
- BUG FIX - Change RA/DEC AxisRates from 0-5, to -5-5 degrees/sec.

V5.20.03 - 2018-Sep-24 Beta - Ray Gralak
----------------------------------------------------------
- NEW FEATURE - Added Park 5
- BUG FIX - Dec MoveAxis was always setting Rate=0
- Removed extra "PEC" label from the Handbox
- When Encoder tracking is enabled on encoder-equipped mounts, disable PEM Enable/Disable buttons, and hide PEM Record button

-Ray Gralak
Author of APCC (Astro-Physics Command Center): http://www.astro-physics.com/index.htm?products/accessories/software/apcc/apcc
Author of PEMPro V3: https://www.ccdware.com
Author of Astro-Physics V2 ASCOM Driver: https://www.siriusimaging.com/apdriver


robert@...
 

This must be back in the archives somewhere, but what is wrong with Park 1? I see dialog boxes here and there warning about its use, people say things like "Good. I would prefer that over Park 1." Etc. It is possessed or something? I don't program my mount to do things without me, so maybe that's why I'm not seeing a problem with it. I have a little bubble level on the saddle that works in P1 and P4, so I use it all the time.

Bob


Roland Christen
 



This must be back in the archives somewhere, but what is wrong with Park 1?
Park 1 is a position where the scope is on the West side of the mount pointing due north. As such it is just a few seconds away from the meridian flip point. So, if you unpark the scope from that position, then go inside to have dinner, then forget that the scope is running (tracking sidereal) after several hours you will find your scope hard against the pier. We never anticipated this when we first came up with our 3 park positions, but people have accidentally left the scope to track into the pier this way.

Park 5 points the scope in the same direction, except the scope is in the East side. If you unpark from that position and leave the scope tracking, it takes a good 12 to 14 hours before the scope runs into the pier.

Of course you could control the mount via APCC and set limits, in which case APCC will stop the tracking at a preset point and no pier crash occurs either way.

Rolando


-----Original Message-----
From: robert@... [ap-gto]
To: ap-gto
Sent: Tue, Oct 2, 2018 11:14 am
Subject: RE: [ap-gto] ASCOM Driver Beta - v5.20.04



This must be back in the archives somewhere, but what is wrong with Park 1? I see dialog boxes here and there warning about its use, people say things like "Good. I would prefer that over Park 1." Etc. It is possessed or something? I don't program my mount to do things without me, so maybe that's why I'm not seeing a problem with it. I have a little bubble level on the saddle that works in P1 and P4, so I use it all the time.

Bob




topboxman
 

Are you planning to add Park 5 to Keypad firmware?

Peter


---In ap-gto@..., <chris1011@...> wrote :



This must be back in the archives somewhere, but what is wrong with Park 1?
Park 1 is a position where the scope is on the West side of the mount pointing due north. As such it is just a few seconds away from the meridian flip point. So, if you unpark the scope from that position, then go inside to have dinner, then forget that the scope is running (tracking sidereal) after several hours you will find your scope hard against the pier. We never anticipated this when we first came up with our 3 park positions, but people have accidentally left the scope to track into the pier this way.

Park 5 points the scope in the same direction, except the scope is in the East side. If you unpark from that position and leave the scope tracking, it takes a good 12 to 14 hours before the scope runs into the pier.

Of course you could control the mount via APCC and set limits, in which case APCC will stop the tracking at a preset point and no pier crash occurs either way.

Rolando


-----Original Message-----
From: robert@... [ap-gto] <ap-gto@...>
To: ap-gto <ap-gto@...>
Sent: Tue, Oct 2, 2018 11:14 am
Subject: RE: [ap-gto] ASCOM Driver Beta - v5.20.04



This must be back in the archives somewhere, but what is wrong with Park 1? I see dialog boxes here and there warning about its use, people say things like "Good. I would prefer that over Park 1." Etc. It is possessed or something? I don't program my mount to do things without me, so maybe that's why I'm not seeing a problem with it. I have a little bubble level on the saddle that works in P1 and P4, so I use it all the time.

Bob




robert@...
 

Ah ha! I thought so. I still push the shutter buttons on and off, so I'm always around.
Thanks!

This must be back in the archives somewhere, but what is wrong with Park 1?
Park 1 is a position where the scope is on the West side of the mount pointing due north. As such it is just a few seconds away from the meridian flip point. So, if you unpark the scope from that position, then go inside to have dinner, then forget that the scope is running (tracking sidereal) after several hours you will find your scope hard against the pier.


topboxman
 

Just wanted to say that Park 5 works well. Will use this park position from now on.

Thanks Ray.

Peter


---In ap-gto@..., <groups3@...> wrote :

Hello all,

Here is new beta version of the AP V2 ASCOM driver. If you see any problems please report them here or to me via private email.

https://www.gralak.com/apdriver/AstroPhysics_V2_Setup_5.20.04.exe

Changes since v5.20.02:

V5.20.04 - 2018-Oct-01 Beta - Ray Gralak
-------------------------------------------------------------------
- IMPROVEMENT - Park/Unpark positions will not change because of the new Park 5 position.
- Update documentation for various features, including Time synchronization options.
- Change wording of sync time during initialization.
- BUG FIX - Change RA/DEC AxisRates from 0-5, to -5-5 degrees/sec.

V5.20.03 - 2018-Sep-24 Beta - Ray Gralak
-------------------------------------------------------------------
- NEW FEATURE - Added Park 5
- BUG FIX - Dec MoveAxis was always setting Rate=0
- Removed extra "PEC" label from the Handbox
- When Encoder tracking is enabled on encoder-equipped mounts, disable PEM Enable/Disable buttons, and hide PEM Record button


-Ray Gralak
Author of APCC (Astro-Physics Command Center): http://www.astro-physics.com/index.htm?products/accessories/software/apcc/apcc
Author of PEMPro V3: https://www.ccdware.com
Author of Astro-Physics V2 ASCOM Driver: https://www.siriusimaging.com/apdriver


Bill Long
 

What is the advantage? 




From: ap-gto@... on behalf of pnagy@... [ap-gto]
Sent: Saturday, October 6, 2018 7:03 PM
To: ap-gto@...
Subject: [ap-gto] Re: ASCOM Driver Beta - v5.20.04
 
 

Just wanted to say that Park 5 works well. Will use this park position from now on.

Thanks Ray.

Peter


---In ap-gto@..., wrote :

Hello all,

Here is new beta version of the AP V2 ASCOM driver. If you see any problems please report them here or to me via private email.

https://www.gralak.com/apdriver/AstroPhysics_V2_Setup_5.20.04.exe

Changes since v5.20.02:

V5.20.04 - 2018-Oct-01 Beta - Ray Gralak
-------------------------------------------------------------------
- IMPROVEMENT - Park/Unpark positions will not change because of the new Park 5 position.
- Update documentation for various features, including Time synchronization options.
- Change wording of sync time during initialization.
- BUG FIX - Change RA/DEC AxisRates from 0-5, to -5-5 degrees/sec.

V5.20.03 - 2018-Sep-24 Beta - Ray Gralak
-------------------------------------------------------------------
- NEW FEATURE - Added Park 5
- BUG FIX - Dec MoveAxis was always setting Rate=0
- Removed extra "PEC" label from the Handbox
- When Encoder tracking is enabled on encoder-equipped mounts, disable PEM Enable/Disable buttons, and hide PEM Record button


-Ray Gralak
Author of APCC (Astro-Physics Command Center): http://www.astro-physics.com/index.htm?products/accessories/software/apcc/apcc
Author of PEMPro V3: https://www.ccdware.com
Author of Astro-Physics V2 ASCOM Driver: https://www.siriusimaging.com/apdriver


topboxman
 

I just like it better. I usually manually position the mount to Park 3, load equipment, position to Park 5 and go from there.

When I was using Park 4, after loading equipment in Park 3 and then position to Park 4, sometimes I would rotate Dec axis in one direction and other times to opposite direction to point the scope to south, the cables inside the mount can get twisted and recently they were twisted so I had to untwist them.

Using Park 5 from Park 3, it's easy to rotate Dec axis in only one direction to point scope to North because rotating Dec axis to opposite direction to point the scope to North is much longer so it's obvious to rotate Dec axis much shorter direction and avoid cables get twisted inside the mount. I hope I am making it clear.

It's mainly a personal preference and easy not to get cables twisted inside the mount from Park 3 to Park 5.

Peter


---In ap-gto@..., <bill@...> wrote :

What is the advantage? 




From: ap-gto@... <ap-gto@...> on behalf of pnagy@... [ap-gto] <ap-gto@...>
Sent: Saturday, October 6, 2018 7:03 PM
To: ap-gto@...
Subject: [ap-gto] Re: ASCOM Driver Beta - v5.20.04
 
 

Just wanted to say that Park 5 works well. Will use this park position from now on.

Thanks Ray.

Peter


---In ap-gto@..., <groups3@...> wrote :

Hello all,

Here is new beta version of the AP V2 ASCOM driver. If you see any problems please report them here or to me via private email.

https://www.gralak.com/apdriver/AstroPhysics_V2_Setup_5.20.04.exe

Changes since v5.20.02:

V5.20.04 - 2018-Oct-01 Beta - Ray Gralak
-------------------------------------------------------------------
- IMPROVEMENT - Park/Unpark positions will not change because of the new Park 5 position.
- Update documentation for various features, including Time synchronization options.
- Change wording of sync time during initialization.
- BUG FIX - Change RA/DEC AxisRates from 0-5, to -5-5 degrees/sec.

V5.20.03 - 2018-Sep-24 Beta - Ray Gralak
-------------------------------------------------------------------
- NEW FEATURE - Added Park 5
- BUG FIX - Dec MoveAxis was always setting Rate=0
- Removed extra "PEC" label from the Handbox
- When Encoder tracking is enabled on encoder-equipped mounts, disable PEM Enable/Disable buttons, and hide PEM Record button


-Ray Gralak
Author of APCC (Astro-Physics Command Center): http://www.astro-physics.com/index.htm?products/accessories/software/apcc/apcc
Author of PEMPro V3: https://www.ccdware.com
Author of Astro-Physics V2 ASCOM Driver: https://www.siriusimaging.com/apdriver