code examples

If you are running into problems compiling the shipped examples or the generated Hello World example from rtiddsgen on a non-Windows platform, one of the first things to check is if your installation directory resides in a path that contains spaces. If it does, then the solution will be to redefine ...
6125 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 ...
3662 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< ...
2608 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 = ...
3718 reads — 0 comments
Note: Applies to RTI Connext 4.x and above. Upon changing the liveliness lease duration of both the DataReader and DataWriter , and instrumenting the on_liveliness_changed() listener callback on the reader side, you will see the callback is called twice when you kill the publishing application. ...
3948 reads — 0 comments
Note: Applies to RTI Connext 4.x and above The narrow method is a class-scope method that implements a safe down-cast for a pointer to an RTI Connext entity. It is a type-safe way to cast a pointer. The Java API does not require this method because Java casts are always type-safe. This method takes ...
3994 reads — 0 comments
Note: Applies to NDDS 3.x. NDDS's internal time representation is in NTP format rather than DDS_Time for computational efficiency reasons. The header osapi/osapi_ntptime.h defines NTP time class ( struct RTINtpTime ) as well as its manipulation methods. A brief excerpt from this header file is ...
2444 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 ...
6792 reads — 0 comments
Note : Applies to RTI Connext 4.x and above. Discovery is not an instantaneous event. It takes some time for the discovery process between applications to complete. The DDS DataWriter and DDS DataReader must discover each other before they can start communicating. Therefore, if you send data ...
10845 reads — 0 comments
Note: Applies to RTI Connext 4.x and above For dynamic discovery to work properly, RTI Connext relies on a globally unique identifier (GUID) that uniquely identifies each instance of a participant in the network. By default, RTI Connext will automatically choose values for the host ID and app ID ...
6968 reads — 3 comments

Pages

Subscribe to RSS - code examples