Solutions

What are the requirements for using the Legacy .NET API?

Note: Applies to the legacy RTI Connext .NET API (4.3e to 6.1). For the new .NET API (6.1 and above), see the Getting Started Guide . 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 ...
gianpiero
Thu, 01/17/2013 - 12:32
7440 reads — 0 comments

What QoS policies do I need to change when creating a reliable reader and writer?

This Solution addresses how to create a reader and a writer that use reliable communication. It also shows, by example, some of the more common QoS policies that you might want to change. Method One for modifying the QoS The following C++ code snippet shows how to change those QoS policies. Data ...
tron
Thu, 01/17/2013 - 12:32
8009 reads — 0 comments

Example Code - Achieving 'Batching' by setting push-on-write to false

Note: Applies to RTI Connext 4.0 and above. This example shows how to achieve batching without using the Batch QoS policy (which was introduced in 4.4). Publisher This Publisher sends out bursts of 32 keyed reliable samples at 20Hz. The point here is that the dataWriterQos.protocol.push_on_write = ...
ken
Thu, 01/17/2013 - 12:32
5366 reads — 0 comments

Why do I see "Error storing RTI DDS sample in table 'database.tablename'" in the RTC console when subscribing to data?

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 ...
erin
Thu, 01/17/2013 - 12:31
3315 reads — 0 comments

How can I improve performance on Windows under a heavy load?

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 ...
alex
Thu, 01/17/2013 - 12:31
17804 reads — 2 comments

Why don't I see any builtin topic data when subscribing to DDS_TopicBuiltinTopicData?

Note: Applies to RTI Data Distribution Service 4.1 and above. The DDS_TopicBuiltinTopicData built-in topic is meant to convey information about discovered Topics. It is a known issue in RTI Data Distribution Service 4.1 and 4.2 that these topic samples are not propagated in a separate packet on the ...
edward
Thu, 01/17/2013 - 12:28
2379 reads — 0 comments

What does the "can't reach: locator" error message mean?

Note: Applies to RTI Connext 4.x. In general, a can't reach:locator: error message means that a DataWriter cannot send to the locator of a DataReader , usually due to a transport configuration error. For example, suppose Participant A has both the UDPv4 and shared-memory built-in transports enabled ...
vishal
Thu, 01/17/2013 - 12:24
23403 reads — 1 comment

Pages