RTI Core Libraries and Utilities

Note: This solution applies to RTI Connext 4.x. and above. This solution explains how to access members of a complex type (e.g.: struct) contained in a sequence using DynamicData If a type is defined as follows: struct Nested { long x; }; struct Hello { sequence<Nested, 3> mySeq; }; The steps ...
3582 reads — 0 comments
Note : This article applies to RTI Connext DDS 4.5f and above and relates to the Traditional C++ API. Since 5.0.0 the Modern C++ API provides better support for generic programming. RTI Connext 4.5f added support for the use of C++ traits on each top level type generated by rtiddsgen. In this ...
6848 reads — 0 comments
Note: This solution applies to RTI Data Distribution Service 4.x. and above. Regular strings in RTI Connext DDS consist of single-byte characters. Hence, only US-ASCII characters can be represented in a string. Characters for other languages, such as Greek, Cyrillic, Coptic, Armenian, Hebrew, ...
6249 reads — 2 comments
Note: RTI Connext 5.3.0 and above has new options in the LoggingQosPolicy, which allow limiting the size of RTI Connext Log Files in an easy way. Prior to RTI Connext 5.3.0, a custom device had to be set for this purpose. This article has been updated to cover both methods of limiting the size of ...
4479 reads — 0 comments
Note: Applies to RTI Connext 4.x and above. When you have multiple applications running on a single machine utilizing the shared memory transport this error will occur of when the shared memory transport property dds.transport.shmem.builtin.parent.message_size_max is not consistent across all RTI ...
6435 reads — 1 comment
Note : Applies to RTI Connext DDS 4.4 and above The following error: NDDS_Transport_UDPv4_SocketFactory_create_receive_socket: No interface found enabled for multicast. happens when a DomainParticipant is created with UDPv4 transport enabled (which is the default value) and all network interfaces ...
7248 reads — 0 comments
The following error: NDDS_Transport_UDPv4_receive_rEA:!precondition: buffer_in->length < (self)->property->message_size_max is caused when the buffer size of the Receiver Pool is less than the message_size_max of a builtin transport (UDPv4 in this case). To fix this issue, all you need ...
5275 reads — 0 comments
Note: Applies to RTI Connext 4.x and above. The following error: [D0004|CREATE Participant|D0004|ENABLE] NDDS_Transport_Shmem_is_segment_compatible:incompatible shared memory protocol detected. Current version 1.0 not compatible with 2.0. is caused when two applications, one using RTI Connext DDS 4 ...
3528 reads — 0 comments
Note: Applies to RTI Connext version 4.x and above OMG Data Distribution Service (DDS) applications send two types of data: meta data used for discovery and user data. Because the core of RTI Connext DDS is transport agnostic, it does not make any assumptions about the actual transports used to ...
3318 reads — 0 comments
Note: This solution applies to RTI Data Distribution Service 4.x. The description in this FAQ only applies to data instances that are allocated with FooTypeSupport::create_data(), which pre-allocates the strings. (It does not apply to situations in which the data instance is allocated on the stack ...
10325 reads — 0 comments

Pages

Subscribe to RSS - RTI Core Libraries and Utilities