Date   

Re: Communications Error Messages in AP Ascom Driver

Don Anderson
 

I tried increasing the timeout to 500. Didn't solve the problem. I also tried a different USB port. No change.
I then went in and looked at one of the logs. I see two error messages that keep popping up.
First is:
Telescope: Warning: Retransmits: then a number
The second which follows the telescope warning retransmits is:
Driver: Error: Comandboot : No response or bad response:  ' : APCC#' , Response= ' '  -> Retrying!
Then you get three lines under "info" Command Clear ()
                                                  "info" Remove 0 bytes in 266 ticks
  "info"  Commandboot  TX=:APCC# '
Then you get the Warning Retransmit: then a number again followed by the line

Driver: Error: Comandboot: No response or bad response: APCC#' , Response= ' ' -> Giving up!
This series or messages will repeat throughout the driver log at appros 1 minute intervals the entire log. I assume the Command Clear () entry is when I clear the error in the driver.
It looks to me like the driver is looking for APCC which I don't have.
Hope this helps
 


Re: Defective CP4 control box

Dale Ghent
 

The power cable that plugs into the CP4 has a Anderson PowerPole connector on the end. This is a common low voltage DC connector that comes from the world of ham radio gear, and is designed to be easy to use, reliable, and quick to make in the field. You can make or buy any number of adaptor cables for it, such as those in the CABPP4SET cable set that AP sells. This way, AP can manufacture and ship one cable for the CP4 and the user can make or buys the other end of that cable that is appropriate for their particular power supplies, with the PowerPole being the common, standard connector between the two.

At any rate, as with Ray's suggestion, calling Astro-Physics and talking to Howard or George would be your best course to getting this resolved.

/dale

On Mar 26, 2019, at 8:15 AM, Joe Renzetti axnyslie@... [ap-gto] <ap-gto@...> wrote:



I can’t do that because of the way the CP4 was designed, with an odd connection cable that doesn’t work with anything but my dedicated power supply. It is a LiFePO4 20ah battery it is highly unlikely to be the problem as it worked for a yes with no issues and is always fully charged for each use.

On Mar 26, 2019, at 7:52 AM, 'Ray Gralak (Groups)' groups3@... [ap-gto] <ap-gto@...> wrote:

Hi Joe,

I wrote:
WiFi problems could indicate interference from nearby sources.
Joe wrote:
It was not interference as I was at a remote dark sight with no WIFI I
couldn’t even get phone service there. That also doesn’t explain the
fact that slew control doesn’t work when WIFI is connected or the
fact the Keypad didn’t work either.
Okay, low voltage can also cause issues. Assuming you tried this, did you also experience the same problems when powering the mount via a regulated power supply?

-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: Tuesday, March 26, 2019 3:52 AM
To: ap-gto@...
Subject: Re: [ap-gto] Defective CP4 control box



It was not interference as I was at a remote dark sight with no WIFI I couldn’t even get phone service there. That also
doesn’t explain the fact that slew control doesn’t work when WIFI is connected or the fact the Keypad didn’t work
either.

Joe

On Mar 26, 2019, at 12:33 AM, 'Ray Gralak (Groups)' groups3@... [ap-gto] <ap-gto@...>
wrote:





HI Joe,

WiFi problems could indicate interference from nearby sources.

As for ASCOM, try looking at COM ports in device manager. When you plug the mount's USB cable into your
computer a COM port should be created. That's the port to which you need to configure APCC to connect.

-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: Monday, March 25, 2019 8:15 PM
To: ap-gto@yahoogroups..com
Subject: [ap-gto] Defective CP4 control box



After several nights of failed troubleshooting I have contended that my CP4 control box is defective. My
Keypad
controller was not working with it, the East and West RA slew would always stick and stall. AP received it last
Wednesday but nobody has contacted me about it since. Now I believe it may have been the CP4 all along
that was
the problem is it has many issues. I have tried to run the 1100 with SkySafari and Luminos and both were
very
problematic. The WIFI connection would constantly drop connections. It would require cycling the mount's
power
supply battery to make the WIFI appear again only to lose the connection after a few minutes. The centering
slew
commands are very unresponsive on both apps and no less that four times I have to yank the power cable in
a panic
because of runaway slews that could not be stopped. ASCOM does not work at all on USB. I tried literally
ever COM
port available only to get mount not found error messages. So can someone at A stro-Physics please contact
me
ASAP on how to rectify this problem.




