RTI Core Libraries and Utilities

Note : Applies to NDDS 3.x and RTI Connext 4.x and above. NDDS 3.x and RTI Connext 4.x (and above) are not wire-protocol compatible. Applications built with these 2 products cannot communicate with each other. The attached 3.x to 4.0 Transition Guide will help you move your application to the 4.0 ...
2777 reads — 0 comments
Prior to RTI Data Distribution Service version 4.4, receiving data over multicast could only be configured on the reader side. The reader Qos specifies to the writer that it wants to receive data using a multicast address. Starting with RTI Data Distribution Service 4.4, in addition to the ...
10205 reads — 0 comments
Note : Applies to RTI Connext 4.x and above. Discovery is not an instantaneous event. It takes some time for the discovery process between applications to complete. The DDS DataWriter and DDS DataReader must discover each other before they can start communicating. Therefore, if you send data ...
16109 reads — 0 comments
Note: Applies to RTI Data Distribution Service 4.0 and 4.1 If you notice unexpected behavior (for example, unintended functions getting called, object creation failing, etc.), check your current stack margin by running the command checkStack . If the margin is low, this is a possible explanation of ...
12787 reads — 0 comments
Note: Applies to RTI Connext 4.x and above For dynamic discovery to work properly, RTI Connext relies on a globally unique identifier (GUID) that uniquely identifies each instance of a participant in the network. By default, RTI Connext will automatically choose values for the host ID and app ID ...
10392 reads — 3 comments
Note: Relevant RTI Connext versions: RTI Connext 4.x and above. The Maximum Participant Index is an optional value at the beginning of a Peer Descriptor. It is used to specify a range of ports where RTI Connext will look for other participants during the discovery process. It tells RTI Connext how ...
6568 reads — 0 comments
Note: Applies to NDDS 3.x (and earlier), RTI Connext 4.x and above. You will need the following: The binaries for your applications. Any shared libraries used by your binary. (If you're linking against static libraries, you do not need to do anything here. The generated makefile links against the ...
2742 reads — 0 comments
Note: Relevant versions RTI Connext 4.x and above. Method One: setting the initial peers and multicast receive address programmatically (applies to all 4.x versions and above) The following C++ code snippet shows how to configure the initial peers and multicast receive address programmatically ( ...
20226 reads — 1 comment
Note: Applies to RTI Connext 4.x and above. RTI Connext uses the concept of exclusive areas (EA) to avoid deadlocks when user listener code calls the RTI Connext APIs. In a nutshell: Each entity has their own EAs. Controlling access into EAs is a way to prevent deadlocking situations. The rule of ...
6240 reads — 0 comments
Note: Applies to RTI Connext 4.x and above. Specific to LynxOS . The error message " icmp-response bandwidth limit " in LynxOS is caused by too many messages sent to ports that are not being listened on by an application. LynxOS sends an icmp-response packet for each incoming message and when those ...
5377 reads — 0 comments

Pages

Subscribe to RSS - RTI Core Libraries and Utilities