Update MTM2Hexapod PDU info. Fix usernames and command #133
Conversation
| @@ -213,16 +213,17 @@ Hard Reboot | |||
|
|
|||
| .. figure:: /Simonyi/Non-Standard-Operations/_static/mtrot-controller-pxi-reboot-1.jpeg | |||
There was a problem hiding this comment.
You can remove this figure becuase -
- outdated
- you can directly link the PDU outlet description page
There was a problem hiding this comment.
Why is this figure outdated? The PDU for MTRot and MTCamHexapod is still the same.
Once we release the PDU pages we can link from here.
There was a problem hiding this comment.
I will leave this figure as I believe this PDU hasn´t changed.
| /etc/init.d/cameraHexapod start | ||
|
|
||
| For *MTM2Hexapod*, replace in the command above *cameraHexapod* | ||
| with *m2Hexapod*. | ||
|
|
||
|
|
||
| #. **Establish an SSH connection to the MTHexapod PXI**: Using the credentials and hostnames found |
There was a problem hiding this comment.
I think you should create a NOTE titled Checking "Ethercat connection" and include the following points from Te-Wei's message here as the first point BEFORE establishing connection -
"If there is the connection issue, you could try:
ping the controller first to see there is the internet response or not.
ssh to the controller. To check the EtherCAT is running correctly or not, do ethercat master should show the frame rate from the slaves. The value should be 200 Hz in hexapod and 4000 Hz for the rotator.
To confirm the system is running or not, you can do:
-> /etc/init.d/ethercat status (for EtherCAT).
-> /etc/init.d/hexapod status (for hexapod)
-> /etc/init.d/rotator status (for rotator).
The ethercat master is the most straight-forward way to know the EtherCAT is running correctly or not. If it is not, the control system hangs up in an internal stage to wait until the EtherCAT is running correctly and you would not be able to use the GUI/CSC to connect to the control system at the moment.
As a reference, the output of ethercat master would look like this:"
There was a problem hiding this comment.
As I mentioned in a DM, I won't include the ethercat diagnosis, as the etherCat debug is beyond the scope for now. We might add it in a future release but for now, Te-Wei agreed we can leave it out for now.
There was a problem hiding this comment.
ok. One more comment --
- can you add that this ssh tunnel has to be created from our local computer/laptop ? I saw many of us getting confused and peopln trying to do it from the hexrot machine. I think a clear explicit instruction is missing here. something like -- "open a terminal locally and create ssh tunnel .... "
There was a problem hiding this comment.
I don't think it matters from where you create the ssh tunnel to the PXI, locally or from the hexrot VM, as long as it´s in the WAP network.
| Connect to the M2 Hex Netbooter *m2-hexapod-netbooter.cp.lsst.org* using the credential stored in the *1Password MainTel | ||
| Vault* under *M2 Hexapod PXI/Drive NetBooter*. | ||
| B. For *MTM2Hexapod* while in the LSST-WAP, | ||
| connect to *https://pdu1-tea-as02.cp.lsst.org* using the credentials stored in the *MainTel vault* |
There was a problem hiding this comment.
Then you need to add a screen shot of this PDU as well. Please also include in the figure labels that these are provisional for now (as they may change !)
There was a problem hiding this comment.
Thanks! I also added the missing captions to both figures.
|
|
||
| #. **Power Cycle PXI and drives**: To **power** :guilabel:`Off` the system, first power off the PXI, followed by | ||
| the drive. | ||
|
|
||
| A. For *MTCamHexapod*, PXI is energized through outlet 8, while the drives correspond to outlet 4 in the *PDU*. | ||
| A. For *MTCamHexapod*, PXI is energized through *outlet 8*, while the drives correspond to *outlet 4* in the *https://tea-pdu01.cp.lsst.org PDU*. |
There was a problem hiding this comment.
- outlet 8 should be :guilabel:
Outlet 8because its a clickable and coonsistent with previous notation. It will also highlight the OUtlet number as we do not want anyone accidently switching something else off - outlet 4 -- > :guilabel:
Outlet 4
There was a problem hiding this comment.
Agree. Thanks for noting! Although it's not strictly a button, I think it will benefit from being enhanced and highlighted.
|
|
||
| B. For *MTM2Hexapod*, power off PXI first , then the drive from the *M2 Hexapod PXI/Drive NetBooter*. | ||
| B. For *MTM2Hexapod*, power off the PXI which is *outlet 2*, then turn off the drives in *outlet 1* in the *https://pdu1-tea-as02.cp.lsst.org PDU*. |
There was a problem hiding this comment.
- outlet 2--> :guilabel:
Outlet 2 - outlet 1 --> :guilabel:
Outlet 1
| /etc/init.d/cameraHexapod start | ||
|
|
||
| For *MTM2Hexapod*, replace in the command above *cameraHexapod* | ||
| with *m2Hexapod*. | ||
|
|
||
|
|
||
| #. **Establish an SSH connection to the MTHexapod PXI**: Using the credentials and hostnames found |
There was a problem hiding this comment.
ok. One more comment --
- can you add that this ssh tunnel has to be created from our local computer/laptop ? I saw many of us getting confused and peopln trying to do it from the hexrot machine. I think a clear explicit instruction is missing here. something like -- "open a terminal locally and create ssh tunnel .... "
| Connect to the M2 Hex Netbooter *m2-hexapod-netbooter.cp.lsst.org* using the credential stored in the *1Password MainTel | ||
| Vault* under *M2 Hexapod PXI/Drive NetBooter*. | ||
| B. For *MTM2Hexapod* while in the LSST-WAP, | ||
| connect to *https://pdu1-tea-as02.cp.lsst.org* using the credentials stored in the *MainTel vault* |
isotuela
force-pushed
the
tickets/SITCOM-1590
branch
from
f4d2604
to
84c2e21
Compare
Hi @Kelks19,
Could you please review these updates based on ticket https://rubinobs.atlassian.net/browse/SITCOM-1590?
Many thanks in advance,
Ioana