Closed marlow-fawn closed 1 year ago
Just following up - it's due to a different DDS implementation. It seems like the default is FastRTPS, and Humble uses Cyclone by default.
Just following up - it's due to a different DDS implementation. It seems like the default is FastRTPS, and Humble uses Cyclone by default.
Similar problem for me @marlow-fawn, I think.
18:24:45.754 [783323948-UserDataServiceReceiver] ERROR p.r.i.s.t.RtpsMessageReceiver#783323948-UserDataServiceReceiver - Read submessage size does not match expected: expected value <36.0>, actual value <32.0>
id.xfunction.PreconditionException: Read submessage size does not match expected: expected value <36.0>, actual value <32.0>
How can I change DDS implementation? Reading from console, I see that jros2client uses RTPSTALK as default:
Hi @marlow-fawn, @dbortoluzzi
How can I change DDS implementation? Reading from console, I see that jros2client uses RTPSTALK as default:
That is right. rtpstalk allows to communicate with FastRTPS, Cyclone and itself. rtpstalk is Java based when FastRTPS, Cyclone are not.
The idea of jrosclient is to be pure Java client which means allowing it to switch to native FastRTPS, Cyclone is not possible.
You can ignore the warning for liveliness for now. I have created issue for rtpstalk to fix it.
Hello,
Just started using this project so I may have missed some configuration step. I'm getting the following warnings when following the tutorial:
A similar message exists for the subscriber.
Both the subscriber and publisher are able to talk to native ros2 topics, but not to each other. Any insight would be great.