Solutions

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 ...
7567 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 ...
7262 reads — 0 comments
IMPORTANT : this article is outdated. For interoperating newer versions of Connext Micro DPSE with Connext Professional please refer to the rticonnextdds-dpse-examples in our RTI Connext DDS Community github repository. RTI Connext DDS Micro provides two ways of determining endpoint information of ...
11469 reads — 2 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 ...
15371 reads — 3 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 ...
4661 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 ...
4858 reads — 0 comments
The error message “File-set is exhausted, recording will stop (no more space available in fileset and rollover inactive)” comes from the fact that the default maximum size for a file segment is 2 GB. When the recorded segment reaches 2 GB, Recorder stops. Below are two options for avoiding this ...
6115 reads — 0 comments

Pages