RTI Routing Service setup

Question

I have a problem getting the RTI Routing Service to work with my applications.

I have created a simple DDS publisher application and a simple DDS subscriber application. The applications communicate while running on 2 different computers over LAN, but I cant get them to work over WAN using the RTI Routing Service.

I followed the "Example 8 - Using the TCP Transport with Routing Service" in "RTI Routing Service - Getting Started Guide". And I can get the RTI Shapes Demo to run over the RTI Routing Service. NB. My applications use the same Domain IDs as the RTI Shapes Demo

My publisher is on PC1 and the subscriber is on PC2. I can see (using rtiddsspy) that PC2 receives data from the RTI Routing Service, but the subscriber application does not get notified on PC2.

Is there something that I have to especially aware of, when creating DDS applications for use over the RTI Routing Service?

Regards John

Answer 1

I can see (using rtiddsspy) that PC2 receives data from the RTI Routing Service, but the subscriber application does not get notified on PC2.

From this information, I would say that the most likely cause is a mismatch in QoS settings between the routing service publisher and your application subscriber. You could verify this in several ways:

• Use the Analyzer tool (if you have it at your disposal) while your system is running. It can show you the QoS settings used on each entity, as well as do QoS matching analysis to uncover mismatches.
• Use the default QoS settings with your application DataReader, so it will be less likely to conflict with any of your Routing Service QoS settings. If your DataReader receives data after that adjustment, then you know that conflicting QoS settings was the cause.

The default QoS settings used by spy are less likely to cause these kinds of mismatches, which is the reason why spy does receive the messages.

For your reference, you can check out this QoS Policy Reference Guide / Cheat-sheet. On the first page, any QoS that has a Y in the RxO column could potentially cause a mismatch.