turtlebot3_bringup stuck at 'Connecting to /dev/ttyACM0 at 115200 baud' but only at ssh

asked 2023-03-09 06:02:57 -0500

madangt gravatar image

I am using Ubuntu 20.04 and ROS Noetic.

I am using the command for turtlebot3_bringup. The output is-

... logging to /home/pi/.ros/log/27662570-be5c-11ed-bfc1-89917e16b466/roslaunch-raspberrymadan-1546.log
Checking log directory for disk usage. This may take a while.
Press Ctrl-C to interrupt
Done checking log file disk usage. Usage is <1GB.

started roslaunch server http://192.168.0.101:37371/

SUMMARY
========

PARAMETERS
 * /rosdistro: noetic
 * /rosversion: 1.15.14
 * /turtlebot3_core/baud: 115200
 * /turtlebot3_core/port: /dev/ttyACM0
 * /turtlebot3_core/tf_prefix: 
 * /turtlebot3_lds/frame_id: base_scan
 * /turtlebot3_lds/port: /dev/ttyUSB0

NODES
  /
    turtlebot3_core (rosserial_python/serial_node.py)
    turtlebot3_diagnostics (turtlebot3_bringup/turtlebot3_diagnostics)
    turtlebot3_lds (hls_lfcd_lds_driver/hlds_laser_publisher)

ROS_MASTER_URI=http://192.168.0.123:11311

process[turtlebot3_core-1]: started with pid [1556]
process[turtlebot3_lds-2]: started with pid [1557]
process[turtlebot3_diagnostics-3]: started with pid [1558]
[INFO] [1678360409.825686, 0.000000]: ROS Serial Python Node
[INFO] [1678360409.884584, 0.000000]: Connecting to /dev/ttyACM0 at 115200 baud

Upon searching, the issue was stated as that there is low power because of which OpenCR is not able to function.

Now, I connected directly to turtlebot3 raspberry and initiated turtlebot3_bringup from its board, and it worked despite having the same battery. I went back again, trying to connect the robot via ssh and gave the bringup command again, and it got stuck again.

I don't know why turtlebot3_bringup gets stuck only when I connect through ssh. My internet connection is okay and has 18mbps speed.

Please help.

edit retag flag offensive close merge delete