RTI Core Libraries and Utilities

Note: Applies to RTI Connext 4.x This solution addresses the following exception: PRESParticipant_assertRemoteParticipant:!assert remote participant c0c80aa3 7e520001 due to different ro area DISCDynamicParticipantSelfDetector_onDataAvailable:!assert remote participant The likely cause of this ...
13865 reads — 0 comments
Note : Applies to RTI Connext 4.x and above. Prior to RTI Data Distribution Service 4.1d, the maximum message size supported by RTI Data Distribution Service was determined by the installed transports. Each transport may impose a maximum message size. The maximum message size supported by a ...
15810 reads — 2 comments
Note: Applies to RTI Connext 4.x and above Problem You are trying to create a new DomainParticipant and see error messages about an invalid port and/or a failure to create a receive resource . For instance: [D0001|ENABLE]NDDS_Transport_UDPv4_Socket_bindWithIp:0X1CF2 in use [D0001|ENABLE] ...
5477 reads — 0 comments
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. ...
9841 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 ...
1965 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 ...
7171 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 ...
9860 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 ...
2377 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 ...
9229 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 ...
14923 reads — 0 comments

Pages

Subscribe to RSS - RTI Core Libraries and Utilities