Joe






Re: Defective CP4 control box

Ray Gralak
 

I also followed troubleshooting through Device Manager to find the CP4 and it will not
find the mount on any of the laptop’s USB ports
Okay, it's probably best if you give A-P a call during their business hours and talk to Howard or George. Have the laptop and mount at hand (with hopefully a regulated power source!).

-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: Tuesday, March 26, 2019 5:57 AM
To: ap-gto@...
Subject: Re: [ap-gto] Defective CP4 control box



I also followed troubleshooting through Device Manager to find the CP4 and it will not find the mount on any of the
laptop’s USB ports

On Mar 26, 2019, at 7:52 AM, 'Ray Gralak (Groups)' groups3@... [ap-gto] <ap-gto@...>
wrote:





Hi Joe,

I wrote:
>> WiFi problems could indicate interference from nearby sources.

Joe wrote:
> It was not interference as I was at a remote dark sight with no WIFI I
> couldn’t even get phone service there. That also doesn’t explain the
> fact that slew control doesn’t work when WIFI is connected or the
> fact the Keypad didn’t work either.

Okay, low voltage can also cause issues. Assuming you tried this, did you also experience the same problems
when powering the mount via a regulated power supply?

-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: Tuesday, March 26, 2019 3:52 AM
> To: ap-gto@...
> Subject: Re: [ap-gto] Defective CP4 control box
>
>
>
> It was not interference as I was at a remote dark sight with no WIFI I couldn’t even get phone service there.
That also
> doesn’t explain the fact that slew control doesn’t work when WIFI is connected or the fact the Keypad didn’t
work
> either.
>
> Joe
>
> On Mar 26, 2019, at 12:33 AM, 'Ray Gralak (Groups)' groups3@... [ap-gto] <ap-
gto@...>
> wrote:
>
>
>
>
>
> HI Joe,
>
> WiFi problems could indicate interference from nearby sources.
>
> As for ASCOM, try looking at COM ports in device manager. When you plug the mount's USB cable into your
> computer a COM port should be created. That's the port to which you need to configure APCC to connect.
>
> -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: Monday, March 25, 2019 8:15 PM
> > To: ap-gto@yahoogroups..com <mailto:ap-gto@...>
> > Subject: [ap-gto] Defective CP4 control box
> >
> >
> >
> > After several nights of failed troubleshooting I have contended that my CP4 control box is defective. My
> Keypad
> > controller was not working with it, the East and West RA slew would always stick and stall. AP received it
last
> > Wednesday but nobody has contacted me about it since. Now I believe it may have been the CP4 all along
> that was
> > the problem is it has many issues. I have tried to run the 1100 with SkySafari and Luminos and both were
> very
> > problematic. The WIFI connection would constantly drop connections. It would require cycling the mount's
> power
> > supply battery to make the WIFI appear again only to lose the connection after a few minutes. The centering
> slew
> > commands are very unresponsive on both apps and no less that four times I have to yank the power cable
in
> a panic
> > because of runaway slews that could not be stopped. ASCOM does not work at all on USB. I tried literally
> ever COM
> > port available only to get mount not found error messages. So can someone at A stro-Physics please
contact
> me
> > ASAP on how to rectify this problem.
> >
> >
> >
> >
> > Joe
> >
> >
> >
>
>
>
>




Re: Defective CP4 control box

Joe Renzetti <axnyslie@...>
 

I also followed troubleshooting through Device Manager to find the CP4 and it will not find the mount on any of the laptop’s USB ports

On Mar 26, 2019, at 7:52 AM, 'Ray Gralak (Groups)' groups3@... [ap-gto] <ap-gto@...> wrote:

 

Hi Joe,

I wrote:
>> WiFi problems could indicate interference from nearby sources.

Joe wrote:
> It was not interference as I was at a remote dark sight with no WIFI I
> couldn’t even get phone service there. That also doesn’t explain the
> fact that slew control doesn’t work when WIFI is connected or the
> fact the Keypad didn’t work either.

