Re: AP1100AE needs exorcism (DEC turned all the way around like Linda Blair)


Ray Gralak
 

Hi Linwood,

035328 2022-01-17 18:19:58.285: ASCOM: Info : SET TargetRightAscension = 3.88285751697392
035329 2022-01-17 18:19:58.285: ASCOM: Info : SET TargetDeclination = 85.2108975166604
035330 2022-01-17 18:19:58.285: Telescope: Info : CommandString
TX=':*SLEW,3.88285751697392,85.2108975166604#'
035331 2022-01-17 18:19:59.300: Telescope: Error : CommandString: NO Response or bad APCC
response: ':APCC,4102,*SLEW,3.88285751697392,85.2108975166604#',
Response='*SLEW,3.88285751697392,85.2108975166604' -> Giving up!
The command didn't actually fail, but the driver timed out waiting for a response.

In APCC's log there is evidence that something else on your computer was consuming lots of CPU so the callback method for mount poll responses was delayed:

0058667 2022-01-17 18:20:00.621: Debug, Command Thread, TX='$GOS#'|RX='11100000#'
0058668 2022-01-17 18:20:00.664: Debug, RA/Dec Slew, New SafeSlew State=BeginSafeSlew
0058669 2022-01-17 18:20:00.668: Debug, PollMount, Elapsed time to Process: 2203 msecs
0058670 2022-01-17 18:20:00.671: Debug, PollMount, Elapsed time to Process: 1844 msecs
0058671 2022-01-17 18:20:00.675: Debug, PollMount, Elapsed time to Process: 1484 msecs
0058672 2022-01-17 18:20:00.678: Debug, PollMount, Elapsed time to Process: 1125 msecs
0058673 2022-01-17 18:20:00.680: Debug, PollMount, Elapsed time to Process: 781 msecs
0058674 2022-01-17 18:20:00.682: Debug, PollMount, Elapsed time to Process: 422 msecs
0058675 2022-01-17 18:20:00.684: Debug, PollMount, Elapsed time to Process: 63 msecs

As to why the mount slewed like that, it looks like there was some sort of error in the model as there is no filename for the model in the log (first line below), and the corrected Dec value is a crazy +511 degrees. I'll take a look at that to make sure that can't happen in the future but I think there was some sort of system event (maybe a disk read error) that kicked this off:

0058723 2022-01-17 18:20:01.028: Debug, Pointing Corrector, Slew - Model:
0058724 2022-01-17 18:20:01.028: Debug, Pointing Corrector, Slew - Current LST = 01:42:22.75
0058725 2022-01-17 18:20:01.028: Debug, Pointing Corrector, Slew - Target Slew: RA = 03:52:58.29, Dec = +85*12:39.2, East Model = True
0058726 2022-01-17 18:20:01.034: Debug, Pointing Corrector, Slew - Corrected Slew: RA = 20:48:07.95, Dec = +511*15:55.4
0058727 2022-01-17 18:20:01.036: Debug, Tracking Corrector, Slew - Side of Pier = EAST
0058728 2022-01-17 18:20:01.036: Debug, Tracking Corrector, Slew - RA Tracking Rate = 6.00000
0058729 2022-01-17 18:20:01.036: Debug, Tracking Corrector, Slew - Dec Tracking Rate = 0.00000
0058730 2022-01-17 18:20:01.036: Debug, SafeSlewStateMachine, New SafeSlew State=WaitPointingCorrectionSlew

-Ray

-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of ap@...
Sent: Monday, January 17, 2022 4:48 PM
To: main@ap-gto.groups.io
Subject: [ap-gto] AP1100AE needs exorcism (DEC turned all the way around like Linda Blair)

I was doing a three point polar alignment in NINA, as I do every night, and when it started slewing (usually a
small movement to be just off the pole), the DEC axis spun clockwise (as viewed from behind/above facing
north) all the way around. I finally hit stop, but not sure if I stopped it, or if it actually got to the right place by
going too far.

Thank goodness for thru-the-mount cables.

Interestingly when I then did a park 3 it unwound. Find home went to the right place.

I started all over and it worked fine.

I tracked this down in the NINA logs and it was just a slew, like any other slew.

I tracked it down in the ASCOM logs and got this:


035328 2022-01-17 18:19:58.285: ASCOM: Info : SET TargetRightAscension = 3.88285751697392
035329 2022-01-17 18:19:58.285: ASCOM: Info : SET TargetDeclination = 85.2108975166604
035330 2022-01-17 18:19:58.285: Telescope: Info : CommandString
TX=':*SLEW,3.88285751697392,85.2108975166604#'
035331 2022-01-17 18:19:59.300: Telescope: Error : CommandString: NO Response or bad APCC
response: ':APCC,4102,*SLEW,3.88285751697392,85.2108975166604#',
Response='*SLEW,3.88285751697392,85.2108975166604' -> Giving up!

There are no comm events shown on the APCC screen. Nothing I can make sense of in the APCC log.

Ray, attempting to anticipate, logs zipped and are here:

https://drive.google.com/file/d/1dpOb6Hw8JwcC0MoHzXXiOV-oX1MEO2eR/view?usp=sharing

That's taken from the mount after 2 restarts of NINA but no restarted of APCC nor did I re-initialize the mount;
the 18:19:58 event and subsequent LONG slew is the one of interest.

My first thought was I had confused something with a bad unpark or such, but Park 3 immediately afterwards
worked perfectly, as did Find Home, another Park 3, then I started NINA and did (+/- movement due to time)
exactly the same thing and it worked fine.

It sort of looks like Ascom and APCC had a disagreement.

Did I do something wrong?

Linwood


Join main@ap-gto.groups.io to automatically receive all group messages.