Real Robot Lab - Turtlebot3 not moving problem

General Support
,
1

Hello,

I am trying to use the Real Robot Lab with TurtleBot3. The web interface shows that I am connected with a latency of around 200ms, but moving the joystick does not make the robot respond. I thought it might be a session issue, so I ended the session and tried again, but it still does not work. When I checked with rosnode list and rosnode info /rosbridge_websocket, only rosbridge-related nodes are running, and there are no TurtleBot3 bringup nodes:

Node [/rosbridge_websocket]
Publications:

  • /client_count [std_msgs/Int32]
  • /cmd_vel [geometry_msgs/Twist]
  • /connected_clients [rosbridge_msgs/ConnectedClients]
  • /rosout [rosgraph_msgs/Log]
    Subscriptions:
  • /odom_status [unknown type]
  • /scan_status [unknown type]
  • /tf_status [unknown type]
    Services:
  • /rosbridge_websocket/get_loggers
  • /rosbridge_websocket/set_logger_level

I would also like to ask a couple of questions:

  • Does the Real Robot Lab operate on weekends (Saturday/Sunday)?
  • I am planning to use the TurtleBot3 during weekday evenings. Is it available at all times on weekdays, regardless of the time?

Thank you very much for your assistance.

2

@daylight1234567
The robot should be working now; please try again.

We are working on intermittent freezes with this robot, which started recently. Kindly bear with us.

The robot is available 24/7.

1 Like
3

Hello,

The issue looks to insist. I have been trying since yesterday to make the robot move (It is connected).
The available topics are:

ros2 topic list
/camera_info
/client_count
/cmd_vel
/connected_clients
/image_raw
/image_raw/compressed
/image_raw/compressedDepth
/image_raw/theora
/imu
/joint_states
/odom
/odom_status
/parameter_events
/rosout
/scan
/scan_status
/tf
/tf_static
/tf_status

but the echo command doesn’t return anything to many of those topics…

Thank you very much for your work. Looking forward to make it move for the first time!

4

I’m sorry about that. Could you please try again? The robot probably froze again.

5

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.