As far as I can tell, the only way to command the base controller is a Twist message. Since the message contains no timestamp, there is no way to prevent delays in command messages from being detected.
I would love to be able to specify the time at which the command I am sending to the base controller becomes invalid. This would be easier to use and more flexible than the current parameter for the controller, and would be robust to delayed delivery of the command message.
It seems like it would be easy to add this feature without breaking backward compatibility by adding an alternate command topic.
Let me know if I'm missing something and there is a safe way of doing this.
As far as I can tell, the only way to command the base controller is a Twist message. Since the message contains no timestamp, there is no way to prevent delays in command messages from being detected.
I would love to be able to specify the time at which the command I am sending to the base controller becomes invalid. This would be easier to use and more flexible than the current parameter for the controller, and would be robust to delayed delivery of the command message.
It seems like it would be easy to add this feature without breaking backward compatibility by adding an alternate command topic.
Let me know if I'm missing something and there is a safe way of doing this.
trac data: