How to Get Your License for RTI Connext (Updated 2017)

RTI is providing a 1-year RTI Connext DDS license to the contestants of the Technical Challenge. To get your license you just need to follow these steps:


Welcome to the RTI+LabVIEW forum!

Have you ever useCompatible with LabVIEWd LabVIEW and found it difficult to communicate to several VIs? Have you ever struggled to create sockets that communicate to just a couple of VIs? Have you ever wished that there was an easy way to integrate your VI with an exisiting C/C++/Java/... application? Have you ever imagined how cool it would be to control your VI from your smartphone?


Collaborate with RTI in your research. Come to RTI's HQ in California to do research!


Are you doing Academic Research in Distributed Systems? Does your research require many computers or aplications to communicate over the network? Are you interested in Publish-Subscribe and Data Distribution Technologies? Secure middleware? Robust / Highly-Available Distributed Systems?


Use RTI free-of-charge for IRAD, Research, and University

Would you like to use the RTI Technology for a Research or IRAD Project?  Join the RTI Research and Academic community!

As a member of the RTI R&A Community you can access the RTI Data Distribution Service Professional Edition free of charge!


New Release: RTI DDS Toolkit for LabVIEW version 2.1.1

We're pleased to announce the latest release of the RTI DDS Toolkit for LabVIEW, delivering improved stability and usability for distributing real-time data between National Instruments LabVIEW® Virtual Instruments and other applications that communicate using the DDS standard.


Using enumerations in XML file with Connector for Python

I have installed the rticonnextdds-connector-master for Python script support and successfully ran the simple ShapeExample demo.  I then tried to modify the XML based on some IDL->XML generated code from rtiddsgen that we are using, as follows:

<enum name="TestEnum">
      <enumerator name="FIRST_THING"/>
      <enumerator name="SECOND_THING"/>


Understanding by_source and source_timestamp_tolerance at the DataWriter side


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:


Announcing RTI Connext DDS 5.3!

When you spend months working on a new feature or release, I think it’s only natural to be excited (really-super-crazy excited!) about it. Don’t you?



Subscribe to RSS - RTI