RTI Core Libraries and Utilities

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 ...
2924 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/ ...
3559 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 ...
5238 reads — 0 comments
Note: Applies to RTI Data Distribution Service 4.1. If you start an application with shared memory as the only transport and then start a second application with a multicast address in NDDS_DISCOVERY_PEERS or in the multicast_receive_addresses field in the Discovery QosPolicy on the same node, you ...
3698 reads — 0 comments
Suppose you have a local variable in your application that is declared as a double (that is, a long long variable declared within an IDL file), and you try to cast it to a RTICdrLongLong variable, like this: double doubleLocalVar = 0; /* Main loop */ for (count=0; (sample_count==0) || (count< ...
3918 reads — 0 comments
The minimum heap required to run a simple HelloWorld publisher and subscriber on an INTEGRITY system is about 11.3MB. Problem You run an example HelloWorld application and create_participant() returns NULL. When you increase the logging verbosity, you see messages such as: !create fast buffer pool ...
2870 reads — 0 comments
Note: Applies to NDDS 3.x and RTI Connext 4.x and above First, it is important to point out that NDDS 3.x and RTI Connext 4.x and above are not wire-protocol compatible. Applications built with these 2 products cannot communicate with each other. Second, although the object models of both products ...
3330 reads — 0 comments
This depends on what version of RTI Software you have installed: Version 4.2x and earlier: rtiddsgen only recognizes keys in the outermost structure. Version 4.3x and later: You can specify the key not only in the top-level message but also in nested structures. Let's look at some use cases: 1) You ...
5602 reads — 2 comments
As described in the online HTML documentation for the DomainParticipantResourceLimits Qos Policy, there is a QoS parameter called topic_data_max_length , which is used to set the maximum length of the topic data to be sent out. topic_data_max_length is a DDS_Long, which is a 32-bit signed long ...
7469 reads — 0 comments
Note: This article applies to RTI Connext DDS version 4.4c and higher. The error indicates that the XML parser encountered a tag for a field that doesn't exist in 4.4c and higher, because it was renamed. Two fields in the DataWriter's protocol.rtps_reliable_writer QoS were renamed in 4.4c: Old name ...
4078 reads — 0 comments

Pages

Subscribe to RSS - RTI Core Libraries and Utilities