Skip to content

Commit ff61605

Browse files
committed
Updated README
1 parent e1b6963 commit ff61605

File tree

1 file changed

+27
-1
lines changed

1 file changed

+27
-1
lines changed

README.md

Lines changed: 27 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
# Overview
2-
This package contains control software and utilities for using the Robot Autonomy course arms.
2+
This package contains control software and utilities for using the robots for the CMU 16-662: Robot Autonomy course.
33

44
# Dependencies
55
This package requires the following software dependencies:
@@ -18,5 +18,31 @@ cd ~/ws/robauton_lab1
1818
catkin_make
1919
```
2020

21+
# Basic Usage
22+
After successful installation and build:
23+
```
24+
source ~/ws/robauton_lab1/devel/setup.bash
25+
cd ~/ws/robauton_lab1/cmu-16662-robot-ctrl
26+
roslaunch launch/position_control.launch
27+
```
28+
29+
While this is running, in a separate terminal window (**NOTE**: the robot will move after these commands):
30+
```
31+
source ~/ws/robauton_lab1/devel/setup.bash
32+
cd ~/ws/robauton_lab1/cmu-16662-robot-ctrl
33+
python scripts/command_joints.py
34+
```
35+
36+
# Troubleshooting
37+
The argument `device_name` in `position_control.launch` needs to be updated to the actual device being used on your platform, which is the USB device that the U2D2 controller is using. If the default parameter in `position_control.launch` is not valid, the following command will show the device name:
38+
```
39+
dmesg | grep 'attached to tty'
40+
```
41+
The message will appear similar to:
42+
```
43+
[ 9.602622] usb 1-3: FTDI USB Serial Device converter now attached to ttyUSB0
44+
```
45+
In this case, `ttyUSB0` is indeed the device name. Change your launch script as appropriate based on the actual device your platform is using.
46+
2147
# Attribution
2248
Thanks to Adithya Murali (@adithyamurali) for creating the skeleton and basic usage scripts.

0 commit comments

Comments
 (0)