DESTINATION_ORDER

11 posts / 0 new
Last post
Offline
Last seen: 1 year 1 month ago
Joined: 12/20/2022
Posts: 6
Unable to change some QoS settings for DDS router

I have some issues with rtiddsrotuer, where some QoS settings i give it doesnt seem to bite. 

In the QoS I have given datareader_qos, datawriter_qos and topic_qos destination order: "BY_SOURCE_TIMESTAMP_DESTINATIONORDER_QOS". But when i look in Adminconsole i see that the router requests _RECEPTION_. And the main issue is when the unpacking router then supplies _RECEPTION_ to my applications (readers) expecting _SOURCE_ (which is incompatilbe). 

3 posts / 0 new
Last post
gustavo@rti.com's picture
Offline
Last seen: 6 years 5 months ago
Joined: 03/06/2017
Posts: 1
Understanding by_source and source_timestamp_tolerance at the DataWriter side

Hi,

I have a question regarding Destination Order QoS, by_source_timestamp and source_timestamp_tolerance at the DW side.

At the DR the behavior is clear for me, I have tests and validated all behaviors. My question is about to the DW side, and the source_timestamp_tolerance at the DW.

According to the docs, if I have a DataWriter with kind DDS_BY_SOURCE_TIMESTAMP_DESTINATIONORDER_QOS:

Organization:
3 posts / 0 new
Last post
Offline
Last seen: 4 years 9 months ago
Joined: 01/09/2013
Posts: 10
Compatibility of Connext Micro with DESTINATION_ORDER QoS

The documentation explains that Connext Micro supports only BY_RECEPTION_TIMESTAMP for the DESTINATION_ORDER QoS. Thus, a Micro application will be able to receive data from a full-DDS application with BY_SOURCE_TIMESTAMP, but not send data to this application.

Subscribe to RSS - DESTINATION_ORDER