Solutions

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 ...
5097 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 ...
7723 reads — 2 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 ...
3253 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 ...
3678 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 ...
4922 reads — 0 comments
The default value for publish_with_original_info is false. When this property is set to false RTI Routing service will change the metadata fields Writer GUID and Sequence Number in every sample. As a consequence, the applications can not know the original source of the sample, that is the ID of the ...
3445 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 ...
5757 reads — 0 comments

Pages