Link Search Menu Expand Document

System Startup

  1. Bringup Commands
  2. Automate the bringup process

Bringup Commands

Note: All commands must be run from your workspace directory

Start ROS


You always need to start with roscore

Bringup the arm

roslaunch ur_modern_driver ur5e_bringup.launch limited:=true robot_ip:=[IP]

Before you can control the robot arm, you first need to start some ROS servers.

  • Start the robot control server
    • roslaunch ur_modern_driver ur5e_bringup.launch limited:=true robot_ip:=
  • Start MoveIt! (This is only nessecary if you’re planning trajectories in cartesian space)
    • With the real robot
      • roslaunch ur5_e_moveit_config ur5_e_moveit_planning_execution.launch limited:=false
      • roslaunch ur5_e_moveit_config moveit_rviz.launch config:=true
    • With a simulated robot
      • roslaunch ur_e_gazebo ur5e.launch
      • roslaunch ur5_e_moveit_config ur5_e_moveit_planning_execution.launch sim:=true
      • roslaunch ur5_e_moveit_config moveit_rviz.launch config:=true

Bringup the hand

roslaunch hand_arm hand_bringup.launch profile:=[PROFILE]

Determine what config profile to use (we’ll use “anthro7” for these tutorials)

  • Start the hand control server (based on pressure_control_ros package)
    • roslaunch hand_arm hand_bringup.launch profile:=anthro7

Bringup the data recording service

roslaunch rosbag_recorder rosbag_recorder.launch pickle:=true

By default, data is recorded in ROS’s “bag” format, which is hard to interact with later. Instead, you should pickle the data so that it can be efficiently stored and processed later.

(Note, pickling could take a long time if you’re saving large amounts of data)

Automate the bringup process

If you don’t want to start all of these programs independently, you can write some bash scripts to start everything. Write a few scripts in your main workspace folder:

Bringup all hardware


This script starts the ROS servers that handle the arm, hand, and data saving. If you just want to run some trajectories that are already built and planned, you only need these running.

Example: bash hid1 anthro8

roscore &
sleep 1

# Start the data loggers
roslaunch rosbag_recorder rosbag_recorder.launch pickle:=true &
sleep 1

# Start the robot arm
roslaunch ur_modern_driver ur5e_bringup.launch limited:=true robot_ip:= &
sleep 1

# Launch the hand

roslaunch hand_arm hand_bringup.launch profile:=${PROFILE} hw_profile:=${HARDWARE} plot_profile:=${PROFILE} &
sleep 1

# Wait until everything finishes
wait $(jobs -p)

Bringup the planning interface


If you need to build and plan tajectories, you need to start MoveIt! and RViz in addition to bringing up the hardware.


  • UR5e: bash ur5_e
  • UR5e with soft hand: bash ur5e_with_soft_hand


roslaunch ${1}_moveit_config ${1}_moveit_planning_execution.launch limited:=false &
sleep 1

roslaunch ${1}_moveit_config moveit_rviz.launch config:=true &
sleep 1

wait $(jobs -p)

Build and plan all at once


The build and plan steps incolve typing the trajectory name for both. This script allows you to build, then plan all at once.


if [ "$1" != "" ]; then
	roslaunch hand_arm pick-place-build-multi.launch traj:=$1
	echo "Done Building"
	roslaunch hand_arm plan_traj.launch traj:=$1
	echo "Done Planning"
    echo "Please input a trajectory to build/plan"

The result: easy quick-start

Now you’ve reduced the bringup process for the arm and hand to only one command, with two additional commands when you need to build and plan:

bash anthro4
bash example/2finger_grid