Windows

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 ...
9177 reads — 7 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 ...
9033 reads — 10 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 ...
2139 reads — 0 comments
This error: The application was unable to start correctly (0xc0150002). Click OK to close the application. happens when you try to start an application compiled against RTI dotnet libraries in a system where the "Visual Studio® 2005 Service Pack 1 Redistributable Package MFC Security Update" is not ...
177509 reads — 0 comments
This error is typically due to array management. Working with LabVIEW arrays and sending them through RTI Connext DDS can be tricky. Here you have some guidelines on how to fix this error For versions of the RTI DDS Toolkit previous to 1.2.0.90 In LabVIEW, arrays are declared with an initial length ...
4702 reads — 0 comments
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 ...
11483 reads — 1 comment
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 ...
7033 reads — 0 comments
QoS profiles provide a way to configure your DDS application, defining most aspects of the DDS paradigm and the underlying communication mechanisms. As part of RTI DDS Toolkit for LabVIEW we provide a set of pre-defined QoS profiles. These profiles solve general use cases such as a Reliable ...
8371 reads — 0 comments
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 ...
3854 reads — 0 comments
RTI Protocol Analyzer with Wireshark uses the Windows Packet capture ( WinPcap ) driver (called NPF) when it starts to capture live data. Loading the driver requires Administrator privileges. Once the NPF driver is loaded, every local user can capture from the driver until it is stopped. On Windows ...
38507 reads — 0 comments

Pages

Subscribe to RSS - Windows