Solutions

Note : Applies to RTI Connext 4.x and above. The message MIGGenerator_addData:serialize buffer too small indicates that the transport-buffer size is too small for the data being sent and needs to be increased. When the transport layer is initialized, it allocates enough resources to serialize/ ...
4203 reads — 0 comments
Note: Applies to RTI Connext 4.3 and above, although the same methodology can be applied to 4.0, 4.1, and 4.2. The following example has been written in C++. Purpose This example illustrates how to extract and print Datawriter and Datareader statuses to a Comma-Separated Values (csv) file. This ...
5791 reads — 0 comments
Note: Applies to RTI Data Distribution Service 4.x and above. First, we need some background to understand how RTI's shared-memory transport works. The RTI Data Distribution Service shared-memory transport uses different standards to access shared mutexes and shared-memory segments, depending on ...
68623 reads — 1 comment
Note: Applies to RTI Data Distribution Service 4.1. If you start an application with shared memory as the only transport and then start a second application with a multicast address in NDDS_DISCOVERY_PEERS or in the multicast_receive_addresses field in the Discovery QosPolicy on the same node, you ...
4204 reads — 0 comments
Suppose you have a local variable in your application that is declared as a double (that is, a long long variable declared within an IDL file), and you try to cast it to a RTICdrLongLong variable, like this: double doubleLocalVar = 0; /* Main loop */ for (count=0; (sample_count==0) || (count< ...
4469 reads — 0 comments
The minimum heap required to run a simple HelloWorld publisher and subscriber on an INTEGRITY system is about 11.3MB. Problem You run an example HelloWorld application and create_participant() returns NULL. When you increase the logging verbosity, you see messages such as: !create fast buffer pool ...
3279 reads — 0 comments
Note: Applies to NDDS 3.x and RTI Connext 4.x and above First, it is important to point out that NDDS 3.x and RTI Connext 4.x and above are not wire-protocol compatible. Applications built with these 2 products cannot communicate with each other. Second, although the object models of both products ...
3749 reads — 0 comments

Pages