HOWTOs

This page contains a set of short informal recipes to help you solve common challenges you may face when using RTI Connext DDS. This recipes include topics such as configuring favorite IDE to work with our libraries, tuning the performance of your application, or configuring your firewall to let DDS traffic through.

You can contribute by commenting on existing HOWTOs or creating your own here (requires logging in).

There are various strategies that can be used to have DDS applications communicate between each other despite the fact that one or more of these applications are protected by a firewall. This HOWTO focuses in the situation where there is a desire to use static configuration (i.e. manually open specific ports or multicast addresses in the firewall) and the applications are protected with Firewalls but are not behind Network Address Translators (NATs).
23360 reads — 1 comment
Xenomai is a real-time development framework that provides interface-agnostic hard real-time support to user-space applications in a Linux environment. The purpose of this HOWTO is to describe the installation and configuration of a Xenomai environment to develop applications using RTI Connext DDS.
17232 reads — 2 comments
DDS has a built-in discovery service. This means it can automatically detect the presence of other DDS applications and their entities, that is DomainParticipants, DataWriters, DataReaders, Topics, as they appear and disappear from the DDS domain.
13663 reads — 3 comments
By default RTI Connext DDS will use multicast to discover other DDS Participants in the network. This post explains how to disable multicast in your applications.
15435 reads — 1 comment
Step by step instructions to setup XCode to develop DDS applications. The installation of DDS comes with many sample application code in the $NDDSHOME/example folder. We will use the Hello_simple C application as an example, and we will setup the XCode environment to build and run the publisher of Hello_simple
7011 reads — 0 comments
DDS provides a reliability protocol that can be tuned for optimum performance on a per data stream basis. The reliability protocol is configured and tuned by these QoS policies: Reliability, History, Resource Limits, DataWriter Protocol, and DataReader Protocol.
27146 reads — 1 comment

I have noticed in our support forums a common question regarding the use of WaitSets and the fact that sometimes they don't behave as people initially expect. Often the question is posed along the lines of "Why does my WaitSet not block? Why does my subscriber using WaitSets consume so much CPU?

11220 reads — 2 comments

Pages