Autoware with a simulated car¶
Lagrange’s sample sedan can be driven by Autoware the way a real car is:
through a vehicle interface that takes Autoware’s control commands and reports the car’s state
back. This page covers that interface (lagrange_autoware), how to build it on Lyrical, and
what to do while Autoware itself is not released for Lyrical.
What the interface does¶
lagrange_autoware_interface sits between Autoware and lagrange_server, where a real car’s
drive-by-wire gateway would be:
Autoware topic |
Type |
Direction |
In the simulator |
|---|---|---|---|
|
|
in |
|
|
|
in |
park and neutral stop the car, reverse backs it up |
|
|
in |
echoed as their reports (the car has no lamps yet) |
|
service |
in |
AUTONOMOUS (the start) forwards the commands; MANUAL stops forwarding them, and the car stops after 0.5 s |
|
|
out |
|
|
|
out |
the two steer joints of |
|
|
out |
the gear and mode as last commanded |
|
|
out |
ground truth in the |
The server takes /ackermann_cmd (ackermann_msgs/AckermannDriveStamped) for any road vehicle
(VehicleAPI_1), beside /cmd_vel: its car controller then steers to the commanded angle and
holds the commanded speed with the throttle and brakes.
The topic names follow Autoware’s vehicle interface
design
and the messages are autoware_msgs 1.11.0.
Building it¶
autoware_control_msgs is released for Lyrical (ros-lyrical-autoware-control-msgs), but
autoware_vehicle_msgs is not (as of 2026-10-25). Without both, colcon build skips
lagrange_autoware with a status message and everything else builds as usual. To build it,
put the messages in an underlay workspace:
mkdir -p ~/autoware_msgs_ws/src && cd ~/autoware_msgs_ws/src
git clone --depth 1 --branch 1.11.0 https://github.com/autowarefoundation/autoware_msgs.git
cd .. && source /opt/ros/lyrical/setup.bash
colcon build --packages-up-to autoware_control_msgs autoware_vehicle_msgs
then build Lagrange on top of it with the dependencies switched on:
source ~/autoware_msgs_ws/install/setup.bash
export LAGRANGE_AUTOWARE=on # package.xml asks for the Autoware messages only with this
colcon build --symlink-install --packages-up-to lagrange_autoware
Running it¶
ros2 launch lagrange_autoware sedan_autoware.launch.py [viewer:=true] [kinematic_state:=false]
starts the server with the sedan in the city block (no demo drive, ROS time on /clock, the
lidar, IMU and front camera renamed into /sensing/...: see SENSOR_REMAPS in the launch file,
and check them against your sensor kit) and the interface. Start Autoware separately with its
own vehicle and sensor-kit descriptions (wheelbase 2.7 m, track 1.56 m, wheel radius 0.316 m,
maximum steering 0.6 rad at the inner wheel for the sample) and use_sim_time:=true.
While Autoware is not on Lyrical¶
Autoware’s own packages are not released for Lyrical yet. Until they are:
Stand-in (what Lagrange tests):
test_autoware_interfacedrives the interface from a stand-in node that publishes what Autoware’s control and the simulator publish, and checks the Ackermann command, the reports and the control-mode service. By hand, the same stand-in publishing a steering angle of 0.1 rad at 4 m/s made the sedan hold 3.99 m/s at a yaw rate of 0.148 rad/s, the bicycle model’s v·tan δ / L.Autoware in its own container on the distribution it is released for, talking to the simulator over DDS on the same domain. The message definitions are the same
autoware_msgsrelease on both sides; whether type hashes match across ROS distributions is TODO(verify) for the Autoware release you use.Without Autoware, any Ackermann stack can publish
/ackermann_cmddirectly.