Solutions

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 ...
4333 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 ...
4593 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 ...
2900 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/ ...
3518 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 ...
5185 reads — 0 comments
Note: Applies to RTI Data Distribution Service 4.x and above. First, we need some background to understand how RTI's shared-memory transport works. The RTI Data Distribution Service shared-memory transport uses different standards to access shared mutexes and shared-memory segments, depending on ...
50273 reads — 1 comment
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 ...
3655 reads — 0 comments

Pages