Solutions

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] ...
5684 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. ...
10009 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 ...
2006 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 ...
7340 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 ...
10014 reads — 0 comments
Note: Applies to NDDS 3.x For machines with multiple NICs, it is sometimes useful to specify which NIC(s) to communicate over. Multicast packets will be sent through all interfaces that satisfy the following criteria: It is enabled for multicast NDDS is configured to use it Enabling a NIC for ...
3884 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 ...
2433 reads — 0 comments

Pages