RTI Core Libraries and Utilities

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), ...
5961 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. ...
2164 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 ...
20225 reads — 1 comment
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 ...
14108 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 ...
4865 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 ...
2540 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 ...
3813 reads — 0 comments
Note: Applies to RTI Connext 4.x and above. The generated makefile assumes the IDL file name matches the type name. You may need to modify the generated makefile to match the actual type name. ...
2538 reads — 0 comments
Note : Applies to RTI Connext 4.x and above. What is the trade-off between having one Subscriber with multiple DataReaders , versus multiple Subscribers that each have one DataReader ? Typically, an application will have one Subscriber with multiple DataReaders . If the DataReaders are set up to ...
8512 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 ...
2110 reads — 0 comments

Pages

Subscribe to RSS - RTI Core Libraries and Utilities