Transports

Note: Applies to RTI Connext 4.x and above The message RTINetioSender_addDestination:no transport for request is a warning that RTI Connext could not find a transport for a specified peer locator. The UDPv4 and shared memory transports are installed by default. When a node tries to add a ...
4487 reads — 0 comments
Note: Applies to RTI Connext 4.x. In general, a can't reach:locator: error message means that a DataWriter cannot send to the locator of a DataReader , usually due to a transport configuration error. For example, suppose Participant A has both the UDPv4 and shared-memory built-in transports enabled ...
25383 reads — 2 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 ...
17038 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 ...
3521 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 ...
7795 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 ...
4047 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 ...
6266 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 ...
5711 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 ...
3666 reads — 0 comments
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 ...
43146 reads — 4 comments

Pages

Subscribe to RSS - Transports