You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm leaving this issue also as a kind of documentation.
The only way I've had success installing H1.x or H2.x on a robot, no matter the xml fastrtps config file, is to first install H0.0, and then install H1.x or H2.x.
I've tested this (experienced this buggy frustration) on multiple robots.
There's no other explanation I can give, no other solution I had found, that made fastrtps behave correctly, regardless of the config file.
Now, to truly behave correctly, I've needed a fastrtps config file on both the robot and the connecting pc, pointing at each other's IP, but that process is documented.
The text was updated successfully, but these errors were encountered:
Thank you a lot for sharing your experience.
We will try to reproduce internally and fix the problem for future releases and add a disclaimer in the docs.
I'm leaving this issue also as a kind of documentation.
The only way I've had success installing H1.x or H2.x on a robot, no matter the xml fastrtps config file, is to first install H0.0, and then install H1.x or H2.x.
I've tested this (experienced this buggy frustration) on multiple robots.
There's no other explanation I can give, no other solution I had found, that made fastrtps behave correctly, regardless of the config file.
Now, to truly behave correctly, I've needed a fastrtps config file on both the robot and the connecting pc, pointing at each other's IP, but that process is documented.
The text was updated successfully, but these errors were encountered: