ROS Resources: Documentation | Support | Discussion Forum | Service Status | Q&A

Integration Service ROS 2 System Handle supports QoS

Integration Service enables a standardized intercommunication of numerous protocols: Fast DDS, FIWARE, ROS, ROS 2 and WebSocket.

It is well known that QoS (Quality of Service) policies are critical to tune communication between nodes (Reliability, Durability, Liveliness, Lease duration,…).

QoS are ROS 2 features that define data behaviour models for the ROS 2 entities. An experienced user with knowledge of ROS 2 systems recognizes how the QoS are applied and what effect they would have on each of the entities.

Now, Integration Service provides support for ROS 2 QoS by means of the ROS 2 System Handle. Meaning that the wide variety of settings that ROS 2 provides can be also configured in Integration Service.

If you want to dig into more details:

  • We have created a NEW detailed example based on a widely extended case in the robotics world: the bridge between DDS and ROS 2.

  • You will find how the YAML file should be configured so that these QoS are made effective in the internal entities of Integration Service. Check it out here.

This functionality, which has been repeatedly asked for by the community, is not yet fully tested. Therefore, we kindly invite users to volunteer using it and provide feedback!

Hi there
To give an interesting update, there is now a Integration Service Docker image available!

The Docker image is provided in the Integration Service download section of eProsima to simplify running the examples.

It contains an installed and ready to use Integration Service workspace and a suite of useful examples:

  • Examples that connect different protocols which handle different types (DDS, ROS2, ROS1, Websocket):
    • Examples based on publisher - subscriber paradigm
    • Examples based on client - server paradigm
  • Examples that bridge logically isolated applications written under the same protocol are also available

One of the biggest advantages to a Docker-based architecture is actually standardization. It provides repeatable development, build, test, and production environments.

You will find more information about the Integration Service Docker importing, running and examples here.