This repo is old, and connects to ROS 1 only. For ROS2 connectivity, use https://github.com/UM-ARM-Lab/vr_ros2_bridge
This is the ROS portion of the armlabs VR teleopeartion suite. You will also need the Unity package. You can find further explanation on the wiki.
Videos of the Robot operated using this software can be found on Youtube:
Dependencies
- moveit (planning interface, visual-tools)
- kuka_iiwa_interface (https://github.com/UM-ARM-Lab/kuka_iiwa_interface)
- robotiq (https://github.com/UM-ARM-Lab/robotiq)
(This is a quick reference. See the tutorials for more detailed instructions)
You will need
- A windows computer with unity connected to the Vive with the Unity package
- A linux computer (or virtual machine) with ROS
- (optionally) A linux computer connected to the physical robot, exposing the proper interface
- (optionally) A linux computer connected to a kinect publishing a pointcloud
Currently in the armlab you will need the computer armor
. You will also need the computer realtime
and loki
if you are running the physical robot.
-
Connect HTC Vive to computer (or plug in battery if using wireless)
-
(If using wireless) Launch VIVE Wireless
-
Launch SteamVR
- Launch Steam
- Click on Library > VR
- Select SteamVR and click play
If you are running SteamVR for first time, please start the SteamVR room setup to calibrate the device.
Note in this example the computer loki
is connected to the Kinect. realtime
provides the interface to the physical robot.
Terminal 1:
ssh loki
roscore
Terminal 2:
ssh realtime
export ROS_MASTER_URI=http://loki.local:11311
roslaunch victor_hardware_interface dual_arm_lcm_bridge.launch
Terminal 3:
ssh loki
roslaunch mps_launch_files kinect_vicon_real_robot.launch pov:="victor_head" fps_limit:="10"
Terminal 4:
export ROS_MASTER_URI=http://loki.local:11311
rosrun dual_arm_teleop make_victor_fast.py
roslaunch unity_launch_files unity_setup.launch
Note: Current version mismatch. Need to edit victor_utils
. Delete the /
from the service call name. Then export ROS_NAMESPACE=/victor
(Note, if make_victor_fast
fails, check that the Victor robot is in impedance mode)
- Launch unity, and open the project
unity_victor_teleop
- Check that the IP is correct.
RosBridgeSettings
from the unity panel must match the IP from the linux computer running the unity setup (The IP of the vm on armor, which you can see usingifconfig
). The form isws://10.10.10.124:9090
Play
the unity environment
The controls for operating the robot are as follows:
- Menu button -
- Trackpad
Teleportation - System button
- Status light
- Micro-USB port
- Tracking sensor
- Trigger - open and close the grippers
- Grip button - "Grab" the robot arm
-
If SteamVR is having trouble detecting the Vive headset, try switching on/off the SteamVR beta
Found by right clicking SteamVR > Properties > Betas > Select the beta you would like to opt into
-
Read the SteamVR for Linux guide to make sure everything is configured properly
-
If Unity is not detecting any input from ROS (kinematics, kinect), check the ip address match between the Unity RosConnector node and the ubuntu VM (run
ifconfig
)
- If errors about missing packages, make sure you installed everything needed for ROS-sharp. e.g.
cannot find rosbridge_websocket
means you missed installingsudo apt-get install ros-kinetic-rosbridge-server