Windows

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 ...
40089 reads — 0 comments
Note: Applies to RTI Connext 4.3e and above 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 (x86) or later must be installed. You can download it from Microsoft Windows Update or ...
5768 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 ...
2405 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 ...
13172 reads — 1 comment
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 ...
2178 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 ...
3981 reads — 0 comments
NOTE: Applies to RTI Data Distribution Service 4.1 and 4.2 By default, RTI Data Distribution Service uses shared memory to communicate with other DomainParticipants on the same node and disables local traffic over the UDPv4 or UDPv6 loopback interface. So, by default, an RTI Data Distribution ...
4230 reads — 0 comments
Note: Applies to RTI Connext 4.x and above. An RTI Connext application installed as a Windows Service application (formerly known as an NT service) will not communicate over shared memory with a DDS application that is not installed as a Windows Service. This is due to the namespace used to create ...
4519 reads — 0 comments
Note: Applies to RTI Data Distribution Service 4.4b and below If a network interface is disconnected or disabled while your application is running, your application might hang when properly shutting down your DomainParticipant. The likely cause is how the middleware cleans up sockets and how ...
2908 reads — 0 comments
Note: Applies to RTI Connext 4.x and above. RTI Data Distribution Service 4.4 and later include support for non-monotonic support. Please refer to the 4.4 User's Manual for details and the list of supported platforms. RTI Data Distribution Service 4.3 and earlier requires a monotonic increasing ...
3361 reads — 1 comment

Pages

Subscribe to RSS - Windows