1. Topics
  2. AP1100AE, while tracking/guiding "Motor Stall"

AP1100AE, while tracking/guiding "Motor Stall"

ap@CaptivePhotons.com
 

I was imaging and it was going great, guiding in the 0.18 to 0.25 or so range, all was well and I glanced at the screen and saw stars streaking.  APCC was showing tracking=0.  I reached over and clicked on the status bar to start it tracking (NINA at the time was doing a plate solve to recenter since it knew there was an issue).   NINA completed the plate solve and slewed to recenter, and continued running. 

Meanwhile I saw the pink Comm Events, clicked it, and there are a bunch of Motor Stalls show over a four seconds.  After I clicked to start tracking NINA centered, and it is once again guiding.

I went outside to check -- nothing was caught (nothing anywhere near anything that could catch), no visible issues.  It's carrying all of about 25 pounds with a TV101is, and I carefully balanced before starting.  It was not near meridian (about 75 minutes until) or any limit. 

If it's useful I can send logs, etc. but below is the apcc log just before and after the first stall, and also ascom.

Am I looking for a hardware issue, some kind of software thing, or what?   This is V1.9.1.3, the beta that was sent out, running with PHD2 (2.6.10) and NINA (1.11 # 171).   I'm not about 20 minutes later no further events.   CP4 -> Mount is ethernet. COM31 is virtual for ASCOM to NINA and PHD2. 

What should I be looking for?  

And is the normal reaction to a motor stall to set tracking to zero (It did not park or disconnect).   

Linwood


0351447 2021-10-26 22:22:40.496:      Debug,        WebReply, <-- 0      (2 msecs)

0351448 2021-10-26 22:22:40.496:      Debug,  Command Thread, TX=':M_S#'|RX='0'

0351449 2021-10-26 22:22:40.497:      Debug, Slew Start Callback, New SafeSlew State=WaitPrimarySlew

0351450 2021-10-26 22:22:40.564:       Info,   VPort1(COM31), RX: :APCC,88184,GR#

0351451 2021-10-26 22:22:40.578:       Info, ProcessVPortCommand, RX from VPort 1: :APCC,88184,GR#

0351452 2021-10-26 22:22:40.578:       Info, ProcessVPortCommand, APCC Seq=   88184, CMD=GR#

0351453 2021-10-26 22:22:40.579:       Info, VPortCheckVPort1(COM31), (RX: GR#), TX: APCC,11,88184,00:43:13.7#

0351454 2021-10-26 22:22:40.763:      Debug,  Command Thread, TX = ':GOS#:GR#:GD#:pS#:GH#:GS#:GM#:HRG#:HDG#:Rr#:Rd#:GC#:GL#:GG#:GP#'

0351455 2021-10-26 22:22:40.764:      Debug,        Web Send, --> http://192.168.135.4/cmd.cgi?CMD=%3AGOS%23%3AGR%23%3AGD%23%3ApS%23%3AGH%23%3AGS%23%3AGM%23%3AHRG%23%3AHDG%23%3ARr%23%3ARd%23%3AGC%23%3AGL%23%3AGG%23%3AGP%23   Timeout(msecs)= 100

0351456 2021-10-26 22:22:40.767:      Debug,        WebReply, <-- 199000202EZ000#<LF>00:43:14.01#<LF>+41*21:02.1#<LF>West#<LF>-01:24:54.63#<LF>23:18:19.38#<LF>00:00:00.00#<LF>-73*27:00.0#<LF>+42*59:02.3#<LF>0#<LF>0#<LF>10/26/21#<LF>22:22:41.75#<LF>04:00:00.00#<LF>00:00:00.00#      (3 msecs)

0351457 2021-10-26 22:22:40.769:      Error,  Command Thread, Motor Stall Detected

0351458 2021-10-26 22:22:40.815:       Info, VPortCheckVPort1(COM31), (RX: ), TX: Z

0351459 2021-10-26 22:22:40.817:      Debug,  Command Thread, TX=':GOS#:GR#:GD#:pS#:GH#:GS#:GM#:HRG#:HDG#:Rr#:Rd#:GC#:GL#:GG#:GP#'|RX='199000202E000#<LF>00:43:14.01#<LF>+41*21:02.1#<LF>West#<LF>-01:24:54.63#<LF>23:18:19.38#<LF>00:00:00.00#<LF>-73*27:00.0#<LF>+42*59:02.3#<LF>0#<LF>0#<LF>10/26/21#<LF>22:22:41.75#<LF>04:00:00.00#<LF>00:00:00.00#'

0351460 2021-10-26 22:22:40.817:      Debug,  Command Thread, TX = '$GOS#'

0351461 2021-10-26 22:22:40.817:      Debug,        Web Send, --> http://192.168.135.4/cmd.cgi?CMD=%24GOS%23   Timeout(msecs)= 100

0351462 2021-10-26 22:22:40.818:      Debug,        WebReply, <-- 11100000#      (1 msecs)

0351463 2021-10-26 22:22:40.818:      Debug,  Command Thread, TX='$GOS#'|RX='11100000#'

0351464 2021-10-26 22:22:40.819:       Info,             GOS, New GOS Value: 199S00202E000

0351465 2021-10-26 22:22:40.859:      Debug,       PollMount, Elapsed time to Process: 42 msecs

0351466 2021-10-26 22:22:40.862:      Debug, SafeSlewStateMachine, New SafeSlew State=StartPointingCorrectionSlew

0351467 2021-10-26 22:22:40.884:       Info,   VPort1(COM31), RX: :APCC,88185,GD#

0351468 2021-10-26 22:22:40.890:       Info, ProcessVPortCommand, RX from VPort 1: :APCC,88185,GD#

0351469 2021-10-26 22:22:40.890:       Info, ProcessVPortCommand, APCC Seq=   88185, CMD=GD#

0351470 2021-10-26 22:22:40.891:       Info, VPortCheckVPort1(COM31), (RX: GD#), TX: APCC,10,88185,+41*21:02#

0351471 2021-10-26 22:22:40.924:      Debug, SafeSlewStateMachine, New SafeSlew State=SlewComplete

0351472 2021-10-26 22:22:40.924:       Info, SafeSlewCompleted, Successful: True 

0351473 2021-10-26 22:22:40.985:       Info, SafeSlewStateMachine, Slew Done

0351474 2021-10-26 22:22:41.048:       Info,   VPort1(COM31), RX: :APCC,88186,GZ#

0351475 2021-10-26 22:22:41.062:       Info, ProcessVPortCommand, RX from VPort 1: :APCC,88186,GZ#

0351476 2021-10-26 22:22:41.062:       Info, ProcessVPortCommand, APCC Seq=   88186, CMD=GZ#

 

Here is the ASCOM log from the similar time: 

745644 2021-10-26 22:22:39.967:           Driver: Info      : CommandString: APCC response: ':APCC,88181,GZ#', Response='+44*22:05#'

745645 2021-10-26 22:22:40.191:            ASCOM: Info      : GET Connected = True

745646 2021-10-26 22:22:40.192:            ASCOM: Info      : GET Connected = True

745647 2021-10-26 22:22:40.193:            ASCOM: Info      : GET Slewing = False, MoveAxis(0)=0, MoveAxis(1)=0

745648 2021-10-26 22:22:40.223:            ASCOM: Info      : GET Connected = True

745649 2021-10-26 22:22:40.224:            ASCOM: Info      : GET Slewing = False, MoveAxis(0)=0, MoveAxis(1)=0

745650 2021-10-26 22:22:40.252:            ASCOM: Info      : GET Connected = True

745651 2021-10-26 22:22:40.253:            ASCOM: Info      : GET AtPark = False

745652 2021-10-26 22:22:40.287:            ASCOM: Info      : GET Connected = True

745653 2021-10-26 22:22:40.287:            ASCOM: Info      : GET RightAscension = 0.720472222222222

745654 2021-10-26 22:22:40.288:            ASCOM: Info      : GET Connected = True

745655 2021-10-26 22:22:40.288:            ASCOM: Info      : GET Declination = 41.3505555555556

745656 2021-10-26 22:22:40.289:            ASCOM: Info      : GET Connected = True

745657 2021-10-26 22:22:40.290:            ASCOM: Info      : GET Connected = True

745658 2021-10-26 22:22:40.290:            ASCOM: Info      : GET AtPark = False

745659 2021-10-26 22:22:40.315:            ASCOM: Info      : GET Connected = True

745660 2021-10-26 22:22:40.315:            ASCOM: Info      : GET CanSetTracking = True

745661 2021-10-26 22:22:40.316:            ASCOM: Info      : GET Connected = True

745662 2021-10-26 22:22:40.316:            ASCOM: Info      : SET Tracking = True

745663 2021-10-26 22:22:40.316:            ASCOM: Info      : SET TrackingRate = 0

745664 2021-10-26 22:22:40.316:           Driver: Info      : CommandBlind TX=':Q#'

745665 2021-10-26 22:22:40.337:           Driver: Info      : CommandBlind TX=':RT2#'

745666 2021-10-26 22:22:40.349:            ASCOM: Info      : GET Connected = True

745667 2021-10-26 22:22:40.350:            ASCOM: Info      : GET CanSlewAsync = True

745668 2021-10-26 22:22:40.350:            ASCOM: Info      : GET Connected = True

745669 2021-10-26 22:22:40.351:            ASCOM: Info      : GET Connected = True

745670 2021-10-26 22:22:40.351:            ASCOM: Info      : SlewToCoordinatesAsync() RA=0.721125656320153, Dec=41.3446761492002

745671 2021-10-26 22:22:40.351:        Telescope: Info      : CommandString TX=':*SLEW,0.721125656320153,41.3446761492002#'

745672 2021-10-26 22:22:40.369:        Telescope: Info      : CommandString: APCC response: ':APCC,88182,*SLEW,0.721125656320153,41.3446761492002#', Response='1#'

745673 2021-10-26 22:22:40.369: SlewToCoordinatesAsync: Info      : Result from APCC *SLEW=1

745674 2021-10-26 22:22:40.370:            ASCOM: Info      : GET Connected = True

745675 2021-10-26 22:22:40.370:            ASCOM: Info      : GET Slewing = True, MoveAxis(0)=0, MoveAxis(1)=0

745676 2021-10-26 22:22:40.452:           Driver: Info      : CommandString TX=':GA#'

745677 2021-10-26 22:22:40.470:           Driver: Info      : CommandString: APCC response: ':APCC,88183,GA#', Response='+67*07:28#'

745678 2021-10-26 22:22:40.639:           Driver: Info      : CommandString TX=':GR#'

745679 2021-10-26 22:22:40.655:           Driver: Info      : CommandString: APCC response: ':APCC,88184,GR#', Response='00:43:13.7#'

745680 2021-10-26 22:22:40.959:           Driver: Info      : CommandString TX=':GD#'

745681 2021-10-26 22:22:40.967:        Telescope: Error     : MOTOR STALL DETECTEDS: 1

745682 2021-10-26 22:22:40.967:           Driver: Info      : CommandString: APCC response: ':APCC,88185,GD#', Response='+41*21:02#'

745683 2021-10-26 22:22:41.123:           Driver: Info      : CommandString TX=':GZ#'

745684 2021-10-26 22:22:41.140:           Driver: Info      : CommandString: APCC response: ':APCC,88186,GZ#', Response='+44*21:52#'

745685 2021-10-26 22:22:41.605:           Driver: Info      : CommandString TX=':GA#'

745686 2021-10-26 22:22:41.621:        Telescope: Error     : MOTOR STALL DETECTEDS: 2

745687 2021-10-26 22:22:41.622:        Telescope: Error     : CommandString: NO Response or bad APCC response: ':APCC,88187,GA#', Response='GA' -> Giving up!

745688 2021-10-26 22:22:41.622:        Alt Query: Error     : No response querying Alt - 1

745689 2021-10-26 22:22:41.691:            ASCOM: Info      : GET Connected = True

745690 2021-10-26 22:22:41.692:            ASCOM: Info      : GET Connected = True

745691 2021-10-26 22:22:41.694:            ASCOM: Info      : GET AtPark = False

745692 2021-10-26 22:22:41.725:            ASCOM: Info      : GET Connected = True

745693 2021-10-26 22:22:41.726:            ASCOM: Info      : GET AtHome = False

745694 2021-10-26 22:22:41.727:            ASCOM: Info      : GET Connected = True

745695 2021-10-26 22:22:41.728:            ASCOM: Info      : GET CanSetTracking = True

745696 2021-10-26 22:22:41.729:            ASCOM: Info      : GET Connected = True

745697 2021-10-26 22:22:41.730:            ASCOM: Info      : GET Tracking = True

745698 2021-10-26 22:22:41.731:            ASCOM: Info      : GET CanSetTracking = True

745699 2021-10-26 22:22:41.731:            ASCOM: Info      : GET TrackingRate = 0

745700 2021-10-26 22:22:41.732:            ASCOM: Info      : GET DeclinationRate = 0

745701 2021-10-26 22:22:41.733:            ASCOM: Info      : GET RightAscensionRate = 0

745702 2021-10-26 22:22:41.733:            ASCOM: Info      : GET Connected = True

 

745703 2021-10-26 22:22:41.733:            ASCOM: Info      : GET Tracking = True
Ray Gralak
 

Hi Linwood,

A motor stall is reported from the firmware and is not something the software could be doing.

When a motor stall occurs, it's like it sounds - the motor stops tracking (it's not the software issuing a stop).

As to why a stall occurred, it could be an imbalance or low power voltage/current. There may be other reasons as well. If you can't find the problem give A-P a call tomorrow.

-Ray

-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of ap@...
Sent: Tuesday, October 26, 2021 7:48 PM
To: main@ap-gto.groups.io
Subject: [ap-gto] AP1100AE, while tracking/guiding "Motor Stall"

I was imaging and it was going great, guiding in the 0.18 to 0.25 or so range, all was well and I glanced at the
screen and saw stars streaking. APCC was showing tracking=0. I reached over and clicked on the status bar
to start it tracking (NINA at the time was doing a plate solve to recenter since it knew there was an issue).
NINA completed the plate solve and slewed to recenter, and continued running.

Meanwhile I saw the pink Comm Events, clicked it, and there are a bunch of Motor Stalls show over a four
seconds. After I clicked to start tracking NINA centered, and it is once again guiding.



I went outside to check -- nothing was caught (nothing anywhere near anything that could catch), no visible
issues. It's carrying all of about 25 pounds with a TV101is, and I carefully balanced before starting. It was not
near meridian (about 75 minutes until) or any limit.

If it's useful I can send logs, etc. but below is the apcc log just before and after the first stall, and also
ascom.

Am I looking for a hardware issue, some kind of software thing, or what? This is V1.9.1.3, the beta that was
sent out, running with PHD2 (2.6.10) and NINA (1.11 # 171). I'm not about 20 minutes later no further events.
CP4 -> Mount is ethernet. COM31 is virtual for ASCOM to NINA and PHD2.

What should I be looking for?

And is the normal reaction to a motor stall to set tracking to zero (It did not park or disconnect).

Linwood




0351447 2021-10-26 22:22:40.496: Debug, WebReply, <-- 0 (2 msecs)

0351448 2021-10-26 22:22:40.496: Debug, Command Thread, TX=':M_S#'|RX='0'

0351449 2021-10-26 22:22:40.497: Debug, Slew Start Callback, New SafeSlew
State=WaitPrimarySlew

0351450 2021-10-26 22:22:40.564: Info, VPort1(COM31), RX: :APCC,88184,GR#

0351451 2021-10-26 22:22:40.578: Info, ProcessVPortCommand, RX from VPort 1:
:APCC,88184,GR#

0351452 2021-10-26 22:22:40.578: Info, ProcessVPortCommand, APCC Seq= 88184, CMD=GR#

0351453 2021-10-26 22:22:40.579: Info, VPortCheckVPort1(COM31), (RX: GR#), TX:
APCC,11,88184,00:43:13.7#

0351454 2021-10-26 22:22:40.763: Debug, Command Thread, TX =
':GOS#:GR#:GD#:pS#:GH#:GS#:GM#:HRG#:HDG#:Rr#:Rd#:GC#:GL#:GG#:GP#'

0351455 2021-10-26 22:22:40.764: Debug, Web Send, -->
http://192.168.135.4/cmd.cgi?CMD=%3AGOS%23%3AGR%23%3AGD%23%3ApS%23%3AGH%23%3AGS%2
3%3AGM%23%3AHRG%23%3AHDG%23%3ARr%23%3ARd%23%3AGC%23%3AGL%23%3AGG%23%3AGP
%23 Timeout(msecs)= 100

0351456 2021-10-26 22:22:40.767: Debug, WebReply, <--
199000202EZ000#<LF>00:43:14.01#<LF>+41*21:02.1#<LF>West#<LF>-
01:24:54.63#<LF>23:18:19.38#<LF>00:00:00.00#<LF>-
73*27:00.0#<LF>+42*59:02.3#<LF>0#<LF>0#<LF>10/26/21#<LF>22:22:41.75#<LF>04:00:00.00#<LF>00:00:00.
00# (3 msecs)

0351457 2021-10-26 22:22:40.769: Error, Command Thread, Motor Stall Detected

0351458 2021-10-26 22:22:40.815: Info, VPortCheckVPort1(COM31), (RX: ), TX: Z

0351459 2021-10-26 22:22:40.817: Debug, Command Thread,
TX=':GOS#:GR#:GD#:pS#:GH#:GS#:GM#:HRG#:HDG#:Rr#:Rd#:GC#:GL#:GG#:GP#'|RX='199000202E000#<L
F>00:43:14.01#<LF>+41*21:02.1#<LF>West#<LF>-01:24:54.63#<LF>23:18:19.38#<LF>00:00:00.00#<LF>-
73*27:00.0#<LF>+42*59:02.3#<LF>0#<LF>0#<LF>10/26/21#<LF>22:22:41.75#<LF>04:00:00.00#<LF>00:00:00.
00#'

0351460 2021-10-26 22:22:40.817: Debug, Command Thread, TX = '$GOS#'

0351461 2021-10-26 22:22:40.817: Debug, Web Send, -->
http://192.168.135.4/cmd.cgi?CMD=%24GOS%23 Timeout(msecs)= 100

0351462 2021-10-26 22:22:40.818: Debug, WebReply, <-- 11100000# (1 msecs)

0351463 2021-10-26 22:22:40.818: Debug, Command Thread, TX='$GOS#'|RX='11100000#'

0351464 2021-10-26 22:22:40.819: Info, GOS, New GOS Value: 199S00202E000

0351465 2021-10-26 22:22:40.859: Debug, PollMount, Elapsed time to Process: 42 msecs

0351466 2021-10-26 22:22:40.862: Debug, SafeSlewStateMachine, New SafeSlew
State=StartPointingCorrectionSlew

0351467 2021-10-26 22:22:40.884: Info, VPort1(COM31), RX: :APCC,88185,GD#

0351468 2021-10-26 22:22:40.890: Info, ProcessVPortCommand, RX from VPort 1:
:APCC,88185,GD#

0351469 2021-10-26 22:22:40.890: Info, ProcessVPortCommand, APCC Seq= 88185, CMD=GD#

0351470 2021-10-26 22:22:40.891: Info, VPortCheckVPort1(COM31), (RX: GD#), TX:
APCC,10,88185,+41*21:02#

0351471 2021-10-26 22:22:40.924: Debug, SafeSlewStateMachine, New SafeSlew
State=SlewComplete

0351472 2021-10-26 22:22:40.924: Info, SafeSlewCompleted, Successful: True

0351473 2021-10-26 22:22:40.985: Info, SafeSlewStateMachine, Slew Done

0351474 2021-10-26 22:22:41.048: Info, VPort1(COM31), RX: :APCC,88186,GZ#

0351475 2021-10-26 22:22:41.062: Info, ProcessVPortCommand, RX from VPort 1:
:APCC,88186,GZ#

0351476 2021-10-26 22:22:41.062: Info, ProcessVPortCommand, APCC Seq= 88186, CMD=GZ#



Here is the ASCOM log from the similar time:



745644 2021-10-26 22:22:39.967: Driver: Info : CommandString: APCC response:
':APCC,88181,GZ#', Response='+44*22:05#'

745645 2021-10-26 22:22:40.191: ASCOM: Info : GET Connected = True

745646 2021-10-26 22:22:40.192: ASCOM: Info : GET Connected = True

745647 2021-10-26 22:22:40.193: ASCOM: Info : GET Slewing = False, MoveAxis(0)=0,
MoveAxis(1)=0

745648 2021-10-26 22:22:40.223: ASCOM: Info : GET Connected = True

745649 2021-10-26 22:22:40.224: ASCOM: Info : GET Slewing = False, MoveAxis(0)=0,
MoveAxis(1)=0

745650 2021-10-26 22:22:40.252: ASCOM: Info : GET Connected = True

745651 2021-10-26 22:22:40.253: ASCOM: Info : GET AtPark = False

745652 2021-10-26 22:22:40.287: ASCOM: Info : GET Connected = True

745653 2021-10-26 22:22:40.287: ASCOM: Info : GET RightAscension = 0.720472222222222

745654 2021-10-26 22:22:40.288: ASCOM: Info : GET Connected = True

745655 2021-10-26 22:22:40.288: ASCOM: Info : GET Declination = 41.3505555555556

745656 2021-10-26 22:22:40.289: ASCOM: Info : GET Connected = True

745657 2021-10-26 22:22:40.290: ASCOM: Info : GET Connected = True

745658 2021-10-26 22:22:40.290: ASCOM: Info : GET AtPark = False

745659 2021-10-26 22:22:40.315: ASCOM: Info : GET Connected = True

745660 2021-10-26 22:22:40.315: ASCOM: Info : GET CanSetTracking = True

745661 2021-10-26 22:22:40.316: ASCOM: Info : GET Connected = True

745662 2021-10-26 22:22:40.316: ASCOM: Info : SET Tracking = True

745663 2021-10-26 22:22:40.316: ASCOM: Info : SET TrackingRate = 0

745664 2021-10-26 22:22:40.316: Driver: Info : CommandBlind TX=':Q#'

745665 2021-10-26 22:22:40.337: Driver: Info : CommandBlind TX=':RT2#'

745666 2021-10-26 22:22:40.349: ASCOM: Info : GET Connected = True

745667 2021-10-26 22:22:40.350: ASCOM: Info : GET CanSlewAsync = True

745668 2021-10-26 22:22:40.350: ASCOM: Info : GET Connected = True

745669 2021-10-26 22:22:40.351: ASCOM: Info : GET Connected = True

745670 2021-10-26 22:22:40.351: ASCOM: Info : SlewToCoordinatesAsync()
RA=0.721125656320153, Dec=41.3446761492002

745671 2021-10-26 22:22:40.351: Telescope: Info : CommandString
TX=':*SLEW,0.721125656320153,41.3446761492002#'

745672 2021-10-26 22:22:40.369: Telescope: Info : CommandString: APCC response:
':APCC,88182,*SLEW,0.721125656320153,41.3446761492002#', Response='1#'

745673 2021-10-26 22:22:40.369: SlewToCoordinatesAsync: Info : Result from APCC *SLEW=1

745674 2021-10-26 22:22:40.370: ASCOM: Info : GET Connected = True

745675 2021-10-26 22:22:40.370: ASCOM: Info : GET Slewing = True, MoveAxis(0)=0,
MoveAxis(1)=0

745676 2021-10-26 22:22:40.452: Driver: Info : CommandString TX=':GA#'

745677 2021-10-26 22:22:40.470: Driver: Info : CommandString: APCC response:
':APCC,88183,GA#', Response='+67*07:28#'

745678 2021-10-26 22:22:40.639: Driver: Info : CommandString TX=':GR#'

745679 2021-10-26 22:22:40.655: Driver: Info : CommandString: APCC response:
':APCC,88184,GR#', Response='00:43:13.7#'

745680 2021-10-26 22:22:40.959: Driver: Info : CommandString TX=':GD#'

745681 2021-10-26 22:22:40.967: Telescope: Error : MOTOR STALL DETECTEDS: 1

745682 2021-10-26 22:22:40.967: Driver: Info : CommandString: APCC response:
':APCC,88185,GD#', Response='+41*21:02#'

745683 2021-10-26 22:22:41.123: Driver: Info : CommandString TX=':GZ#'

745684 2021-10-26 22:22:41.140: Driver: Info : CommandString: APCC response:
':APCC,88186,GZ#', Response='+44*21:52#'

745685 2021-10-26 22:22:41.605: Driver: Info : CommandString TX=':GA#'

745686 2021-10-26 22:22:41.621: Telescope: Error : MOTOR STALL DETECTEDS: 2

745687 2021-10-26 22:22:41.622: Telescope: Error : CommandString: NO Response or bad
APCC response: ':APCC,88187,GA#', Response='GA' -> Giving up!

745688 2021-10-26 22:22:41.622: Alt Query: Error : No response querying Alt - 1

745689 2021-10-26 22:22:41.691: ASCOM: Info : GET Connected = True

745690 2021-10-26 22:22:41.692: ASCOM: Info : GET Connected = True

745691 2021-10-26 22:22:41.694: ASCOM: Info : GET AtPark = False

745692 2021-10-26 22:22:41.725: ASCOM: Info : GET Connected = True

745693 2021-10-26 22:22:41.726: ASCOM: Info : GET AtHome = False

745694 2021-10-26 22:22:41.727: ASCOM: Info : GET Connected = True

745695 2021-10-26 22:22:41.728: ASCOM: Info : GET CanSetTracking = True

745696 2021-10-26 22:22:41.729: ASCOM: Info : GET Connected = True

745697 2021-10-26 22:22:41.730: ASCOM: Info : GET Tracking = True

745698 2021-10-26 22:22:41.731: ASCOM: Info : GET CanSetTracking = True

745699 2021-10-26 22:22:41.731: ASCOM: Info : GET TrackingRate = 0

745700 2021-10-26 22:22:41.732: ASCOM: Info : GET DeclinationRate = 0

745701 2021-10-26 22:22:41.733: ASCOM: Info : GET RightAscensionRate = 0

745702 2021-10-26 22:22:41.733: ASCOM: Info : GET Connected = True



745703 2021-10-26 22:22:41.733: ASCOM: Info : GET Tracking = True
ap@CaptivePhotons.com
 

Ray wrote:

A motor stall is reported from the firmware and is not something the software could be doing.
When a motor stall occurs, it's like it sounds - the motor stops tracking (it's not the software issuing a stop).
As to why a stall occurred, it could be an imbalance or low power voltage/current.
There may be other reasons as well. If you can't find the problem give A-P a call tomorrow.
The mount is on its own Powerwerx 25A supply powered by AC (set at 14.1 fixed), with 12awg wire closeby. Not power I think. Definitely not balance.

Help me with some perspective -- is this the sort of thing you should ignore if it happens once, and wait for it to get more chronic? Write it off to cosmic rays? (no relation I assume)

Or is this the kind of thing I should pursue even for one event as it might presage something going wrong?

At this point other than the sporadic clouds it continues to work. The mount was not power cycled or anything.

Linwood
Ray Gralak
 

The mount is on its own Powerwerx 25A supply powered by AC (set at 14.1 fixed), with 12awg wire closeby.
Not power I think. Definitely not balance.
Do you have a UPS backing that Powerwex? Brownouts do occur.

Or is this the kind of thing I should pursue even for one event as it might presage something going wrong?
Idk. If the occasional motor stall doesn't affect your imaging sessions, then you probably could ignore it. If it does affect imaging, then you probably will want to contact A-P to track down what is causing the motor stalls.

-Ray

-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of ap@...
Sent: Tuesday, October 26, 2021 8:04 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] AP1100AE, while tracking/guiding "Motor Stall"

Ray wrote:

A motor stall is reported from the firmware and is not something the software could be doing.
When a motor stall occurs, it's like it sounds - the motor stops tracking (it's not the software issuing a
stop).

As to why a stall occurred, it could be an imbalance or low power voltage/current.
There may be other reasons as well. If you can't find the problem give A-P a call tomorrow.
The mount is on its own Powerwerx 25A supply powered by AC (set at 14.1 fixed), with 12awg wire closeby.
Not power I think. Definitely not balance.

Help me with some perspective -- is this the sort of thing you should ignore if it happens once, and wait for it
to get more chronic? Write it off to cosmic rays? (no relation I assume)

Or is this the kind of thing I should pursue even for one event as it might presage something going wrong?

At this point other than the sporadic clouds it continues to work. The mount was not power cycled or
anything.

Linwood
ap@CaptivePhotons.com
 

Ray wrote:

The mount is on its own Powerwerx 25A supply powered by AC (set at 14.1 fixed), with 12awg wire closeby.
Not power I think. Definitely not balance.
Do you have a UPS backing that Powerwex? Brownouts do occur.
No, but I have continual monitoring of the utility power (124.0 to 125.5 in the 20 minutes or so around that time), as well as 3 UPS's inside, none of which reported any issues. Unless the PW PSU is bad, it wasn't power.

Or is this the kind of thing I should pursue even for one event as it might presage something going wrong?
Idk. If the occasional motor stall doesn't affect your imaging sessions, then you probably could ignore it. If it does affect imaging, then you probably will want to contact A-P to track down what is causing the motor stalls.
I actually don't know whether NINA's normal efforts to recenter would have restarted tracking or not, since I hit the tracking first thing. So I do not know the answer to that.

I'll wait and see if it happens again for now. It feels like the kind of thing hard to diagnose in retrospect with a single occurrence.

Unless you think they will find any more info in the logs, than that it happened.

I'm still going with cosmic rays. It's just happy as can be.... error is a really high 0.24". 😊

Thanks for the insight.

Linwood
Peter Nagy
 

Too tight gear mesh can cause motor stall.

Peter
ap@CaptivePhotons.com
 

Peter Nagy wrote:

 

  • Too tight gear mesh can cause motor stall.

 

Gosh, I hope not, I just got it a couple months ago, not ready to start adjusting things yet.   


So you didn't buy the cosmic ray theory.  ☹

 

Thanks, hopefully it will either get worse-enough AP can guide me to adjusting easily, or it will never occur again.

 

Linwood

 
Peter Nagy
 

One time I loosened all clutches in both axes to try to loosen the axes so I can balance easier. The clutches were loosened far enough that when I was swinging RA axis back and forth and one of the clutch knobs slammed on the RA motor box and shifted the gear mesh pretty tight and caused motor stall. I re-meshed the gears and all is well.

Those who own 1100GTO, do not loosen the clutch knobs too far.

Peter
ap@CaptivePhotons.com
 

Peter Nagy wrote:

 

  • One time I loosened all clutches in both axes to try to loosen the axes so I can balance easier. The clutches were loosened far enough that when I was swinging RA axis back and forth and one of the clutch knobs slammed on the RA motor box and shifted the gear mesh pretty tight and caused motor stall. I re-meshed the gears and all is well.

 

Those who own 1100GTO, do not loosen the clutch knobs too far.

 

Hmmm… I use the gear switch to balance.  Other than just to try it once to get a feel for it, I never loosen the clutches.


But noted.   Thanks.

 

Did that log section indicate which motor stalled, RA or DEC?   I don't know the command language well enough to be sure, and since I was guiding I know it might be moving both.

 

Linwood

 

 
Peter Nagy
 

Mine is a first run 1100GTO so it does not have gear switch or lever. It's possible the shipping the mount to your house may have shifted gear mesh. 

Peter
Bill Long
 

A one time motor stall is not likely cause for concern because it recovered fine. If you get repeated stalls then yeah you should probably investigate.

From: main@ap-gto.groups.io <main@ap-gto.groups.io> on behalf of ap@... <ap@...>
Sent: Tuesday, October 26, 2021 8:04 PM
To: main@ap-gto.groups.io <main@ap-gto.groups.io>
Subject: Re: [ap-gto] AP1100AE, while tracking/guiding "Motor Stall"
 
Ray wrote:

> A motor stall is reported from the firmware and is not something the software could be doing.

> When a motor stall occurs, it's like it sounds -  the motor stops tracking (it's not the software issuing a stop).

> As to why a stall occurred, it could be an imbalance or low power voltage/current.
> There may be other reasons as well. If you can't find the problem give A-P a call tomorrow.

The mount is on its own Powerwerx 25A supply powered by AC (set at 14.1 fixed), with 12awg wire closeby.  Not power I think.   Definitely not balance.

Help me with some perspective -- is this the sort of thing you should ignore if it happens once, and wait for it to get more chronic?  Write it off to cosmic rays?  (no relation I assume)  

Or is this the kind of thing I should pursue even for one event as it might presage something going wrong?

At this point other than the sporadic clouds it continues to work.  The mount was not power cycled or anything.

Linwood
Bill Long
 

You do not need to adjust the mesh of modern 1100 mounts. They auto adjust.

From: main@ap-gto.groups.io <main@ap-gto.groups.io> on behalf of ap@... <ap@...>
Sent: Tuesday, October 26, 2021 8:29 PM
To: main@ap-gto.groups.io <main@ap-gto.groups.io>
Subject: Re: [ap-gto] AP1100AE, while tracking/guiding "Motor Stall"
 

Peter Nagy wrote:

 

  • Too tight gear mesh can cause motor stall.

 

Gosh, I hope not, I just got it a couple months ago, not ready to start adjusting things yet.   


So you didn't buy the cosmic ray theory.  ☹

 

Thanks, hopefully it will either get worse-enough AP can guide me to adjusting easily, or it will never occur again.

 

Linwood

 
ap@CaptivePhotons.com
 

Bill Long wrote:

 

  • A one time motor stall is not likely cause for concern because it recovered fine. If you get repeated stalls then yeah you should probably investigate.

 

Thank you Bill for both notes.  FWIW it ran the rest of the evening with no further errors, well, other than clouds that just moved in, but I do not think that's covered by warranty.

 

Linwood

 
1 - 13 of 13