Here is the Kin's personal edited ros-bridge

ROS/ROS2 bridge for CARLA simulator

This ROS package aims at providing a simple ROS/ROS2 bridge for CARLA simulator.

This version requires CARLA 0.9.11

Features

• Provide Sensor Data (Lidar, Semantic lidar, Cameras (depth, segmentation, rgb, dvs), GNSS, Radar, IMU)
• Provide Object Data (Transforms (via tf), Traffic light status, Visualization markers, Collision, Lane invasion)
• Control AD Agents (Steer/Throttle/Brake)
• Control CARLA (Play/pause simulation, Set simulation parameters)

Additional Functionality

Beside the bridging functionality, there are many more features provided in separate packages.

For a quick overview, after following the Setup section, please run the CARLA AD Demo. It provides a ready-to-use demonstrator of many of the features.

Setup

ROS and ROS2 are supported by using separate implementations with a common interface.

Please follow the instructions:

• ROS
• ROS2

Configuration

Certain parameters can be set within the launch file carla_ros_bridge.launch.

If the rolename is within the list specified by argument ego_vehicle_role_name, it is interpreted as an controllable ego vehicle and all relevant ROS topics are created.

Map

The bridge is able to load a CARLA map by setting the launch-file parameter town. Either specify an available CARLA Town (e.g. 'Town01') or a OpenDRIVE file (with ending '.xodr').

Mode

The bridge operates by default in CARLA synchronous mode, waiting for all sensor data that is expected within the current frame to ensure reproducible results. The bridge should only be used in this mode.

CAUTION: In synchronous mode, only one CARLA client is allowed to tick. The ROS bridge will by default be the only client allowed to tick the CARLA server unless passive mode is enabled. Enabling passive mode will make the ROS bridge step back and allow another client to tick the CARLA server.

Additionally you might set synchronous_mode_wait_for_vehicle_control_command to true to wait for a vehicle control command before executing the next tick.

The usage of the asynchronous mode is discouraged. Users may enable this mode running the bridge in the following way:

# ROS1
roslaunch carla_ros_bridge carla_ros_bridge.launch synchronous_mode:=False

# ROS2
ros2 launch carla_ros_bridge carla_ros_bridge.launch.py synchronous_mode:=False

Control Synchronous Mode

It is possible to control the simulation execution:

• Pause/Play
• Execute single step

The following topic allows to control the stepping.

A CARLA Control rqt plugin is available to publish to the topic.

Available ROS Topics

Sensors

Sensor data is provided via topic with prefix /carla/[<PARENTS ROLE NAME>]/<SENSOR ROLE NAME>/[<TOPIC NAME>]

The following sensors are available:

CARLA sensors

RGB camera

Depth camera

Semantic segmentation camera

DVS camera

Lidar

Semantic lidar

Radar

IMU

GNSS

Collision Sensor

Lane Invasion Sensor

Pseudo sensors

TF Sensor

The tf data for the ego vehicle is published when this pseudo sensor is spawned.

Note: Sensors publish the tf data when the measurement is done. The child_frame_id corresponds with the prefix of the sensor topics.

Odometry Sensor

Speedometer Sensor

Map Sensor

Object Sensor

Marker Sensor

Traffic Lights Sensor

Actor List Sensor

Actor Control Sensor

This pseudo-sensor allows to control the position and velocity of the actor it is attached to (e.g. an ego_vehicle) by publishing pose and velocity within Pose and Twist datatypes. CAUTION: This control method does not respect the vehicle constraints. It allows movements impossible in the real world, like flying or rotating. Currently this sensor applies the complete linear vector, but only the yaw from angular vector.

Ego Vehicle

Control

There are two modes to control the vehicle.

1. Normal Mode (reading commands from /carla/<ROLE NAME>/vehicle_control_cmd)
2. Manual Mode (reading commands from /carla/<ROLE NAME>/vehicle_control_cmd_manual)

This allows to manually override a Vehicle Control Commands published by a software stack. You can toggle between the two modes by publishing to /carla/<ROLE NAME>/vehicle_control_manual_override.

carla_manual_control makes use of this feature.

For testing purposes, you can stear the ego vehicle from the commandline by publishing to the topic /carla/<ROLE NAME>/vehicle_control_cmd.

Examples for a ego vehicle with role_name 'ego_vehicle':

Max forward throttle:

# for ros1
 rostopic pub /carla/ego_vehicle/vehicle_control_cmd carla_msgs/CarlaEgoVehicleControl "{throttle: 1.0, steer: 0.0}" -r 10
# for ros2
 ros2 topic pub /carla/ego_vehicle/vehicle_control_cmd carla_msgs/CarlaEgoVehicleControl "{throttle: 1.0, steer: 0.0}" -r 10

Max forward throttle with max steering to the right:

# for ros1
 rostopic pub /carla/ego_vehicle/vehicle_control_cmd carla_msgs/CarlaEgoVehicleControl "{throttle: 1.0, steer: 1.0}" -r 10
# for ros2
 ros2 topic pub /carla/ego_vehicle/vehicle_control_cmd carla_msgs/CarlaEgoVehicleControl "{throttle: 1.0, steer: 1.0}" -r 10

The current status of the vehicle can be received via topic /carla/<ROLE NAME>/vehicle_status. Static information about the vehicle can be received via /carla/<ROLE NAME>/vehicle_info

Carla Ackermann Control

In certain cases, the Carla Control Command is not ideal to connect to an AD stack. Therefore a ROS-based node carla_ackermann_control is provided which reads AckermannDrive messages. You can find further documentation here.

Other topics

Status of CARLA

Walker

Debug Marker

It is possible to draw markers in CARLA.

Caution: Markers might affect the data published by sensors.

The following markers are supported in 'map'-frame:

• Arrow (specified by two points)
• Points
• Cube
• Line Strip

Troubleshooting

ImportError: No module named carla

You're missing Carla Python. Please execute:

export PYTHONPATH=$PYTHONPATH:<path/to/carla/>/PythonAPI/carla/dist/<your_egg_file>

Please note that you have to put in the complete path to the egg-file including the egg-file itself. Please use the one, that is supported by your Python version. Depending on the type of CARLA (pre-build, or build from source), the egg files are typically located either directly in the PythonAPI folder or in PythonAPI/dist.

Check the installation is successfull by trying to import carla from python:

python -c 'import carla;print("Success")'

You should see the Success message without any errors.