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
That documentation is very old and was created during the ROS 1 Kinetic era. And unfortunately the instructions to Run ros_serial indicate that it is not compatible with ROS 2.
The way to solve this issue is to modify OpenCR's TB3 FW (Turtlebot3 core), but I cannot provide any specific code. Thanks.
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.
ros2 launch turtlebot3_bringup robot.launch.py
ros2 topic echo /sensor_state
IR (cliff) and bumper information is always 0 even tough the sensors are correctly plugged into the OpenCR
After connecting in a correct way the sensors (either IR or bumper) to the OLLO pins of the OpenCR (by following the instructions in https://emanual.robotis.com/docs/en/platform/turtlebot3/additional_sensors/), I launch the turtlebot3 bringup commands and then try to read the output from the sensors in the ros2 topic /sensor_state (respectively the field 'cliff 'and 'bumper'), but the values are always at 0, even if I click the bumper or point the IR to different distances. I uploaded the OpenCR firmware from https://github.com/ROBOTIS-GIT/OpenCR-Binaries/raw/master/turtlebot3/ROS2/latest/opencr_update.tar.bz2 , as explained in section 3.3 of https://emanual.robotis.com/docs/en/platform/turtlebot3/opencr_setup/#opencr-setup (without passing by the Arduino IDE, section 3.4) and the bringup, the lidar, the battery, the encoders, the voltage and all the other sensors work just fine. Do you know to what this problem could be due and how to solve it?
Thank you very much in advance!
The text was updated successfully, but these errors were encountered: