Solutions

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 ...
1606 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 ...
2843 reads — 0 comments
Note : Applies to RTI Connext 4.x and above. Discovery is not an instantaneous event. It takes some time for the discovery process between applications to complete. The DDS DataWriter and DDS DataReader must discover each other before they can start communicating. Therefore, if you send data ...
10449 reads — 0 comments
Note: Applies to RTI Data Distribution Service 4.0 and 4.1 If you notice unexpected behavior (for example, unintended functions getting called, object creation failing, etc.), check your current stack margin by running the command checkStack . If the margin is low, this is a possible explanation of ...
7569 reads — 0 comments
Note: Applies to RTI Connext 4.x and above For dynamic discovery to work properly, RTI Connext relies on a globally unique identifier (GUID) that uniquely identifies each instance of a participant in the network. By default, RTI Connext will automatically choose values for the host ID and app ID ...
6799 reads — 3 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 ...
3590 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 ...
1626 reads — 0 comments

Pages