Permalink
Browse files

Added some clarifications

  • Loading branch information...
1 parent b480fe2 commit 042aff4ac00ea2f3693385026e32ab2515f99d76 @ipa-robotino ipa-robotino committed Feb 13, 2012
Showing with 2 additions and 2 deletions.
  1. +2 −2 manual/Administrator_manual.tex
  2. BIN manual/Care-O-bot_manual.pdf
@@ -215,7 +215,7 @@ \subsubsection{Setup bash environment}
\begin{lstlisting}
cp ~/git/setup/cob-pcs/user.bashrc ~/.bashrc
\end{lstlisting}
-In the bashrc of the users you have to define the correct ROBOT (cob3-X), lines 113 and 114, and the ROBOT\_ENV line 115.\\
+In the bashrc of the users you have to define on the bottom the \textit{ROS\_MASTER\_URI}(http://cob3-X-pc1:11311), the \textit{ROBOT} (cob3-X) and the \textit{ROBOT\_ENV}.\\
If you logout and login again or source your \textit{$\sim$/.bashrc}, you should see different terminal colors for each pc and the \textit{ROS\_PACKAGE\_PATH} should be configured. If you check
\begin{lstlisting}
roscd cob_bringup
@@ -300,7 +300,7 @@ \subsection{Create a new user account}
sudo ./cobadduser new_user_name
\end{lstlisting}
-All you need to do now is to login as the new user, create an ssh-key and add the key to the authorized keys to be able to login to all pcs without password. This is necessary for launching nodes remotely on all pcs.
+All you need to do now is to login as the new user, create an ssh-key and add the key to the authorized keys to be able to login to all pcs without password. This is necessary for launching nodes remotely on all pcs. The following lines are an example for cob3-3:
\begin{lstlisting}
ssh-keygen
ssh-copy-id cob3-3-pc1
Binary file not shown.

0 comments on commit 042aff4

Please sign in to comment.