Skip to content

INTERACT-tud-amr/dinova

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

82 Commits
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Dinova

ROS software stack for Dinova (dingo + kinova).

Running a real robot

Turn off default ros packages by Clearpath

sudo systemctl stop ros.service

To launch the control interface for Dinova:

roslaunch dinova_bringup dinova.launch

To launch the control interface for Dingo:

roslaunch dinova_bringup dingo.launch

To launch the control interface for Kinova:

roslaunch dinova_bringup kinova.launch

Running a real robot with Vicon

The default config for Vicon consists of the robot and the mug1 object. To change it, you need to modify the launch file in an appropriate launch file within the dinova_bringup package.

To launch the control interface for Dinova with Vicon:

roslaunch dinova_bringup dinova.launch

To launch the control interface for Dingo with Vicon:

roslaunch dinova_bringup dingo.launch

To launch the control interface for Dinova with Vicon and an (unactive) lidar-stack:

roslaunch dinova_bringup dinova.launch lidar:=true

Description

  1. dinova_bringup -> Contains launch files for controlling Dinova, Kinova and Dingo.
  2. dinova_control -> Contains ROS driver for Kinova and the node that collects states from all robots. For more information here.
  3. dinova_description -> URDF files for Dinova, Kinova and Dingo. For more information here.
  4. dinova_gazebo -> Gazebo package for simulating Dinova, Kinova and Dingo. For more information here.

Sensors

  • Lidar Velodyne VLP16

TODO:

  1. Vicon node is missing
  2. Gripper_driver