File: README.md

package info (click to toggle)
fastdds 2.9.1%2Bds-1%2Bdeb12u2
  • links: PTS, VCS
  • area: main
  • in suites: bookworm
  • size: 31,412 kB
  • sloc: cpp: 378,073; xml: 7,623; ansic: 4,596; python: 2,545; sh: 189; makefile: 36
file content (30 lines) | stat: -rw-r--r-- 1,330 bytes parent folder | download | duplicates (2)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
# Deadline QoS example

## Application description

This example illustrates the Deadline QoS feature on a FastDDS Application.

To launch this example open two different consoles:

In the first one launch: ./DDSDeadlineQoSExample publisher  
In the second one launch: ./DDSDeadlineQoSExample subscriber

## Application behaviour

The application will use a topic with three different keys,
one of which (the third one) sends a sample only half of the times.

By default the deadline period is set to 2000 ms and the publisher write rate to 1000 ms, so
that the third instance misses the deadline 50% of the time. The number of samples that will be written is set to 10. 

The default behaviour can be changed by providing the following command line arguments:

./DDSDeadlineQoSExample publisher [--deadline <deadline_ms>] [--sleep <writer_sleep_ms>] [--samples <samples>]  
./DDSDeadlineQoSExample subscriber [--deadline <deadline_ms>]

For example:

./DDSDeadlineQoSExample publisher --deadline 1000 --sleep 500 --samples 5  
./DDSDeadlineQosExample subscriber --deadline 1000

will setup the publisher and subscriber to use a deadline period of 1000 ms, the publisher will write a new sample every 500 ms for the first two keys and every 1000 ms for the third one, and a total of 5 samples will be sent.