Linux

Modern C++ API with GCC > 5.1 in Connext 5.2.x

GCC 5.1 introduced a new version of libstdc++ with a library ABI that includes new implementations of std::string and std::list (see in GCC online documentation). This new ABI breaks backwards compatibility with applications and libraries linked against older versions of libstdc++ using std::string ...
israel
Wed, 01/04/2017 - 08:08
6013 reads — 0 comments

How do I use the Traditional C++ and Modern C++ APIs in the same application?

Note: Applies to RTI Connext DDS 5.2.0 and above. The Modern C++ API was introduced with RTI Connext DDS 5.2.0. This solution explains how to use the Modern and Traditional C++ APIs in the same application. To make them work together, you must not use both of them in the same .cpp file. That is, do ...
Benito Palacios
Mon, 10/19/2015 - 03:23
5765 reads — 0 comments

How licensing works in RTI DDS Toolkit for LabVIEW

Note: Applies to RTI DDS Toolkit for LabVIEW version 3.1.1 or later The best way to understand the licensing methods of the RTI DDS Toolkit for LabVIEW is to separate them per platform: Windows and NI Linux. Licensing in Windows When you download the RTI DDS Toolkit for LabVIEW (from the VI Package ...
sara
Wed, 07/08/2015 - 10:25
5761 reads — 0 comments

I see GTK and GDK warnings when I run some RTI applications, is this normal?

When running some of the RTI tools on Linux (e.g. RTI Shapes Demo, RTI Launcher) you may see the following or similar warning messages thrown by GTK/GDK: (Gtk-CRITICAL **: IA__gtk_widget_get_direction: assertion `GTK_IS_WIDGET (widget)' failed) or Gdk-WARNING **: gdk_window_set_icon_list: icons too ...
juan
Thu, 07/02/2015 - 02:40
4044 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
59256 reads — 7 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
17085 reads — 10 comments

How to send big TypeCodes and TypeObjects

Note : Applies to RTI Connext 4.x and above. In this solution we show how to configure RTI Connext to send TypeCodes and TypeObjects larger than the default maximum serialized sizes (2kB and 3kB respectively). In this example, the modifications needed to the transport settings are shown for the UDPv4 builtin transport. ...
jose
Tue, 06/18/2013 - 08:04
19186 reads — 1 comment

How to check the size of the topic's TypeCode using RTI Monitor

Note : Applies to RTI Connext 4.5d and above. This solution shows how to check the size of the topic’s TypeCode using RTI Monitor . It consists of two steps: Enable RTI Monitoring Library in the application. Acess to TypeCode's information from RTI Monitor. Enable RTI Monitoring Library in the ...
jose
Mon, 06/17/2013 - 14:51
9863 reads — 0 comments

What causes this error: "incompatible shared memory protocol detected."

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 ...
bobby
Wed, 02/06/2013 - 14:05
5841 reads — 0 comments

What does RTI Analyzer error code 127 or 'shell error undefined symbol: _ZN4nsID5ParseEPKc' in libswt mean?

If you are running RTI Analyzer on Linux and you see the following message: JVM terminated. Exit code=127 and the following error on the command shell: /usr/local/rti/RTI_Developer_Platform_1.3.0/jre/bin/java: symbol lookup error: /usr/local/rti/RTI_Developer_Platform_1.3.0/apps/RTI_Analyzer_1.3.0/ ...
Ran
Thu, 01/17/2013 - 12:56
4050 reads — 0 comments

Pages

Subscribe to RSS - Linux