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
When invalid trajectory is detected these messages freeze terminal and if it launched from main launch file it might freeze whole robot to the point that even ctrl+c is not responding
Ubuntu 20.04 Noetic
I'm using teleop_twist_keyboard which /cmd_vel topic is mapped to assisted_teleop node. When robot is next to wall single short key press produces ~200-300 WARN messages.
Workaround
Set higher logger level for planner in the same launch file where we launch assited_teleop it solves freezing issue and reduces cpu usage by quite a lot when invalid trajectory is detected <node pkg="rosservice" type="rosservice" name="supress_warn" args="call --wait /assisted_teleop/set_logger_level "{logger: 'ros.base_local_planner', level: 'error'}"" />
The text was updated successfully, but these errors were encountered:
When invalid trajectory is detected these messages freeze terminal and if it launched from main launch file it might freeze whole robot to the point that even ctrl+c is not responding
More info:
Ubuntu 20.04 Noetic
I'm using teleop_twist_keyboard which /cmd_vel topic is mapped to assisted_teleop node. When robot is next to wall single short key press produces ~200-300 WARN messages.
Workaround
Set higher logger level for planner in the same launch file where we launch assited_teleop it solves freezing issue and reduces cpu usage by quite a lot when invalid trajectory is detected
<node pkg="rosservice" type="rosservice" name="supress_warn" args="call --wait /assisted_teleop/set_logger_level "{logger: 'ros.base_local_planner', level: 'error'}"" />
The text was updated successfully, but these errors were encountered: