Discovery

Communication between participants using Simple Participant Discovery Protocol (SPDP) and Simple Participant Discovery Protocol 2.0 (SPDP2) is not possible by default. Both participant and endpoint discovery will fail to complete between an SPDP and SPDP2 participant. See Discovery Overview in the ...
14569 reads — 0 comments
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 ...
31664 reads — 0 comments
By default, a DataWriter of an unbounded type won’t be able to communicate with a DataReader of a bounded type. DDS includes the max size of a bounded type as part of the data type information (known as TypeCode or TypeObject). Since the data type information is used during the Discovery phase, if ...
3320 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 ...
5873 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 ...
8729 reads — 1 comment
For complex systems with hundreds of participants and endpoints, discovery may cause long startup times and high network utilization. There are several options that help increase discovery performance: 1) Reduce the size of discovery packets 1.1. You can configure the middleware to not send the ...
37456 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 ...
8572 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 ...
3643 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 ...
7343 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 ...
15839 reads — 2 comments

Pages

Subscribe to RSS - Discovery