Solutions

Note: Applies to RTI Data Distribution Service 4.0 and 4.1. RTI Data Distribution Service selects well-known static ports based on this formula: 7400 + A * (DomainID + (B * Participant_index)) + (0 | 1 | 2) Where A and B are user-definable, with defaults of 10 and 100, respectively. To run multiple ...
3432 reads — 0 comments
Note: Applies to RTI DDS and Connext versions: NDDS 3.x, RTI Connext 4.x and above. rtiddsgen -example accepts most, but not all, platforms supported by RTI Connext. Any source code generated by rtiddsgen is platform independent, including the example application created using the optional -example ...
2689 reads — 0 comments
Note: Relevant RTI Connext versions: RTI Connext 4.x and above. There are a few QoS that relate to redundancy. In order to support redundancy, you will want to use the Ownership QoS to specify a strength for each writer and specify DDS_EXCLUSIVE_OWNERSHIP_QOS on both writers and readers. There is ...
5781 reads — 0 comments
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 ...
4035 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 ...
3322 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 ...
3498 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 ...
7803 reads — 1 comment

Pages