qos

Summary This article explains how to configure RTI Connext Professional so DomainParticipants discover each other using UDPv4-unicast or SHMEM only. Target outcome: No discovery multicast (discovery multicast receive disabled) Explicit unicast peers for discovery Optional hard disable of UDP ...
49 reads — 0 comments
This article explains what Instances and Instance States are, describes how they apply whether you use them or not, and clears up some common configurations affecting Instance States. ...
6385 reads — 0 comments
Unlike Connext DDS Professional, Connext DDS Micro only supports finite resource limits to ensure that memory growth is bounded. Configuring these limits is therefore an important part of the system design. Here are some considerations to help you determine the optimal resource limits: How many ...
7114 reads — 0 comments
RTI Admin Console uses several non-default QoS settings when interacting with Topics that are used to communicate with other RTI products. The out-of-the-box settings attempt to satisfy the majority of use cases customers have with other configurations, but sometimes it is necessary to change these ...
60572 reads — 0 comments
It is possible to create an Entity (a DataReader , DataWriter, or DomainParticipant ) with a QoS profile defined in the USER_QOS_PROFILES.xml file. In the Java, C, Traditional C++ and .NET APIs, there are methods such as: DDS_Publisher_create_datawriter_with_profile() Depending on what kind of ...
7909 reads — 0 comments
Setting the PUBLISH_MODE QoS Policy's kind to ASYNCHRONOUS_PUBLISH_MODE allows you to make non-blocking write() calls. This means that instead of sending a sample before returning from write() , the data is enqueued and sent according to a flow controller. The HISTORY QoS Policy determines the size ...
4338 reads — 0 comments
Participants are able to know when other participants in the same domain are reachable or not (alive or dead). This is called Participant’s Liveliness. Discovery_Config QosPolicy has three properties that define this Participant’s Liveliness behavior: participant_liveliness_assert_period is the ...
14812 reads — 0 comments
The TRANSPORT_PRIORITY DataWriter Qos Policy controls the transport-level priority settings. Each transport maps it to a transport-specific prioritization mechanism which in the case of UDP are the IP packet diffserv ToS/DSCP bits . Out-of-the box this feature is not enabled, but this forum thread ...
5459 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 UDPv4 builtin transport. ...
22749 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 ...
11260 reads — 0 comments

Pages

Subscribe to RSS - qos