Solutions

Modern C++ API code examples

The following examples demonstrate how to use the Modern C++ API: New! Flat Data and Zero Copy Latency (C++11) New! Flat Data API (C++11) Lambda Content Filter (C++11) Content Filtered Topic (C++03) Asynchronous Publisher (C++03) Batching and Turbo Mode (C++03) Builtin Topics (C++03) Listeners (C++03) Polling QueryCondition (C++03) Ordered Presentation (C++11) Recursive Data Type (C++03) DynamicData nested types (C++03) DynamicData publish and subscribe (C++11) DynamicData acess to union discriminator (C++03 and C++11) Partitions (C++03) Builtin Qos Profiles (C++03) Get Publishers (C++03) Using QoS Profiles (C++03) WaitSets (C++03) WaitSet with Query Conditions (C++11) WaitSet with Status Conditions (C++03) Custom Content Filters (C++03) DynamicData Accessing Sequence Members (C++03) Keyed Data (C++03) Coherent Presentation (C++03) Content Filtered Topic -- String Filter (C++03) Keyed Data Advanced (C++03) Ordered Presentation Group (C++03) Time-based Filters (C++03) Custom Flow Controllers (C++03) Deadline and Content Filtering (C++03) Multichannel (C++03) Using Type Codes (C++03) Polling Read (C++03) ...
alexc
Thu, 05/14/2015 - 15:31
83595 reads — 0 comments

What causes this error: "PRESParticipant_checkTransportInfoMatching:Warning: discovered remote participant 'yyyyy' using the 'shmem' transport with class ID 2"

Note: Applies to RTI Connext 5.2.0 and above. The following error: PRESParticipant_checkTransportInfoMatching:Warning: discovered remote participant 'yyyyy' using the 'shmem' transport with class ID 2. This class ID does not match the class ID 16777216 of the same transport in the local participant ...
belen
Wed, 03/25/2015 - 10:05
96865 reads — 7 comments

WaitSets: What can I do to reduce my CPU usage?

For high-rate data, the usage of a WaitSet may lead to a very high CPU usage if the WaitSet wakes up too often. By default, a WaitSet is created without any properties specified. In this case, the WaitSet wakes up immediately every time a trigger event occurs. However, "waking up" involves a ...
sonia
Wed, 01/28/2015 - 16:47
7654 reads — 0 comments

Why do I see a packet that starts by RTPX instead of RTPS?

Packets starting by RTPX are default domain discovery announcements. This is a new non-standard packet introduced in Connext 5.1.0 to help the tools discover applications running in other domains (for instance, RTI Admin Console). This packet is sent to the default multicast address and port for ...
Juanjo Martin
Tue, 01/20/2015 - 08:09
6222 reads — 0 comments

What causes this error: "COMMENDBeReaderService_onSubmessage:!get ber remoteWriter"

The following error during shutdown: COMMENDBeReaderService_onSubmessage:!get ber remoteWriter indicates that a DataReader has received a sample but the corresponding remote DataWriter has already been deleted. If you are shutting down your entire system, you can probably ignore this message. ...
belen
Thu, 01/08/2015 - 03:47
4048 reads — 0 comments

How to use Request/Reply communication pattern in LabVIEW RTI DDS Toolkit for LabVIEW

This solution is only a workaround until the Request/Reply API is available in LabVIEW. This will only work for one Requester and one Replier. The Request/Reply communication pattern is pretty useful for industrial applications. It is quite normal to have an application requesting an action to ...
sara
Thu, 10/09/2014 - 10:11
22415 reads — 10 comments

What error can occur if a thread stack_size is not large enough?

If you create a large number of instances or entities and there is insufficient thread stack space, you can get the following error: REDAFastBufferPool_getBuffer:!precondition: pool==((void *)0) REDASkiplistNode_new:!create node REDASkiplist_assertNodeEA:!create node ...
bobby
Thu, 07/24/2014 - 23:27
4844 reads — 0 comments

Pages