Okay, low voltage can also cause issues. Assuming you tried this, did you also experience the same problems when powering the mount via a regulated power supply?

-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: Tuesday, March 26, 2019 3:52 AM
> To: ap-gto@...
> Subject: Re: [ap-gto] Defective CP4 control box
>
>
>
> It was not interference as I was at a remote dark sight with no WIFI I couldn’t even get phone service there. That also
> doesn’t explain the fact that slew control doesn’t work when WIFI is connected or the fact the Keypad didn’t work
> either.
>
> Joe
>
> On Mar 26, 2019, at 12:33 AM, 'Ray Gralak (Groups)' groups3@... [ap-gto] <ap-gto@...>
> wrote:
>
>
>
>
>
> HI Joe,
>
> WiFi problems could indicate interference from nearby sources.
>
> As for ASCOM, try looking at COM ports in device manager. When you plug the mount's USB cable into your
> computer a COM port should be created. That's the port to which you need to configure APCC to connect.
>
> -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: Monday, March 25, 2019 8:15 PM
> > To: ap-gto@...
> > Subject: [ap-gto] Defective CP4 control box
> >
> >
> >
> > After several nights of failed troubleshooting I have contended that my CP4 control box is defective. My
> Keypad
> > controller was not working with it, the East and West RA slew would always stick and stall. AP received it last
> > Wednesday but nobody has contacted me about it since. Now I believe it may have been the CP4 all along
> that was
> > the problem is it has many issues. I have tried to run the 1100 with SkySafari and Luminos and both were
> very
> > problematic. The WIFI connection would constantly drop connections. It would require cycling the mount's
> power
> > supply battery to make the WIFI appear again only to lose the connection after a few minutes. The centering
> slew
> > commands are very unresponsive on both apps and no less that four times I have to yank the power cable in
> a panic
> > because of runaway slews that could not be stopped. ASCOM does not work at all on USB. I tried literally
> ever COM
> > port available only to get mount not found error messages. So can someone at A stro-Physics please contact
> me
> > ASAP on how to rectify this problem.
> >
> >
> >
> >
> > Joe
> >
> >
> >
>
>
>
>


Re: Defective CP4 control box

Ray Gralak
 

I can’t do that because of the way the CP4 was designed, with an odd connection cable that doesn’t work with
anything but my dedicated power supply.
I have a CP4 on two of my own mounts and one on my desktop for development. The cable is a two-piece design that can come apart so that you can use different adapter cables into a power source. For instance to power my mounts I use the cigarette lighter plug cable/adapter into a Pyramid PS-15KX regulated power supply, which is plugged into a 120V outlet.

-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: Tuesday, March 26, 2019 5:16 AM
To: ap-gto@...
Subject: Re: [ap-gto] Defective CP4 control box



I can’t do that because of the way the CP4 was designed, with an odd connection cable that doesn’t work with
anything but my dedicated power supply. It is a LiFePO4 20ah battery it is highly unlikely to be the problem as it
worked for a yes with no issues and is always fully charged for each use.

On Mar 26, 2019, at 7:52 AM, 'Ray Gralak (Groups)' groups3@... [ap-gto] <ap-gto@...>
wrote:





Hi Joe,

I wrote:
>> WiFi problems could indicate interference from nearby sources.

Joe wrote:
> It was not interference as I was at a remote dark sight with no WIFI I
> couldn’t even get phone service there. That also doesn’t explain the
> fact that slew control doesn’t work when WIFI is connected or the
> fact the Keypad didn’t work either.

Okay, low voltage can also cause issues. Assuming you tried this, did you also experience the same problems
when powering the mount via a regulated power supply?

