ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange

Attention: Answers.ros.org is deprecated as of August the 11th, 2023. Please visit robotics.stackexchange.com to ask a new question. This site will remain online in read-only mode during the transition and into the foreseeable future. Selected questions and answers have been migrated, and redirects have been put in place to direct users to the corresponding questions on Robotics Stack Exchange. Additional details are available here.

Revision history [back]

The only thing the mux does is if a message with a higher priority comes in, it blocks all the messages with lower priority. Once that message has been received, it receives all the other messages again which creates exactly the behaviour you described. Looking at the cmd_vel_mux wiki you can defined a timeout after which the topic is considered inactive. Try increasing that for the safety topic.

ROS Answers is licensed under Creative Commons Attribution 3.0 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.

Powered by Askbot version 0.10.2