Hi,
I currently use mavros with ros2 and SITL ardupilot.
the problem is that when I change the parameters values in apm_config.yaml file, there is no any effect and all mavros parameters set to default values, I have confirmed by (ros2 parm get..) command.
I actually solved the problem but I don't know why :).
After some digging into mavros code and the ros2 documentation, the problem was about namespacing in apm_config.yaml file so I edited the file to be as below:
old syntax:
/mavros/**/sys:
ros__parameters:
min_voltage: [10.0]
disable_diag: false
new syntax:
/mavros/sys:
ros__parameters:
min_voltage: [10.0]
disable_diag: false
that is mean the problem was the in the namespace. Beer in mind that if I use the / as a namespace to set the parameters to any node under any namespace, it works fine .
I think this doesn't make sense but it worked and I wnat to know... why???
MAVROS version and platform
Mavros: 2.6.0
ROS: Foxy
OS: Ubuntu 20.04.6
However, I believe that this issue is not specific to a particular version of ROS 2. This implies that the same issue is likely to occur in other ROS2 versions as well.
Issue details
Hi, I currently use mavros with ros2 and SITL ardupilot. the problem is that when I change the parameters values in apm_config.yaml file, there is no any effect and all mavros parameters set to default values, I have confirmed by (ros2 parm get..) command. I actually solved the problem but I don't know why :). After some digging into mavros code and the ros2 documentation, the problem was about namespacing in apm_config.yaml file so I edited the file to be as below:
old syntax: /mavros/**/sys: ros__parameters: min_voltage: [10.0] disable_diag: false
new syntax: /mavros/sys: ros__parameters: min_voltage: [10.0]
disable_diag: false that is mean the problem was the in the namespace. Beer in mind that if I use the / as a namespace to set the parameters to any node under any namespace, it works fine . I think this doesn't make sense but it worked and I wnat to know... why???
MAVROS version and platform
Mavros: 2.6.0 ROS: Foxy OS: Ubuntu 20.04.6 However, I believe that this issue is not specific to a particular version of ROS 2. This implies that the same issue is likely to occur in other ROS2 versions as well.