Dynamic Data API

12 posts / 0 new
Last post
Offline
Last seen: 2 years 11 months ago
Joined: 03/03/2015
Posts: 19
Sending byte array using DDS_Dynamic Data

Hello,

I'm using the DDS_DynamicData feature to send data of multiple types using RTI DDS. I managed to define my dynamic data type support for simple types (primitives). However, I have more complex data types which I want to send using the DynamicData feature, like arrays, strings, structs, etc. 

I want to make the application as generic as possible, so I don't really want to create a type support for each data type, as I want to send the complex types as "byte array" or something similar. 

3 posts / 0 new
Last post
Offline
Last seen: 6 months 3 weeks ago
Joined: 08/13/2014
Posts: 55
Error in Serialization and Deserialization

Hi,

I'm using RTI version 5.2.0 (Modern C++ API) and I sometimes get the following error in my output terminal. What is this error and what should I do? For your information, my program is a small version of recording service and I do serialization and deserialization of dynamic data and synamic type in my program. I have also brought my codes for serialization and deserialization of dynamic type below. For dynamic data serialization and deserialization, I use "to_cdr_buffer" and "from_cdr_buffer" functions respectively. 

3 posts / 0 new
Last post
Offline
Last seen: 7 years 1 month ago
Joined: 02/06/2012
Posts: 1
Dynamic Data API or IDL ? which one

In the past I have always used IDL to describe data types. Now I have a code generator which amongst other things is designed to generate the DDS related code.

One approach is to generate the Dynamic Data API code. The other is to generate IDL and then translate that.  I also want to deserialize the incoming data directly into C++ data types such as Eigen::Vector3d etc. Here are my questions

1) Do I lose anything by not using the IDL approach. i.e., is the generated code faster or is the generated when rtiddsgen is used.

Subscribe to RSS - Dynamic Data API