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
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
|
<?xml version="1.0" encoding="utf-8"?>
<!--
Description
XML QoS Profile
The QoS configuration of the DDS entities in the generated example is
loaded from this file.
This file is used only when it is in the current working directory
or when the enviroment variable
NDDS_QOS_PROFILES is defined and points to this file.
For more information about XML QoS Profiles see Chapter 15 in the
RTI Data Distribution Service user manual.
-->
<dds xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="c:/ndds/ndds.4.4d/scripts/../resource/rtiddsgen/../qos_profiles_4.4d/schema/rti_dds_qos_profiles.xsd" version="4.4d">
<!-- QoS Library containing the QoS profile used in the generated example.
A QoS library is a named set of QoS profiles.
-->
<qos_library name="HelloTest_Library">
<!-- QoS profile used to configure reliable communication between the DataWriter
and DataReader created in the example code.
A QoS profile groups a set of related QoS.
-->
<qos_profile name="Hello_Profile" is_default_qos="true">
<participant_qos>
<participant_name>
<name>RTI Hello World Example</name>
</participant_name>
<!-- increase total property string max length -->
<resource_limits>
<participant_property_string_max_length>
2048
</participant_property_string_max_length>
</resource_limits>
<property>
<value>
<!-- ================= -->
<!-- enable monitoring -->
<!-- ================= -->
<element>
<name>rti.monitor.library</name>
<!-- must match the library type for the DDS
application -->
<!--
<value>rtimonitoring</value>
<value>rtimonitoringd</value>
-->
<value>rtimonitoring</value>
<propagate>false</propagate>
</element>
<element>
<name>rti.monitor.create_function</name>
<value>RTIDefaultMonitor_create</value>
<propagate>false</propagate>
</element>
<!-- ========================= -->
<!-- monitoring configurations -->
<!-- ========================= -->
<!-- how often to sample and publish monitoirng
topics in seconds, default 5 -->
<!--
<element>
<name>rti.monitor.config.publish_period</name>
<value>5</value>
<propagate>false</propagate>
</element>
-->
<!-- monitoring topics that are sent out,
default * (no filter) -->
<!--
<element>
<name>rti.monitor.config.topics</name>
<value>*</value>
<propagate>false</propagate>
</element>
-->
<!-- user topic filter, default * (no filter) -->
<!--
<element>
<name>rti.monitor.config.usertopics</name>
<value>*</value>
<propagate>false</propagate>
</element>
-->
<!-- Uncomment this if you want statistics to be
published by a new separate particpant,
with the specified domain ID. Default:
not specified (use user participant for
publishing monitoring data) -->
<!--
<element>
<name>rti.monitor.config.new_participant_domain_id</name>
<value>10</value>
<propagate>false</propagate>
</element>
-->
<!-- Uncomment this if you want to use specific
QoS profile for entities created by
monitoring. Default: not specified
(use internal QoS values) -->
<!--
<element>
<name>rti.monitor.config.qos_library</name>
<value>RTIMonitoringQosLibrary</value>
<propagate>false</propagate>
</element>
<element>
<name>rti.monitor.config.qos_profile</name>
<value>RTIMonitoringPublishingQosProfile</value>
<propagate>false</propagate>
</element>
-->
<!-- Uncomment this if you want to control the
property of the thread that sample and publish
monitoring data -->
<!-- default -2 for windows, -999999 for linux -->
<!--
<element>
<name>rti.monitor.config.publish_thread_priority</name>
<value>-2</value>
<propagate>false</propagate>
</element>
-->
<!-- default 0 for windows, -1 for linux -->
<!--
<element>
<name>rti.monitor.config.publish_thread_stacksize</name>
<value>0</value>
<propagate>false</propagate>
</element>
-->
<!-- default FLOATING_POINT | STDIO -->
<!--
<element>
<name>rti.monitor.config.publish_thread_options</name>
<value></value>
<propagate>false</propagate>
</element>
-->
<!-- do we want to montior memory and CPU usage,
default true -->
<!--
<element>
<name>rti.monitor.config.get_process_statistics</name>
<value>true</value>
<propagate>false</propagate>
</element>
-->
<!-- Do we want to skip monitoring internal entitities
and not include them in entity counts,
default true -->
<!--
<element>
<name>rti.monitor.config.skip_monitor_entities</name>
<value>true</value>
<propagate>false</propagate>
</element>
-->
<!-- do you want monitoring library to reset
status change count after access, default false -->
<!--
<element>
<name>rti.monitor.config.reset_status_change_counts</name>
<value>false</value>
<propagate>false</propagate>
</element>
-->
<!-- monitoring library verbosity for internal
debugging purpose, default 1 -->
<!--
<element>
<name>rti.monitor.config.verbosity</name>
<value>1</value>
<propagate>false</propagate>
</element>
-->
<!-- maximum size of the preallocated buffer.
If sample serialized size is
larger than this value (unless the value is -1),
dynamic memory allocation will be used.
Default -1 (preallocated buffer is set
according to max size serialized of the data
type, no dynamic memory allocation) -->
<!--
<element>
<name>rti.monitor.config.writer_pool_buffer_max_size</name>
<value>-1</value>
<propagate>false</propagate>
</element>
-->
</value>
</property>
<!-- monitoring types can have large data -->
<receiver_pool>
<buffer_size>65530</buffer_size>
</receiver_pool>
</participant_qos>
<!-- QoS used to configure the data writer created in the example code -->
<datawriter_qos>
<reliability>
<kind>BEST_EFFORT_RELIABILITY_QOS</kind>
</reliability>
<durability>
<kind>TRANSIENT_DURABILITY_QOS</kind>
</durability>
<history>
<kind>KEEP_ALL_HISTORY_QOS</kind>
</history>
<protocol>
<rtps_reliable_writer>
<max_heartbeat_retries>10</max_heartbeat_retries>
</rtps_reliable_writer>
</protocol>
</datawriter_qos>
<!-- QoS used to configure the data reader created in the example code -->
<datareader_qos>
<reliability>
<kind>BEST_EFFORT_RELIABILITY_QOS</kind>
</reliability>
<history>
<kind>KEEP_ALL_HISTORY_QOS</kind>
</history>
<durability>
<kind>TRANSIENT_DURABILITY_QOS</kind>
</durability>
</datareader_qos>
</qos_profile>
</qos_library>
</dds>
|
