RTI Core Libraries and Utilities

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 ...
5556 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 ...
6290 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 ...
8075 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 ...
3566 reads — 0 comments
Note: Applies to RTI Connext 4.x and above If you have an RTI Connext application running on a QNX machine and it is unable to communicate with other applications running on the same machine started by another user, or if your application fails to start (with an error related to shared memory), ...
7243 reads — 0 comments
Note: Applies to RTI Connext 4.x and above. The LynxOS version does not have a multicast address in its peer host list by default. You need to modify the initial_peers list in the Discovery QoS policy to either include the multicast address, or to explicitly list the hosts that need to communicate. ...
2534 reads — 0 comments
Note : Applies to RTI Connext 4.x and above. On a machine with multiple NICs, you can restrict RTI Connext traffic to a subset of the available network interfaces (NICs). For example, this would allow you to segregate DDS traffic from other application-specific data. Selecting specific NICs ...
23309 reads — 2 comments
Note: Applies to RTI DDS 4.0. This problem was resolved in RTI DDS 4.1b. Let's start with some general background information: #pragma statements provide a way to control some features of the compiler. Some examples of #pragma statements implemented by different compilers include: enabling or ...
15443 reads — 0 comments
Note: Applies to RTI Connext 4.x and above Generally speaking, if a regular 'ping' does not work in both directions, RTI Connext traffic will not be able to get through either. There are several other possible reasons that your reader and writer applications may not be communicating with each other ...
5800 reads — 0 comments
Note: Relevant RTI Connext versions: RTI Connext 4.x and above. Every host architecture comes with a corresponding Java architecture. If you use rtiddsgen with the -language Java option, you must also specify -example with a j2sdk or jdk architecture. For example: rtiddsgen -language Java -example ...
2947 reads — 0 comments

Pages

Subscribe to RSS - RTI Core Libraries and Utilities