Windows

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. ...
21175 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 ...
10522 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 ...
12667 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 ...
6469 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 ...
47095 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 ...
8411 reads — 0 comments
Note: Applies to RTI Real-Time Connect 4.x and above. One possible reason might be your ODBC driver. The following error may appear when RTI Real-Time Connect tries to store a sample and after creating a new entry in the RTC database table RTIDDS_SUBSCRIPTIONS , such as table_history_depth : RTI ...
4227 reads — 0 comments
When running a subscribing application on a Windows system under heavy load (such as when running performance tests), you may experience erratic behavior when receiving samples, due to reassembly failures. You may see that the application temporarily stops receiving data. You can verify this ...
20831 reads — 2 comments
Yes, you can run your RTI Connext-based application on a virtual machine. Make sure that any time synchronization or jumps occur before starting your RTI Connext application. In versions 4.4b and higher, we have improved support for virtual machines by introducing a feature to specify which clock ...
3268 reads — 0 comments
The short answer is that you need to remove the trailing backslash from your NDDSHOME environment variable. The rtiddsgen code generator calls a Java program within a batch script. This script passes %NDDSHOME% as a define argument to java. If NDDSHOME ends with a backslash, the shell escapes the ...
6556 reads — 0 comments

Pages

Subscribe to RSS - Windows