Open junu5121 opened 3 years ago
Hi @junu5121 Have you set up the USB Port in the SBC section as below?
$ rosrun turtlebot3_bringup create_udev_rules
Once you see the [OK] jump_to_fw
, the firmware is successfully uploaded to OpenCR.
I think there's something wrong with your serial port setting with Linux.
Hi @junu5121 Have you set up the USB Port in the SBC section as below?
$ rosrun turtlebot3_bringup create_udev_rules
Once you see the
[OK] jump_to_fw
, the firmware is successfully uploaded to OpenCR. I think there's something wrong with your serial port setting with Linux.
Thank you for your reply @ROBOTIS-Will Yes, I did. But It didn't work....
@junu5121 Sorry about the delayed response. Have you tried disabling the modem manager?
$ sudo apt-get purge modemmanager
@ROBOTIS-Will I try your method, but still not working.
Same Issue, Is this issue fixed or not?
@Kuo-Feng Please give us more information about your system:
@Kuo-Feng Please give us more information about your system:
- Which OS you installed on SBC?
- Which ROS version are you using?
- Which RPi model do you have?
- Have you tried with a provided SBC image from ROBOTIS eManual?
I installed Ubuntu 20.04 on SBC, from the image that provided on the tutorials. And the ROS version is noetic. The RPi model is the one that Turtlebot 3 burger used.
There will have that message, but I think the firmware is uploaded to OpenCR sucessfully, because I can remote control the burger through teleop_key package.
Not sure that failure will have impact or not. But currently, it works just fine.
Thank you.
@Kuo-Feng If Raspberry Pi fails to access the ttyACM0 port to communicate with OpenCR, it could cause malfunction in operating TurtleBot3. Since you have successfully operated with teleop_key node, it looks fine, but the cause of the problem looks like the modemmanager as described in the RPi forum below. https://raspberrypi.stackexchange.com/questions/102022/bad-serial-connection-on-usb-otg-serial-on-pi-zero Thank you.
Same Issue here on TurtleBot3 Burger ROS2 (FOXY) It says [OK] jump_to_fw, can I proceed, or I will get some problems in the future?
@Lopetex I'm also getting the same error. Did you find a fix? or did you not face any other issues related to this?
Hi @keerthanamanivannan, I'm sorry but I couldn't find a fix, but as far as I know this message might not be crucial to make the robot work. In my experience, I kept encountering problems working with ROS2 and I arrived to one dead point where I couldn't communicate with the robot. The communication system changes between ROS and ROS2 so I tried ROS Noetic instead and worked amazing. Good luck!
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.