Windows

Starting with Connext DDS 5.3.0, all Connext DDS libraries for Windows platforms (static release/debug, dynamic release/debug) now link with the dynamic Windows C Runtime (CRT). If you have previous Windows projects that were linking with the Connext DDS static libraries, it will be necessary to ...
860 reads — 0 comments
What is the Monitoring Library and how do I enable it? RTI Monitoring Library is a plug-in that enables an RTI Connext DDS application to provide monitoring data. This data can be visualized through RTI Monitor or a separate application. In RTI Connext DDS , monitoring data are a series of topics ...
1543 reads — 0 comments
DSCP (Differentiated Services Code Point) is a series of bits in the IP header for classification purposes. These bits specify the precedence value of the packet, the drop probability, and the network service used. Before setting the DSCP flag with a desired value, you need to take some things into ...
3273 reads — 0 comments
It is possible to run any of the RTI DDS Services as a Windows Service. Starting with version 5.2.0, program nssm.exe can be found on directory %NDDSHOME%\resource\app\bin\%ARCH% In case you are running a version of RTI Connext DDS which does not include nssm, it can be downloaded from https://nssm ...
2089 reads — 0 comments
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 ...
2166 reads — 0 comments
Note: Applies to RTI DDS Toolkit for LabVIEW version 1.3.0.x 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 ...
2110 reads — 0 comments
Description The discovery phase in DDS applications can be considered a high throughput scenario under some circumstances. Some examples are: The applications have a lot of DDS entities. More than 2 hosts are involved. The type definitions are sent within the discovery packets (i.e., TypeCode and ...
3478 reads — 0 comments
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 ...
6073 reads — 6 comments
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 ...
6351 reads — 9 comments
When running on Microsoft Windows, the Routing Service 5.1.0 can unexpectedly stop working with the following dialog being displayed: This can also occur when terminating the application with Ctrl-C. The problem might be caused by a bug in an optimization introduced in Routing Service 5.1.0 that ...
1718 reads — 0 comments

Pages

Subscribe to RSS - Windows