tickets/SITCOM-1638 #163
tickets/SITCOM-1638 #163
Conversation
There was a problem hiding this comment.
Hi Kris, a few comments to consider as well as a suggestion to improve the procedure. I know the task was to just translate the confluence page to obs-ops, but if we are going to add this procedure to our official documentation page I think we need to update the recovery section.
|
|
||
| This is a hardware issue related to a lost communication with the top-end or rotating part of the dome. | ||
| This can happen after a dome cabinets reboot, a power-off-on sequence or a power outage, that, not done | ||
| in the proper order, can cause communication failures. Contact Mario Rivera or someone at the summit, to |
There was a problem hiding this comment.
This should be more clear, "someone at the summit" could be anyone. The procedure to power cycle them in the correct order is not inherently dangerous, so we shouldn't rely on having an expert available. We should try to capture that procedure here. Can you reach out to @mgomezjimenez, Mario, or @craiglagegit to capture the procedure and add it here?
There was a problem hiding this comment.
Sounds good Erik. I will reach out to Manuel and Craig about writing a procedure.
There was a problem hiding this comment.
@edennihy I added a procedure to this page. Please take a look and let me know if you decide to approve the changes.
kpmort97
force-pushed
the
tickets/SITCOM-1638
branch
from
955dbd4 to
c4fbd11
Compare
I migrated the ATDome Top Comm Error page on Confluence over to obs-ops. Please look it over and provide comments as I am not familiar with the procedures in the document or if there needs to be updates. Thank you!