-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: Tuesday, March 26, 2019 3:52 AM
> To: ap-gto@...
> Subject: Re: [ap-gto] Defective CP4 control box
>
>
>
> It was not interference as I was at a remote dark sight with no WIFI I couldn’t even get phone service there.
That also
> doesn’t explain the fact that slew control doesn’t work when WIFI is connected or the fact the Keypad didn’t
work
> either.
>
> Joe
>
> On Mar 26, 2019, at 12:33 AM, 'Ray Gralak (Groups)' groups3@... [ap-gto] <ap-
gto@...>
> wrote:
>
>
>
>
>
> HI Joe,
>
> WiFi problems could indicate interference from nearby sources.
>
> As for ASCOM, try looking at COM ports in device manager. When you plug the mount's USB cable into your
> computer a COM port should be created. That's the port to which you need to configure APCC to connect.
>
> -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: Monday, March 25, 2019 8:15 PM
> > To: ap-gto@yahoogroups..com <mailto:ap-gto@...>
> > Subject: [ap-gto] Defective CP4 control box
> >
> >
> >
> > After several nights of failed troubleshooting I have contended that my CP4 control box is defective. My
> Keypad
> > controller was not working with it, the East and West RA slew would always stick and stall. AP received it
last
> > Wednesday but nobody has contacted me about it since. Now I believe it may have been the CP4 all along
> that was
> > the problem is it has many issues. I have tried to run the 1100 with SkySafari and Luminos and both were
> very
> > problematic. The WIFI connection would constantly drop connections. It would require cycling the mount's
> power
> > supply battery to make the WIFI appear again only to lose the connection after a few minutes. The centering
> slew
> > commands are very unresponsive on both apps and no less that four times I have to yank the power cable
in
> a panic
> > because of runaway slews that could not be stopped. ASCOM does not work at all on USB. I tried literally
> ever COM
> > port available only to get mount not found error messages. So can someone at A stro-Physics please
contact
> me
> > ASAP on how to rectify this problem.
> >
> >
> >
> >
> > Joe
> >
> >
> >
>
>
>
>




Re: Defective CP4 control box

Joe Renzetti <axnyslie@...>
 

I can’t do that because of the way the CP4 was designed, with an odd connection cable that doesn’t work with anything but my dedicated power supply. It is a LiFePO4 20ah battery it is highly unlikely to be the problem as it worked for a yes with no issues and is always fully charged for each use.

On Mar 26, 2019, at 7:52 AM, 'Ray Gralak (Groups)' groups3@... [ap-gto] <ap-gto@...> wrote:

 

Hi Joe,

I wrote:
>> WiFi problems could indicate interference from nearby sources.

Joe wrote:
> It was not interference as I was at a remote dark sight with no WIFI I
> couldn’t even get phone service there. That also doesn’t explain the
> fact that slew control doesn’t work when WIFI is connected or the
> fact the Keypad didn’t work either.

Okay, low voltage can also cause issues. Assuming you tried this, did you also experience the same problems when powering the mount via a regulated power supply?

-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: Tuesday, March 26, 2019 3:52 AM
> To: ap-gto@...
> Subject: Re: [ap-gto] Defective CP4 control box
>
>
>
> It was not interference as I was at a remote dark sight with no WIFI I couldn’t even get phone service there. That also
> doesn’t explain the fact that slew control doesn’t work when WIFI is connected or the fact the Keypad didn’t work
> either.
>
> Joe
>
> On Mar 26, 2019, at 12:33 AM, 'Ray Gralak (Groups)' groups3@... [ap-gto] <ap-gto@...>
> wrote:
>
>
>
>
>
> HI Joe,
>
> WiFi problems could indicate interference from nearby sources.
>
> As for ASCOM, try looking at COM ports in device manager. When you plug the mount's USB cable into your
> computer a COM port should be created. That's the port to which you need to configure APCC to connect.
>
> -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: Monday, March 25, 2019 8:15 PM
> > To: ap-gto@...
> > Subject: [ap-gto] Defective CP4 control box
> >
> >
> >
> > After several nights of failed troubleshooting I have contended that my CP4 control box is defective. My
> Keypad
> > controller was not working with it, the East and West RA slew would always stick and stall. AP received it last
> > Wednesday but nobody has contacted me about it since. Now I believe it may have been the CP4 all along
> that was
> > the problem is it has many issues. I have tried to run the 1100 with SkySafari and Luminos and both were
> very
> > problematic. The WIFI connection would constantly drop connections. It would require cycling the mount's
> power
> > supply battery to make the WIFI appear again only to lose the connection after a few minutes. The centering
> slew
> > commands are very unresponsive on both apps and no less that four times I have to yank the power cable in
> a panic
> > because of runaway slews that could not be stopped. ASCOM does not work at all on USB. I tried literally
> ever COM
> > port available only to get mount not found error messages. So can someone at A stro-Physics please contact
> me
> > ASAP on how to rectify this problem.
> >
> >
> >
> >
> > Joe
> >
> >
> >
>
>
>
>


