MacOS

High CPU usage after SHMEM resources are removed by a third-party

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 ...
scardenete
Wed, 02/14/2024 - 08:41
327 reads — 0 comments

How to use the Real-Time WAN Transport

In Connext DDS Professional 6.1.0 and above, a new UDP-based transport is available for communicating over a wide area network (WAN). The Real-Time WAN Transport is a smart transport that enables secure, scalable, and high-performance communication over WANs, including public networks. Real-Time ...
grayson
Thu, 05/20/2021 - 13:03
2827 reads — 0 comments

Integrating RTI Connext DDS Micro 3.0.3 with RTI Connext Tools 6.0.1

Some requirements for building a complex IIoT system are outside the scope of a stand-alone middleware. In order to support these system-level requirements, RTI created a suite of tools that accelerate development for the most complex use cases, including those using Connext DDS Micro due to ...
dryan
Wed, 11/04/2020 - 13:35
2673 reads — 0 comments

Advanced data access using Connector (Javascript)

Introduction RTI Connector offers a simplified API to Data Distribution Service. Different than the full DDS API, this lightweight API does not offer a one-to-one data mapping between the published or subscribed to datatype defined by the language (Javascript/Python). For example, if you use the C ...
fabrizio
Thu, 02/13/2020 - 14:49
2178 reads — 0 comments

NDDSUtility_sleep() issues on macOS systems

If you are running on a macOS® 10.9 (Mavericks) system (or higher), you may experience timing issues in your calls to NDDSUtility_sleep(). If you request to sleep for a small enough time period, you will notice that the actual sleep time is significantly longer. ...
Jesus Checa
Mon, 05/20/2019 - 07:10
2233 reads — 0 comments

Using Dynamic or Static Libraries with DDS Secure

When you link your application with the RTI Connext DDS libraries, you can choose whether to use dynamic or static linking. But what is the best approach if you want to use the DDS Secure plug-in? There are some situations that you need to be aware of and avoid. This article describes the possible ...
fabrizio
Wed, 03/27/2019 - 09:34
4471 reads — 0 comments

When do I need to send TypeCode or TypeObject?

Note: Applies to Connext DDS 5.x and above Sending TypeCode/TypeObject on the wire provides convenience over specifying the type via XML configuration, but has the disadvantage that more data must be sent during endpoint discovery. This can cause network congestion problems when the TypeCode/ ...
grayson
Thu, 03/14/2019 - 11:48
4833 reads — 0 comments

How do I use the Traditional C++ and Modern C++ APIs in the same application?

Note: Applies to RTI Connext DDS 5.2.0 and above. The Modern C++ API was introduced with RTI Connext DDS 5.2.0. This solution explains how to use the Modern and Traditional C++ APIs in the same application. To make them work together, you must not use both of them in the same .cpp file. That is, do ...
Benito Palacios
Mon, 10/19/2015 - 03:23
5256 reads — 0 comments

What causes this error: "PRESParticipant_checkTransportInfoMatching:Warning: discovered remote participant 'yyyyy' using the 'shmem' transport with class ID 2"

Note: Applies to RTI Connext 5.2.0 and above. The following error: PRESParticipant_checkTransportInfoMatching:Warning: discovered remote participant 'yyyyy' using the 'shmem' transport with class ID 2. This class ID does not match the class ID 16777216 of the same transport in the local participant ...
belen
Wed, 03/25/2015 - 10:05
46387 reads — 7 comments

What causes this error: "incompatible shared memory protocol detected."

Note: Applies to RTI Connext 4.x and above. The following error: [D0004|CREATE Participant|D0004|ENABLE] NDDS_Transport_Shmem_is_segment_compatible:incompatible shared memory protocol detected. Current version 1.0 not compatible with 2.0. is caused when two applications, one using RTI Connext DDS 4 ...
bobby
Wed, 02/06/2013 - 14:05
5360 reads — 0 comments

Pages

Subscribe to RSS - MacOS