Solutions

The shared memory built-in transport in RTI Connext uses IPC segments and semaphores under the hood to perform DDS communication between DomainParticipants. It is important that those IPC resources are not destroyed while RTI Connext applications are using them. Failure to do so may result in ...
93 reads — 0 comments
Achieving low jitter and more deterministic write times and real-time performance requires in-depth tuning at the OS layer and DDS layer. It tends to involve a long list of recommendations to apply e.g. you can see advice online that involves similar checklists. This article summarizes best practices, and we recommend exploring and testing all the recommendations listed here. ...
654 reads — 0 comments
The multiple APIs of Connext have an internal concept named User Storage, which is used to store API-specific data required for certain features. This concept is normally part of the DomainParticipant entities and is configured through code as a QoS. While the APIs will configure this concept ...
5170 reads — 0 comments
There are three steps to take to configure Connext Micro not to use multicast. Set disable_auto_interface_config to true. Micro will scan the system for available interfaces and use them. Note, however, when this is set to true, Micro relies on just the manually added interfaces. Add an interface ...
636 reads — 0 comments
When using asynchronous publication and Best Effort reliability, you may see the warning: PRESWriterHistoryDriver_completeBeAsynchPub:!make_sample_reclaimable in topic 'MyTopic' This warning message may be caused by a small history depth you are configuring. Since you are using asynchronous ...
639 reads — 0 comments
The version of the Connext header files and Connext libraries is tied to each Connext release. The header files and libraries used for compiling your application must come from the same version of Connext. An inconsistency between versions might cause undefined behaviors such as segmentation faults ...
656 reads — 0 comments
Communication between participants using Simple Participant Discovery Protocol (SPDP) and Simple Participant Discovery Protocol 2.0 (SPDP2) is not possible by default. Both participant and endpoint discovery will fail to complete between an SPDP and SPDP2 participant. See Discovery Overview in the ...
12672 reads — 0 comments

Pages