3.2.8. RTI Connext Micro

3.2.8.1. Connext Micro 3 not compatible with DDS-level fragmentation in Connext Professional 7

Starting in Connext 7.0.0, a DataWriter using DDS-level fragmentation will not be able to communicate with a Connext Micro 3 DataReader. The Connext Micro DataReader will receive samples, but they will be corrupted. If you need to use DDS-level fragmentation with Connext Micro 3, contact support@rti.com.

3.2.8.2. Connext Professional DataWriter not compatible with Connext Micro/Cert DataReader under certain conditions

The following compatibility problem exists between a Connext Professional DataWriter and Connext Micro DataReader when migrating to release 7.3.0.

In release 7.3.0, Connext introduced a feature to handle the padding bits in the encapsulation header of a sample payload. This enhancement was aimed at resolving a specific issue (RTI Issue ID CORE-9042, in the Core Libraries Release Notes) where DataReaders, configured with appendable types, might receive samples with incorrect values due to how padding was interpreted.

This change, however, may have led to a compatibility issue causing a Professional DataWriter to not match with a Micro/Cert DataReader in the following Micro/Cert versions: 2.4.12.z and lower, 2.4.13.1, 2.4.13.2, 2.4.13.3, 2.4.13.4, 2.4.13.5, 2.4.14.0, 2.4.14.1, 2.4.15.1, and 3.x.y.z.

For details on this incompatibility (which only happens under certain conditions) and instructions on working around it, see Extensible Types Compliance Mask in the Core Libraries Extensible Types Guide for more information.

Note

By applying this workaround, be aware that you are potentially exposing your system to the issue initially addressed by the fix for CORE-9042. It’s important to weigh the benefits of restoring compatibility against the potential risks of encountering the original padding interpretation issue.