ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
1 | initial version |
For anyone else trying to find the answer to this in the future: it doesn't appear to be possible, but there's a workaround.
The ROS_LOG_THROTTLE macro statically defines last_hit
, so there's only one timer per invocation of that line (regardless of whether you try a ROS_*_THROTTLE_NAMED
call as well).
My suggestion would be to manually throttle it using ROS_*_COND
instead. It's unsatisfactory, but it seems to be the best solution.