Robot Operating System (ROS) is a communication interface that enables different parts of a robot system to discover, send, and receive data. MATLAB® support for ROS is a library of functions that allows you to exchange data with ROS-enabled physical robots, or robot simulators such as Gazebo®.
This example introduces how to:
Set up ROS within MATLAB
Get information about capabilities in a ROS network
Get information about ROS messages
A ROS network comprises different parts of a robot system (such as a planner or a camera interface) that communicate over ROS. The network can be distributed over several machines.
A ROS master coordinates the different parts of a ROS network. It is identified by a Master URI (Uniform Resource Identifier) that specifies the hostname or IP address of the machine where the master is running.
A ROS node is an entity that contains a collection of related ROS capabilities (such as publishers, subscribers and services). A ROS network can have many ROS nodes.
Publishers, subscribers, and services are different kinds of ROS entities that process data. They exchange data using messages.
A publisher sends messages to a specific topic (such as "odometry"), and subscribers to that topic receive those messages. There can be multiple publishers and subscribers associated with a single topic.
to initialize ROS. By default,
rosinit creates a ROS master in MATLAB and starts a "global node" that is connected to the master. The "global node" is automatically used by other ROS functions.
Initializing ROS master on http://bat6303glnxa64:11311/. Initializing global node /matlab_global_node_87922 with NodeURI http://bat6303glnxa64:33679/
to see all nodes in the ROS network. Note that the only available node is the global node created by
exampleHelperROSCreateSampleNetwork to populate the ROS network with three additional nodes and sample publishers and subscribers.
rosnode list again, and observe that there are three new nodes (
/matlab_global_node_87922 /node_1 /node_2 /node_3
A visual representation of the current state of the ROS network is shown below. Use it as a reference when you explore this sample network in the remainder of the example.
The MATLAB global node is disconnected since it currently does not have any publishers, subscribers or services.
to see available topics in the ROS network. Observe that there are three active topics:
rosout is a default logging topic that is always present in the ROS network. The other two topics were created as part of the sample network.
/pose /rosout /scan
to get specific information about a specific topic. The command below shows that
/node_1 publishes (sends messages to) the
/pose topic, and
/node_2 subscribes (receives messages from) that topic (see Exchange Data with ROS Publishers and Subscribers for more information).
rostopic info /pose
Type: geometry_msgs/Twist Publishers: * /node_1 (http://bat6303glnxa64:41584/) Subscribers: * /node_2 (http://bat6303glnxa64:57054/)
to get information about a specific node. The command below show that
node_1 publishes to
/rosout topics, and subscribes to the
rosnode info /node_1
Node: [/node_1] URI: [http://bat6303glnxa64:41584/] Publications (2 Active Topics): * /pose * /rosout Subscriptions (1 Active Topics): * /scan Services (0 Active):
ROS Services provide a mechanism for "procedure calls" across the ROS network. A service client sends a request message to a service server, which processes the information in the request and returns with a response message (see Call and Provide ROS Services).
to see all available service servers in the ROS network. The command below shows that two services (
/reply) are available.
to get information about a specific service.
rosservice info /add
Node: /node_3 URI: rosrpc://bat6303glnxa64:41925/ Type: roscpp_tutorials/TwoInts Args: A B
Publishers, subscribers, and services use ROS messages to exchange information. Each ROS message has an associated message type that defines the datatypes and layout of information in that message (See Work with Basic ROS Messages).
to see the message type used by a topic. The command below shows that the
/pose topic uses messages of type
rostopic type /pose
to view the properties of a message type. The
geometry_msgs/Twist message type has two properties,
Angular. Each property is a message of type
geometry_msgs/Vector3, which in turn has three properties of type
rosmsg show geometry_msgs/Twist
% This expresses velocity in free space broken into its Linear and Angular parts. Vector3 Linear Vector3 Angular
rosmsg show geometry_msgs/Vector3
% This represents a vector in free space. double X double Y double Z
to see the full list of message types available in MATLAB.
ackermann_msgs/AckermannDrive ackermann_msgs/AckermannDriveStamped actionlib/TestAction actionlib/TestActionFeedback actionlib/TestActionGoal actionlib/TestActionResult actionlib/TestFeedback actionlib/TestGoal actionlib/TestRequestAction actionlib/TestRequestActionFeedback actionlib/TestRequestActionGoal actionlib/TestRequestActionResult actionlib/TestRequestFeedback actionlib/TestRequestGoal actionlib/TestRequestResult actionlib/TestResult actionlib/TwoIntsAction actionlib/TwoIntsActionFeedback actionlib/TwoIntsActionGoal actionlib/TwoIntsActionResult ...
exampleHelperROSShutDownSampleNetwork to remove the sample nodes, publishers, and subscribers from the ROS network. This command is only needed if the sample network was created earlier using
to shut down the ROS network in MATLAB. This shuts down the ROS master that was started by
rosinit and deletes the global node. It is recommended to use
rosshutdown once you are done working with the ROS network.
Shutting down global node /matlab_global_node_87922 with NodeURI http://bat6303glnxa64:33679/ Shutting down ROS master on http://bat6303glnxa64:11311/.