RTI Core Libraries and Utilities

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 ...
3432 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 ...
3943 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 ...
7036 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 ...
8837 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 ...
5054 reads — 0 comments
SENS/TORNADO 2.0 NETWORK STACK CONFIGURATION/PERFORMANCE ISSUES -------------------------------- 1. INTRODUCTION 1.1 NETWORK STACK VERSIONS 1.2 NET POOLS 1.2.1 CLUSTERS 1.2.2 CLUSTER BLOCKS 1.2.3 MBLOCKS 1.3 RECEIVING: DATA FLOW FROM DRIVER TO APPLICATION LEVEL 1.4 SENDING: DATA FLOW FROM ...
12016 reads — 0 comments
Note: Applies to the legacy RTI Connext .NET API (4.3e to 6.1). For the new .NET API (6.1 and above), see the Getting Started Guide . For applications to use the RTI Connext .NET API, the following MUST be true for the target machine: The Microsoft .NET Framework Version 2.0 Redistributable Package ...
8426 reads — 0 comments
This Solution addresses how to create a reader and a writer that use reliable communication. It also shows, by example, some of the more common QoS policies that you might want to change. Method One for modifying the QoS The following C++ code snippet shows how to change those QoS policies. Data ...
8971 reads — 0 comments
Note: Applies to RTI Connext 4.0 and above. This example shows how to achieve batching without using the Batch QoS policy (which was introduced in 4.4). Publisher This Publisher sends out bursts of 32 keyed reliable samples at 20Hz. The point here is that the dataWriterQos.protocol.push_on_write = ...
6279 reads — 0 comments
Note: Applies to RTI Data Distribution Service 4.1 and above. The DDS_TopicBuiltinTopicData built-in topic is meant to convey information about discovered Topics. It is a known issue in RTI Data Distribution Service 4.1 and 4.2 that these topic samples are not propagated in a separate packet on the ...
2759 reads — 0 comments

Pages

Subscribe to RSS - RTI Core Libraries and Utilities