Closed mossmaurice closed 1 year ago
@elBoberido Would you mind reviewing this PR?
FYI @budrus @ZhenshengLee if you interested in having a look.
Currently, this PR is blocked by https://github.com/eclipse-iceoryx/iceoryx/pull/1505 and https://github.com/eclipse-iceoryx/iceoryx/issues/1668. Once iceoryx Blueberry v2.0.3
has been released, this PR can be merged.
rmw_*
functions need for request-response aka ROS 2 service-client communication.IceoryxServer
andIceoryxClient
rmw_get_service_names_and_types
is not fully implemented and only contains the data available throughServiceDiscovery
as the server and clients and not yet published via the introspection portsCommands for a quick test:
Open questions:
Is the writer GUID needed?:heavy_check_mark:Is there a better workaround than sleeping in:heavy_check_mark: Bug in iceoryx, see https://github.com/eclipse-iceoryx/iceoryx/issues/1855rmw_send_response
? See here forrmw_cyclonedds
commentHow can the full type be aquired via rosidl to do an:heavy_check_mark: Created https://github.com/eclipse-iceoryx/iceoryx/issues/1845alignof()
?ServiceDiscovery
to query node and other relevant info, tbd in the next developer meetup -> Added to the meeting agenda :heavy_check_mark:Known limitations:
rmw_request_id_t
and add avoid *
there if accepted in upstream https://github.com/ros2/rmw/. For now, the limitation exists to always callrmw_take_request
followed byrmw_send_response
and not call e.g. 2x timesrmw_take_request
and then 2xrmw_send_response
.Closes #76 (partly)