Open mhl787156 opened 2 years ago
After some thought, I think this is due to the ROS2 discovery destroying the network such that the parameter server is no longer accessible to the parameter bridge somehow. Therefore it cannot read the specified parameters.
Possible fix right now is to stagger the starts of each node so that each individual discovery broadcast does not bottleneck everything else.
There have been many instances when bringing up the mavros container where the parameter bridge fails to read the parameter bridge configuration file. The logs show often show the following printouts:
This has been observed in both simulation and on the real drones. However re-running the container a few times almost always eventually fixes the issue.
I am unsure as to the cause, but best guess is some race between the configuration file been read in and parsed as a ros param, and the parameter bridge attempting to read the ros2 params. Unsure how to solve.