Re: Defective CP4 control box

Ray Gralak
 

Hi Joe,

I wrote:
WiFi problems could indicate interference from nearby sources.
Joe wrote:
It was not interference as I was at a remote dark sight with no WIFI I
couldn’t even get phone service there. That also doesn’t explain the
fact that slew control doesn’t work when WIFI is connected or the
fact the Keypad didn’t work either.
Okay, low voltage can also cause issues. Assuming you tried this, did you also experience the same problems when powering the mount via a regulated power supply?

-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: Tuesday, March 26, 2019 3:52 AM
To: ap-gto@...
Subject: Re: [ap-gto] Defective CP4 control box



It was not interference as I was at a remote dark sight with no WIFI I couldn’t even get phone service there. That also
doesn’t explain the fact that slew control doesn’t work when WIFI is connected or the fact the Keypad didn’t work
either.

Joe

On Mar 26, 2019, at 12:33 AM, 'Ray Gralak (Groups)' groups3@... [ap-gto] <ap-gto@...>
wrote:





HI Joe,

WiFi problems could indicate interference from nearby sources.

As for ASCOM, try looking at COM ports in device manager. When you plug the mount's USB cable into your
computer a COM port should be created. That's the port to which you need to configure APCC to connect.

-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: Monday, March 25, 2019 8:15 PM
> To: ap-gto@...
> Subject: [ap-gto] Defective CP4 control box
>
>
>
> After several nights of failed troubleshooting I have contended that my CP4 control box is defective. My
Keypad
> controller was not working with it, the East and West RA slew would always stick and stall. AP received it last
> Wednesday but nobody has contacted me about it since. Now I believe it may have been the CP4 all along
that was
> the problem is it has many issues. I have tried to run the 1100 with SkySafari and Luminos and both were
very
> problematic. The WIFI connection would constantly drop connections. It would require cycling the mount's
power
> supply battery to make the WIFI appear again only to lose the connection after a few minutes. The centering
slew
> commands are very unresponsive on both apps and no less that four times I have to yank the power cable in
a panic
> because of runaway slews that could not be stopped. ASCOM does not work at all on USB. I tried literally
ever COM
> port available only to get mount not found error messages. So can someone at A stro-Physics please contact
me
> ASAP on how to rectify this problem.
>
>
>
>
> Joe
>
>
>




Re: Defective CP4 control box

Joe Renzetti <axnyslie@...>
 

It was not interference as I was at a remote dark sight with no WIFI I couldn’t even get phone service there. That also doesn’t explain the fact that slew control doesn’t work when WIFI is connected or the fact the Keypad didn’t work either.

Joe

On Mar 26, 2019, at 12:33 AM, 'Ray Gralak (Groups)' groups3@... [ap-gto] <ap-gto@...> wrote:

 

HI Joe,

WiFi problems could indicate interference from nearby sources.

As for ASCOM, try looking at COM ports in device manager. When you plug the mount's USB cable into your computer a COM port should be created. That's the port to which you need to configure APCC to connect.

-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: Monday, March 25, 2019 8:15 PM
> To: ap-gto@...
> Subject: [ap-gto] Defective CP4 control box
>
>
>
> After several nights of failed troubleshooting I have contended that my CP4 control box is defective. My Keypad
> controller was not working with it, the East and West RA slew would always stick and stall. AP received it last
> Wednesday but nobody has contacted me about it since. Now I believe it may have been the CP4 all along that was
> the problem is it has many issues. I have tried to run the 1100 with SkySafari and Luminos and both were very
> problematic. The WIFI connection would constantly drop connections. It would require cycling the mount's power
> supply battery to make the WIFI appear again only to lose the connection after a few minutes. The centering slew
> commands are very unresponsive on both apps and no less that four times I have to yank the power cable in a panic
> because of runaway slews that could not be stopped. ASCOM does not work at all on USB. I tried literally ever COM
> port available only to get mount not found error messages. So can someone at A stro-Physics please contact me
> ASAP on how to rectify this problem.
>
>
>
>
> Joe
>
>
>


