Book Image

Mastering ROS for Robotics Programming - Second Edition

By : Jonathan Cacace, Lentin Joseph
Book Image

Mastering ROS for Robotics Programming - Second Edition

By: Jonathan Cacace, Lentin Joseph

Overview of this book

In this day and age, robotics has been gaining a lot of traction in various industries where consistency and perfection matter. Automation is achieved via robotic applications and various platforms that support robotics. The Robot Operating System (ROS) is a modular software platform to develop generic robotic applications. This book focuses on the most stable release of ROS (Kinetic Kame), discusses advanced concepts, and effectively teaches you programming using ROS. We begin with aninformative overview of the ROS framework, which will give you a clear idea of how ROS works. During the course of this book, you’ll learn to build models of complex robots, and simulate and interface the robot using the ROS MoveIt! motion planning library and ROS navigation stacks. Learn to leverage several ROS packages to embrace your robot models. After covering robot manipulation and navigation, you’ll get to grips with the interfacing I/O boards, sensors, and actuators of ROS. Vision sensors are a key component of robots, and an entire chapter is dedicated to the vision sensor and image elaboration, its interface in ROS and programming. You’ll also understand the hardware interface and simulation of complex robots to ROS and ROS Industrial. At the end of this book, you’ll discover the best practices to follow when programming using ROS.
Table of Contents (22 chapters)
Title Page
Copyright and Credits
www.PacktPub.com
Contributors
Preface
Index

ROS-Industrial robot driver package


In this section, we will discuss the industrial robot driver package. If we take the ABB robot as an example, it has a package called abb_driver. This package is responsible for communicating with the industrial robot controller. This package contains industrial robot clients and launches the file to start communicating with the controller. We can check what's inside the abb_driver/launch folder. The following is a definition of a launch file called robot_interface.launch:

<launch> 
  <!-- robot_ip: IP-address of the robot's socket-messaging server --> 
  <arg name="robot_ip" /> 
 
  <!-- J23_coupled: set TRUE to apply correction for J2/J3 parallel linkage --> 
  <arg name="J23_coupled" default="false" /> 
 
  <!-- copy the specified arguments to the Parameter Server, for use by nodes below --> 
  <param name="robot_ip_address" type="str" value="$(arg robot_ip)"/> 
  <param name="J23_coupled" type="bool" value...