Pablo Garrido
Pablo Garrido
Which distro of ROS 2 you have installed? Have you tried to build against your local SPDLog installation using the flag `UAGENT_USE_SYSTEM_LOGGER`? https://github.com/eProsima/Micro-XRCE-DDS-Agent/blob/40954c2379dfcb2bfa9f6ba22146c57c6742b5b7/CMakeLists.txt#L32
Yes, I have seen this issue in the past: https://github.com/micro-ROS/micro-ROS-Agent/issues/186 or https://github.com/micro-ROS/micro-ROS-Agent/issues/50 If I recall correctly Humble has an spdlog version installed, at least, the docker image has it: ...
Did you start in a clean environment? Ensure that build, log and install folder are removed before running the colcon command
Are you sure that you have a clean humble installation? I have just tried to replicate in a clean ROS 2 Humble docker with no problem: https://asciinema.org/a/6aU9thzS4ivJTzBH0yD930EkQ
Just check the differences between your environment and a clean one, and make sure that you are not installing/modifying spdlog anywhere.
Is it not possible for you to use the dockerized version of the micro-ROS Agent? https://hub.docker.com/r/microros/micro-ros-agent
Could you provide a quick replicator?
Why do you need to sync time so quickly? This approach was designed to calculate drift between clocks and then assume a certain stability for the drift variance. Which is...
This approach uses an NTP-like algorithm for calculating the time offset between the MCU and the Agent's clocks. This is not a high-precision approach that targets to provide a valid...
You are right, replies from different requests still can cause problems. It seems that the wire protocol is not designed to handle this because the definition of the sync request...