Skip to content

Commit f07e5bc

Browse files
committed
adding accions of the cmd: setZeroAz
1 parent 958db37 commit f07e5bc

File tree

1 file changed

+7
-3
lines changed

1 file changed

+7
-3
lines changed

Simonyi/Troubleshooting/MTCS/MTDome/MTDome-re-home.rst

Lines changed: 7 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -60,7 +60,7 @@ Procedure Steps
6060

6161
1. Move the MTDome to the azimuth of 328 deg, the position can be verified through the camera systems `UniFi at Cam-04`_ (via VPN). This is the **zero position or park position** for the MTDome.
6262

63-
2. Note that the readings reported by the MTDome in `LOVE dashboard`_ or `Chronograf`_ will show different numbers, so you need to calculate the value that the unaligned encoders would read at the park position of 328 degrees and send the MTDome to that angle.
63+
2. Note that the readings reported by the MTDome in `LOVE dashboard`_ or *Chronograf* will show different numbers, so you need to calculate the value that the unaligned encoders would read at the park position of 328 degrees and send the MTDome to that angle.
6464

6565
* For example: you notice the MTDome dashboard is reporting 10 degree in azimuth, but the camera marks 25.2 degrees.
6666
* Due to the encoder is 15.2 degrees behind, to send the MTDome to home at 328 degrees, you need to command the dome to move to **(328 - 15.2) = 312.8 degrees**
@@ -98,6 +98,11 @@ Procedure Steps
9898
..
9999
100100

101+
* This *setZeroAz* command reset the *actualPosition* of the azimuth telemetry to 328º.
102+
* Only if that doesn't work, try a reboot of the cRIO. This will reset the zero position in the cRIO, so after a reboot no *setZeroAz command* is necessary.
103+
* After a reboot, always send an *exitFault* command (cmd: exitFault). If the azimuth control software is not in fault, the command will still be accepted.
104+
105+
101106
.. _MTDome-MTDome-re-Home-Post-Condition:
102107

103108

@@ -109,5 +114,4 @@ Post-Condition
109114

110115
Contingency
111116
===========
112-
* If the above procedure was not successful, report the issue in *#summit-simonyi, #simonyi-operations* and *#rubinobs-mtdome* channels.
113-
117+
* If the above procedure was not successful, report the issue in *#summit-simonyi, #simonyi-operations* and *#rubinobs-mtdome* channels and please open an OBS Jira ticket if neccesary.

0 commit comments

Comments
 (0)