RTI Core Libraries and Utilities

Note: Applies to RTI Connext version 4.x and above OMG Data Distribution Service (DDS) applications send two types of data: meta data used for discovery and user data. Because the core of RTI Connext DDS is transport agnostic, it does not make any assumptions about the actual transports used to ...
5479 reads — 0 comments
Note: This solution applies to RTI Data Distribution Service 4.x. The description in this FAQ only applies to data instances that are allocated with FooTypeSupport::create_data(), which pre-allocates the strings. (It does not apply to situations in which the data instance is allocated on the stack ...
12867 reads — 0 comments
Performance is a function of how well hardware and software components work together with the middleware. The relationship is certainly not easily predictable. With very fast hardware, the limitation seems to be the hardware bus speed. The PCI just cannot keep up and this leads to high CPU ...
3287 reads — 0 comments
Note: Applies to RTI Data Distribution Service 4.1, 4.2; While the design pattern also works for RTI Data Distribution Service 4.3 and above, its batching feature is a better way to achieve aggregation. Purpose Publisher This example shows how to create an application that aggregates data. This ...
4519 reads — 0 comments
Note: Applies to RTI Data Distribution Service 4.3x and above, Both rtiddsping and rtiddsspy can be configured to use multicast for discovery announcements by specifying a multicast address as part of the initial peer list (using -preer <PEER> ). However, rtiddsping and rtiddsspy do not have ...
5705 reads — 0 comments
Note: Applies to RTI Data Distribution Service 4.3 and above. The following example is written in C++. Publisher This throughput test is based on the throughput test in $NDDSHOME/example/CPP/performance/throughput, with modifications to batch data samples for aggregation. Instead of sending ...
3718 reads — 0 comments
Note: Applies to RTI Connext 4.x and above The message RTINetioSender_addDestination:no transport for request is a warning that RTI Connext could not find a transport for a specified peer locator. The UDPv4 and shared memory transports are installed by default. When a node tries to add a ...
4286 reads — 0 comments
You might see the following messages in the DDS log. PRESParticipant_createContentFilteredTopicPolicy:content filter compile error 1 or PRESParticipant_createContentFilteredTopicPolicy:content filter compile error 2 Although the compile() function considers these messages real errors, they are not ...
5722 reads — 1 comment
When you use an RTI Data Distribution Service 4.4b XML QoS profiles file with 4.3e or 4.4a, you may see the following error: RTIXMLParser_onStartTag:Parse error at line 13: Unexpected attribute 'xmlns:xsi' RTIXMLParser_parseFromFile:error parsing XML file DDS_XMLParser_parse_from_file:Error parsing ...
4373 reads — 0 comments
DDS_TransportUnicastQosPolicy defines the unicast transport network interfaces that an entity will use to receive messages. Versions of RTI Connext DDS prior to 5.3.0 use a maximum of four network interfaces — the first four reported by the operating system. From RTI Connext DDS 5.3.0 onwards, this ...
4651 reads — 0 comments

Pages

Subscribe to RSS - RTI Core Libraries and Utilities