RTI Core Libraries and Utilities

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 ...
11637 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 ...
9531 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 ...
5907 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 ...
2465 reads — 0 comments
Note: Relevant versions RTI Connext 4.x and above. Method One: setting the initial peers and multicast receive address programmatically (applies to all 4.x versions and above) The following C++ code snippet shows how to configure the initial peers and multicast receive address programmatically ( ...
18662 reads — 1 comment
Note: Applies to RTI Connext 4.x and above. RTI Connext uses the concept of exclusive areas (EA) to avoid deadlocks when user listener code calls the RTI Connext APIs. In a nutshell: Each entity has their own EAs. Controlling access into EAs is a way to prevent deadlocking situations. The rule of ...
5421 reads — 0 comments
Note: Applies to RTI Connext 4.x and above. Specific to LynxOS . The error message " icmp-response bandwidth limit " in LynxOS is caused by too many messages sent to ports that are not being listened on by an application. LynxOS sends an icmp-response packet for each incoming message and when those ...
5027 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 ...
5250 reads — 0 comments
Note: Applies to RTI Connext 4.x and above, C and C++ APIs Statically allocated arrays For C, use FooSeq_to_array . For C++, use FooSeq::to_array . Dinamically allocated arrays There is an easy way to copy from sequence into an array. RTI Connext will always create a contiguous internal buffer for ...
7132 reads — 1 comment
Note: Applies to RTI Connext 4.x and above These are some common errors when specifying the key in the IDL: In the IDL file, you must use //@key after the key field. Do not use a space between any of these characters: //@key Also note that the directive is case-sensitive — use all lower case. Only ...
3067 reads — 0 comments

Pages

Subscribe to RSS - RTI Core Libraries and Utilities