RTI Core Libraries and Utilities

Note : Relevant RTI Connext version 4.x and above. In order to guarantee that RTI Connext will deliver all messages, both the data writer and data reader must be configured for strict reliable communication. Strict reliability ensures that every message will be received by all known data readers. ...
13083 reads — 0 comments
Note: Applies to RTI Connext 4.x and above This solution shows, by an example, how to read data using conditions and waitsets . It uses rtiddsgen to generate a pub-sub example that accesses data through a listener. Refer to the Core Libraries and Utilities Getting Started Guide and Core Libraries ...
2915 reads — 0 comments
Note : Applies to RTI Connext 4.x and above. There is a separate FAQ for 3.x. RTI Connext supports various transports to deliver data samples. Not all of these transports guarantee that all samples are delivered. For example, when using UDP, samples can be lost or can arrive out of order. The OMG ...
10048 reads — 0 comments
Note : Relevant RTI Connext versions: RTI Connext 4.x and above The default settings for RTI Connext 4.x and above will allow approximately 11 (5 for 4.4c and below) domain participants in a single application (address space). The number of domain participants on a given node is only limited by ...
12219 reads — 0 comments
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 ...
3398 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 ...
11799 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 ...
18904 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 ...
15185 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 ...
12392 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 ...
15423 reads — 0 comments

Pages

Subscribe to RSS - RTI Core Libraries and Utilities