RTI Core Libraries and Utilities

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 ...
6210 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 ...
7924 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 ...
5053 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 ...
5459 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 ...
8360 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 ...
5549 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 ...
6475 reads — 0 comments
The most common cause of the following timestamp order errors is that the system clock of the publishing application has been modified to a time in the past: PRESPsWriterQueue_add:!timestamp order PRESPsWriter_write:!timestamp order RTI Data Distribution Service requires a monotonically increasing ...
4040 reads — 0 comments
Note : Applies to RTI Connext 4.x and above. The message MIGGenerator_addData:serialize buffer too small indicates that the transport-buffer size is too small for the data being sent and needs to be increased. When the transport layer is initialized, it allocates enough resources to serialize/ ...
5470 reads — 0 comments
Note: Applies to RTI Connext 4.3 and above, although the same methodology can be applied to 4.0, 4.1, and 4.2. The following example has been written in C++. Purpose This example illustrates how to extract and print Datawriter and Datareader statuses to a Comma-Separated Values (csv) file. This ...
6660 reads — 0 comments

Pages

Subscribe to RSS - RTI Core Libraries and Utilities