NDDS

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 ...
2999 reads — 0 comments
Note : Applies to RTI NDDS 2.x and earlier, and NDDS 3.x. This Solution describes errors you may see when running an NDDS application on VxWorks 5.4.x or 5.5.x. These error messages most likely mean that the amount and/or sizing of your stack buffers are incorrect. NDDS is unable to send "NDDS ...
5569 reads — 0 comments
Note: Applies to NDDS 3.x (and earlier), RTI Connext 4.x and above. You will need the following: The binaries for your applications. Any shared libraries used by your binary. (If you're linking against static libraries, you do not need to do anything here. The generated makefile links against the ...
3081 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 ...
6485 reads — 0 comments
Note: Relevant RTI Connext versions: NDDS 3.x, RTI Connext 4.x and above You may want to use your own serialize/deserialize functions if there are existing message formats and data structures that you want to keep. In this case, the fastest way to take advantage of RTI Connext’s cross-platform ...
4532 reads — 0 comments
Note: Applies to NDDS 3.x and RTI Connext 4.x and above. The Java API in NDDS 3.x is based on the JMSRT interface, which is similar to the JMS interface. The Java API in RTI Connext 4.x and above complies with the DDS standard and is much more consistent with its C and C++ interfaces, but is very ...
2665 reads — 0 comments
Note: Applies to RTI DDS and Connext versions: NDDS 3.x, RTI Connext 4.x and above. rtiddsgen -example accepts most, but not all, platforms supported by RTI Connext. Any source code generated by rtiddsgen is platform independent, including the example application created using the optional -example ...
3260 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 ...
4074 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 ...
49468 reads — 4 comments
Note: Applies to NDDS 3.x, RTI Connext 4.x and above. Many operating systems, including Linux, limit the number of multicast group memberships that a machine can belong to simultaneously. (A "multicast group membership" indicates that a machine is listening to messages for a specific multicast IP ...
18553 reads — 0 comments

Pages

Subscribe to RSS - NDDS