Look below for guidance on the labs
The SAs have provided a sample .bashrc file, which can be found HERE
To install, run: cd ~ && curl -O https://raw.githubusercontent.com/RBE300X-Lab/RBE3002_info/main/.bashrc && source .bashrc in your terminal
These are the only supported versions
- See the Troubleshooting Guide
- To report unresolved hardware/TurtleBot issues, please add repair notes to the TurtleBot Checklist document.
TurtleBot Netowork Configuration Guide
DO NOT DO:
- Keep the battery with the robot, instead return it to the charging station and plug it in
- Use the robot on a random table where it might fall
PLEASE DO:
- Use the cable instead of the battery as much as possible (the batteries have a limited number of recharges)
- If you are using the robot with the cable, place the robot on the power supply so the wheels do not touch the ground (no robots falling on the floor)
- Always store the battery in the provided bag
- Use the robot only on the ground or in the arena we made available
Connecting to a Turtlebot
- To connect to your Turtlebot, type
ssh ubuntu@TURTLEBOT-NAME.dyn.wpi.eduwhere TURTLEBOT-NAME is the name on the turtlebot (ignore the number)- The passowrd for all turtlebots is
turtlebot
- The passowrd for all turtlebots is
- To disconnect from the Turtlebot (and leave the robot on), type
exitin the terminal you ssh'ed from - To disconnect and shutdown the Turtlebot, type
sudo shutdown nowin the terminal you ssh'ed from
-
Please copy and paste terminal commands while running the ROS installation. You can do this
CTRL + SHIFT + Cto copy from the terminal andCTRL + SHIFT + Vfor pasting into the terminal -
If you have errors at
sudo apt install curl, runsudo apt-get install --fix-missingand then try the first command again. Proceed from there. -
You will need to add
source /opt/ros/noetic/setup.bashto your .bashrc file. This file is run every time you open a new terminal, and will source ROS automatically for you. You can access this file by runninggedit ~/.bashrc(or similar text editing options). Pastesource /opt/ros/noetic/setup.bashinto this file. -
Also add source
~/catkin_ws/devel/setup.bashto your .bashrc as well, this can prevent issues when adding packages to your catkin workspace -
There is a sample .bashrc in this repository, which can be found HERE
-
Note in the above command that you should be using ROS Noetic. Anytime you see kinetic or melodic in a command, you need to replace it with noetic.
- Edit the roslaunch nodeprocess Python script using
sudo nano /opt/ros/noetic/lib/python3/dist-packages/roslaunch/nodeprocess.py- Other editors are allowed, but this does require
sudoaccess (editing files in protected directories), so it cannot be done on the lab computers
- Other editors are allowed, but this does require
- Change the default timeout values:
DEFAULT_TIMEOUT_SIGINTon line 59 will make Gazebo quit faster, we suggest changing this value from the default 15 to 1DEFAULT_TIMEOUT_SIGTERMon line 60 will make ROS quit faster if something hangs and will not close any other way, keeping the default 2 is fine- If something has hung (like a Python infinite loop), you can also force quit them from the terminal using
CTRL + \
- If something has hung (like a Python infinite loop), you can also force quit them from the terminal using
- With the switch to Python3, the tf scirpt
view_framesis broken, to fix it, follow these instructions - Edit the source code by running:
sudo nano /opt/ros/noetic/lib/tf/view_frames- Other editors are allowed, but this does require
sudoaccess (editing files in protected directories), so it cannot be done on the lab computers
- Other editors are allowed, but this does require
- Replace line 89 (
m = (r.search(vstr))) withm = r.search(vstr.decode('utf-8'))
Username: rbe | Password: RBE3002
- Download the RBE3002.pvm.zip from the HERE
- Move the RBE3002.pvm.zip file to your Parallels VM Directory
(ex: /Users/<Your Username>/Parallels/) - Unzip the file (this will take a few minutes)
- Open Parallels Desktop
- Drag the new .pvm file into Parallels
- Open the VM settings (click the gear)
- Navigate to
Hardware->Network - Change
SourcetoWi-Fi - Click
Advanced..and thenGeneratea new MAC Address - Log into netreg.wpi.edu and click
Register New Device - Use the newly generate MAC Address to register your VM on the network
- If you get either a
Multicast MAC AddressesorLocally Administered Addresses (LAA)errors, change the second character of the MAC Address (the X: 0X-B0-D0-63-C2-26) to an8and retry - This is because the 2 least significant bits of the first octet (the first two characters) are used as flags for device administration (the Universal vs Local and Unicast vs Multicast bits respectively) for WPI Netreg they must be set to 0
- Download the RBE3002.utm.zip from the HERE
- Move the RBE3002.utm.zip file to your UTM VM Directory
(ex: /Users/<Your Username>/Library/Containers/com.utmapp.UTM/Data/Documents/)
- Unzip the file (this will take a few minutes)
- Open UTM (there should be a new VM called RBE 3002)
- Open the VM settings (click the sliders in the top right of the window)
- Navigate to
Network - Change
Network ModetoBridged (Advanced) - Generate a new MAC Address using
random - Log into netreg.wpi.edu and click
Register New Device - Use the newly generate MAC Address to register your VM on the network
- If you get either an
Locally Administered Addresses (LAA)orMulticast MAC Addresseserrors, change the second character of the MAC Address (the X: 0X-B0-D0-63-C2-26) to an8and retry - This is because the 2 least significant bits of the first octet (the first two characters) are used as flags for device administration (the Universal vs Local and Unicast vs Multicast bits respectively) for WPI Netreg they must be set to 0