New Released versions of APCC Standard/Pro (v1.7.1.0 / v1.7.1.1)


Ray Gralak
 

Astro-Physics would like to thank everyone that helped with beta testing and to announce the availability of the public RELEASE version of APCC Standard v1.7.1.0 and APCC Pro v1.7.1.1. Please use these versions with the latest AP V2 ASCOM driver, v5.20.09.

The direct download links are as follows:

AP V2 ASCOM Driver (Released February 11, 2019)
https://www.siriusimaging.com/apdriver/AstroPhysics_V2_Setup_5.20.09.exe

APCC Standard v1.7.1.0 (Released March 14, 2019)
http://www.apastrosoftware.com/apcc_download/APCC_Standard_Setup_1.7.1.0.exe

APCC Pro v1.7.1.1 (Released March 14, 2019)
http://www.apastrosoftware.com/apcc_download/APCC_Pro_Setup_1.7.1.1.exe

APCC version history can be found here:
https://www.siriusimaging.com/Help/APCC/version_history.htm

If you see any issues please post them here and be prepared to share log files and a way to reproduce an issue exactly.

Thank you!

-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
 

Thanks Ray and AP for a wonderful software package! 🙂


From: ap-gto@... <ap-gto@...> on behalf of 'Ray Gralak (Groups)' groups3@... [ap-gto] <ap-gto@...>
Sent: Sunday, March 17, 2019 3:53 PM
To: ap-gto@...
Subject: [ap-gto] New Released versions of APCC Standard/Pro (v1.7.1.0 / v1.7.1.1)
 
 

Astro-Physics would like to thank everyone that helped with beta testing and to announce the availability of the public RELEASE version of APCC Standard v1.7.1.0 and APCC Pro v1.7.1.1. Please use these versions with the latest AP V2 ASCOM driver, v5.20.09.

The direct download links are as follows:

AP V2 ASCOM Driver (Released February 11, 2019)
https://www.siriusimaging.com/apdriver/AstroPhysics_V2_Setup_5.20.09.exe

APCC Standard v1.7.1.0 (Released March 14, 2019)
http://www.apastrosoftware.com/apcc_download/APCC_Standard_Setup_1.7.1.0.exe

APCC Pro v1.7.1.1 (Released March 14, 2019)
http://www.apastrosoftware.com/apcc_download/APCC_Pro_Setup_1.7.1.1.exe

APCC version history can be found here:
https://www.siriusimaging.com/Help/APCC/version_history.htm

If you see any issues please post them here and be prepared to share log files and a way to reproduce an issue exactly.

Thank you!

-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


Ray Gralak
 

Thanks Ray and AP for a wonderful software package! 🙂
Thanks Bill!

-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: Sunday, March 17, 2019 6:14 PM
To: 'Ray Gralak (Groups)' groups3@gralak.com [ap-gto]
Subject: Re: [ap-gto] New Released versions of APCC Standard/Pro (v1.7.1.0 / v1.7.1.1)



Thanks Ray and AP for a wonderful software package! 🙂

________________________________

From: ap-gto@yahoogroups.com <ap-gto@yahoogroups.com> on behalf of 'Ray Gralak (Groups)'
groups3@gralak.com [ap-gto] <ap-gto@yahoogroups.com>
Sent: Sunday, March 17, 2019 3:53 PM
To: ap-gto@yahoogroups.com
Subject: [ap-gto] New Released versions of APCC Standard/Pro (v1.7.1.0 / v1.7.1.1)



Astro-Physics would like to thank everyone that helped with beta testing and to announce the availability of the
public RELEASE version of APCC Standard v1.7.1.0 and APCC Pro v1.7.1.1. Please use these versions with the
latest AP V2 ASCOM driver, v5.20.09.

The direct download links are as follows:

AP V2 ASCOM Driver (Released February 11, 2019)
https://www.siriusimaging.com/apdriver/AstroPhysics_V2_Setup_5.20.09.exe

APCC Standard v1.7.1.0 (Released March 14, 2019)
http://www.apastrosoftware.com/apcc_download/APCC_Standard_Setup_1.7.1.0.exe

APCC Pro v1.7.1.1 (Released March 14, 2019)
http://www.apastrosoftware.com/apcc_download/APCC_Pro_Setup_1.7.1.1.exe

APCC version history can be found here:
https://www.siriusimaging.com/Help/APCC/version_history.htm

If you see any issues please post them here and be prepared to share log files and a way to reproduce an issue
exactly.

Thank you!

-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




Michael Fulbright <mike.fulbright@...>
 

Ray,

  I've encountered what may be an issue with 1.7.1.0 versus 1.7.0.10 Standard.

  I discovered it last night after upgrading to 1.7.1.0.  Slews will work if the distance is over around 60 arc-minutes but slews smaller than this fail and the log exception is:

