|
Problem: ShaneAO Motor Failure
Manifestation:
In Shane AO motor control GUI:
-
Motor value(s) do not change when commanded (e.g. following a back on-axis command).
-
A subset of functions flagged with either a red check mark and/or yellow warning triangle.
-
Detail panel reports: Modify failed: dispatcher currently blocking nonread
requests
-
Motors fail to move or cease moving.
Solution/Recovery:
-
Note there are separate, specific recoveries for
TT CAM X,
TT Filter
and
Sodium Filter
functions.
-
Verify communications:
ping shark.ucolick.org
ping real.ucolick.org
ping musher.ucolick.org
ping covert.ucolick.org
ping stealthie.ucolick.org
ping saorouter.ucolick.org
ping ao-serial-1.ucolick.org
ping ao-serial-2.ucolick.org
ping ao-agilent.ucolick.org
ping ao-lantr-ip.ucolick.org
-
Status of the dispatcher services can be queried with the following commands:
user@shark.ucolick.org > ao status saomot queries all dispatchers.
user@shark.ucolick.org > ao status saomot2 queries specific dispatcher
(e.g. saomot2).
-
It may be necessary to (re-)start dispatchers, regardless of the reported status.
-
Stop individual dispatcher services, with the following command(s):
user@shark.ucolick.org > ao stop saomot1
user@shark.ucolick.org > ao stop saomot2
user@shark.ucolick.org > ao stop saomot3
user@shark.ucolick.org > ao stop saomot4
user@shark.ucolick.org > ao stop saomot5
user@shark.ucolick.org > ao stop saomot7
Alternatively, stop all dispatcher services, with the following command:
user@shark.ucolick.org > ao stop saomot
-
Start individual dispatcher services, with the following command(s):
user@shark.ucolick.org > ao start saomot1
user@shark.ucolick.org > ao start saomot2
user@shark.ucolick.org > ao start saomot3
user@shark.ucolick.org > ao start saomot4
user@shark.ucolick.org > ao start saomot5
user@shark.ucolick.org > ao start saomot7
Alternatively, start all dispatchers, with the following command:
user@shark.ucolick.org > ao start saomot
-
Alternatively, re-start individual dispatcher services, with the following command(s):
user@shark.ucolick.org > ao restart saomot1
user@shark.ucolick.org > ao restart saomot2
user@shark.ucolick.org > ao restart saomot3
user@shark.ucolick.org > ao restart saomot4
user@shark.ucolick.org > ao restart saomot5
user@shark.ucolick.org > ao restart saomot7
Alternatively, restart all dispatcher services, with the following command:
user@shark.ucolick.org > ao restart saomot
-
In Shane AO motor control GUI: Ensure Orientation is set to
On Telescope.
-
In Shane AO motor control GUI: Actions...; Enable Motion.
-
In Shane AO motor control GUI: Open detail view panel for affected
function(s)/motor(s) and Re-calibrate.
-
In fieldsteer.tcl GUI, it may be necessary to issue a
Back On-Axis command in NGS mode, LGS mode or both.
This should position
WFS X
and
WFS Y
to nominal on-axis values.
-
Refer to Motor Control GUI Start-up Procedure for current nominal on-axis positions.
Intervention:
Cause:
-
Possible binding of motor stage and/or associated limit switches.
-
Generally provoked by stopping and re-starting dispatcher(s)
(saomotX).
Associated Issues:
-
Affects TT CAM X, TT CAM Y, Sodium filter.
-
Issue 10620 (Shane AO motor control: Dispatcher currently blocking nonread requests).
-
Issue 10038 (Unable to remove Sodium filter).
Change Log:
- 2020-10-27: Updated following 2019/2020 upgrade of WFS mechanism.
- 2018-02-02: Updated.
- 2017-08-05: Updated (binding/lubrication of limit switches).
- 2016-11-11: Updated (shred replaces shard).
- 2015-07-01: Updated.
- 2014-05-09: First version.
|