Help us make these docs great!

All rapyuta.io docs are open source. See something that's wrong or unclear? Submit a pull request.

Make a contribution

ROS Publisher Subscriber (Native)

A ROS publisher is part of a ROS package. It is a public git repository, which is built into a running docker container on the fly when the package is being deployed. A ROS subscriber is also a part of the same ROS package.

Learning objectives

The tutorial will show you how to deploy and establish a communication in a basic ROS package with a ROS publisher and ROS subscriber components running on the cloud by using a native network.

Prerequisites

  1. Ensure that the Google Chrome browser is installed on the computer.
  2. You should be familiar with the below tools:
    1. Git
    2. UNIX/LINUX command terminal
    3. ROS topics
    4. ROS services

Estimated time

15 minutes

Creating the io-tutorial build

To create the build, follow below steps. Skip the following steps if you have already created an io-tutorials build earlier.

  1. On the left navigation bar, click Development>Builds.
  2. Click on ADD NEW BUILD
  3. In the Build Name box, enter a name for the build say io-tutorials
  4. In the Git repository box, enter the URL address : https://github.com/rapyuta/io_tutorials and select Build Recipe as Catkin.
  5. Go to the next step and click on next, the build will be created.

The build takes about two to five minutes to build the source code in the io_tutorials repository into a running docker container. You may analyze the corresponding build logs, which helps in debugging failed builds. Please proceed to creation of package once the build is complete.

Creating the Package

To create the native publisher subscriber package using the console, follow the steps:

  1. On the left navigation bar, click Development>Catalog.
  2. Click ADD NEW PACKAGE.
  3. In the Package Name box, type in a name for the package say Native publisher subscriber
  4. In the Package Version box, enter the version of the package you are creating. The default value is 1.0.0
  5. Ensure that Is a bindable package is selected.
  6. In the Description box, provide a summary of the package.
  7. Click NEXT.

The package has two components: the talker and listener running on the cloud.

  1. Talker component (aka ROS publisher)
    1. In the Component Name box, enter a name for the component, say talker

      The name of a component must consist of alphabets [A-Z, a-z], digits [0-9], hyphen - and an underscore _ character. It must not begin with a digit.

    2. For Component Runtime, click Cloud.

    3. Ensure Is ROS Component is selected.

    4. Ensure the ROS Version is Kinetic.

    5. Set the value of Replicas to run the component to the number 1 (default value).

    6. In the Executable Name box, enter a name for the executable say talkerExecutable

      The name of an executable must consist of alphabets [A-Z, a-z], digits[0-9], hyphen - and an underscore _ character, and must not start with a digit.

    7. For Executable Type, click on Builds.

    8. In the Choose Build select the first Build io-tutorials from the drop-down list.

    9. In the Command to run in the docker container box, enter the command:

      roslaunch talker talker.launch
      

      Ensure you always execute the command roslaunch to explicitly start the ROS Master instead of running the rosrun command, because the ROS Master will fail to start on rosrun, and eventually, the deployment will fail as well. talkerExecutable

    10. The talkerExecutable publishes a ROS topic, /telemetry
      To add a ROS topic, click Add ROS topic. In the Name box, enter the name of the ROS topic. Select Maximum for QoS.

  2. Listener component (aka ROS subscriber)
    1. In the Component Name box, type in a name for the component, say listener

      The name of a component must consist of alphabets [A-Z, a-z], digits [0-9], hyphen - and an underscore _ character, and must not begin with a digit.

    2. For Component Runtime, click Cloud.

    3. Ensure Is ROS Component is selected.

    4. Ensure the ROS Version is Kinetic.

    5. In the Executable Name box, type in a name for the executable, for example, listenerExecutable

      The name of an executable must consist of alphabets [A-Z, a-z], digits [0-9], hyphen - and an underscore _ character, and must not begin with a digit.

    6. For Executable Type, click on Builds.

    7. In the Choose Build select the second Build io-tutorials from the drop-down list.

    8. In the Command to run in the docker container box, enter the command:

      roslaunch listener listener.launch
      

      Ensure you always execute the command roslaunch to explicitly start the ROS Master instead of running the rosrun command, because the ROS Master will fail to start on rosrun, and eventually, the deployment will fail as well.

    9. Click NEXT > CONFIRM PACKAGE CREATION.

Create a Native Network

If you have already created a native network, you can skip this procedure. For more information about native network, click here

Perform the following procedure to create a native network.

  1. On the left navigation bar, click Networking>Networks.

  2. Click ADD NETWORK and select the network type as Native Network.

  3. In the Create new native network dialog-box, enter cloud_native_network1 as the name for the native network.

  4. Select ROS Distro, as Kinetic.

  5. Select the Runtime as Cloud.

  6. From the Resource limit field, select the memory allocation and computational ability of the routed network. These resources are reserved in the platform for effective ROS communication. For this tutorial, you can select Small: 1cpu core, 4 GiB memory as the resource limit.

  7. Click CONTINUE and wait for the native network to be successfully running.

Deploying the package

To deploy a package using the console, follow the steps:

  1. On the left navigation bar, click Development>Catalog.
  2. Select the native publisher subscriber package.
  3. Click Deploy package.
  4. In the Name of deployment box, enter a name for the deployment you are creating say Native Publisher Subscriber Deployment.
  5. Click on Native NETWORK > Add, select the native network, cloud_native_network1, from the drop-down list.
  6. Click CREATE DEPLOYMENT > Confirm.

You will be redirected to the newly created deployment’s Details page where a green colored bar moves from In progress to Succeeded with Status:Running indicating that the DEPLOYMENT PHASE has Succeeded, and the STATUS is Running.

You may also analyze the corresponding deployment logs to check if everything is working OK.

Docker Publisher Subscriber Deployment

The listener-listenerExecutable will be streaming /listener I heard hello_world logs.

ROS Subscriber logs

while talker-talkerExecutable will be publishing hello_world logs.

ROS Publisher logs