API

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< ...
4163 reads — 0 comments
As described in the online HTML documentation for the DomainParticipantResourceLimits Qos Policy, there is a QoS parameter called topic_data_max_length , which is used to set the maximum length of the topic data to be sent out. topic_data_max_length is a DDS_Long, which is a 32-bit signed long ...
7888 reads — 0 comments
Note: Applies to the legacy RTI Connext .NET API (4.3e to 6.1). For the new .NET API (6.1 and above), see the Getting Started Guide . For applications to use the RTI Connext .NET API, the following MUST be true for the target machine: The Microsoft .NET Framework Version 2.0 Redistributable Package ...
7772 reads — 0 comments
Note: Applies to RTI Connext 4.0 and above. This example shows how to achieve batching without using the Batch QoS policy (which was introduced in 4.4). Publisher This Publisher sends out bursts of 32 keyed reliable samples at 20Hz. The point here is that the dataWriterQos.protocol.push_on_write = ...
5704 reads — 0 comments
The short answer is that only the platforms listed in the Release Notes are supported. A platform is defined by a CPU architecture, an operating system and its version, and a compiler version. For example, i86Linux2.6gcc4.1.1 means Linux 2.6 on an Intel processor with version 4.1.1of the gcc ...
3264 reads — 0 comments
As described in TCP/IP Illustrated, Volume 1, by W. Richard Stevens, Section 11.9 , ARP entries that expire may introduce high latencies on the next send. Entry expiration details are system-dependent; for instance, a packet sent to a particular address may refresh the timeout. On a VxWorks target ...
5061 reads — 0 comments
We do support the ability for local DataWriters and DataReaders of the same topic to ignore each other, i.e., the local DataReader to only receive messages from remote DataWriters , not local ones. To do so, you can call ignore_participant() . For example: DDSDomainParticipant *dP; dP-> ...
7997 reads — 0 comments
Note: Applies to RTI Connext 4.x and above RTI Connext does not support the IDL interface data type because it corresponds to remote procedure calls, a concept that does not apply to the data-centric, publish-subscribe (DCPS) communications model of the DDS standard. The valuetype data type is ...
5159 reads — 0 comments
Note : Relevant RTI Connext versions: RTI Connext 4.x and above The default settings for RTI Connext 4.x and above will allow approximately 11 (5 for 4.4c and below) domain participants in a single application (address space). The number of domain participants on a given node is only limited by ...
10369 reads — 0 comments
Prior to RTI Data Distribution Service version 4.4, receiving data over multicast could only be configured on the reader side. The reader Qos specifies to the writer that it wants to receive data using a multicast address. Starting with RTI Data Distribution Service 4.4, in addition to the ...
9926 reads — 0 comments

Pages

Subscribe to RSS - API