Open mwsatman opened 1 year ago
Hi @mwsatman You can modify opencr source code to operate turtlebot as you want. Below link is opencr source which you should modify
https://github.com/ROBOTIS-GIT/OpenCR/blob/master/arduino/opencr_arduino/opencr/libraries/turtlebot3_ros2/src/turtlebot3/turtlebot3.cpp https://github.com/ROBOTIS-GIT/OpenCR/blob/master/arduino/opencr_arduino/opencr/libraries/turtlebot3_ros2/src/turtlebot3/turtlebot3_controller.cpp
I wish you achieve your purpose.
ISSUE TEMPLATE ver. 0.4.0
Which TurtleBot3 platform do you use?
Which ROS is working with TurtleBot3?
Which SBC(Single Board Computer) is working on TurtleBot3?
Which OS you installed on SBC?
Which OS you installed on Remote PC?
Specify the software and firmware version(Can be found from Bringup messages)
Specify the commands or instructions to reproduce the issue.
Copy and Paste the error messages on terminal.
Please describe the issue in detail.
Hi,
I am using Turtlebot3 Burger for my research project. In the past I have been using the ROS1 Noetic and just recently upgraded my setup to ROS2. For my research I control the robot by creating a controller node and periodically sending vel_cmd every 20ms.
In ROS1 Noetic, if the controller is slow and can not fulfill the 20ms window, the robot typically do a move-stop-move motion. In which I assume when there is no vel_cmd being published the default behavior of the robot is to stop. However, after upgrading to ROS2, the robot seems to maintain the previous vel_cmd when no new vel_cmd is published. For my use-case the ROS1 behavior is preferable.
Is there any way to revert the original behavior in ROS1? If it is, what do I need to do to change it?