0029137 2019-03-23 16:16:13.074:       Info, SafeSlewStateMachine, Slewing from RA/Dec = 5.05497 (05h 03m 17.90s), 61.1058
3 (+61° 06' 21.0")
0029138 2019-03-23 16:16:13.074:       Info, SafeSlewStateMachine, Slewing to   RA/Dec = 5.13668 (05h 08m 12.05s), 61.1958
3 (+61° 11' 45.0")
0029139 2019-03-23 16:16:13.074:       Info, SafeSlewStateMachine, Starting Meridian Delay = 0.00
0029140 2019-03-23 16:16:13.074:       Info, SafeSlewStateMachine, Start PierSide/CWUP = WEST, False
0029141 2019-03-23 16:16:13.074:       Info, GetDestinationPierSide, RA,Dec,LST,EastMD,WestMD =   5.137,  61.196,   3.085,
   0.000.   0.000: PS = WEST: CWUP = False
0029142 2019-03-23 16:16:13.074:       Info, SafeSlewStateMachine,   IsUnsafeSlew = False
0029143 2019-03-23 16:16:13.074:       Info, SafeSlewStateMachine,   END PierSide/CWUP = WEST, False
0029144 2019-03-23 16:16:13.074:       Info, SafeSlewStateMachine, Ending   Meridian Delay = 0.00
0029145 2019-03-23 16:16:13.075:      Debug, SafeSlewStateMachine, New SafeSlew State=StartPrimarySlew
0029146 2019-03-23 16:16:13.075:       Info, ProcessVPortCommand, RX from VPort 1: :APCC,2749,GR#
0029147 2019-03-23 16:16:13.075:       Info, ProcessVPortCommand, APCC Seq=    2749, CMD=GR#
0029148 2019-03-23 16:16:13.075:       Info, VPortCheckVPort1(COM21), (RX: GR#), TX: APCC,11,2749,05:03:17.9#
0029149 2019-03-23 16:16:13.089:      Debug,  Command Thread, TX=':GM#'|RX='00:00:00.0#'
0029150 2019-03-23 16:16:13.089:      Debug,  Command Thread, TX = ':HRG#'
0029151 2019-03-23 16:16:13.121:      Debug,  Command Thread, TX=':HRG#'|RX='-1266*06:14#'
0029152 2019-03-23 16:16:13.121:      Debug,  Command Thread, TX = ':HDG#'
0029153 2019-03-23 16:16:13.136:       Info, SafeSlewStateMachine, Slewing to   RA/Dec = 5.1367, 61.1958
0029154 2019-03-23 16:16:13.136:      Debug, SafeSlewStateMachine, New SafeSlew State=WaitStartPrimarySlew
0029155 2019-03-23 16:16:13.145:      Debug, RestoreFormPosition, EmergencyStop: Restore = False
0029156 2019-03-23 16:16:13.145:      Debug, RestoreFormPosition, EmergencyStop: Not restoring form - option is disabled or CONTROL key is pressed
0029157 2019-03-23 16:16:13.153:      Debug,  Command Thread, TX=':HDG#'|RX='+4123*31:36#'
0029158 2019-03-23 16:16:13.153:      Debug,  Command Thread, TX = '#:GP#'
0029159 2019-03-23 16:16:13.185:      Debug,  Command Thread, TX='#:GP#'|RX='00:00:56.4#'
0029160 2019-03-23 16:16:13.185:      Debug,  Command Thread, TX = ':Rr#'
0029161 2019-03-23 16:16:13.201:      Debug,  Command Thread, TX=':Rr#'|RX='0#'
0029162 2019-03-23 16:16:13.201:      Debug,  Command Thread, TX = ':Rd#'
0029163 2019-03-23 16:16:13.217:      Debug,  Command Thread, TX=':Rd#'|RX='0#'
0029164 2019-03-23 16:16:13.217:      Debug,  Command Thread, TX = ':Sr05:08:12.1#'
0029165 2019-03-23 16:16:13.231:       Info,   VPort1(COM21), RX: :APCC,2750,GZ#
0029166 2019-03-23 16:16:13.249:      Debug,  Command Thread, TX=':Sr05:08:12.1#'|RX='1'
0029167 2019-03-23 16:16:13.249:      Debug,  Command Thread, TX = ':Sd+61*11:45#'
0029168 2019-03-23 16:16:13.262:       Info, ProcessVPortCommand, RX from VPort 1: :APCC,2750,GZ#
0029169 2019-03-23 16:16:13.263:       Info, ProcessVPortCommand, APCC Seq=    2750, CMD=GZ#
0029170 2019-03-23 16:16:13.263:       Info, VPortCheckVPort1(COM21), (RX: GZ#), TX: APCC,10,2750,+27*06:40#
0029171 2019-03-23 16:16:13.265:      Debug,  Command Thread, TX=':Sd+61*11:45#'|RX='1'
0029172 2019-03-23 16:16:13.265:      Debug,  Command Thread, TX = ':M_S#'
0029173 2019-03-23 16:16:13.365:  Exception, ProcessQAC: ComPort Read error. Sent=:M_S#, The operation has timed out.
0029174 2019-03-23 16:16:13.365:      Debug,  Command Thread, TX=':M_S#'|RX=''
0029175 2019-03-23 16:16:13.366:      Debug, Slew Start Callback, New SafeSlew State=WaitPrimarySlew
0029176 2019-03-23 16:16:13.366:      Error,   mySlewStarted, No response from mount
ª

I can send you a complete log if it would help - it is rather large so I didn't attach it here.

Slews of around 60 arc-minutes or greater are working fine.  I only noticed this because the precise slews that Voyager were doing were failing to get within my threshold (60 arc-seconds).  The plate solve/sync was successful but then when the slew was requested the mount simply didn't move the small distance required.

I went back to 1.7.0.10 and it is working fine.

Thank You,
Michael Fulbright

On 3/17/19 6:53 PM, 'Ray Gralak (Groups)' groups3@... [ap-gto] wrote:
 

Astro-Physics would like to thank everyone that helped with beta testing and to announce the availability of the public RELEASE version of APCC Standard v1.7.1.0 and APCC Pro v1.7.1.1. Please use these versions with the latest AP V2 ASCOM driver, v5.20.09.

The direct download links are as follows:

AP V2 ASCOM Driver (Released February 11, 2019)
https://www.siriusimaging.com/apdriver/AstroPhysics_V2_Setup_5.20.09.exe

APCC Standard v1.7.1.0 (Released March 14, 2019)
http://www.apastrosoftware.com/apcc_download/APCC_Standard_Setup_1.7.1.0.exe

APCC Pro v1.7.1.1 (Released March 14, 2019)
http://www.apastrosoftware.com/apcc_download/APCC_Pro_Setup_1.7.1.1.exe

APCC version history can be found here:
https://www.siriusimaging.com/Help/APCC/version_history.htm

If you see any issues please post them here and be prepared to share log files and a way to reproduce an issue exactly.

Thank you!

-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



Ray Gralak
 

Hi Michael,

If the mount is timing out is not necessarily a bug in APCC. It suggests you may be running old firmware and so the mount doesn't understand the command. Please make sure you have the latest GTOCP4 firmware installed and also the latest AP V2 ASCOM driver.

-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: Saturday, March 23, 2019 1:33 PM
To: ap-gto@yahoogroups.com
Subject: Re: [ap-gto] New Released versions of APCC Standard/Pro (v1.7.1.0 / v1.7.1.1)



Ray,

I've encountered what may be an issue with 1.7.1.0 versus 1.7.0.10 Standard.

I discovered it last night after upgrading to 1.7.1.0. Slews will work if the distance is over around 60 arc-minutes
but slews smaller than this fail and the log exception is:

0029137 2019-03-23 16:16:13.074: Info, SafeSlewStateMachine, Slewing from RA/Dec = 5.05497 (05h 03m
17.90s), 61.1058
3 (+61° 06' 21.0")
0029138 2019-03-23 16:16:13.074: Info, SafeSlewStateMachine, Slewing to RA/Dec = 5.13668 (05h 08m
12.05s), 61.1958
3 (+61° 11' 45.0")
0029139 2019-03-23 16:16:13.074: Info, SafeSlewStateMachine, Starting Meridian Delay = 0.00
0029140 2019-03-23 16:16:13.074: Info, SafeSlewStateMachine, Start PierSide/CWUP = WEST, False
0029141 2019-03-23 16:16:13.074: Info, GetDestinationPierSide, RA,Dec,LST,EastMD,WestMD = 5.137,
61.196, 3.085,
0.000. 0.000: PS = WEST: CWUP = False
0029142 2019-03-23 16:16:13.074: Info, SafeSlewStateMachine, IsUnsafeSlew = False
0029143 2019-03-23 16:16:13.074: Info, SafeSlewStateMachine, END PierSide/CWUP = WEST, False
0029144 2019-03-23 16:16:13.074: Info, SafeSlewStateMachine, Ending Meridian Delay = 0.00
0029145 2019-03-23 16:16:13.075: Debug, SafeSlewStateMachine, New SafeSlew State=StartPrimarySlew
0029146 2019-03-23 16:16:13.075: Info, ProcessVPortCommand, RX from VPort 1: :APCC,2749,GR#
0029147 2019-03-23 16:16:13.075: Info, ProcessVPortCommand, APCC Seq= 2749, CMD=GR#
0029148 2019-03-23 16:16:13.075: Info, VPortCheckVPort1(COM21), (RX: GR#), TX:
APCC,11,2749,05:03:17.9#
0029149 2019-03-23 16:16:13.089: Debug, Command Thread, TX=':GM#'|RX='00:00:00.0#'
0029150 2019-03-23 16:16:13.089: Debug, Command Thread, TX = ':HRG#'
0029151 2019-03-23 16:16:13.121: Debug, Command Thread, TX=':HRG#'|RX='-1266*06:14#'
0029152 2019-03-23 16:16:13.121: Debug, Command Thread, TX = ':HDG#'
0029153 2019-03-23 16:16:13.136: Info, SafeSlewStateMachine, Slewing to RA/Dec = 5.1367, 61.1958
0029154 2019-03-23 16:16:13.136: Debug, SafeSlewStateMachine, New SafeSlew
State=WaitStartPrimarySlew
0029155 2019-03-23 16:16:13.145: Debug, RestoreFormPosition, EmergencyStop: Restore = False
0029156 2019-03-23 16:16:13.145: Debug, RestoreFormPosition, EmergencyStop: Not restoring form - option
is disabled or CONTROL key is pressed
0029157 2019-03-23 16:16:13.153: Debug, Command Thread, TX=':HDG#'|RX='+4123*31:36#'
0029158 2019-03-23 16:16:13.153: Debug, Command Thread, TX = '#:GP#'
0029159 2019-03-23 16:16:13.185: Debug, Command Thread, TX='#:GP#'|RX='00:00:56.4#'
0029160 2019-03-23 16:16:13.185: Debug, Command Thread, TX = ':Rr#'
0029161 2019-03-23 16:16:13.201: Debug, Command Thread, TX=':Rr#'|RX='0#'
0029162 2019-03-23 16:16:13.201: Debug, Command Thread, TX = ':Rd#'
0029163 2019-03-23 16:16:13.217: Debug, Command Thread, TX=':Rd#'|RX='0#'
0029164 2019-03-23 16:16:13.217: Debug, Command Thread, TX = ':Sr05:08:12.1#'
0029165 2019-03-23 16:16:13.231: Info, VPort1(COM21), RX: :APCC,2750,GZ#
0029166 2019-03-23 16:16:13.249: Debug, Command Thread, TX=':Sr05:08:12.1#'|RX='1'
0029167 2019-03-23 16:16:13.249: Debug, Command Thread, TX = ':Sd+61*11:45#'
0029168 2019-03-23 16:16:13.262: Info, ProcessVPortCommand, RX from VPort 1: :APCC,2750,GZ#
0029169 2019-03-23 16:16:13.263: Info, ProcessVPortCommand, APCC Seq= 2750, CMD=GZ#
0029170 2019-03-23 16:16:13.263: Info, VPortCheckVPort1(COM21), (RX: GZ#), TX:
APCC,10,2750,+27*06:40#
0029171 2019-03-23 16:16:13.265: Debug, Command Thread, TX=':Sd+61*11:45#'|RX='1'
0029172 2019-03-23 16:16:13.265: Debug, Command Thread, TX = ':M_S#'
0029173 2019-03-23 16:16:13.365: Exception, ProcessQAC: ComPort Read error. Sent=:M_S#, The operation
has timed out.
0029174 2019-03-23 16:16:13.365: Debug, Command Thread, TX=':M_S#'|RX=''
0029175 2019-03-23 16:16:13.366: Debug, Slew Start Callback, New SafeSlew State=WaitPrimarySlew
0029176 2019-03-23 16:16:13.366: Error, mySlewStarted, No response from mount
ª

I can send you a complete log if it would help - it is rather large so I didn't attach it here.

Slews of around 60 arc-minutes or greater are working fine. I only noticed this because the precise slews that
Voyager were doing were failing to get within my threshold (60 arc-seconds). The plate solve/sync was successful
but then when the slew was requested the mount simply didn't move the small distance required.

I went back to 1.7.0.10 and it is working fine.

Thank You,
Michael Fulbright


On 3/17/19 6:53 PM, 'Ray Gralak (Groups)' groups3@gralak.com [ap-gto] wrote:




Astro-Physics would like to thank everyone that helped with beta testing and to announce the availability of
the public RELEASE version of APCC Standard v1.7.1.0 and APCC Pro v1.7.1.1. Please use these versions with
the latest AP V2 ASCOM driver, v5.20.09.

The direct download links are as follows:

AP V2 ASCOM Driver (Released February 11, 2019)
https://www.siriusimaging.com/apdriver/AstroPhysics_V2_Setup_5.20.09.exe

APCC Standard v1.7.1.0 (Released March 14, 2019)
http://www.apastrosoftware.com/apcc_download/APCC_Standard_Setup_1.7.1.0.exe

APCC Pro v1.7.1.1 (Released March 14, 2019)
http://www.apastrosoftware.com/apcc_download/APCC_Pro_Setup_1.7.1.1.exe

APCC version history can be found here:
https://www.siriusimaging.com/Help/APCC/version_history.htm

If you see any issues please post them here and be prepared to share log files and a way to reproduce an
issue exactly.

Thank you!

-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





Michael Fulbright <mike.fulbright@...>
 

Understood - I have the latest ASCOM but not the latest firmware.  I will stick with the 1.7.0.10 APCC for now since it has been working well.

Might want to consider flagging if a given APCC release level requires a certain level of firmware with a popup on startup if that level isn't detected.

Since everything has been working for quite awhile I tend not to upgrade unless the release notes flag a high severity bug has been discovered and fixed.

Thanks,
Michael Fulbright

On 3/23/19 5:23 PM, 'Ray Gralak (Groups)' groups3@... [ap-gto] wrote:
 

Hi Michael,

If the mount is timing out is not necessarily a bug in APCC. It suggests you may be running old firmware and so the mount doesn't understand the command. Please make sure you have the latest GTOCP4 firmware installed and also the latest AP V2 ASCOM driver.

-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@... [mailto:ap-gto@...]
> Sent: Saturday, March 23, 2019 1:33 PM
> To: ap-gto@...
> Subject: Re: [ap-gto] New Released versions of APCC Standard/Pro (v1.7..1.0 / v1.7.1.1)
>
>
>
> Ray,
>
> I've encountered what may be an issue with 1.7.1.0 versus 1.7.0.10 Standard.
>
> I discovered it last night after upgrading to 1.7.1.0. Slews will work if the distance is over around 60 arc-minutes
> but slews smaller than this fail and the log exception is:
>
> 0029137 2019-03-23 16:16:13.074: Info, SafeSlewStateMachine, Slewing from RA/Dec = 5.05497 (05h 03m
> 17.90s), 61.1058
> 3 (+61° 06' 21.0")
> 0029138 2019-03-23 16:16:13.074: Info, SafeSlewStateMachine, Slewing to RA/Dec = 5.13668 (05h 08m
> 12.05s), 61.1958
> 3 (+61° 11' 45.0")
> 0029139 2019-03-23 16:16:13.074: Info, SafeSlewStateMachine, Starting Meridian Delay = 0.00
> 0029140 2019-03-23 16:16:13.074: Info, SafeSlewStateMachine, Start PierSide/CWUP = WEST, False
> 0029141 2019-03-23 16:16:13.074: Info, GetDestinationPierSide, RA,Dec,LST,EastMD,WestMD = 5.137,
> 61.196, 3.085,
> 0.000. 0.000: PS = WEST: CWUP = False
> 0029142 2019-03-23 16:16:13.074: Info, SafeSlewStateMachine, IsUnsafeSlew = False
> 0029143 2019-03-23 16:16:13.074: Info, SafeSlewStateMachine, END PierSide/CWUP = WEST, False
> 0029144 2019-03-23 16:16:13.074: Info, SafeSlewStateMachine, Ending Meridian Delay = 0.00
> 0029145 2019-03-23 16:16:13.075: Debug, SafeSlewStateMachine, New SafeSlew State=StartPrimarySlew
> 0029146 2019-03-23 16:16:13.075: Info, ProcessVPortCommand, RX from VPort 1: :APCC,2749,GR#
> 0029147 2019-03-23 16:16:13.075: Info, ProcessVPortCommand, APCC Seq= 2749, CMD=GR#
> 0029148 2019-03-23 16:16:13.075: Info, VPortCheckVPort1(COM21), (RX: GR#), TX:
> APCC,11,2749,05:03:17.9#
> 0029149 2019-03-23 16:16:13.089: Debug, Command Thread, TX=':GM#'|RX='00:00:00.0#'
> 0029150 2019-03-23 16:16:13.089: Debug, Command Thread, TX = ':HRG#'
> 0029151 2019-03-23 16:16:13.121: Debug, Command Thread, TX=':HRG#'|RX='-1266*06:14#'
> 0029152 2019-03-23 16:16:13.121: Debug, Command Thread, TX = ':HDG#'
> 0029153 2019-03-23 16:16:13.136: Info, SafeSlewStateMachine, Slewing to RA/Dec = 5.1367, 61.1958
> 0029154 2019-03-23 16:16:13.136: Debug, SafeSlewStateMachine, New SafeSlew
> State=WaitStartPrimarySlew
> 0029155 2019-03-23 16:16:13.145: Debug, RestoreFormPosition, EmergencyStop: Restore = False
> 0029156 2019-03-23 16:16:13.145: Debug, RestoreFormPosition, EmergencyStop: Not restoring form - option
> is disabled or CONTROL key is pressed
> 0029157 2019-03-23 16:16:13.153: Debug, Command Thread, TX=':HDG#'|RX='+4123*31:36#'
> 0029158 2019-03-23 16:16:13.153: Debug, Command Thread, TX = '#:GP#'
> 0029159 2019-03-23 16:16:13.185: Debug, Command Thread, TX='#:GP#'|RX='00:00:56.4#'
> 0029160 2019-03-23 16:16:13.185: Debug, Command Thread, TX = ':Rr#'
> 0029161 2019-03-23 16:16:13.201: Debug, Command Thread, TX=':Rr#'|RX='0#'
> 0029162 2019-03-23 16:16:13.201: Debug, Command Thread, TX = ':Rd#'
> 0029163 2019-03-23 16:16:13.217: Debug, Command Thread, TX=':Rd#'|RX='0#'
> 0029164 2019-03-23 16:16:13.217: Debug, Command Thread, TX = ':Sr05:08:12.1#'
> 0029165 2019-03-23 16:16:13.231: Info, VPort1(COM21), RX: :APCC,2750,GZ#
> 0029166 2019-03-23 16:16:13.249: Debug, Command Thread, TX=':Sr05:08:12.1#'|RX='1'
> 0029167 2019-03-23 16:16:13.249: Debug, Command Thread, TX = ':Sd+61*11:45#'
> 0029168 2019-03-23 16:16:13.262: Info, ProcessVPortCommand, RX from VPort 1: :APCC,2750,GZ#
> 0029169 2019-03-23 16:16:13.263: Info, ProcessVPortCommand, APCC Seq= 2750, CMD=GZ#
> 0029170 2019-03-23 16:16:13.263: Info, VPortCheckVPort1(COM21), (RX: GZ#), TX:
> APCC,10,2750,+27*06:40#
> 0029171 2019-03-23 16:16:13.265: Debug, Command Thread, TX=':Sd+61*11:45#'|RX='1'
> 0029172 2019-03-23 16:16:13.265: Debug, Command Thread, TX = ':M_S#'
> 0029173 2019-03-23 16:16:13.365: Exception, ProcessQAC: ComPort Read error. Sent=:M_S#, The operation
> has timed out.
> 0029174 2019-03-23 16:16:13.365: Debug, Command Thread, TX=':M_S#'|RX=''
> 0029175 2019-03-23 16:16:13.366: Debug, Slew Start Callback, New SafeSlew State=WaitPrimarySlew
> 0029176 2019-03-23 16:16:13.366: Error, mySlewStarted, No response from mount
> ª
>
> I can send you a complete log if it would help - it is rather large so I didn't attach it here.
>
> Slews of around 60 arc-minutes or greater are working fine. I only noticed this because the precise slews that
> Voyager were doing were failing to get within my threshold (60 arc-seconds). The plate solve/sync was successful
> but then when the slew was requested the mount simply didn't move the small distance required.
>
> I went back to 1.7.0.10 and it is working fine.
>
> Thank You,
> Michael Fulbright
>
>
> On 3/17/19 6:53 PM, 'Ray Gralak (Groups)' groups3@... [ap-gto] wrote:
>
>
>
>
> Astro-Physics would like to thank everyone that helped with beta testing and to announce the availability of
> the public RELEASE version of APCC Standard v1.7.1.0 and APCC Pro v1.7..1.1. Please use these versions with
> the latest AP V2 ASCOM driver, v5.20.09.
>
> The direct download links are as follows:
>
> AP V2 ASCOM Driver (Released February 11, 2019)
> https://www.siriusimaging.com/apdriver/AstroPhysics_V2_Setup_5.20.09.exe
>
> APCC Standard v1.7.1.0 (Released March 14, 2019)
> http://www.apastrosoftware.com/apcc_download/APCC_Standard_Setup_1.7.1.0.exe
>
> APCC Pro v1.7.1.1 (Released March 14, 2019)
> http://www.apastrosoftware.com/apcc_download/APCC_Pro_Setup_1.7.1.1.exe
>
> APCC version history can be found here:
> https://www.siriusimaging.com/Help/APCC/version_history.htm
>
> If you see any issues please post them here and be prepared to share log files and a way to reproduce an
> issue exactly.
>
> Thank you!
>
> -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
>
>
>
>
>



Ray Gralak
 

Understood - I have the latest ASCOM but not the latest firmware.
I will stick with the 1.7.0.10 APCC for now
since it has been working well.
I think that is risky. The latest firmware has a important fixes and has been in use for a while now. Also, there have been a number of important bug fixes to APCC. The version you are running is a BETA version.

BTW, the M_S slew command that is not responding in your log is most useful when the mount is in a counterweight-up position. It will keep the mount from slewing to the meridian and back again to the counterweight up position. It doesn't do anything different for counterweight down slews.

-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: Saturday, March 23, 2019 2:32 PM
To: ap-gto@yahoogroups.com
Subject: Re: [ap-gto] New Released versions of APCC Standard/Pro (v1.7.1.0 / v1.7.1.1)



Understood - I have the latest ASCOM but not the latest firmware. I will stick with the 1.7.0.10 APCC for now
since it has been working well.

Might want to consider flagging if a given APCC release level requires a certain level of firmware with a popup on
startup if that level isn't detected.

Since everything has been working for quite awhile I tend not to upgrade unless the release notes flag a high
severity bug has been discovered and fixed.

Thanks,
Michael Fulbright


On 3/23/19 5:23 PM, 'Ray Gralak (Groups)' groups3@gralak.com [ap-gto] wrote:




Hi Michael,

If the mount is timing out is not necessarily a bug in APCC. It suggests you may be running old firmware
and so the mount doesn't understand the command. Please make sure you have the latest GTOCP4 firmware
installed and also the latest AP V2 ASCOM driver.

-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: Saturday, March 23, 2019 1:33 PM
> To: ap-gto@yahoogroups.com
> Subject: Re: [ap-gto] New Released versions of APCC Standard/Pro (v1.7..1.0 / v1.7.1.1)
>
>
>
> Ray,
>
> I've encountered what may be an issue with 1.7.1.0 versus 1.7.0.10 Standard.
>
> I discovered it last night after upgrading to 1.7.1.0. Slews will work if the distance is over around 60 arc-
minutes
> but slews smaller than this fail and the log exception is:
>
> 0029137 2019-03-23 16:16:13.074: Info, SafeSlewStateMachine, Slewing from RA/Dec = 5.05497 (05h
03m
> 17.90s), 61.1058
> 3 (+61° 06' 21.0")
> 0029138 2019-03-23 16:16:13.074: Info, SafeSlewStateMachine, Slewing to RA/Dec = 5.13668 (05h 08m
> 12.05s), 61.1958
> 3 (+61° 11' 45.0")
> 0029139 2019-03-23 16:16:13.074: Info, SafeSlewStateMachine, Starting Meridian Delay = 0.00
> 0029140 2019-03-23 16:16:13.074: Info, SafeSlewStateMachine, Start PierSide/CWUP = WEST, False
> 0029141 2019-03-23 16:16:13.074: Info, GetDestinationPierSide, RA,Dec,LST,EastMD,WestMD = 5.137,
> 61.196, 3.085,
> 0.000. 0.000: PS = WEST: CWUP = False
> 0029142 2019-03-23 16:16:13.074: Info, SafeSlewStateMachine, IsUnsafeSlew = False
> 0029143 2019-03-23 16:16:13.074: Info, SafeSlewStateMachine, END PierSide/CWUP = WEST, False
> 0029144 2019-03-23 16:16:13.074: Info, SafeSlewStateMachine, Ending Meridian Delay = 0.00
> 0029145 2019-03-23 16:16:13.075: Debug, SafeSlewStateMachine, New SafeSlew
State=StartPrimarySlew
> 0029146 2019-03-23 16:16:13.075: Info, ProcessVPortCommand, RX from VPort 1: :APCC,2749,GR#
> 0029147 2019-03-23 16:16:13.075: Info, ProcessVPortCommand, APCC Seq= 2749, CMD=GR#
> 0029148 2019-03-23 16:16:13.075: Info, VPortCheckVPort1(COM21), (RX: GR#), TX:
> APCC,11,2749,05:03:17.9#
> 0029149 2019-03-23 16:16:13.089: Debug, Command Thread, TX=':GM#'|RX='00:00:00.0#'
> 0029150 2019-03-23 16:16:13.089: Debug, Command Thread, TX = ':HRG#'
> 0029151 2019-03-23 16:16:13.121: Debug, Command Thread, TX=':HRG#'|RX='-1266*06:14#'
> 0029152 2019-03-23 16:16:13.121: Debug, Command Thread, TX = ':HDG#'
> 0029153 2019-03-23 16:16:13.136: Info, SafeSlewStateMachine, Slewing to RA/Dec = 5.1367, 61.1958
> 0029154 2019-03-23 16:16:13.136: Debug, SafeSlewStateMachine, New SafeSlew
> State=WaitStartPrimarySlew
> 0029155 2019-03-23 16:16:13.145: Debug, RestoreFormPosition, EmergencyStop: Restore = False
> 0029156 2019-03-23 16:16:13.145: Debug, RestoreFormPosition, EmergencyStop: Not restoring form -
option
> is disabled or CONTROL key is pressed
> 0029157 2019-03-23 16:16:13.153: Debug, Command Thread, TX=':HDG#'|RX='+4123*31:36#'
> 0029158 2019-03-23 16:16:13.153: Debug, Command Thread, TX = '#:GP#'
> 0029159 2019-03-23 16:16:13.185: Debug, Command Thread, TX='#:GP#'|RX='00:00:56.4#'
> 0029160 2019-03-23 16:16:13.185: Debug, Command Thread, TX = ':Rr#'
> 0029161 2019-03-23 16:16:13.201: Debug, Command Thread, TX=':Rr#'|RX='0#'
> 0029162 2019-03-23 16:16:13.201: Debug, Command Thread, TX = ':Rd#'
> 0029163 2019-03-23 16:16:13.217: Debug, Command Thread, TX=':Rd#'|RX='0#'
> 0029164 2019-03-23 16:16:13.217: Debug, Command Thread, TX = ':Sr05:08:12.1#'
> 0029165 2019-03-23 16:16:13.231: Info, VPort1(COM21), RX: :APCC,2750,GZ#
> 0029166 2019-03-23 16:16:13.249: Debug, Command Thread, TX=':Sr05:08:12.1#'|RX='1'
> 0029167 2019-03-23 16:16:13.249: Debug, Command Thread, TX = ':Sd+61*11:45#'
> 0029168 2019-03-23 16:16:13.262: Info, ProcessVPortCommand, RX from VPort 1: :APCC,2750,GZ#
> 0029169 2019-03-23 16:16:13.263: Info, ProcessVPortCommand, APCC Seq= 2750, CMD=GZ#
> 0029170 2019-03-23 16:16:13.263: Info, VPortCheckVPort1(COM21), (RX: GZ#), TX:
> APCC,10,2750,+27*06:40#
> 0029171 2019-03-23 16:16:13.265: Debug, Command Thread, TX=':Sd+61*11:45#'|RX='1'
> 0029172 2019-03-23 16:16:13.265: Debug, Command Thread, TX = ':M_S#'
> 0029173 2019-03-23 16:16:13.365: Exception, ProcessQAC: ComPort Read error. Sent=:M_S#, The
operation
> has timed out.
> 0029174 2019-03-23 16:16:13.365: Debug, Command Thread, TX=':M_S#'|RX=''
> 0029175 2019-03-23 16:16:13.366: Debug, Slew Start Callback, New SafeSlew State=WaitPrimarySlew
> 0029176 2019-03-23 16:16:13.366: Error, mySlewStarted, No response from mount
> ª
>
> I can send you a complete log if it would help - it is rather large so I didn't attach it here.
>
> Slews of around 60 arc-minutes or greater are working fine. I only noticed this because the precise slews
that
> Voyager were doing were failing to get within my threshold (60 arc-seconds). The plate solve/sync was
successful
> but then when the slew was requested the mount simply didn't move the small distance required.
>
> I went back to 1.7.0.10 and it is working fine.
>
> Thank You,
> Michael Fulbright
>
>
> On 3/17/19 6:53 PM, 'Ray Gralak (Groups)' groups3@gralak.com [ap-gto] wrote:
>
>
>
>
> Astro-Physics would like to thank everyone that helped with beta testing and to announce the availability
of
> the public RELEASE version of APCC Standard v1.7.1.0 and APCC Pro v1.7..1.1. Please use these
versions with
> the latest AP V2 ASCOM driver, v5.20.09.
>
> The direct download links are as follows:
>
> AP V2 ASCOM Driver (Released February 11, 2019)
> https://www.siriusimaging.com/apdriver/AstroPhysics_V2_Setup_5.20.09.exe
>
> APCC Standard v1.7.1.0 (Released March 14, 2019)
> http://www.apastrosoftware.com/apcc_download/APCC_Standard_Setup_1.7.1.0.exe
>
> APCC Pro v1.7.1.1 (Released March 14, 2019)
> http://www.apastrosoftware.com/apcc_download/APCC_Pro_Setup_1.7.1.1.exe
>
> APCC version history can be found here:
> https://www.siriusimaging.com/Help/APCC/version_history.htm
>
> If you see any issues please post them here and be prepared to share log files and a way to reproduce
an
> issue exactly.
>
> Thank you!
>
> -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
>
>
>
>
>





Michael Fulbright <mike.fulbright@...>
 

Thanks Ray I'll get around to the upgrade soon.  Just need to finish this run of nights through the weekend without any hiccups...

Michael

On 3/23/19 5:45 PM, 'Ray Gralak (Groups)' groups3@... [ap-gto] wrote:
 

> Understood - I have the latest ASCOM but not the latest firmware.
> I will stick with the 1.7.0.10 APCC for now
> since it has been working well.

I think that is risky. The latest firmware has a important fixes and has been in use for a while now. Also, there have been a number of important bug fixes to APCC. The version you are running is a BETA version.

BTW, the M_S slew command that is not responding in your log is most useful when the mount is in a counterweight-up position. It will keep the mount from slewing to the meridian and back again to the counterweight up position.. It doesn't do anything different for counterweight down slews.

-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@... [mailto:ap-gto@...]
> Sent: Saturday, March 23, 2019 2:32 PM
> To: ap-gto@...
> Subject: Re: [ap-gto] New Released versions of APCC Standard/Pro (v1.7..1.0 / v1.7.1.1)
>
>
>
> Understood - I have the latest ASCOM but not the latest firmware. I will stick with the 1.7.0.10 APCC for now
> since it has been working well.
>
> Might want to consider flagging if a given APCC release level requires a certain level of firmware with a popup on
> startup if that level isn't detected.
>
> Since everything has been working for quite awhile I tend not to upgrade unless the release notes flag a high
> severity bug has been discovered and fixed.
>
> Thanks,
> Michael Fulbright
>
>
> On 3/23/19 5:23 PM, 'Ray Gralak (Groups)' groups3@... [ap-gto] wrote:
>
>
>
>
> Hi Michael,
>
> If the mount is timing out is not necessarily a bug in APCC. It suggests you may be running old firmware
> and so the mount doesn't understand the command. Please make sure you have the latest GTOCP4 firmware
> installed and also the latest AP V2 ASCOM driver.
>
> -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@... [mailto:ap-gto@...]
> > Sent: Saturday, March 23, 2019 1:33 PM
> > To: ap-gto@...
> > Subject: Re: [ap-gto] New Released versions of APCC Standard/Pro (v1.7..1.0 / v1.7.1.1)
> >
> >
> >
> > Ray,
> >
> > I've encountered what may be an issue with 1.7.1.0 versus 1.7.0.10 Standard.
> >
> > I discovered it last night after upgrading to 1.7.1.0. Slews will work if the distance is over around 60 arc-
> minutes
> > but slews smaller than this fail and the log exception is:
> >
> > 0029137 2019-03-23 16:16:13.074: Info, SafeSlewStateMachine, Slewing from RA/Dec = 5.05497 (05h
> 03m
> > 17.90s), 61.1058
> > 3 (+61° 06' 21.0")
> > 0029138 2019-03-23 16:16:13.074: Info, SafeSlewStateMachine, Slewing to RA/Dec = 5.13668 (05h 08m
> > 12.05s), 61.1958
> > 3 (+61° 11' 45.0")
> > 0029139 2019-03-23 16:16:13.074: Info, SafeSlewStateMachine, Starting Meridian Delay = 0.00
> > 0029140 2019-03-23 16:16:13.074: Info, SafeSlewStateMachine, Start PierSide/CWUP = WEST, False
> > 0029141 2019-03-23 16:16:13.074: Info, GetDestinationPierSide, RA,Dec,LST,EastMD,WestMD = 5.137,
> > 61.196, 3.085,
> > 0.000. 0.000: PS = WEST: CWUP = False
> > 0029142 2019-03-23 16:16:13.074: Info, SafeSlewStateMachine, IsUnsafeSlew = False
> > 0029143 2019-03-23 16:16:13.074: Info, SafeSlewStateMachine, END PierSide/CWUP = WEST, False
> > 0029144 2019-03-23 16:16:13.074: Info, SafeSlewStateMachine, Ending Meridian Delay = 0.00
> > 0029145 2019-03-23 16:16:13.075: Debug, SafeSlewStateMachine, New SafeSlew
> State=StartPrimarySlew
> > 0029146 2019-03-23 16:16:13.075: Info, ProcessVPortCommand, RX from VPort 1: :APCC,2749,GR#
> > 0029147 2019-03-23 16:16:13.075: Info, ProcessVPortCommand, APCC Seq= 2749, CMD=GR#
> > 0029148 2019-03-23 16:16:13.075: Info, VPortCheckVPort1(COM21), (RX: GR#), TX:
> > APCC,11,2749,05:03:17.9#
> > 0029149 2019-03-23 16:16:13.089: Debug, Command Thread, TX=':GM#'|RX='00:00:00.0#'
> > 0029150 2019-03-23 16:16:13.089: Debug, Command Thread, TX = ':HRG#'
> > 0029151 2019-03-23 16:16:13.121: Debug, Command Thread, TX=':HRG#'|RX='-1266*06:14#'
> > 0029152 2019-03-23 16:16:13.121: Debug, Command Thread, TX = ':HDG#'
> > 0029153 2019-03-23 16:16:13.136: Info, SafeSlewStateMachine, Slewing to RA/Dec = 5.1367, 61.1958
> > 0029154 2019-03-23 16:16:13.136: Debug, SafeSlewStateMachine, New SafeSlew
> > State=WaitStartPrimarySlew
> > 0029155 2019-03-23 16:16:13.145: Debug, RestoreFormPosition, EmergencyStop: Restore = False
> > 0029156 2019-03-23 16:16:13.145: Debug, RestoreFormPosition, EmergencyStop: Not restoring form -
> option
> > is disabled or CONTROL key is pressed
> > 0029157 2019-03-23 16:16:13.153: Debug, Command Thread, TX=':HDG#'|RX='+4123*31:36#'
> > 0029158 2019-03-23 16:16:13.153: Debug, Command Thread, TX = '#:GP#'
> > 0029159 2019-03-23 16:16:13.185: Debug, Command Thread, TX='#:GP#'|RX='00:00:56.4#'
> > 0029160 2019-03-23 16:16:13.185: Debug, Command Thread, TX = ':Rr#'
> > 0029161 2019-03-23 16:16:13.201: Debug, Command Thread, TX=':Rr#'|RX='0#'
> > 0029162 2019-03-23 16:16:13.201: Debug, Command Thread, TX = ':Rd#'
> > 0029163 2019-03-23 16:16:13.217: Debug, Command Thread, TX=':Rd#'|RX='0#'
> > 0029164 2019-03-23 16:16:13.217: Debug, Command Thread, TX = ':Sr05:08:12.1#'
> > 0029165 2019-03-23 16:16:13.231: Info, VPort1(COM21), RX: :APCC,2750,GZ#
> > 0029166 2019-03-23 16:16:13.249: Debug, Command Thread, TX=':Sr05:08:12.1#'|RX='1'
> > 0029167 2019-03-23 16:16:13.249: Debug, Command Thread, TX = ':Sd+61*11:45#'
> > 0029168 2019-03-23 16:16:13.262: Info, ProcessVPortCommand, RX from VPort 1: :APCC,2750,GZ#
> > 0029169 2019-03-23 16:16:13.263: Info, ProcessVPortCommand, APCC Seq= 2750, CMD=GZ#
> > 0029170 2019-03-23 16:16:13.263: Info, VPortCheckVPort1(COM21), (RX: GZ#), TX:
> > APCC,10,2750,+27*06:40#
> > 0029171 2019-03-23 16:16:13.265: Debug, Command Thread, TX=':Sd+61*11:45#'|RX='1'
> > 0029172 2019-03-23 16:16:13.265: Debug, Command Thread, TX = ':M_S#'
> > 0029173 2019-03-23 16:16:13.365: Exception, ProcessQAC: ComPort Read error. Sent=:M_S#, The
> operation
> > has timed out.
> > 0029174 2019-03-23 16:16:13.365: Debug, Command Thread, TX=':M_S#'|RX=''
> > 0029175 2019-03-23 16:16:13.366: Debug, Slew Start Callback, New SafeSlew State=WaitPrimarySlew
> > 0029176 2019-03-23 16:16:13.366: Error, mySlewStarted, No response from mount
> > ª
> >
> > I can send you a complete log if it would help - it is rather large so I didn't attach it here.
> >
> > Slews of around 60 arc-minutes or greater are working fine. I only noticed this because the precise slews
> that
> > Voyager were doing were failing to get within my threshold (60 arc-seconds). The plate solve/sync was
> successful
> > but then when the slew was requested the mount simply didn't move the small distance required.
> >
> > I went back to 1.7.0.10 and it is working fine.
> >
> > Thank You,
> > Michael Fulbright
> >
> >
> > On 3/17/19 6:53 PM, 'Ray Gralak (Groups)' groups3@gralak..com [ap-gto] wrote:
> >
> >
> >
> >
> > Astro-Physics would like to thank everyone that helped with beta testing and to announce the availability
> of
> > the public RELEASE version of APCC Standard v1.7.1.0 and APCC Pro v1.7..1.1. Please use these
> versions with
> > the latest AP V2 ASCOM driver, v5.20.09.
> >
> > The direct download links are as follows:
> >
> > AP V2 ASCOM Driver (Released February 11, 2019)
> > https://www.siriusimaging.com/apdriver/AstroPhysics_V2_Setup_5.20.09.exe
> >
> > APCC Standard v1.7.1.0 (Released March 14, 2019)
> > http://www.apastrosoftware.com/apcc_download/APCC_Standard_Setup_1.7.1.0.exe
> >
> > APCC Pro v1.7.1.1 (Released March 14, 2019)
> > http://www.apastrosoftware.com/apcc_download/APCC_Pro_Setup_1.7.1.1.exe
> >
> > APCC version history can be found here:
> > https://www.siriusimaging.com/Help/APCC/version_history.htm
> >
> > If you see any issues please post them here and be prepared to share log files and a way to reproduce
> an
> > issue exactly.
> >
> > Thank you!
> >
> > -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
> >
> >
> >
> >
> >
>
>
>
>
>