RTI Core Libraries and Utilities

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 ...
659 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. ...
1489 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 ...
7582 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 ...
17595 reads — 0 comments
To determine if your Linux platform is compatible with an RTI architecture, you will need to know the CPU architecture (e.g. x64 or ARM), GLIBC, and GLIBCXX versions in your target platform. To find the GLIBC library, here are the steps we recommend you run on your target platform: $ ldd `which ls ...
1345 reads — 0 comments
Jitter when making API calls can result in inconsistent execution time for making those calls. For example, the median call to return_loan() may take ~4,500 nanoseconds, but there could be execution outliers that take 5-10x this median time. What could cause this kind of behavior? The cause of such ...
2471 reads — 0 comments
Note : This article discusses the coherent_set_info field, which is only available in Connext Professional 6.1.0 and higher. The information about the coherent set that a sample belongs to is stored in the optional field coherent_set_info , which is part of the SampleInfo structure. This optional ...
1545 reads — 0 comments
Occasionally users will run into the following error message, or something similar, when starting their Connext application and will have a hard time identifying the cause. Error: Failed to create Connector: RTIXMLObject_addChild: XML object with name '<xml_obj_name>' already exists ...
2428 reads — 0 comments
Connext applications can enjoy consistent "me-first" execution by running at an elevated priority on the Linux RT_PREEMPT kernel. RT_PREEMPT is a kernel enhancement that enables real-time preemption and settable priorities for processes and threads, similar to an RTOS. This can be put to use for ...
1989 reads — 0 comments
In 2020, Microsoft released .NET 5 with the goal of unifying the .NET world and effectively deprecating .NET Framework, .NET Core, and .NET Standard (in technical terms, .NET 5 is the evolution of .NET Core 3.1). Taking this into account, the documentation for the new RTI Connext C# API released in ...
4425 reads — 0 comments

Pages

Subscribe to RSS - RTI Core Libraries and Utilities