Solutions

There are a some restrictions to take into account when integrating RTI Database Integration Service (DIS) and RTI DDS Toolkit for LabVIEW together. These are the following: The database limitations, see Appendix B on DIS User's Manual. National Instrument (NI) Cluster types are mapped to IDL types ...
2701 reads — 0 comments
In some cases RTI Database Integration Service fails to start even when the libraries are properly configured. The triggered error is the following: [root@localhost ~]# rtirtc_mysql -cfgName default -noDaemon RTI Database Integration Service to MySQL, Release 5.2.0: startup succeeded [ ...
4717 reads — 0 comments
RTI Connext supports two ways of filtering data : using QueryConditions and ContentFilteredTopics . These two options differ in the moment when DDS applies the filter. QueryConditions filter data after the DataReader has received and queued it. That means that the application will receive all ...
3443 reads — 2 comments
A ‘match’ between the local and remote entities occurs only if the DataReader and DataWriter have the same Topic , compatible QoS policies, and a compatible data type. By default, type matching is done using the TypeObject . The DataReader’s type must be assignable from the DataWriter’s type. If ...
6111 reads — 0 comments
It is possible to run any of the RTI DDS Services as a Windows Service. Starting with version 5.2.0, program nssm.exe can be found on directory %NDDSHOME%\resource\app\bin\%ARCH% In case you are running a version of RTI Connext DDS which does not include nssm, it can be downloaded from https://nssm ...
5746 reads — 0 comments
Type object and type code information maximum length can be set in QoS by adding to your QoS file <participant_qos> <resource_limits> <type_code_max_serialized_length>0</type_code_max_serialized_length> <type_object_max_serialized_length>0</ ...
4918 reads — 0 comments
Setting the PUBLISH_MODE QoS Policy's kind to ASYNCHRONOUS_PUBLISH_MODE allows you to make non-blocking write() calls. This means that instead of sending a sample before returning from write() , the data is enqueued and sent according to a flow controller. The HISTORY QoS Policy determines the size ...
3068 reads — 0 comments

Pages