Re: Defective CP4 control box

Ray Gralak
 

HI Joe,

WiFi problems could indicate interference from nearby sources.

As for ASCOM, try looking at COM ports in device manager. When you plug the mount's USB cable into your computer a COM port should be created. That's the port to which you need to configure APCC to connect.

-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: Monday, March 25, 2019 8:15 PM
To: ap-gto@...
Subject: [ap-gto] Defective CP4 control box



After several nights of failed troubleshooting I have contended that my CP4 control box is defective. My Keypad
controller was not working with it, the East and West RA slew would always stick and stall. AP received it last
Wednesday but nobody has contacted me about it since. Now I believe it may have been the CP4 all along that was
the problem is it has many issues. I have tried to run the 1100 with SkySafari and Luminos and both were very
problematic. The WIFI connection would constantly drop connections. It would require cycling the mount's power
supply battery to make the WIFI appear again only to lose the connection after a few minutes. The centering slew
commands are very unresponsive on both apps and no less that four times I have to yank the power cable in a panic
because of runaway slews that could not be stopped. ASCOM does not work at all on USB. I tried literally ever COM
port available only to get mount not found error messages. So can someone at A stro-Physics please contact me
ASAP on how to rectify this problem.




Joe



Re: Communications Error Messages in AP Ascom Driver

Ray Gralak
 

Hi Don,

Any ideas what's wrong?
Try increasing the timeout value in the driver to see if that makes a difference. Also, try using a different USB port on your laptop if you can.

If the problem still happens, take a look at your log file and search for the words "error", then "exception". That might provide a clue as to what commands are timing out.

-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: Monday, March 25, 2019 7:38 PM
To: ap-gto@...
Subject: [ap-gto] Communications Error Messages in AP Ascom Driver



