RTI Administration Console

Background: 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 ...
187 reads — 0 comments
This article quickly illustrates how the RTI Admin Console can be used to determine the TypeCode and TypeObject sizes (note 2). In the example below, the RTI Shapes Demo is publishing Circles, Squares, and Triangles. The Admin Console displays the TypeCode and TypeObject sizes in several places. In ...
380 reads — 0 comments
RTI Connext DDS Micro provides two ways of determining endpoint information of other DomainParticipants: Dynamic Endpoint Discovery , and Static Endpoint Discovery . Dynamic endpoint discovery uses the DDS Simple Discovery Protocol, which uses builtin discovery DataWriters and DataReaders to ...
3427 reads — 0 comments
When running some of the RTI tools on Linux (e.g. RTI Shapes Demo, RTI Launcher) you may see the following or similar warning messages thrown by GTK/GDK: (Gtk-CRITICAL **: IA__gtk_widget_get_direction: assertion `GTK_IS_WIDGET (widget)' failed) or Gdk-WARNING **: gdk_window_set_icon_list: icons too ...
2509 reads — 0 comments
For a complex topic data type that has many fields or long field names, Admin Console may not be able to show the topic’s data type, DDS Spy may not be able to print the samples’ contents, Recording Service may not be able to record the data, and Analyzer may show the warning “Failed to create ...
7642 reads — 0 comments
I've changed my transport settings to increase the amount of throughput I can achieve in my application, or I am using RTI Connext DDS 5.1.0 tools with previous versions of the middleware. When I run RTI Analyzer, RTI Monitor, or RTI Admin Console on a different machine I get incomplete discovery. ...
6012 reads — 0 comments
Subscribe to RSS - RTI Administration Console