Nav2 Real Robot Error while launching rosbridge

Hi,

I just connected to the real robot for ROS2 Navigation course. However, I could not do anything. I tried to launch the rosbridge and it crashed. The commands that I launched are the ones given in the jupyter notebook.

I got the following prompts when running rosbridge:

[ WARN] [1706914111.614511859]: Shutdown request received.
Trying to create bidirectional bridge for topic 'tf' with ROS 2 type 'tf2_msgs/msg/TFMessage'
[INFO] [1706914111.715317552] [ros_bridge]: create bidirectional bridge for topic tf
[ WARN] [1706914111.768123106]: Reason given for shutdown: [[/ros_bridge] Reason: new node registered with same name]
Trying to create bidirectional bridge for topic 'tf_static' with ROS 2 type 'tf2_msgs/msg/TFMessage'
[INFO] [1706914112.037918078] [ros_bridge]: create bidirectional bridge for topic tf_static
Trying to create bidirectional bridge for topic 'scan' with ROS 2 type 'sensor_msgs/msg/LaserScan'
[INFO] [1706914112.039210875] [ros_bridge]: create bidirectional bridge for topic scan
Trying to create bidirectional bridge for topic 'odom' with ROS 2 type 'nav_msgs/msg/Odometry'
[INFO] [1706914112.042078928] [ros_bridge]: create bidirectional bridge for topic odom
Trying to create bidirectional bridge for topic 'clock' with ROS 2 type 'rosgraph_msgs/msg/Clock'
[INFO] [1706914112.044173077] [ros_bridge]: create bidirectional bridge for topic clock
Trying to create bidirectional bridge for topic 'robot/cmd_vel' with ROS 2 type 'geometry_msgs/msg/Twist'
[INFO] [1706914112.045911897] [ros_bridge]: create bidirectional bridge for topic robot/cmd_vel
Trying to create bidirectional bridge for topic 'cmd_vel' with ROS 2 type 'geometry_msgs/msg/Twist'
[INFO] [1706914112.047591148] [ros_bridge]: create bidirectional bridge for topic cmd_vel
Trying to create bidirectional bridge for topic 'elevator_up' with ROS 2 type 'std_msgs/msg/String'
[INFO] [1706914112.048452762] [ros_bridge]: create bidirectional bridge for topic elevator_up
Trying to create bidirectional bridge for topic 'elevator_down' with ROS 2 type 'std_msgs/msg/String'
[INFO] [1706914112.050213411] [ros_bridge]: create bidirectional bridge for topic elevator_down
The parameter 'services_1_to_2' either doesn't exist or isn't an array
The parameter 'services_2_to_1' either doesn't exist or isn't an array
 WARN] [1706914188.379797732]: Shutdown request received.
[ WARN] [1706914188.494021892]: Reason given for shutdown: [[/ros_bridge] Reason: new node registered with samename]
created 2to1 bridge for topic '/clock' with ROS 2 type 'rosgraph_msgs/msg/Clock' and ROS 1 type 'rosgraph_msgs/Clock'
created 2to1 bridge for topic '/cmd_vel' with ROS 2 type 'geometry_msgs/msg/Twist' and ROS 1 type 'geometry_msgs/Twist'
created 2to1 bridge for topic '/elevator_down' with ROS 2 type 'std_msgs/msg/String' and ROS 1 type 'std_msgs/String'
created 2to1 bridge for topic '/elevator_up' with ROS 2 type 'std_msgs/msg/String' and ROS 1 type 'std_msgs/String'
created 2to1 bridge for topic '/odom' with ROS 2 type 'nav_msgs/msg/Odometry' and ROS 1 type 'nav_msgs/Odometry'
created 2to1 bridge for topic '/robot/cmd_vel' with ROS 2 type 'geometry_msgs/msg/Twist' and ROS 1 type 'geometry_msgs/Twist'
created 2to1 bridge for topic '/rosout' with ROS 2 type 'rcl_interfaces/msg/Log' and ROS 1 type 'rosgraph_msgs/Log'
created 2to1 bridge for topic '/scan' with ROS 2 type 'sensor_msgs/msg/LaserScan' and ROS 1 type 'sensor_msgs/LaserScan'
created 2to1 bridge for topic '/tf' with ROS 2 type 'tf2_msgs/msg/TFMessage' and ROS 1 type 'tf2_msgs/TFMessage'
created 2to1 bridge for topic '/tf_static' with ROS 2 type 'tf2_msgs/msg/TFMessage' and ROS 1 type 'tf2_msgs/TFMessage'
created 1to2 bridge for topic '/battery_state' with ROS 1 type 'sensor_msgs/BatteryState' and ROS 2 type 'sensor_msgs/msg/BatteryState'
created 1to2 bridge for topic '/client_count' with ROS 1 type 'std_msgs/Int32' and ROS 2 type 'std_msgs/msg/Int32'
created 1to2 bridge for topic '/cmd_vel_rc100' with ROS 1 type 'geometry_msgs/Twist' and ROS 2 type 'geometry_msgs/msg/Twist'
created 1to2 bridge for topic '/diagnostics' with ROS 1 type 'diagnostic_msgs/DiagnosticArray' and ROS 2 type 'diagnostic_msgs/msg/DiagnosticArray'
created 1to2 bridge for topic '/imu' with ROS 1 type 'sensor_msgs/Imu' and ROS 2 type 'sensor_msgs/msg/Imu'
created 1to2 bridge for topic '/joint_states' with ROS 1 type 'sensor_msgs/JointState' and ROS 2 type 'sensor_msgs/msg/JointState'
created 1to2 bridge for topic '/magnetic_field' with ROS 1 type 'sensor_msgs/MagneticField' and ROS 2 type 'sensor_msgs/msg/MagneticField'
created 1to2 bridge for topic '/odom' with ROS 1 type 'nav_msgs/Odometry' and ROS 2 type 'nav_msgs/msg/Odometry'
created 1to2 bridge for topic '/rosout' with ROS 1 type 'rosgraph_msgs/Log' and ROS 2 type 'rcl_interfaces/msg/Log'
created 1to2 bridge for topic '/rosout_agg' with ROS 1 type 'rosgraph_msgs/Log' and ROS 2 type 'rcl_interfaces/msg/Log'
created 1to2 bridge for topic '/scan' with ROS 1 type 'sensor_msgs/LaserScan' and ROS 2 type 'sensor_msgs/msg/LaserScan'
created 1to2 bridge for topic '/tf' with ROS 1 type 'tf2_msgs/TFMessage' and ROS 2 type 'tf2_msgs/msg/TFMessage'
created 1to2 bridge for topic '/tf_static' with ROS 1 type 'tf2_msgs/TFMessage' and ROS 2 type 'tf2_msgs/msg/TFMessage'
replace 2to1 bridge for topic '/cmd_vel'
created 2to1 bridge for topic '/cmd_vel' with ROS 2 type 'geometry_msgs/msg/Twist' and ROS 1 type ''
Created 2 to 1 bridge for service /start_motor
Created 2 to 1 bridge for service /stop_motor

I would appreciate if you give me feedback on what could be the reason for this, I have just spend 50 min of real robot session without testing my main code.

Kind regards,

Ronaldo

Hi @w.ronaldo.cd, you actually don’t need the ros1_bridge anymore when using the real robot. It will already offer the ROS 2 topics you need for the project.

To get the updated rosject instructions you would need to re-fork the original project rosject (it just removes the ros1_bridge launch).

Hi @roalgoal, thanks for your answer.

Kind regards,

Ronaldo

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