XCDR DataRespresentation XML syntax

5 posts / 0 new
Last post
Offline
Last seen: 1 week 2 days ago
Joined: 04/13/2019
Posts: 7
XCDR DataRespresentation XML syntax

I'm using the RTI Python Connector for v6.0 and want to write to an old system running v5.3. In the datawriter_qos I believe I have to specify the DataRepresentation for xcdr version 1. But I'm having trouble finding the exact syntax / keywords to use.

<qos_library name= .....
  <qos_profile name= ....
    <datawriter_qos>
      <data_representation?>
        <version?> "xcdr?" </version?>
      </data_representation>
       .....

Offline
Last seen: 1 day 19 hours ago
Joined: 04/02/2013
Posts: 112

The default data representation in 6.0 is still XCDR1. XCDR2 is available, but it's not used by default.

 

Offline
Last seen: 4 days 23 hours ago
Joined: 10/22/2018
Posts: 34

Are you having trouble communicating between the two applications or were you just expecting that you might have to change the data representation?
As mentioned above it isn't necessary to change the data representation version (since they both use XCDR1 by default).

If you are struggling to get communication between these 2 versions, one reason could be related to your type. If it contains unbounded sequences or strings, the way we represent these is different between these two versions. You can read more here but you might need to add stringMaxLen to unbounded strings in your XML type.

Offline
Last seen: 1 week 2 days ago
Joined: 04/13/2019
Posts: 7

I was using stringMaxLength="256" with v6.0 and should have used "255" to have it compatible with existing devices using DDS v5.3. Also, now the same v6.0 QoS files work with v5.3. I just change the reader base index.
 
I thought I saw something on the forum about RTI working on 'professionalizing' the RTI Connector but can't relocate it. Any comment? Python binding?

Thanks for clarifying the XCDR.

Offline
Last seen: 4 days 23 hours ago
Joined: 10/22/2018
Posts: 34

RTI Connector for Python and for Javascript will be productised in Q4 of 2019. The other bindings (Go, C# among others) will not be modified.

Sam