Discovery

In RTI Connext DDS 6.0.0, the RTPS version has been changed to 2.3. This RTPS version is propagated during the discovery process and is verified by the receiving Connext DDS or Connext DDS Micro application to verify compatibility. In Connext DDS Micro 2.4.11 and earlier, this check is hard-coded ...
303 reads — 0 comments
If you have more than 5 DomainParticipants in the same machine, you may notice that your applications are not able to communicate with Participant number 6 and following ones. This is because by default we discover up to 5 DomainParticipants in one location. This behavior is controlled by the Peer ...
2464 reads — 0 comments
Description The discovery phase in DDS applications can be considered a high throughput scenario under some circumstances. Some examples are: The applications have a lot of DDS entities. More than 2 hosts are involved. The type definitions are sent within the discovery packets (i.e., TypeCode and ...
4346 reads — 0 comments
For complex systems, discovery may take a big percentage of the available bandwidth in the network when some of the hosts are rebooted. There are several options that help reducing the impact of discovery in these systems: 1) Reduce the size of discovery packets You can configure the middleware to ...
4424 reads — 0 comments
There are some situations in which two applications, even though they have been configured to have each other in their initial peers lists, will not discover each other. Two applications are on the same machine and have only either 127.0.0.1 or "localhost" in their initial peers lists AND ...
4518 reads — 0 comments
Note: Applies to RTI Data Distribution Service 4.1. If you start an application with shared memory as the only transport and then start a second application with a multicast address in NDDS_DISCOVERY_PEERS or in the multicast_receive_addresses field in the Discovery QosPolicy on the same node, you ...
2212 reads — 0 comments
As described in the online HTML documentation for the DomainParticipantResourceLimits Qos Policy, there is a QoS parameter called topic_data_max_length , which is used to set the maximum length of the topic data to be sent out. topic_data_max_length is a DDS_Long, which is a 32-bit signed long ...
3686 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 ...
8971 reads — 2 comments
Note : The following discussion applies to RTI Data Distribution Service 3.x only. (There is a separate FAQ for 4.x.) Heartbeats (HBs) are sent for one of two reasons: Every SendQueueSize / HeartBeatsPerSendQueue issues, RTI Data Distribution Service will append a HB to the issue to request that it ...
2010 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 ...
4275 reads — 0 comments

Pages

Subscribe to RSS - Discovery