Solutions

Note: RTI Data Distribution Service 4.0 and 4.1. RTI Data Distribution Service 4.1d provides native support for these 64-bit platforms: Red Hat Enterprise Linux 3.0 and 4.0 Solaris 10 Windows XP Professional x64 Edition To build and run earlier versions of RTI Data Distribution Service applications ...
2926 reads — 0 comments
Note: Applies to NDDS 3.x, RTI Connext 4.x and above. You can run a publisher and subscriber on the same node or on different nodes. However, even if you are only using one node, by default, RTI Connext looks for a network connection. The default discovery behavior is to look for peers using ...
2298 reads — 0 comments
Note: Applies to NDDS 3.x, RTI Connext 4.x and above. There are several drawbacks to using broadcast. There is a performance degradation problem when using broadcast. It disrupts EVERY node in the system-even the ones that do not want ANY data! Such a system is clearly not scalable. With broadcast ...
2318 reads — 0 comments
Note: Applies to RTI Data Distribution Service 4.0x and higher. RTI Connext must discover and keep track of remote entities, such as new participants in the domain or new DataReaders of a particular topic in order to work. This information may also be important to the application itself, which may ...
4797 reads — 0 comments
Note: Applies to RTI Data Distribution Service 4.1 and higher and all RTI Connext versions. You may want to use Visual Studio Express because it's free. Please note, however, that Visual Studio Express has some limitations: It does not include Microsoft programming libraries, such as MFC, ATL, and ...
6339 reads — 0 comments
Note: Applies to RTI Connext versions 4.x and above Configuration data structures such as QoS structures are passed to RTI Connext by value, as they are only used to initialize the internal state of the entity being created. After the call to create the object, the user application can free the ...
1910 reads — 0 comments
Note: The ports used are different between RTI Connext 4.x and NDDS 3.x. RTI Connext The built-in UDP transport in RTI Connext 4.x and above uses port numbers that are based on the domain ID and participant ID. Because the RTPS spec changed, the mapping is different before and after Version 4.2 of ...
20230 reads — 2 comments

Pages