RTI Core Libraries and Utilities

The error "RTI Data Distribution Service No source for License information" happens when the license file cannot be found or the license has expired. If that is the case, the user application will be unable to initialize Connext DDS, depending on the terms of the license. You can trigger this error ...
4665 reads — 0 comments
GCC 5.1 introduced a new version of libstdc++ with a library ABI that includes new implementations of std::string and std::list (see in GCC online documentation). This new ABI breaks backwards compatibility with applications and libraries linked against older versions of libstdc++ using std::string ...
3212 reads — 0 comments
It is possible to create an Entity (a DataReader , DataWriter, or DomainParticipant ) with a QoS profile defined in the USER_QOS_PROFILES.xml file. In the Java, C, Traditional C++ and .NET APIs, there are methods such as: DDS_Publisher_create_datawriter_with_profile() Depending on what kind of ...
2868 reads — 0 comments
RTI Connext DDS Micro provides two ways of determining endpoint information of other DomainParticipants: Dynamic Endpoint Discovery , and Static Endpoint Discovery . Dynamic endpoint discovery uses the DDS Simple Discovery Protocol, which uses builtin discovery DataWriters and DataReaders to ...
3340 reads — 0 comments
TypeObject and TypeCode support in RTI Connext DDS During the matching process , RTI Connext DDS compares the structure of the topic types provided by the DataWriters and DataReaders to determine if they can communicate. To do so, the TypeObject or TypeCode is needed. If the TypeObject or TypeCode ...
4796 reads — 0 comments
By default, a DataWriter of an unbounded type won’t be able to communicate with a DataReader of a bounded type. DDS includes the max size of a bounded type as part of the data type information (known as TypeCode or TypeObject). Since the data type information is used during the Discovery phase, if ...
1907 reads — 0 comments
The DDS_SampleInfo associated with each sample contains the fields original_publication_virtual_guid and original_publication_virtual_sequence_number . This pair forms the SampleIdentity which uniquely identifies each individual sample. When a DataWriter uses write_w_params (), it can explicitly ...
1878 reads — 0 comments
If you have more than 5 DomainParticipants in the same machine, you may notice that your applications are not able to communicate with Participant number 6 and following ones. This is because by default we discover up to 5 DomainParticipants in one location. This behavior is controlled by the Peer ...
2950 reads — 0 comments
RTI Connext supports two ways of filtering data : using QueryConditions and ContentFilteredTopics . These two options differ in the moment when DDS applies the filter. QueryConditions filter data after the DataReader has received and queued it. That means that the application will receive all ...
2035 reads — 0 comments
A ‘match’ between the local and remote entities occurs only if the DataReader and DataWriter have the same Topic , compatible QoS policies, and a compatible data type. By default, type matching is done using the TypeObject . The DataReader’s type must be assignable from the DataWriter’s type. If ...
3154 reads — 0 comments

Pages

Subscribe to RSS - RTI Core Libraries and Utilities