Discovery

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 ...
3551 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 ...
7865 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 ...
4079 reads — 0 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 ...
6346 reads — 0 comments
Note: Applies to NDDS 3.x, RTI Connext 4.x and above Yes, RTI Connext will cause IGMP messages to be sent, allowing routers to appropriately handle multicast traffic delivery. The RTI code does not send the IGMP messages itself, but the host's network stack should send them when needed. When RTI ...
5771 reads — 0 comments
Note: Applies to NDDS 3.x, RTI Connext 4.x and above. You can run a publisher and subscriber on the same node or on different nodes. However, even if you are only using one node, by default, RTI Connext looks for a network connection. The default discovery behavior is to look for peers using ...
3625 reads — 0 comments
Note: Applies to NDDS 3.x, RTI Connext 4.x and above. There are several drawbacks to using broadcast. There is a performance degradation problem when using broadcast. It disrupts EVERY node in the system-even the ones that do not want ANY data! Such a system is clearly not scalable. With broadcast ...
3703 reads — 0 comments
Note: Applies to RTI Data Distribution Service 4.0x and higher. RTI Connext must discover and keep track of remote entities, such as new participants in the domain or new DataReaders of a particular topic in order to work. This information may also be important to the application itself, which may ...
8244 reads — 1 comment
Note: The ports used are different between RTI Connext 4.x and NDDS 3.x. RTI Connext The built-in UDP transport in RTI Connext 4.x and above uses port numbers that are based on the domain ID and participant ID. Because the RTPS spec changed, the mapping is different before and after Version 4.2 of ...
43577 reads — 4 comments
Applies to RTI Connext 4.x and above With default settings, the maximum number of domains and participants in the same machine is limited as follows: Versions 4.1e and lower: 100 domains (0 .. 99) and 58 participants (0 .. 57) per domain on the same machine when the domain ID is 0. Version 4.2e and ...
28700 reads — 3 comments

Pages

Subscribe to RSS - Discovery