Integration

.gitignore

@@ -11,5 +11,8 @@ venv
 # Vim stuff
 *.swp
 
+# Ansible stuff
+*.retry
 
+# Catkin stuff
 CATKIN_IGNORE

.gitmodules

@@ -9,3 +9,13 @@
 [submodule "realsense-ros"]
 	path = submodules/realsense-ros
 	url = [email protected]:IntelRealSense/realsense-ros.git
+[submodule "submodules/gpd"]
+	path = submodules/gpd
+	url = https://github.com/kekeblom/gpd
+[submodule "submodules/gpd_ros"]
+	path = submodules/gpd_ros
+	url = ssh://[email protected]/kekeblom/gpd_ros
+[submodule "submodules/yumi"]
+	path = submodules/yumi
+	url = [email protected]:ethz-asl/yumi.git
+	branch = asl-devel

README.md

@@ -39,18 +39,15 @@ More detailed instructions on the setup and operation of our robotic platforms,
 
 ## Ansible Playbooks
 
-This section needs to be updated.
+The `operations/` directory contains some Ansible playbooks which are there to automate and document how to set up a computer.
 
-The `playbooks/` directory contains some Ansible playbooks which are there to automate and document how to set up the machine. `playbooks/setup_ros.yaml` will install ROS. `playbooks/setup_repo.yaml` will create a catkin workspace and clone this repository on the machine. `playbooks/setup_realsense.yaml` will install realsense dependencies and clone the [realsense-ros](https://github.com/IntelRealSense/realsense-ros) repository.
+To run a playbook, first install Ansible (`pip install --user ansible`). Copy the hosts file `operations/hosts` to `/etc/ansible/hosts`.
 
-To run a playbook, first install Ansible (`pip install --user ansible`). Copy the file `playbooks/hosts` to `/opt/ansible/hosts` or specify the inventory file with the `-i` option every time you run `ansible-playbook` (e.g. `ansible-playbook playbooks/setup_ros.yaml -i playbooks/hosts --ask-pass --ask-become-pass`.
-
-The hosts file is an inventory file specifying which machines the playbooks are run against. Currently it only contains one group `franka-box` which's ip should point to the ubuntu machine controlling the Franka arm.
-
-Setting up the machine is done by running the commands:
+The hosts file is an inventory file specifying groups of hosts. A playbook is always run against a group and all the commands will be run on all machines in that group.
 
+To set up the franka control computer, run:
 ```
-ansible-playbook playbooks/setup_ros.yaml --ask-pass --ask-become-pass
-ansible-playbook playbooks/setup_repo.yaml --ask-pass --ask-become-pass
-ansible-playbook playbooks/setup_realsense.yaml --ask-pass --ask-become-pass
+ansible-playbook operations/setup_franka.yaml --ask-pass --ask-become-pass
 ```
+The `--ask-pass` flag is not needed if ssh authentication is being used.
+

moma_bringup/launch/mobmi_control_moveit_rviz.launch

@@ -0,0 +1,28 @@
+<?xml version="1.0" ?>
+<launch>
+
+  <arg name="launch_rviz" default="true"/>
+
+  <!-- Load robot description -->
+  <param name="robot_description" command="$(find xacro)/xacro '$(find moma_description)/urdf/mobmi.urdf.xacro'" />
+
+  <!-- Launch Yumi drivers -->
+  <include file="$(find yumi_support)/launch/robot_interface.launch"/>
+
+  <!-- Launch MoveIt -->
+  <include file="$(find mobmi_moveit_config)/launch/move_group.launch">
+    <arg name="load_robot_description" value="false" />
+    <arg name="allow_trajectory_execution" value="true" />
+    <arg name="fake_execution" value="false"/>
+    <arg name="info" value="true"/>
+  </include>
+
+  <!-- Launch state publisher -->
+  <node name="robot_state_publisher" pkg="robot_state_publisher" type="robot_state_publisher" respawn="true" output="screen"/>
+
+  <!-- Launch rviz if requested -->
+  <include if="$(arg launch_rviz)" file="$(find mobmi_moveit_config)/launch/moveit_rviz.launch">
+    <arg name="rviz_config" value="$(find mobmi_moveit_config)/launch/moveit.rviz" />
+  </include>
+
+</launch>

moma_bringup/launch/yumi_control_moveit_rviz.launch

@@ -1,14 +1,18 @@
 <?xml version="1.0" ?>
 <launch>
 
-  <arg name="rviz" default="true"/>
+  <arg name="launch_rviz" default="true"/>
+
+  <!-- Load robot description -->
+  <param name="robot_description" command="$(find xacro)/xacro '$(find moma_description)/urdf/yumi.urdf.xacro'" />
 
   <!-- Launch Yumi drivers -->
   <include file="$(find yumi_support)/launch/robot_interface.launch"/>
 
   <!-- Launch MoveIt -->
   <include file="$(find yumi_moveit_config)/launch/move_group.launch">
-    <arg name="allow_trajectory_execution" value="true"/>
+    <arg name="load_robot_description" value="false" />
+    <arg name="allow_trajectory_execution" value="true" />
     <arg name="fake_execution" value="false"/>
     <arg name="info" value="true"/>
   </include>
@@ -17,7 +21,7 @@
   <node name="robot_state_publisher" pkg="robot_state_publisher" type="robot_state_publisher" respawn="true" output="screen"/>
 
   <!-- Launch rviz if requested -->
-  <include if="$(arg rviz)" file="$(find yumi_moveit_config)/launch/moveit_rviz.launch">
+  <include if="$(arg launch_rviz)" file="$(find yumi_moveit_config)/launch/moveit_rviz.launch">
     <arg name="rviz_config" value="$(find yumi_moveit_config)/launch/moveit.rviz" />
   </include>
 

moma_demos/fetch_demo/README.md

@@ -3,34 +3,26 @@
 
 ## Launching the demo on the multi-machine setup
 
-### As a single launch file
-
-On the machine used for the user interface, run the following command to distribute the nodes.
-
-```bash
-roslaunch fetch_demo single_command.launch
-```
-
 ### Via SSH
 
 There is one launch file for each machine in the setup. They can all be launch from the user interface laptop via SSH as follows.
 
 Navigation nodes on ridgeback machine:
 
 ```bash
-ssh asl-admin@asl-ridgeback "source /home/asl-admin/catkin_ws/devel/setup.zsh && roslaunch fetch_demo navigation.launch"
+ssh -t asl-admin@asl-ridgeback "source /home/asl-admin/.zshrc && roslaunch fetch_demo navigation.launch"
 ```
 
 Manipulation nodes on YuMi machine:
 
 ```bash
-ssh asl-admin@asl-yumi "source /home/asl-admin/catkin_ws/devel/setup.zsh && roslaunch fetch_demo manipulation.launch"
+ssh -t asl-admin@asl-yumi "source /home/asl-admin/.zshrc && roslaunch fetch_demo manipulation.launch"
 ```
 
 Perception nodes on moma-laptop:
 
 ```bash
-ssh asl-admin@moma-laptop "source /home/asl-admin/catkin_ws/devel/setup.zsh && roslaunch fetch_demo perception.launch"
+ssh -t asl-admin@moma-laptop "source /home/asl-admin/.zshrc && roslaunch fetch_demo perception.launch"
 ```
 
 On local user interface machine:
@@ -40,3 +32,30 @@ roslaunch fetch_demo user_interface.launch
 ```
 
 Each of these commands is blocking, they should be run in separate terminals.
+
+### As a single launch file
+
+On the machine used for the user interface, run the following command to distribute the nodes.
+
+```bash
+roslaunch fetch_demo single_command.launch
+```
+
+This only works if all nodes in this launch file are also installed on the local machine.
+
+
+## Useful commands
+
+### Test the approach node
+
+Send goals directly to move_base:
+
+``bash
+rosrun actionlib axclient.py move_base move_base_msgs/MoveBaseAction
+```
+
+Send goals to the approach action:
+
+```bash
+rosrun actionlib axclient.py approach_action fetch_demo/ApproachAction
+```

moma_demos/fetch_demo/config/joint_configurations.yaml

@@ -0,0 +1,11 @@
+home_joints_l: [0, -2.26893, 0.5235, 0, 0.698132, 0, 2.35619]
+ready_joints_l:  [0.15707963, -1.58824962,  0.55850536,  0.31415927,  1.23918377, -0.78539816,  0.54105207]
+grasp_waypoint_l: [ 0.45378561, -0.64577182,  0.34906585,  0.68067841,  0.9424778 , -0.78539816, -0.38397244]
+
+search_joints_r: [-0.36651914, -1.79768913,  1.04719755,  1.79768913,  0.27925268, 0.2443461 ,  1.34390352]
+
+scan_joint_values: 
+ - [ 0.01745329, -1.36135682, -0.12217305, -0.12217305,  2.12930169, 1.44862328, -0.31415927]
+ - [-0.34906585, -0.76794487, -0.41887902, -0.2268928 ,  2.16420827, 1.44862328,  0.2443461 ]
+ - [-1.25663706, -1.02974426, -0.48869219,  0.19198622,  2.25147474, 1.57079633,  0.52359878]
+ - [-1.46607657, -1.20427718, -0.45378561, -0.17453293,  2.11184839, 1.57079633,  1.27409035]