I set up my AP 900 GOTO CP3 with version V firmware rig in my basement last night to do some software and
firmware upgrades last night on my two laptops (main unit Lenovo i7 Win 10 home with 8 gig ram, backup unit Sony
Vaio i5 Win 7 pro with 4 gig ram. I started with my old but trusty Win 7 Pro Sony Vaio laptop which has worked trouble
free for years. I updated the AP Ascom driver to the latest 5.20.09 version and did some firmware updates on my
focuser hub. When I started everything up, everything worked fine but after a minute or so I got the flashing yellow
panel at the top of the driver indicating communication errors. I opened the driver extension windows to the final one
and did a reset. Again after a minute or so the yellow warning flashed again. I then rebooted the computer and had the
same result. I tried uninstalling the driver and reinstalling. Same problem. I rolled back to different older versions
(5.20.08 then 5.10.02) of the driver but had the same pr oblem. I then tried my Lenovo and had the same
communication error warning popping up in the driver every minute or so.

My current hardware configuration is to run the mount through a Keyspan Triplite 19HS (FTDI) singe port USB to serial
converter connected to a 7 port powered USB hub to which the mount, focuser, main and guide cameras and filter
wheel are connected. I connect the powered hub to the laptop with either a 10' usb cable or a 65' powered usb cable
depending on where I am. I was using the 10' cable last night. The mount has its own dedicated pyramid 5 amp power
supply.

The above setup has has worked trouble free for years. However, suspecting a hub problem, I disconnected the hub
and all accessory equipment and ran the mount directly to the laptop via th e Keyspan 19HS serial to USB converter. I
had no other device connected at this point. Same problem occurred. I then swapped out the existing Keyspan unit
with a new spare unit that I had, and tried a different 10' USB cable as well. Same problem with communication error
messages popping up after about a minute. Even with the communication errors, things seem to work ok though.
Mount slews to objects in both The SKY 6 and MaximDL 6.08. I then tried cleaning all the relevant electrical plugs and
contacts with contact cleaner. Didn't help.

Any ideas what's wrong?

Don Anderson


Re: Communications Error Messages in AP Ascom Driver

Don Anderson
 

Hi Keith
Yes I am using the latest Ascom platform. As I said in my post, everything was working well last November when I used my rig last. It's strange that both the Win 7 and Win 10 laptops have the same problem. Both were working well last fall. Here is another twist to the story. I just finished setting up all my software on my old desktop machine which has Win 10 Pro installed. The driver works perfectly on it! I checked the driver config settings and they are the same on all three machines. Go figure!
Don


Defective CP4 control box

axnyslie@...
 

After several nights of failed troubleshooting I have contended that my CP4 control box is defective. My Keypad controller was not working with it, the East and West RA slew would always stick and stall. AP received it last Wednesday but nobody has contacted me about it since. Now I believe it may have been the CP4 all along that was the problem is it has many issues. I have tried to run the 1100 with SkySafari and Luminos and both were very problematic. The WIFI connection would constantly drop connections. It would require cycling the mount's power supply battery to make the WIFI appear again only to lose the connection after a few minutes. The centering slew commands are very unresponsive on both apps and no less that four times I have to yank the power cable in a panic because of runaway slews that could not be stopped. ASCOM does not work at all on USB. I tried literally ever COM port available only to get mount not found error messages. So can someone at Astro-Physics please contact me ASAP on how to rectify this problem.


Joe


Re: Communications Error Messages in AP Ascom Driver

mogollonobs
 

Hi Don,

Sorry to hear of your troubles. You using the current ASCOM Platform 6.4SP1? The reason I ask is that I had an issue, although different, before I updated the platform.

Hope you get it sorted out,
Keith


Communications Error Messages in AP Ascom Driver

Don Anderson
 

I set up my AP 900 GOTO CP3 with version V firmware rig in my basement last night to do some software and firmware upgrades last night on my two laptops (main unit Lenovo i7 Win 10 home with 8 gig ram, backup unit Sony Vaio i5 Win 7 pro with 4 gig ram. I started with my old but trusty Win 7 Pro Sony Vaio laptop which has worked trouble free for years. I updated the AP Ascom driver to the latest 5.20.09 version and did some firmware updates on my focuser hub. When I started everything up, everything worked fine but after a minute or so I got the flashing yellow panel at the top of the driver indicating communication errors. I opened the driver extension windows to the final one and did a reset. Again after a minute or so the yellow warning flashed again. I then rebooted the computer and had the same result. I tried uninstalling the driver and reinstalling. Same problem. I rolled back to different older versions (5.20.08 then 5.10.02) of the driver but had the same problem. I then tried my Lenovo and had the same communication error warning popping up in the driver every minute or so. 

My current hardware configuration is to run the mount through a Keyspan Triplite 19HS (FTDI) singe port USB to serial converter connected to a 7 port powered USB hub to which the mount, focuser, main and guide cameras and filter wheel are connected. I connect the powered hub to the laptop with either a 10' usb cable or a 65' powered usb cable depending on where I am. I was using the 10' cable last night. The mount has its own dedicated pyramid 5 amp power supply.

The above setup has has worked trouble free for years. However, suspecting a hub problem, I disconnected the hub and all accessory equipment and ran the mount directly to the laptop via the Keyspan 19HS serial to USB converter. I had no other device connected at this point. Same problem occurred. I then swapped out the existing Keyspan unit with a new spare unit that I had, and tried a different 10' USB cable as well. Same problem with communication error messages popping up after about a minute. Even with the communication errors, things seem to work ok though. Mount slews to objects in both The SKY 6 and MaximDL 6.08. I then tried cleaning all the relevant electrical plugs and contacts with contact cleaner. Didn't help. 

Any ideas what's wrong?

Don Anderson


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

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
> >
> >
> >
> >
> >
>
>
>
>
>



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

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@... [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@... [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
>
>
>
>
>





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

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
>
>
>
>
>



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

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@... [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





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

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



Re: M51 and First Light With AP 1100GTO Mount

Stuart Heggie <stuart.j.heggie@...>
 

Ben, I'm running twin rigs now (again). I suggest practicing hanging wallpaper with one hand tied behind your back. That skill will come in handy. ;-)


On Sat, 23 Mar 2019 at 10:44, benjamin.e.c.koltenbah@... [ap-gto] <ap-gto@...> wrote:
 

Thank you all!  I''m sure looking forward to using this mount.

It's my intention to have two rigs running simultaneously.  The Mach1 mount will be used mainly with smaller scopes.  I'm almost ready to run each system independently.

Ben