Revision history [back]

The first steps would obviously be to google/search the wiki if someone has done this already. It looks like you already did that, so you'll need to port the robot on your own. Unfortunately, I am not aware of a generic "porting robots to ROS" guide. Here are (some) of the steps that you'll need to do for that, assuming that you not only want to use ROS for communication, but also want to utilize other packages like, e.g. navigation.

• Setup a URDF description for your robot. You should have understood tf and read the following REPS:
  • http://www.ros.org/reps/rep-0103.html
  • http://www.ros.org/reps/rep-0105.html
• Port your drivers to ROS, here it is very advisable to look for common ROS messages, that obvisouly depend on the hardware. Some examples:
  • geometry_msgs/Twist for controlling base movements
  • sensor_msgs/JointState for publishing joint states (angles) of articulated robots
  • sensor_msgs/LaserScan for lasers
• Setup launch files that bring up your robot

This should leave you with a robot that runs, can be teleoperated, and where you can visualize everything in rviz.

More things to look into are diagnostics, navigation, arm navigation.

The first steps would obviously be to google/search the wiki if someone has done this already. It looks like you already did that, so you'll need to port the robot on your own. Unfortunately, I am not aware of a generic "porting robots to ROS" guide. Here are (some) of the steps that you'll need to do for that, assuming that you not only want to use ROS for communication, but also want to utilize other packages like, e.g. navigation.

• Setup a URDF URDF description for your robot. You should have understood tf tf and read the following REPS:
  • http://www.ros.org/reps/rep-0103.html
  • http://www.ros.org/reps/rep-0105.htmlREP 103
  • REP 105
• Port your drivers to ROS, here it is very advisable to look for common ROS messages, that obvisouly depend on the hardware. Some examples:
  • geometry_msgs/Twist for controlling base movements
  • sensor_msgs/JointState for publishing joint states (angles) of articulated robots
  • sensor_msgs/LaserScan for lasers
• Setup launch files that bring up your robot

This should leave you with a robot that runs, can be teleoperated, and where you can visualize everything in rviz.

More things to look into are diagnostics, diagnostics, navigation, arm navigation.

The first steps would obviously be to google/search the wiki if someone has done this already. At least some parts are probably already done, for example laser or camera drivers. It looks like you already did that, so you'll need to port the robot on your own. Unfortunately, I am not aware of a generic "porting robots to ROS" guide. Here are (some) of the steps that you'll need to do for that, assuming that you not only want to use ROS for communication, but also want to utilize other packages like, e.g. navigation.

• Setup a URDF description for your robot. You should have understood tf and read the following REPS:
  • REP 103
  • REP 105
• Port your drivers to ROS, here it is very advisable to look for common ROS messages, that obvisouly depend on the hardware. Some examples:
  • geometry_msgs/Twist for controlling base movements
  • sensor_msgs/JointState for publishing joint states (angles) of articulated robots
  • sensor_msgs/LaserScan for lasers
• Setup launch files that bring up your robot

This should leave you with a robot that runs, can be teleoperated, and where you can visualize everything in rviz.

More things to look into are diagnostics, navigation, arm navigation.