Replies: 1 comment
-
Hi @sven1904 , One of the most relevant updates that came with Fast-DDS 3 is a refactored XTypes module that is now compliant with the DDS-XTypes standard. With this change it was also decided to publish type information by default. Currently there seems to be interoperability issues with Cyclone DDS due to this fact, but these would probably be avoided by disabling type propagation. Could you please test that? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I'm currently testing the communication between Fast DDS and Cyclone DDS.
While doing that, I encountered that Fast DDS 3.x has some issues while Fast DDS 2.x doesn't.
Fast DDS 2.x can publish messages which can be read by Cyclone DDS and vice versa.
On the other side, a Fast DDS 3.x subscriber is not able to read from a Cyclone DDS publisher.
The behavior of a Fast DDS 3.x publisher in combination with a Cyclone DDS subscriber is even more interesting.
The publisher 'detects' that someone actually subscribed to the given topic which is why it starts writing messages, but the subscriber does not recognize them and still waits for messages.
The Fast DDS code is taken from the example generated by fastddsgen with the CMake option.
The Cyclone DDS code is also generated by their idlc tool and the publisher/subscriber code is taken from the website.
This is the used IDL file CiaoMondo.idl (which has been used for code generation):
Since Cyclone DDS publisher and subscriber are not generated by icdl, i'll also put them here:
Btw, I also checked different versions of Cyclone DDS which made no difference, neither for Fast DDS 3.x nor 2.x.
Beta Was this translation helpful? Give feedback.
All reactions