Solutions

When designing Connext applications, one important task is identify communication patterns and ensure the appropriate pattern is used for each topic. There are typically three common data communication patterns, each optimized for different system behaviors and reliability requirements. Each ...
86 reads — 0 comments
Wireshark is an essential tool for optimizing and debugging RTI Connext applications but can be intimidating to someone who is not familiar with Wireshark or who is not familiar with analyzing DDS/RTPS traffic in Wireshark. The goal of this post is to provide you with tools, techniques, and links ...
248 reads — 0 comments
Summary On Linux/Windows and potentially other operating systems, when a DataWriter sends data samples to a multicast address, the performance of the underlying UDP sendmsg() call varies depending on whether multicast DataReaders are located on the same local host. If there are no local, multicast ...
956 reads — 0 comments
By default, Connext data serialization is not fully compliant with Extended CDR encoding. While this doesn't affect correctness it may prevent interoperability with other vendors. To make Connext compatible with the OMG 'Extensible and Dynamic Topic Types for DDS' specification, version 1.3 , you ...
1496 reads — 0 comments
In some cases, you may receive the wrong version of an RTI Connext Professional free trial or Connext Express license. If you do, you will receive the following error: RTI Connext DDS feature license not found: RTI_LICENSE_FILE = /home/my_user/rti_license57814.dat. Please contact support@rti.com ...
1445 reads — 0 comments
(This article expands on the community post: How do I restrict RTI Connext to use only a subset of interfaces? ) On a machine with multiple NICs, users can restrict RTI Connext® traffic to a subset of the available network interfaces (NICs). RTI’s Connext DDS 7.3 introduced the capability to ...
3597 reads — 0 comments
When processing a metadata sample that indicates the instance transition change to NOT_ALIVE_NO_WRITERS or NOT_ALIVE_DISPOSED, you may see the following WARNING messages when calling the get_key_value API: WARNING PRESCstReaderCollator_getKey:instance not found WARNING PRESPsReader_getKey:!collator ...
1271 reads — 0 comments

Pages