AP ASCOM Driver or Mount reported slew complete while slew in progress!?


Andy Galasso
 

I had an incident last night that wreaked havoc with my imaging sequence. The imaging app issued a slew to the AP ASCOM driver at 2017-10-09 00:27:00.982, and at 2017-10-09 00:27:02.562 the driver reported that the slew was complete (Slewing = False), but the mount was in fact still slewing. The slew actually completed around 00:27:14.


Is this a known bug? Is there any fix or workaround available?


Full log file is here: AP ASCOM Driver Log


Thanks,

Andy


278256 2017-10-09 00:27:00.015:            ASCOM: Info      : GET Declination = 30.9580555555556

278267 2017-10-09 00:27:00.982:            ASCOM: Info      : SlewToCoordinatesAsync() RA=22.3336740181631, Dec=56.0817333512933

278279 2017-10-09 00:27:01.231:            ASCOM: Info      : GET Declination = 30.9580555555556

278306 2017-10-09 00:27:01.828:    SLEW COMPLETE: Info      : Slew complete: Setting tracking rates

278313 2017-10-09 00:27:02.313:            ASCOM: Info      : GET Declination = 30.9744444444444

278316 2017-10-09 00:27:02.562:            ASCOM: Info      : GET Slewing = False

278323 2017-10-09 00:27:03.391:            ASCOM: Info      : GET Declination = 33.9533333333333

278331 2017-10-09 00:27:04.468:            ASCOM: Info      : GET Declination = 36.5363888888889

278335 2017-10-09 00:27:04.733:            ASCOM: Info      : GET Slewing = False

278338 2017-10-09 00:27:04.813:            ASCOM: Info      : GET Declination = 36.5363888888889

278344 2017-10-09 00:27:04.922:            ASCOM: Info      : GET Declination = 36.5363888888889

278349 2017-10-09 00:27:05.546:            ASCOM: Info      : GET Declination = 39.1997222222222

278363 2017-10-09 00:27:06.622:            ASCOM: Info      : GET Declination = 42.9166666666667

278366 2017-10-09 00:27:06.685:            ASCOM: Info      : GET Declination = 42.9166666666667

278373 2017-10-09 00:27:07.699:            ASCOM: Info      : GET Declination = 45.4963888888889

278381 2017-10-09 00:27:08.775:            ASCOM: Info      : GET Declination = 48.0769444444445

278385 2017-10-09 00:27:09.290:            ASCOM: Info      : GET Declination = 48.0769444444445

278391 2017-10-09 00:27:09.742:            ASCOM: Info      : GET Slewing = True

278394 2017-10-09 00:27:09.854:            ASCOM: Info      : GET Declination = 50.7361111111111

278402 2017-10-09 00:27:10.930:            ASCOM: Info      : GET Declination = 53.3216666666667

278412 2017-10-09 00:27:12.006:            ASCOM: Info      : GET Declination = 55.6897222222222

278420 2017-10-09 00:27:13.083:            ASCOM: Info      : GET Declination = 56.1075

278428 2017-10-09 00:27:14.159:            ASCOM: Info      : GET Declination = 56.0819444444444

278432 2017-10-09 00:27:14.752:            ASCOM: Info      : GET Slewing = True

278437 2017-10-09 00:27:15.238:            ASCOM: Info      : GET Declination = 56.0819444444444

278459 2017-10-09 00:27:16.439:            ASCOM: Info      : GET Declination = 56.0819444444444

278468 2017-10-09 00:27:16.626:    SLEW COMPLETE: Info      : Slew complete: Setting tracking rates

278479 2017-10-09 00:27:17.563:            ASCOM: Info      : GET Declination = 56.0819444444444

278489 2017-10-09 00:27:18.686:            ASCOM: Info      : GET Declination = 56.0819444444444

278497 2017-10-09 00:27:19.763:            ASCOM: Info      : GET Declination = 56.0819444444444

278498 2017-10-09 00:27:19.778:            ASCOM: Info      : GET Slewing = False

278502 2017-10-09 00:27:19.874:            ASCOM: Info      : GET Declination = 56.0819444444444

278508 2017-10-09 00:27:19.983:            ASCOM: Info      : GET Declination = 56.0819444444444

278518 2017-10-09 00:27:20.903:            ASCOM: Info      : GET Declination = 56.0819444444444

278532 2017-10-09 00:27:21.995:            ASCOM: Info      : GET Declination = 56.0819444444444

278540 2017-10-09 00:27:23.072:            ASCOM: Info      : GET Declination = 56.0819444444444

278548 2017-10-09 00:27:24.148:            ASCOM: Info      : GET Declination = 56.0819444444444

278552 2017-10-09 00:27:24.772:            ASCOM: Info      : GET Slewing = False




Howard Hedlund
 

Hi Andy,

First off, please update to the latest driver.  Yours is from July of 2016.  This looks like a timing issue to me, and there were some timing issues fixed in later versions.  In particular, it appears that the driver decided the slew was complete based on old data from before the slew was issued.   The "Slew Complete" occurs less than half a second after the actual slew command was issued to the mount, and there were no intervening polls that would have told the driver otherwise.  In the meantime, I'll get with Ray on this.  It may need further action; it may already be fixed.   There is actually a new AP V2 Driver version that we need to get up on the website.  It is 5.10.02   I'll try to get that going ASAP.


Andy Galasso
 

Hi Howard,
Thanks for looking into it and confirming the issue. Looking forward to hearing what you learn from Ray.
Andy


Ray Gralak
 

Andy,

Thanks for looking into it and confirming the issue. Looking forward to hearing what you learn from Ray.
As Howard has said, please update your driver to a newer version, and if the problem continues then post another log file.

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

-----Original Message-----
From: ap-gto@yahoogroups.com [mailto:ap-gto@yahoogroups.com]
Sent: Tuesday, October 10, 2017 11:40 AM
To: ap-gto@yahoogroups.com
Subject: Re: [ap-gto] Re: AP ASCOM Driver or Mount reported slew complete while slew in progress!?



Hi Howard,
Thanks for looking into it and confirming the issue. Looking forward to hearing what you learn from Ray.
Andy



Andy Galasso
 

On Tue, Oct 10, 2017 at 10:03 PM, 'Ray Gralak (Groups)' groups3@... [ap-gto] <ap-gto@...> wrote:
 


As Howard has said, please update your driver to a newer version, and if the problem continues then post another log file.


Thanks Ray. I have upgraded and will post another log if I see it again.

Andy


Ray Gralak
 

Thanks Ray. I have upgraded and will post another log if I see it again.
Ok, thanks Andy. I believe that Howard's assessment is correct. This was a timing issue that could cause the driver to check a stale slewing state, thus making the driver think that the slew had completed when it had just started. I think this was fixed a while ago.

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


-----Original Message-----
From: ap-gto@yahoogroups.com [mailto:ap-gto@yahoogroups.com]
Sent: Tuesday, October 10, 2017 7:07 PM
To: ap-gto@yahoogroups.com
Subject: Re: [ap-gto] Re: AP ASCOM Driver or Mount reported slew complete while slew in progress!?



On Tue, Oct 10, 2017 at 10:03 PM, 'Ray Gralak (Groups)' groups3@gralak.com [ap-gto] <ap-
gto@yahoogroups.com> wrote:






As Howard has said, please update your driver to a newer version, and if the problem continues then
post another log file.



Thanks Ray. I have upgraded and will post another log if I see it again.

Andy



Andy Galasso
 

That is good news. Thank you both for looking into it.
Andy