Custom Vehicle
A vehicle SDF describes its links, geometry, mass, inertia, joints, sensors and installed plugins. Start with the SDF exported from your selected vehicle so its controller and sensor connections match your runtime.
Download, edit and apply
- Select your terrain and vehicle in Workspace → Custom world and open the start review.
- Expand Edit SDF files and select Download vehicle SDF. A built-in profile is saved as a generated vehicle revision before export.
- Edit the numeric settings in a copy of
model.sdf. Keep names, links, plugin identities, resource paths and topic routes. - Choose Upload edited vehicle SDF in the same review. Validation creates and selects a new revision. Your original remains available.
- Start the world and check a stationary test before commanding motion. Editing a saved file does not change an already running world.
Generated SDF uploads retain the structure chosen in the vehicle builder. Use Edit a copy to add or remove sensors, change the control mode or select a provider. Uploading a new native plugin requires an engine installation with that plugin; an SDF does not install software.
Read the model section by section
| SDF section | Meaning and editing guidance |
|---|---|
model / pose |
Model reference position and orientation. The workspace places the vehicle at the selected geographic start. |
link / pose |
Link frame relative to its parent. Translations use metres; roll, pitch and yaw use radians. |
inertial / mass and inertial / pose |
Mass in kg and centre-of-mass frame. Keep them consistent with physical dimensions. |
inertia |
Six independent tensor entries in kg·m². Use CAD or measured mass distribution. Validation rejects non-positive or physically inconsistent inertia. |
visual / geometry |
Display geometry and mesh scale. A larger visual alone does not change collision geometry or mass. |
collision / geometry |
Contact shape. Use a simple closed shape where possible and match the physical hull. |
joint / pose / axis |
Joint location and direction. Keep parent, child and joint names so propulsion and controllers remain connected. |
| Hydrodynamic and buoyancy plugins | Installed model coefficients for displaced water, added mass and drag. Check sign conventions in Marine dynamics & rendering. |
| Thruster and controller plugins | Existing propulsion axes, coefficients and control channels. Check low-speed response after changing geometry. |
sensor and sensor plugins |
Mount, rate, optical/acoustic settings and noise. See Custom Sensors. |
The full files below contain real installed model values, not a universal calibration for a physical vehicle. Numeric and Boolean edits are supported within the template’s structure and validated sensor limits. Start-review uploads are limited to 1 MB. Unsupported changes identify the rejected SDF path; correct that field and upload again.
Complete WAM-V SDF
The examples use Linux engine plugin paths. On macOS or another host, start from that host’s own export and retain the exported ZIP for the matching meshes and resources.
Download WAM-V model.sdf. This example selects forward and downward cameras, DVL and 2D LiDAR, with Autopilot and GNSS. Other supported payloads appear as inactive examples in comments.
wamv.sdf
<?xml version='1.0' encoding='utf-8'?>
<sdf xmlns:gz="http://gazebosim.org" version="1.7">
<!--
Model assembly: links hold rigid bodies, joints connect them, and plugins provide
simulation behavior. Keep model, link and joint names consistent with the exported
controllers.
-->
<model name="wamv">
<!--
Exported vehicle configuration. The active model follows this comment. Select sensors and providers in the vehicle editor so topic routes and world systems stay aligned. Mount limits: position ±10 m; rotation ±2π rad. recipe.json:
{
"control_mode": "autopilot",
"gnss": true,
"schema_version": 1,
"sensors": [
"camera",
"camera_down",
"dvl",
"lidar_2d"
],
"settings": {
"camera": {
"height": 480,
"horizontal_fov": 1.4,
"pose": [
1.5,
0.0,
0.8,
0.0,
0.0,
0.0
],
"update_rate": 5,
"width": 640
},
"camera_down": {
"height": 600,
"horizontal_fov": 1.4,
"pose": [
0.0,
0.0,
-0.5,
0.0,
1.5707963267948966,
0.0
],
"update_rate": 5,
"width": 800
},
"dvl": {
"pose": [
0.0,
0.0,
-0.5,
0.0,
0.0,
0.0
],
"range_max": 20,
"update_rate": 1
},
"lidar_2d": {
"pose": [
0.0,
0.0,
2.5,
0.0,
0.0,
0.0
],
"range_max": 50,
"update_rate": 5
}
},
"vehicle": "wamv"
}
-->
<enable_wind>true</enable_wind>
<!--
Rigid body and its local coordinate frame. Geometry, mass properties and sensors
inside this link move together.
-->
<link name="base_link">
<!--
Visible surface for rendering and cameras. Changing a visual does not automatically
resize the collision shape or change mass.
-->
<visual name="visual">
<geometry>
<!--
Mesh resource and optional axis scale. Keep the exported asset path and bundle
together; scale multiplies the mesh coordinates.
-->
<mesh>
<uri>assets/04f3ad2d4ac28cde0632b52f0ffaf7bb5f09da574a1a0b1402122ff2e1f2fbea.dae</uri>
</mesh>
</geometry>
</visual>
<!--
Contact geometry used by physics. Keep dimensions and placement consistent with the
hull; a simplified shape reduces collision computation.
-->
<collision name="collision">
<geometry>
<!--
Mesh resource and optional axis scale. Keep the exported asset path and bundle
together; scale multiplies the mesh coordinates.
-->
<mesh>
<uri>assets/31b5b6c712bf5c02a523be90f933526bf7a53b6abd84e2e279d8daabec043807.stl</uri>
</mesh>
</geometry>
</collision>
<!--
Mass properties: mass is in kg; pose locates and orients the centre-of-mass frame
relative to the link. Use measured or CAD-derived values.
-->
<inertial>
<!--
Pose: x y z in metres, then roll pitch yaw in radians. Values use the parent frame
unless relative_to specifies another frame.
-->
<pose>0 0 0 0 0 0</pose>
<mass>180</mass>
<!--
Inertia tensor in kg*m^2 at the centre of mass. ixx/iyy/izz are diagonal terms;
ixy/ixz/iyz are cross terms. Keep the tensor physically consistent with mass and
shape.
-->
<inertia>
<ixx>120</ixx>
<ixy>0</ixy>
<iyy>393</iyy>
<iyz>0</iyz>
<izz>446</izz>
</inertia>
</inertial>
<!--
Sensor attached to this link. Its pose sets the mounting position; type selects the
measurement implementation. The builder also prepares topic routes and required world
systems.
-->
<sensor name="payload_camera" type="camera">
<always_on>true</always_on>
<!--
Requested sensor update frequency in Hz. Delivered rate also depends on simulation
speed and rendering load.
-->
<update_rate>5</update_rate>
<!--
Gazebo Transport output topic. Keep it aligned with the exported sensor manifest and
ROS bridge routes.
-->
<topic>/vehicle/sensors/camera</topic>
<!--
Camera: horizontal_fov is in radians; image width/height are pixels. clip near/far are
rendering distances in metres. camera_info_topic publishes calibration data.
-->
<camera>
<horizontal_fov>1.4</horizontal_fov>
<image>
<width>640</width>
<height>480</height>
</image>
<clip>
<near>.1</near>
<far>100</far>
</clip>
<camera_info_topic>/vehicle/sensors/camera/camera_info</camera_info_topic>
</camera>
<!--
Pose: x y z in metres, then roll pitch yaw in radians. Values use the parent frame
unless relative_to specifies another frame.
-->
<pose>1.5 0.0 0.8 0.0 0.0 0.0</pose>
<frame_id>vehicle/camera</frame_id>
</sensor>
<!--
Sensor attached to this link. Its pose sets the mounting position; type selects the
measurement implementation. The builder also prepares topic routes and required world
systems.
-->
<sensor name="payload_camera_down" type="camera">
<always_on>true</always_on>
<!--
Requested sensor update frequency in Hz. Delivered rate also depends on simulation
speed and rendering load.
-->
<update_rate>5</update_rate>
<!--
Gazebo Transport output topic. Keep it aligned with the exported sensor manifest and
ROS bridge routes.
-->
<topic>/vehicle/sensors/camera_down</topic>
<!--
Camera: horizontal_fov is in radians; image width/height are pixels. clip near/far are
rendering distances in metres. camera_info_topic publishes calibration data.
-->
<camera>
<horizontal_fov>1.4</horizontal_fov>
<image>
<width>800</width>
<height>600</height>
</image>
<clip>
<near>.1</near>
<far>100</far>
</clip>
<camera_info_topic>/vehicle/sensors/camera_down/camera_info</camera_info_topic>
</camera>
<!--
Pose: x y z in metres, then roll pitch yaw in radians. Values use the parent frame
unless relative_to specifies another frame.
-->
<pose>0.0 0.0 -0.5 0.0 1.5707963267948966 0.0</pose>
<frame_id>vehicle/camera_down</frame_id>
</sensor>
<!--
Sensor attached to this link. Its pose sets the mounting position; type selects the
measurement implementation. The builder also prepares topic routes and required world
systems.
-->
<sensor name="payload_dvl" type="custom" gz:type="dvl">
<!--
Pose: x y z in metres, then roll pitch yaw in radians. Values use the parent frame
unless relative_to specifies another frame.
-->
<pose>0.0 0.0 -0.5 0.0 0.0 0.0</pose>
<always_on>true</always_on>
<!--
Requested sensor update frequency in Hz. Delivered rate also depends on simulation
speed and rendering load.
-->
<update_rate>1</update_rate>
<!--
Gazebo Transport output topic. Keep it aligned with the exported sensor manifest and
ROS bridge routes.
-->
<topic>/vehicle/sensors/dvl</topic>
<!--
DVL beam geometry and bottom tracking. arrangement declares its angular unit; range
and resolution use metres. The world needs DopplerVelocityLogSystem, and the ROS
adapter publishes velocity and status.
-->
<gz:dvl>
<type>phased_array</type>
<arrangement degrees="true">
<beam id="1">
<aperture>2</aperture>
<rotation>45</rotation>
<tilt>30</tilt>
</beam>
<beam id="2">
<aperture>2</aperture>
<rotation>135</rotation>
<tilt>30</tilt>
</beam>
<beam id="3">
<aperture>2</aperture>
<rotation>-45</rotation>
<tilt>30</tilt>
</beam>
<beam id="4">
<aperture>2</aperture>
<rotation>-135</rotation>
<tilt>30</tilt>
</beam>
</arrangement>
<tracking>
<bottom_mode>
<when>best</when>
<!--
Measurement noise. For Gaussian noise, mean and stddev use the units of the measured
quantity; stddev controls the random spread.
-->
<noise type="gaussian">
<stddev>0.002</stddev>
</noise>
<visualize>false</visualize>
</bottom_mode>
</tracking>
<resolution>0.01</resolution>
<maximum_range>20</maximum_range>
<minimum_range>0.1</minimum_range>
<reference_frame>0 0 0 0 0 0</reference_frame>
</gz:dvl>
<frame_id>vehicle/dvl</frame_id>
</sensor>
<!--
Sensor attached to this link. Its pose sets the mounting position; type selects the
measurement implementation. The builder also prepares topic routes and required world
systems.
-->
<sensor name="payload_lidar_2d" type="gpu_lidar">
<always_on>true</always_on>
<!--
Requested sensor update frequency in Hz. Delivered rate also depends on simulation
speed and rendering load.
-->
<update_rate>5</update_rate>
<!--
Gazebo Transport output topic. Keep it aligned with the exported sensor manifest and
ROS bridge routes.
-->
<topic>/vehicle/sensors/lidar_2d</topic>
<!--
Ray-based range sensor. scan sets horizontal/vertical samples and angles in radians;
range sets minimum/maximum distance and resolution in metres. Single Ping uses this
GPU ray implementation.
-->
<lidar>
<scan>
<horizontal>
<samples>360</samples>
<resolution>1</resolution>
<min_angle>-3.141592653589793</min_angle>
<max_angle>3.141592653589793</max_angle>
</horizontal>
</scan>
<range>
<min>0.1</min>
<max>50</max>
<resolution>0.01</resolution>
</range>
</lidar>
<!--
Pose: x y z in metres, then roll pitch yaw in radians. Values use the parent frame
unless relative_to specifies another frame.
-->
<pose>0.0 0.0 2.5 0.0 0.0 0.0</pose>
<frame_id>vehicle/lidar_2d</frame_id>
</sensor>
<!--
Optional sensor camera: inactive default example. Active payload_* elements elsewhere in the model define the selected sensors. Use the vehicle editor to change the selection and keep this example inside its comment. Editable limits and output routes:
update_rate: 0.1 … 30 Hz
width: 64 … 1920 px
height: 64 … 1920 px
horizontal_fov: 0.1 … 3 rad
width * height * update_rate <= 30000000 px/s
Gazebo: /vehicle/sensors/camera
frame_id: vehicle/camera
ROS: /vehicle/sensors/camera (sensor_msgs/msg/Image)
ROS: /vehicle/sensors/camera/camera_info (sensor_msgs/msg/CameraInfo)
<sensor name="payload_camera" type="camera">
<always_on>true</always_on>
<update_rate>5</update_rate>
<topic>/vehicle/sensors/camera</topic>
<camera>
<horizontal_fov>1.4</horizontal_fov>
<image>
<width>640</width>
<height>480</height>
</image>
<clip>
<near>.1</near>
<far>100</far>
</clip>
<camera_info_topic>/vehicle/sensors/camera/camera_info</camera_info_topic>
</camera>
<pose>1.5 0.0 0.8 0.0 0.0 0.0</pose>
<frame_id>vehicle/camera</frame_id>
</sensor>
-->
<!--
Optional sensor camera_down: inactive default example. Active payload_* elements elsewhere in the model define the selected sensors. Use the vehicle editor to change the selection and keep this example inside its comment. Editable limits and output routes:
update_rate: 0.1 … 30 Hz
width: 64 … 1920 px
height: 64 … 1920 px
horizontal_fov: 0.1 … 3 rad
width * height * update_rate <= 30000000 px/s
Gazebo: /vehicle/sensors/camera_down
frame_id: vehicle/camera_down
ROS: /vehicle/sensors/camera_down (sensor_msgs/msg/Image)
ROS: /vehicle/sensors/camera_down/camera_info (sensor_msgs/msg/CameraInfo)
<sensor name="payload_camera_down" type="camera">
<always_on>true</always_on>
<update_rate>5</update_rate>
<topic>/vehicle/sensors/camera_down</topic>
<camera>
<horizontal_fov>1.4</horizontal_fov>
<image>
<width>800</width>
<height>600</height>
</image>
<clip>
<near>.1</near>
<far>100</far>
</clip>
<camera_info_topic>/vehicle/sensors/camera_down/camera_info</camera_info_topic>
</camera>
<pose>0.0 0.0 -0.5 0.0 1.5707963267948966 0.0</pose>
<frame_id>vehicle/camera_down</frame_id>
</sensor>
-->
<!--
Optional sensor ping_down: inactive default example. Active payload_* elements elsewhere in the model define the selected sensors. Use the vehicle editor to change the selection and keep this example inside its comment. Editable limits and output routes:
update_rate: 0.1 … 30 Hz
range_max: 1 … 100 m
Gazebo: /vehicle/sensors/ping_down
frame_id: vehicle/ping_down
ROS: /vehicle/sensors/ping_down (sensor_msgs/msg/LaserScan)
ROS: /vehicle/sensors/ping_down/range (sensor_msgs/msg/Range)
runtime: practice_ping.py
Choose either DVL or single Ping; they cannot be enabled together.
<sensor name="payload_ping_down" type="gpu_lidar">
<always_on>true</always_on>
<update_rate>5</update_rate>
<topic>/vehicle/sensors/ping_down</topic>
<lidar>
<scan>
<horizontal>
<samples>5</samples>
<resolution>1</resolution>
<min_angle>-0.00872665</min_angle>
<max_angle>0.00872665</max_angle>
</horizontal>
<vertical>
<samples>5</samples>
<resolution>1</resolution>
<min_angle>-0.00872665</min_angle>
<max_angle>0.00872665</max_angle>
</vertical>
</scan>
<range>
<min>0.1</min>
<max>30</max>
<resolution>0.01</resolution>
</range>
</lidar>
<pose>0.0 0.0 -0.5 0.0 1.5707963267948966 0.0</pose>
<frame_id>vehicle/ping_down</frame_id>
</sensor>
-->
<!--
Optional sensor multibeam_forward: inactive default example. Active payload_* elements elsewhere in the model define the selected sensors. Use the vehicle editor to change the selection and keep this example inside its comment. Editable limits and output routes:
update_rate: 0.1 … 30 Hz
Gazebo: /vehicle/sensors/multibeam_forward
frame_id: vehicle/multibeam_forward
ROS: /vehicle/sensors/multibeam_forward/sonar_image_raw (marine_acoustic_msgs/msg/ProjectedSonarImage)
Requires a compatible POSIM acoustic sonar provider and its world system. This example remains a reference when the provider is unavailable. Ray and acoustic fields are provider defaults; the builder exposes update rate and pose.
<sensor xmlns:gz="http://gazebosim.org" name="payload_multibeam_forward" type="custom" gz:type="multibeam_sonar">
<always_on>true</always_on>
<update_rate>2</update_rate>
<topic>/vehicle/sensors/multibeam_forward</topic>
<visualize>true</visualize>
<gz:multibeam_sonar>
<ray degrees="false">
<scan>
<horizontal>
<beams>256</beams>
<min_angle>-1.0471975511965976</min_angle>
<max_angle>1.0471975511965976</max_angle>
</horizontal>
<vertical>
<rays>256</rays>
<min_angle>-0.17453292519943295</min_angle>
<max_angle>0.17453292519943295</max_angle>
</vertical>
</scan>
<range>
<min>0.2</min>
<max>15</max>
</range>
</ray>
<spec>
<verticalFOV>20</verticalFOV>
<sonarFreq>700e3</sonarFreq>
<bandwidth>29.9e3</bandwidth>
<soundSpeed>1500</soundSpeed>
<sourceLevel>220</sourceLevel>
<maxDistance>15</maxDistance>
<raySkips>1</raySkips>
<sensorGain>0.02</sensorGain>
<writeLog>false</writeLog>
<debugFlag>false</debugFlag>
<writeFrameInterval>5</writeFrameInterval>
<pointCloudTopicName>geometry/points</pointCloudTopicName>
<sonarImageRawTopicName>sonar_image_raw</sonarImageRawTopicName>
<sonarImageTopicName>sonar_image</sonarImageTopicName>
<frameName>vehicle/multibeam_forward</frameName>
<visibilityMask>3892314111</visibilityMask>
</spec>
</gz:multibeam_sonar>
<pose>1.5 0.0 -0.5 0.0 0.35 0.0</pose>
<frame_id>vehicle/multibeam_forward</frame_id>
</sensor>
-->
<!--
Optional sensor dvl: inactive default example. Active payload_* elements elsewhere in the model define the selected sensors. Use the vehicle editor to change the selection and keep this example inside its comment. Editable limits and output routes:
update_rate: 0.1 … 30 Hz
range_max: 1 … 100 m
Gazebo: /vehicle/sensors/dvl
frame_id: vehicle/dvl
ROS: /vehicle/sensors/dvl/velocity (geometry_msgs/msg/Vector3Stamped)
ROS: /vehicle/sensors/dvl/status (std_msgs/msg/String)
runtime: practice_dvl_bridge.py
Choose either DVL or single Ping; they cannot be enabled together.
<sensor xmlns:gz="http://gazebosim.org" name="payload_dvl" type="custom" gz:type="dvl">
<pose>0.0 0.0 -0.5 0.0 0.0 0.0</pose>
<always_on>true</always_on>
<update_rate>1</update_rate>
<topic>/vehicle/sensors/dvl</topic>
<gz:dvl>
<type>phased_array</type>
<arrangement degrees="true">
<beam id="1">
<aperture>2</aperture>
<rotation>45</rotation>
<tilt>30</tilt>
</beam>
<beam id="2">
<aperture>2</aperture>
<rotation>135</rotation>
<tilt>30</tilt>
</beam>
<beam id="3">
<aperture>2</aperture>
<rotation>-45</rotation>
<tilt>30</tilt>
</beam>
<beam id="4">
<aperture>2</aperture>
<rotation>-135</rotation>
<tilt>30</tilt>
</beam>
</arrangement>
<tracking>
<bottom_mode>
<when>best</when>
<noise type="gaussian">
<stddev>0.002</stddev>
</noise>
<visualize>false</visualize>
</bottom_mode>
</tracking>
<resolution>0.01</resolution>
<maximum_range>20</maximum_range>
<minimum_range>0.1</minimum_range>
<reference_frame>0 0 0 0 0 0</reference_frame>
</gz:dvl>
<frame_id>vehicle/dvl</frame_id>
</sensor>
-->
<!--
Optional sensor lidar_2d: inactive default example. Active payload_* elements elsewhere in the model define the selected sensors. Use the vehicle editor to change the selection and keep this example inside its comment. Editable limits and output routes:
update_rate: 0.1 … 30 Hz
range_max: 1 … 100 m
Gazebo: /vehicle/sensors/lidar_2d
frame_id: vehicle/lidar_2d
ROS: /vehicle/sensors/lidar_2d (sensor_msgs/msg/LaserScan)
<sensor name="payload_lidar_2d" type="gpu_lidar">
<always_on>true</always_on>
<update_rate>5</update_rate>
<topic>/vehicle/sensors/lidar_2d</topic>
<lidar>
<scan>
<horizontal>
<samples>360</samples>
<resolution>1</resolution>
<min_angle>-3.141592653589793</min_angle>
<max_angle>3.141592653589793</max_angle>
</horizontal>
</scan>
<range>
<min>0.1</min>
<max>50</max>
<resolution>0.01</resolution>
</range>
</lidar>
<pose>0.0 0.0 2.5 0.0 0.0 0.0</pose>
<frame_id>vehicle/lidar_2d</frame_id>
</sensor>
-->
</link>
<!--
Rigid body and its local coordinate frame. Geometry, mass properties and sensors
inside this link move together.
-->
<link name="left_engine_link">
<!--
Pose: x y z in metres, then roll pitch yaw in radians. Values use the parent frame
unless relative_to specifies another frame.
-->
<pose>-2.373776 1.027135 0.318237 0 0 0</pose>
<!--
Visible surface for rendering and cameras. Changing a visual does not automatically
resize the collision shape or change mass.
-->
<visual name="visual">
<geometry>
<!--
Mesh resource and optional axis scale. Keep the exported asset path and bundle
together; scale multiplies the mesh coordinates.
-->
<mesh>
<uri>assets/4fc1c298164ee6bb48d06e66af95a8eec7a63ffaf822b4226750043b316d4e2e.dae</uri>
</mesh>
</geometry>
</visual>
<!--
Contact geometry used by physics. Keep dimensions and placement consistent with the
hull; a simplified shape reduces collision computation.
-->
<collision name="engine_vertical_axis_collision">
<!--
Pose: x y z in metres, then roll pitch yaw in radians. Values use the parent frame
unless relative_to specifies another frame.
-->
<pose>-0.16 0 -0.215 0 0 0</pose>
<geometry>
<box>
<size>0.2 0.1 0.83</size>
</box>
</geometry>
</collision>
<!--
Contact geometry used by physics. Keep dimensions and placement consistent with the
hull; a simplified shape reduces collision computation.
-->
<collision name="engine_rear_end_collision">
<!--
Pose: x y z in metres, then roll pitch yaw in radians. Values use the parent frame
unless relative_to specifies another frame.
-->
<pose>-0.34 0 0.12 0 0 0</pose>
<geometry>
<box>
<size>0.12 0.15 0.12</size>
</box>
</geometry>
</collision>
<!--
Mass properties: mass is in kg; pose locates and orients the centre-of-mass frame
relative to the link. Use measured or CAD-derived values.
-->
<inertial>
<mass>15</mass>
<!--
Inertia tensor in kg*m^2 at the centre of mass. ixx/iyy/izz are diagonal terms;
ixy/ixz/iyz are cross terms. Keep the tensor physically consistent with mass and
shape.
-->
<inertia>
<ixx>0.88924</ixx>
<ixy>0</ixy>
<iyy>0.911125</iyy>
<iyz>0</iyz>
<izz>0.078125</izz>
</inertia>
</inertial>
</link>
<!--
Joint connecting parent and child links. fixed locks their relative motion; revolute
permits rotation about axis/xyz. Preserve names used by thruster and controller
plugins.
-->
<joint name="left_engine_joint" type="fixed">
<parent>base_link</parent>
<child>left_engine_link</child>
</joint>
<!--
Rigid body and its local coordinate frame. Geometry, mass properties and sensors
inside this link move together.
-->
<link name="right_engine_link">
<!--
Pose: x y z in metres, then roll pitch yaw in radians. Values use the parent frame
unless relative_to specifies another frame.
-->
<pose>-2.373776 -1.027135 0.318237 0 0 0</pose>
<!--
Visible surface for rendering and cameras. Changing a visual does not automatically
resize the collision shape or change mass.
-->
<visual name="visual">
<geometry>
<!--
Mesh resource and optional axis scale. Keep the exported asset path and bundle
together; scale multiplies the mesh coordinates.
-->
<mesh>
<uri>assets/4fc1c298164ee6bb48d06e66af95a8eec7a63ffaf822b4226750043b316d4e2e.dae</uri>
</mesh>
</geometry>
</visual>
<!--
Contact geometry used by physics. Keep dimensions and placement consistent with the
hull; a simplified shape reduces collision computation.
-->
<collision name="engine_vertical_axis_collision">
<!--
Pose: x y z in metres, then roll pitch yaw in radians. Values use the parent frame
unless relative_to specifies another frame.
-->
<pose>-0.16 0 -0.215 0 0 0</pose>
<geometry>
<box>
<size>0.2 0.1 0.83</size>
</box>
</geometry>
</collision>
<!--
Contact geometry used by physics. Keep dimensions and placement consistent with the
hull; a simplified shape reduces collision computation.
-->
<collision name="engine_rear_end_collision">
<!--
Pose: x y z in metres, then roll pitch yaw in radians. Values use the parent frame
unless relative_to specifies another frame.
-->
<pose>-0.34 0 0.12 0 0 0</pose>
<geometry>
<box>
<size>0.12 0.15 0.12</size>
</box>
</geometry>
</collision>
<!--
Mass properties: mass is in kg; pose locates and orients the centre-of-mass frame
relative to the link. Use measured or CAD-derived values.
-->
<inertial>
<mass>15</mass>
<!--
Inertia tensor in kg*m^2 at the centre of mass. ixx/iyy/izz are diagonal terms;
ixy/ixz/iyz are cross terms. Keep the tensor physically consistent with mass and
shape.
-->
<inertia>
<ixx>0.88924</ixx>
<ixy>0</ixy>
<iyy>0.911125</iyy>
<iyz>0</iyz>
<izz>0.078125</izz>
</inertia>
</inertial>
</link>
<!--
Joint connecting parent and child links. fixed locks their relative motion; revolute
permits rotation about axis/xyz. Preserve names used by thruster and controller
plugins.
-->
<joint name="right_engine_joint" type="fixed">
<parent>base_link</parent>
<child>right_engine_link</child>
</joint>
<!--
Rigid body and its local coordinate frame. Geometry, mass properties and sensors
inside this link move together.
-->
<link name="left_propeller_link">
<!--
Pose: x y z in metres, then roll pitch yaw in radians. Values use the parent frame
unless relative_to specifies another frame.
-->
<pose relative_to="left_propeller_joint">0 0 0 0 0 0</pose>
<!--
Visible surface for rendering and cameras. Changing a visual does not automatically
resize the collision shape or change mass.
-->
<visual name="visual">
<geometry>
<!--
Mesh resource and optional axis scale. Keep the exported asset path and bundle
together; scale multiplies the mesh coordinates.
-->
<mesh>
<uri>assets/2c891453932798e772dab9792855c0ff84fc0315a662eb1c872f8e16bb692c25.dae</uri>
</mesh>
</geometry>
</visual>
<!--
Contact geometry used by physics. Keep dimensions and placement consistent with the
hull; a simplified shape reduces collision computation.
-->
<collision name="collision">
<!--
Pose: x y z in metres, then roll pitch yaw in radians. Values use the parent frame
unless relative_to specifies another frame.
-->
<pose>-0.11 0 0 0 1.570796 0</pose>
<geometry>
<cylinder>
<length>0.08</length>
<radius>0.24</radius>
</cylinder>
</geometry>
</collision>
<!--
Mass properties: mass is in kg; pose locates and orients the centre-of-mass frame
relative to the link. Use measured or CAD-derived values.
-->
<inertial>
<mass>0.5</mass>
<!--
Inertia tensor in kg*m^2 at the centre of mass. ixx/iyy/izz are diagonal terms;
ixy/ixz/iyz are cross terms. Keep the tensor physically consistent with mass and
shape.
-->
<inertia>
<ixx>0.008545</ixx>
<ixy>0</ixy>
<iyy>0.008545</iyy>
<iyz>0</iyz>
<izz>0.0144</izz>
</inertia>
</inertial>
</link>
<!--
Joint connecting parent and child links. fixed locks their relative motion; revolute
permits rotation about axis/xyz. Preserve names used by thruster and controller
plugins.
-->
<joint name="left_propeller_joint" type="revolute">
<!--
Pose: x y z in metres, then roll pitch yaw in radians. Values use the parent frame
unless relative_to specifies another frame.
-->
<pose relative_to="left_engine_link">-0.278156 0 -0.509371 0 0 0</pose>
<parent>left_engine_link</parent>
<child>left_propeller_link</child>
<axis>
<xyz>1 0 0</xyz>
<dynamics>
<damping>0.01</damping>
</dynamics>
<limit>
<lower>-1e+16</lower>
<upper>1e+16</upper>
</limit>
</axis>
</joint>
<!--
Rigid body and its local coordinate frame. Geometry, mass properties and sensors
inside this link move together.
-->
<link name="right_propeller_link">
<!--
Pose: x y z in metres, then roll pitch yaw in radians. Values use the parent frame
unless relative_to specifies another frame.
-->
<pose relative_to="right_propeller_joint">0 0 0 0 0 0</pose>
<!--
Visible surface for rendering and cameras. Changing a visual does not automatically
resize the collision shape or change mass.
-->
<visual name="visual">
<geometry>
<!--
Mesh resource and optional axis scale. Keep the exported asset path and bundle
together; scale multiplies the mesh coordinates.
-->
<mesh>
<uri>assets/2c891453932798e772dab9792855c0ff84fc0315a662eb1c872f8e16bb692c25.dae</uri>
</mesh>
</geometry>
</visual>
<!--
Contact geometry used by physics. Keep dimensions and placement consistent with the
hull; a simplified shape reduces collision computation.
-->
<collision name="collision">
<!--
Pose: x y z in metres, then roll pitch yaw in radians. Values use the parent frame
unless relative_to specifies another frame.
-->
<pose>-0.11 0 0 0 1.570796 0</pose>
<geometry>
<cylinder>
<length>0.08</length>
<radius>0.24</radius>
</cylinder>
</geometry>
</collision>
<!--
Mass properties: mass is in kg; pose locates and orients the centre-of-mass frame
relative to the link. Use measured or CAD-derived values.
-->
<inertial>
<mass>0.5</mass>
<!--
Inertia tensor in kg*m^2 at the centre of mass. ixx/iyy/izz are diagonal terms;
ixy/ixz/iyz are cross terms. Keep the tensor physically consistent with mass and
shape.
-->
<inertia>
<ixx>0.008545</ixx>
<ixy>0</ixy>
<iyy>0.008545</iyy>
<iyz>0</iyz>
<izz>0.0144</izz>
</inertia>
</inertial>
</link>
<!--
Joint connecting parent and child links. fixed locks their relative motion; revolute
permits rotation about axis/xyz. Preserve names used by thruster and controller
plugins.
-->
<joint name="right_propeller_joint" type="revolute">
<!--
Pose: x y z in metres, then roll pitch yaw in radians. Values use the parent frame
unless relative_to specifies another frame.
-->
<pose relative_to="right_engine_link">-0.278156 0 -0.509371 0 0 0</pose>
<parent>right_engine_link</parent>
<child>right_propeller_link</child>
<axis>
<xyz>1 0 0</xyz>
<dynamics>
<damping>0.01</damping>
</dynamics>
<limit>
<lower>-1e+16</lower>
<upper>1e+16</upper>
</limit>
</axis>
</joint>
<!--
Rigid body and its local coordinate frame. Geometry, mass properties and sensors
inside this link move together.
-->
<link name="imu_link">
<!--
Mass properties: mass is in kg; pose locates and orients the centre-of-mass frame
relative to the link. Use measured or CAD-derived values.
-->
<inertial>
<!--
Pose: x y z in metres, then roll pitch yaw in radians. Values use the parent frame
unless relative_to specifies another frame.
-->
<pose>0 0 0 0 0 0</pose>
<mass>0.15</mass>
<!--
Inertia tensor in kg*m^2 at the centre of mass. ixx/iyy/izz are diagonal terms;
ixy/ixz/iyz are cross terms. Keep the tensor physically consistent with mass and
shape.
-->
<inertia>
<ixx>0.00001</ixx>
<ixy>0</ixy>
<ixz>0</ixz>
<iyy>0.00002</iyy>
<iyz>0</iyz>
<izz>0.00002</izz>
</inertia>
</inertial>
<!--
Sensor attached to this link. Its pose sets the mounting position; type selects the
measurement implementation. The builder also prepares topic routes and required world
systems.
-->
<sensor name="imu_sensor" type="imu">
<!--
Pose: x y z in metres, then roll pitch yaw in radians. Values use the parent frame
unless relative_to specifies another frame.
-->
<pose>0 0 0 3.141593 0 0</pose>
<always_on>1</always_on>
<!--
Requested sensor update frequency in Hz. Delivered rate also depends on simulation
speed and rendering load.
-->
<update_rate>200</update_rate>
</sensor>
</link>
<!--
Joint connecting parent and child links. fixed locks their relative motion; revolute
permits rotation about axis/xyz. Preserve names used by thruster and controller
plugins.
-->
<joint name="imu_joint" type="fixed">
<child>imu_link</child>
<parent>base_link</parent>
</joint>
<!--
Loaded engine plugin. filename identifies an installed library and name selects its
implementation. Preserve both when uploading numeric edits; an SDF file does not
install plugins.
-->
<!--
Propeller thrust model: fluid_density is kg/m^3, propeller_diameter is metres, and
thrust_coefficient relates angular speed to thrust. use_angvel_cmd selects rad/s
commands when true, or force in N when false.
-->
<plugin filename="gz-sim-thruster-system" name="gz::sim::systems::Thruster">
<namespace>wamv</namespace>
<joint_name>left_propeller_joint</joint_name>
<use_angvel_cmd>0</use_angvel_cmd>
<fluid_density>1000</fluid_density>
<propeller_diameter>0.48</propeller_diameter>
<thrust_coefficient>0.01</thrust_coefficient>
<velocity_control>1</velocity_control>
<max_thrust_cmd>2000.0</max_thrust_cmd>
<min_thrust_cmd>-2000.0</min_thrust_cmd>
</plugin>
<!--
Loaded engine plugin. filename identifies an installed library and name selects its
implementation. Preserve both when uploading numeric edits; an SDF file does not
install plugins.
-->
<!--
Propeller thrust model: fluid_density is kg/m^3, propeller_diameter is metres, and
thrust_coefficient relates angular speed to thrust. use_angvel_cmd selects rad/s
commands when true, or force in N when false.
-->
<plugin filename="gz-sim-thruster-system" name="gz::sim::systems::Thruster">
<namespace>wamv</namespace>
<joint_name>right_propeller_joint</joint_name>
<use_angvel_cmd>0</use_angvel_cmd>
<fluid_density>1000</fluid_density>
<propeller_diameter>0.48</propeller_diameter>
<thrust_coefficient>0.01</thrust_coefficient>
<velocity_control>1</velocity_control>
<max_thrust_cmd>2000.0</max_thrust_cmd>
<min_thrust_cmd>-2000.0</min_thrust_cmd>
</plugin>
<!--
Loaded engine plugin. filename identifies an installed library and name selects its
implementation. Preserve both when uploading numeric edits; an SDF file does not
install plugins.
-->
<plugin filename="/opt/wwos/competition_hydrodynamics/lib/libwwos-competition-hydrodynamics.so" name="gz::sim::systems::CompetitionHydrodynamics">
<enable>wamv::base_link</enable>
<!--
Water-force coefficients. damping_on, viscous_drag_on and pressure_drag_on enable
their respective terms. cDampL/R tune linear/angular damping; pressure-drag
coefficients use this plugin's model and are not interchangeable with other solvers.
-->
<hydrodynamics>
<damping_on>1</damping_on>
<viscous_drag_on>1</viscous_drag_on>
<pressure_drag_on>1</pressure_drag_on>
<cDampL1>1.0E-6</cDampL1>
<cDampL2>1.0E-6</cDampL2>
<cDampR1>1.0E-6</cDampR1>
<cDampR2>1.0E-6</cDampR2>
<cPDrag1>1.0E+2</cPDrag1>
<cPDrag2>1.0E+2</cPDrag2>
<fPDrag>0.4</fPDrag>
<cSDrag1>1.0E+2</cSDrag1>
<cSDrag2>1.0E+2</cSDrag2>
<fSDrag>0.4</fSDrag>
<vRDrag>1.0</vRDrag>
</hydrodynamics>
<current_user_configurable>true</current_user_configurable>
<current_session_tag>0</current_session_tag>
<current_start_enabled>false</current_start_enabled>
</plugin>
<!--
Loaded engine plugin. filename identifies an installed library and name selects its
implementation. Preserve both when uploading numeric edits; an SDF file does not
install plugins.
-->
<!--
ArduPilot simulator connection: network endpoint, lock-step timing, coordinate
transforms and IMU name. Preserve these connections when adjusting the vehicle's
physical parameters.
-->
<plugin name="ArduPilotPlugin" filename="libArduPilotPlugin.so">
<fdm_addr>127.0.0.1</fdm_addr>
<fdm_port_in>9002</fdm_port_in>
<connectionTimeoutMaxCount>5</connectionTimeoutMaxCount>
<lock_step>1</lock_step>
<modelXYZToAirplaneXForwardZDown>0 0 0 3.14159265359 0 0</modelXYZToAirplaneXForwardZDown>
<gazeboXYZToNED>0 0 0 3.14159265359 0 1.57079632679</gazeboXYZToNED>
<imuName>imu_sensor</imuName>
<!--
Maps one controller channel to a joint command topic. servo_min/max define its input
range; offset and multiplier set the output offset and scale. Retain the channel and
topic mapping.
-->
<control channel="0">
<jointName>left_propeller_joint</jointName>
<servo_min>1000</servo_min>
<servo_max>2000</servo_max>
<type>COMMAND</type>
<cmd_topic>/model/wamv/joint/left_propeller_joint/cmd_thrust</cmd_topic>
<offset>-.5</offset>
<multiplier>500</multiplier>
</control>
<!--
Maps one controller channel to a joint command topic. servo_min/max define its input
range; offset and multiplier set the output offset and scale. Retain the channel and
topic mapping.
-->
<control channel="2">
<jointName>right_propeller_joint</jointName>
<servo_min>1000</servo_min>
<servo_max>2000</servo_max>
<type>COMMAND</type>
<cmd_topic>/model/wamv/joint/right_propeller_joint/cmd_thrust</cmd_topic>
<offset>-.5</offset>
<multiplier>500</multiplier>
</control>
</plugin>
<!--
Loaded engine plugin. filename identifies an installed library and name selects its
implementation. Preserve both when uploading numeric edits; an SDF file does not
install plugins.
-->
<!--
Publishes simulated odometry with the configured frames and frequency in Hz. These
values describe simulator state; use the sensor topics for simulated measurements.
-->
<plugin filename="gz-sim-odometry-publisher-system" name="gz::sim::systems::OdometryPublisher">
<dimensions>3</dimensions>
<odom_frame>map</odom_frame>
<robot_base_frame>base_link</robot_base_frame>
<odom_publish_frequency>20</odom_publish_frequency>
<odom_topic>/model/wamv/odometry</odom_topic>
</plugin>
<!--
Rigid body and its local coordinate frame. Geometry, mass properties and sensors
inside this link move together.
-->
<link name="gnss_link">
<!--
Pose: x y z in metres, then roll pitch yaw in radians. Values use the parent frame
unless relative_to specifies another frame.
-->
<pose relative_to="base_link">0 0 1.8 0 0 0</pose>
<!--
Mass properties: mass is in kg; pose locates and orients the centre-of-mass frame
relative to the link. Use measured or CAD-derived values.
-->
<inertial>
<mass>.001</mass>
<!--
Inertia tensor in kg*m^2 at the centre of mass. ixx/iyy/izz are diagonal terms;
ixy/ixz/iyz are cross terms. Keep the tensor physically consistent with mass and
shape.
-->
<inertia>
<ixx>0.000001</ixx>
<iyy>0.000001</iyy>
<izz>0.000001</izz>
</inertia>
</inertial>
<!--
Sensor attached to this link. Its pose sets the mounting position; type selects the
measurement implementation. The builder also prepares topic routes and required world
systems.
-->
<sensor name="gnss" type="custom" gz:type="posim_gnss">
<always_on>true</always_on>
<!--
Requested sensor update frequency in Hz. Delivered rate also depends on simulation
speed and rendering load.
-->
<update_rate>5</update_rate>
<!--
Gazebo Transport output topic. Keep it aligned with the exported sensor manifest and
ROS bridge routes.
-->
<topic>/model/wamv/gnss</topic>
</sensor>
</link>
<!--
Joint connecting parent and child links. fixed locks their relative motion; revolute
permits rotation about axis/xyz. Preserve names used by thruster and controller
plugins.
-->
<joint name="gnss_joint" type="fixed">
<parent>base_link</parent>
<child>gnss_link</child>
</joint>
<!--
Loaded engine plugin. filename identifies an installed library and name selects its
implementation. Preserve both when uploading numeric edits; an SDF file does not
install plugins.
-->
<!--
GNSS receiver model. update_rate is Hz; latency and reacquire_seconds are seconds.
Position noise and dry_margin use metres; velocity_stddev uses m/s. link_name, topic
and wave_topic connect the antenna, output and water-surface input.
-->
<plugin name="posim::Gnss" filename="libposim_gnss.so">
<update_rate>5</update_rate>
<latency>0.2</latency>
<reacquire_seconds>3</reacquire_seconds>
<dry_margin>0.05</dry_margin>
<horizontal_stddev>0.7</horizontal_stddev>
<vertical_stddev>1.2</vertical_stddev>
<velocity_stddev>0.1</velocity_stddev>
<water_level>0</water_level>
<seed>42</seed>
<enabled>true</enabled>
<link_name>gnss_link</link_name>
<topic>/model/wamv/gnss</topic>
<wave_topic>/wwos/wave_surface</wave_topic>
</plugin>
<!--
Loaded engine plugin. filename identifies an installed library and name selects its
implementation. Preserve both when uploading numeric edits; an SDF file does not
install plugins.
-->
<plugin filename="gz-sim-pose-publisher-system" name="gz::sim::systems::PosePublisher">
<publish_model_pose>true</publish_model_pose>
<publish_link_pose>true</publish_link_pose>
<publish_sensor_pose>true</publish_sensor_pose>
<publish_nested_model_pose>true</publish_nested_model_pose>
<publish_visual_pose>false</publish_visual_pose>
<publish_collision_pose>false</publish_collision_pose>
<use_pose_vector_msg>true</use_pose_vector_msg>
<update_frequency>20</update_frequency>
<topic>/model/wamv/wwos/poses</topic>
</plugin>
</model>
</sdf>
Complete BlueROV2 SDF
Download BlueROV2 model.sdf. This example selects forward and downward cameras and single Ping, with Autopilot and GNSS. DVL and the acoustic provider examples remain visible in comments. DVL and single Ping are alternatives.
bluerov2.sdf
<?xml version='1.0' encoding='utf-8'?>
<sdf xmlns:gz="http://gazebosim.org" version="1.6">
<!--
Model assembly: links hold rigid bodies, joints connect them, and plugins provide
simulation behavior. Keep model, link and joint names consistent with the exported
controllers.
-->
<model name="bluerov2">
<!--
Exported vehicle configuration. The active model follows this comment. Select sensors and providers in the vehicle editor so topic routes and world systems stay aligned. Mount limits: position ±10 m; rotation ±2π rad. recipe.json:
{
"control_mode": "autopilot",
"gnss": true,
"schema_version": 1,
"sensors": [
"camera",
"camera_down",
"ping_down"
],
"settings": {
"camera": {
"height": 480,
"horizontal_fov": 1.4,
"pose": [
0.4,
0.0,
-0.1,
0.0,
0.0,
0.0
],
"update_rate": 5,
"width": 640
},
"camera_down": {
"height": 600,
"horizontal_fov": 1.4,
"pose": [
-0.1,
0.0,
0.0,
0.0,
1.5707963267948966,
0.0
],
"update_rate": 5,
"width": 800
},
"ping_down": {
"pose": [
-0.15,
0.0,
-0.095,
0.0,
1.5707963267948966,
0.0
],
"range_max": 30,
"update_rate": 5
}
},
"vehicle": "bluerov2"
}
-->
<!--
Pose: x y z in metres, then roll pitch yaw in radians. Values use the parent frame
unless relative_to specifies another frame.
-->
<pose>0 0 0 0 0 0</pose>
<!--
Rigid body and its local coordinate frame. Geometry, mass properties and sensors
inside this link move together.
-->
<link name="base_link">
<!--
Mass properties: mass is in kg; pose locates and orients the centre-of-mass frame
relative to the link. Use measured or CAD-derived values.
-->
<inertial>
<!--
Pose: x y z in metres, then roll pitch yaw in radians. Values use the parent frame
unless relative_to specifies another frame.
-->
<pose>0.0 0.0 0.011 0 0 0</pose>
<mass>10.0</mass>
<!--
Inertia tensor in kg*m^2 at the centre of mass. ixx/iyy/izz are diagonal terms;
ixy/ixz/iyz are cross terms. Keep the tensor physically consistent with mass and
shape.
-->
<inertia>
<ixx>0.099</ixx>
<ixy>0</ixy>
<ixz>0</ixz>
<iyy>0.178</iyy>
<iyz>0</iyz>
<izz>0.269</izz>
</inertia>
</inertial>
<!--
Visible surface for rendering and cameras. Changing a visual does not automatically
resize the collision shape or change mass.
-->
<visual name="base_link_visual">
<geometry>
<!--
Mesh resource and optional axis scale. Keep the exported asset path and bundle
together; scale multiplies the mesh coordinates.
-->
<mesh>
<uri>assets/c73a7bc28f98fdcad54bf77d3ca61d26bb299e0d39be90cb56b77314d1499dde.dae</uri>
<scale>0.025 0.025 0.025</scale>
</mesh>
</geometry>
</visual>
<!--
Contact geometry used by physics. Keep dimensions and placement consistent with the
hull; a simplified shape reduces collision computation.
-->
<collision name="base_link_collision">
<!--
Pose: x y z in metres, then roll pitch yaw in radians. Values use the parent frame
unless relative_to specifies another frame.
-->
<pose>0.0 0.0 0.06 0 0 0</pose>
<geometry>
<box>
<size>0.457 0.338 0.065</size>
</box>
</geometry>
</collision>
<!--
Sensor attached to this link. Its pose sets the mounting position; type selects the
measurement implementation. The builder also prepares topic routes and required world
systems.
-->
<sensor name="imu_sensor" type="imu">
<!--
Pose: x y z in metres, then roll pitch yaw in radians. Values use the parent frame
unless relative_to specifies another frame.
-->
<pose>0 0 0 3.142 0 0</pose>
<always_on>1</always_on>
<!--
Requested sensor update frequency in Hz. Delivered rate also depends on simulation
speed and rendering load.
-->
<update_rate>1000.0</update_rate>
</sensor>
<!--
Sensor attached to this link. Its pose sets the mounting position; type selects the
measurement implementation. The builder also prepares topic routes and required world
systems.
-->
<sensor name="wwos_magnetometer" type="magnetometer">
<always_on>true</always_on>
<!--
Requested sensor update frequency in Hz. Delivered rate also depends on simulation
speed and rendering load.
-->
<update_rate>20</update_rate>
<!--
Gazebo Transport output topic. Keep it aligned with the exported sensor manifest and
ROS bridge routes.
-->
<topic>/model/bluerov2/magnetometer</topic>
</sensor>
<!--
Sensor attached to this link. Its pose sets the mounting position; type selects the
measurement implementation. The builder also prepares topic routes and required world
systems.
-->
<sensor name="payload_camera" type="camera">
<always_on>true</always_on>
<!--
Requested sensor update frequency in Hz. Delivered rate also depends on simulation
speed and rendering load.
-->
<update_rate>5</update_rate>
<!--
Gazebo Transport output topic. Keep it aligned with the exported sensor manifest and
ROS bridge routes.
-->
<topic>/vehicle/sensors/camera</topic>
<!--
Camera: horizontal_fov is in radians; image width/height are pixels. clip near/far are
rendering distances in metres. camera_info_topic publishes calibration data.
-->
<camera>
<horizontal_fov>1.4</horizontal_fov>
<image>
<width>640</width>
<height>480</height>
</image>
<clip>
<near>.1</near>
<far>100</far>
</clip>
<camera_info_topic>/vehicle/sensors/camera/camera_info</camera_info_topic>
</camera>
<!--
Pose: x y z in metres, then roll pitch yaw in radians. Values use the parent frame
unless relative_to specifies another frame.
-->
<pose>0.4 0.0 -0.1 0.0 0.0 0.0</pose>
<frame_id>vehicle/camera</frame_id>
</sensor>
<!--
Sensor attached to this link. Its pose sets the mounting position; type selects the
measurement implementation. The builder also prepares topic routes and required world
systems.
-->
<sensor name="payload_camera_down" type="camera">
<always_on>true</always_on>
<!--
Requested sensor update frequency in Hz. Delivered rate also depends on simulation
speed and rendering load.
-->
<update_rate>5</update_rate>
<!--
Gazebo Transport output topic. Keep it aligned with the exported sensor manifest and
ROS bridge routes.
-->
<topic>/vehicle/sensors/camera_down</topic>
<!--
Camera: horizontal_fov is in radians; image width/height are pixels. clip near/far are
rendering distances in metres. camera_info_topic publishes calibration data.
-->
<camera>
<horizontal_fov>1.4</horizontal_fov>
<image>
<width>800</width>
<height>600</height>
</image>
<clip>
<near>.1</near>
<far>100</far>
</clip>
<camera_info_topic>/vehicle/sensors/camera_down/camera_info</camera_info_topic>
</camera>
<!--
Pose: x y z in metres, then roll pitch yaw in radians. Values use the parent frame
unless relative_to specifies another frame.
-->
<pose>-0.1 0.0 0.0 0.0 1.5707963267948966 0.0</pose>
<frame_id>vehicle/camera_down</frame_id>
</sensor>
<!--
Sensor attached to this link. Its pose sets the mounting position; type selects the
measurement implementation. The builder also prepares topic routes and required world
systems.
-->
<sensor name="payload_ping_down" type="gpu_lidar">
<always_on>true</always_on>
<!--
Requested sensor update frequency in Hz. Delivered rate also depends on simulation
speed and rendering load.
-->
<update_rate>5</update_rate>
<!--
Gazebo Transport output topic. Keep it aligned with the exported sensor manifest and
ROS bridge routes.
-->
<topic>/vehicle/sensors/ping_down</topic>
<!--
Ray-based range sensor. scan sets horizontal/vertical samples and angles in radians;
range sets minimum/maximum distance and resolution in metres. Single Ping uses this
GPU ray implementation.
-->
<lidar>
<scan>
<horizontal>
<samples>5</samples>
<resolution>1</resolution>
<min_angle>-0.00872665</min_angle>
<max_angle>0.00872665</max_angle>
</horizontal>
<vertical>
<samples>5</samples>
<resolution>1</resolution>
<min_angle>-0.00872665</min_angle>
<max_angle>0.00872665</max_angle>
</vertical>
</scan>
<range>
<min>0.1</min>
<max>30</max>
<resolution>0.01</resolution>
</range>
</lidar>
<!--
Pose: x y z in metres, then roll pitch yaw in radians. Values use the parent frame
unless relative_to specifies another frame.
-->
<pose>-0.15 0.0 -0.095 0.0 1.5707963267948966 0.0</pose>
<frame_id>vehicle/ping_down</frame_id>
</sensor>
<!--
Optional sensor camera: inactive default example. Active payload_* elements elsewhere in the model define the selected sensors. Use the vehicle editor to change the selection and keep this example inside its comment. Editable limits and output routes:
update_rate: 0.1 … 30 Hz
width: 64 … 1920 px
height: 64 … 1920 px
horizontal_fov: 0.1 … 3 rad
width * height * update_rate <= 30000000 px/s
Gazebo: /vehicle/sensors/camera
frame_id: vehicle/camera
ROS: /vehicle/sensors/camera (sensor_msgs/msg/Image)
ROS: /vehicle/sensors/camera/camera_info (sensor_msgs/msg/CameraInfo)
<sensor name="payload_camera" type="camera">
<always_on>true</always_on>
<update_rate>5</update_rate>
<topic>/vehicle/sensors/camera</topic>
<camera>
<horizontal_fov>1.4</horizontal_fov>
<image>
<width>640</width>
<height>480</height>
</image>
<clip>
<near>.1</near>
<far>100</far>
</clip>
<camera_info_topic>/vehicle/sensors/camera/camera_info</camera_info_topic>
</camera>
<pose>0.4 0.0 -0.1 0.0 0.0 0.0</pose>
<frame_id>vehicle/camera</frame_id>
</sensor>
-->
<!--
Optional sensor camera_down: inactive default example. Active payload_* elements elsewhere in the model define the selected sensors. Use the vehicle editor to change the selection and keep this example inside its comment. Editable limits and output routes:
update_rate: 0.1 … 30 Hz
width: 64 … 1920 px
height: 64 … 1920 px
horizontal_fov: 0.1 … 3 rad
width * height * update_rate <= 30000000 px/s
Gazebo: /vehicle/sensors/camera_down
frame_id: vehicle/camera_down
ROS: /vehicle/sensors/camera_down (sensor_msgs/msg/Image)
ROS: /vehicle/sensors/camera_down/camera_info (sensor_msgs/msg/CameraInfo)
<sensor name="payload_camera_down" type="camera">
<always_on>true</always_on>
<update_rate>5</update_rate>
<topic>/vehicle/sensors/camera_down</topic>
<camera>
<horizontal_fov>1.4</horizontal_fov>
<image>
<width>800</width>
<height>600</height>
</image>
<clip>
<near>.1</near>
<far>100</far>
</clip>
<camera_info_topic>/vehicle/sensors/camera_down/camera_info</camera_info_topic>
</camera>
<pose>-0.1 0.0 0.0 0.0 1.5707963267948966 0.0</pose>
<frame_id>vehicle/camera_down</frame_id>
</sensor>
-->
<!--
Optional sensor ping_down: inactive default example. Active payload_* elements elsewhere in the model define the selected sensors. Use the vehicle editor to change the selection and keep this example inside its comment. Editable limits and output routes:
update_rate: 0.1 … 30 Hz
range_max: 1 … 100 m
Gazebo: /vehicle/sensors/ping_down
frame_id: vehicle/ping_down
ROS: /vehicle/sensors/ping_down (sensor_msgs/msg/LaserScan)
ROS: /vehicle/sensors/ping_down/range (sensor_msgs/msg/Range)
runtime: practice_ping.py
Choose either DVL or single Ping; they cannot be enabled together.
<sensor name="payload_ping_down" type="gpu_lidar">
<always_on>true</always_on>
<update_rate>5</update_rate>
<topic>/vehicle/sensors/ping_down</topic>
<lidar>
<scan>
<horizontal>
<samples>5</samples>
<resolution>1</resolution>
<min_angle>-0.00872665</min_angle>
<max_angle>0.00872665</max_angle>
</horizontal>
<vertical>
<samples>5</samples>
<resolution>1</resolution>
<min_angle>-0.00872665</min_angle>
<max_angle>0.00872665</max_angle>
</vertical>
</scan>
<range>
<min>0.1</min>
<max>30</max>
<resolution>0.01</resolution>
</range>
</lidar>
<pose>-0.15 0.0 -0.095 0.0 1.5707963267948966 0.0</pose>
<frame_id>vehicle/ping_down</frame_id>
</sensor>
-->
<!--
Optional sensor multibeam_forward: inactive default example. Active payload_* elements elsewhere in the model define the selected sensors. Use the vehicle editor to change the selection and keep this example inside its comment. Editable limits and output routes:
update_rate: 0.1 … 30 Hz
Gazebo: /vehicle/sensors/multibeam_forward
frame_id: vehicle/multibeam_forward
ROS: /vehicle/sensors/multibeam_forward/sonar_image_raw (marine_acoustic_msgs/msg/ProjectedSonarImage)
Requires a compatible POSIM acoustic sonar provider and its world system. This example remains a reference when the provider is unavailable. Ray and acoustic fields are provider defaults; the builder exposes update rate and pose.
<sensor xmlns:gz="http://gazebosim.org" name="payload_multibeam_forward" type="custom" gz:type="multibeam_sonar">
<always_on>true</always_on>
<update_rate>2</update_rate>
<topic>/vehicle/sensors/multibeam_forward</topic>
<visualize>true</visualize>
<gz:multibeam_sonar>
<ray degrees="false">
<scan>
<horizontal>
<beams>256</beams>
<min_angle>-1.0471975511965976</min_angle>
<max_angle>1.0471975511965976</max_angle>
</horizontal>
<vertical>
<rays>256</rays>
<min_angle>-0.17453292519943295</min_angle>
<max_angle>0.17453292519943295</max_angle>
</vertical>
</scan>
<range>
<min>0.2</min>
<max>15</max>
</range>
</ray>
<spec>
<verticalFOV>20</verticalFOV>
<sonarFreq>700e3</sonarFreq>
<bandwidth>29.9e3</bandwidth>
<soundSpeed>1500</soundSpeed>
<sourceLevel>220</sourceLevel>
<maxDistance>15</maxDistance>
<raySkips>1</raySkips>
<sensorGain>0.02</sensorGain>
<writeLog>false</writeLog>
<debugFlag>false</debugFlag>
<writeFrameInterval>5</writeFrameInterval>
<pointCloudTopicName>geometry/points</pointCloudTopicName>
<sonarImageRawTopicName>sonar_image_raw</sonarImageRawTopicName>
<sonarImageTopicName>sonar_image</sonarImageTopicName>
<frameName>vehicle/multibeam_forward</frameName>
<visibilityMask>3892314111</visibilityMask>
</spec>
</gz:multibeam_sonar>
<pose>0.24 0.0 -0.1 0.0 0.35 0.0</pose>
<frame_id>vehicle/multibeam_forward</frame_id>
</sensor>
-->
<!--
Optional sensor dvl: inactive default example. Active payload_* elements elsewhere in the model define the selected sensors. Use the vehicle editor to change the selection and keep this example inside its comment. Editable limits and output routes:
update_rate: 0.1 … 30 Hz
range_max: 1 … 100 m
Gazebo: /vehicle/sensors/dvl
frame_id: vehicle/dvl
ROS: /vehicle/sensors/dvl/velocity (geometry_msgs/msg/Vector3Stamped)
ROS: /vehicle/sensors/dvl/status (std_msgs/msg/String)
runtime: practice_dvl_bridge.py
Choose either DVL or single Ping; they cannot be enabled together.
<sensor xmlns:gz="http://gazebosim.org" name="payload_dvl" type="custom" gz:type="dvl">
<pose>0.0 0.0 -0.12 0.0 0.0 0.0</pose>
<always_on>true</always_on>
<update_rate>1</update_rate>
<topic>/vehicle/sensors/dvl</topic>
<gz:dvl>
<type>phased_array</type>
<arrangement degrees="true">
<beam id="1">
<aperture>2</aperture>
<rotation>45</rotation>
<tilt>30</tilt>
</beam>
<beam id="2">
<aperture>2</aperture>
<rotation>135</rotation>
<tilt>30</tilt>
</beam>
<beam id="3">
<aperture>2</aperture>
<rotation>-45</rotation>
<tilt>30</tilt>
</beam>
<beam id="4">
<aperture>2</aperture>
<rotation>-135</rotation>
<tilt>30</tilt>
</beam>
</arrangement>
<tracking>
<bottom_mode>
<when>best</when>
<noise type="gaussian">
<stddev>0.002</stddev>
</noise>
<visualize>false</visualize>
</bottom_mode>
</tracking>
<resolution>0.01</resolution>
<maximum_range>20</maximum_range>
<minimum_range>0.1</minimum_range>
<reference_frame>0 0 0 0 0 0</reference_frame>
</gz:dvl>
<frame_id>vehicle/dvl</frame_id>
</sensor>
-->
</link>
<!--
Rigid body and its local coordinate frame. Geometry, mass properties and sensors
inside this link move together.
-->
<link name="camera_link">
<!--
Pose: x y z in metres, then roll pitch yaw in radians. Values use the parent frame
unless relative_to specifies another frame.
-->
<pose relative_to="camera_mount_link">0 0 0 0 0 0</pose>
<!--
Mass properties: mass is in kg; pose locates and orients the centre-of-mass frame
relative to the link. Use measured or CAD-derived values.
-->
<inertial>
<mass>0.0001</mass>
<!--
Inertia tensor in kg*m^2 at the centre of mass. ixx/iyy/izz are diagonal terms;
ixy/ixz/iyz are cross terms. Keep the tensor physically consistent with mass and
shape.
-->
<inertia>
<ixx>0.0001</ixx>
<ixy>0</ixy>
<ixz>0</ixz>
<iyy>0.0001</iyy>
<iyz>0</iyz>
<izz>0.0001</izz>
</inertia>
</inertial>
</link>
<!--
Rigid body and its local coordinate frame. Geometry, mass properties and sensors
inside this link move together.
-->
<link name="camera_mount_link">
<!--
Pose: x y z in metres, then roll pitch yaw in radians. Values use the parent frame
unless relative_to specifies another frame.
-->
<pose relative_to="base_link">0.19 0 0.067 0 0 0</pose>
<!--
Mass properties: mass is in kg; pose locates and orients the centre-of-mass frame
relative to the link. Use measured or CAD-derived values.
-->
<inertial>
<mass>0.0001</mass>
<!--
Inertia tensor in kg*m^2 at the centre of mass. ixx/iyy/izz are diagonal terms;
ixy/ixz/iyz are cross terms. Keep the tensor physically consistent with mass and
shape.
-->
<inertia>
<ixx>0.0001</ixx>
<ixy>0</ixy>
<ixz>0</ixz>
<iyy>0.0001</iyy>
<iyz>0</iyz>
<izz>0.0001</izz>
</inertia>
</inertial>
</link>
<!--
Joint connecting parent and child links. fixed locks their relative motion; revolute
permits rotation about axis/xyz. Preserve names used by thruster and controller
plugins.
-->
<joint name="camera_joint" type="fixed">
<parent>camera_mount_link</parent>
<child>camera_link</child>
</joint>
<!--
Joint connecting parent and child links. fixed locks their relative motion; revolute
permits rotation about axis/xyz. Preserve names used by thruster and controller
plugins.
-->
<joint name="camera_mount_joint" type="fixed">
<parent>base_link</parent>
<child>camera_mount_link</child>
</joint>
<!--
Rigid body and its local coordinate frame. Geometry, mass properties and sensors
inside this link move together.
-->
<link name="thruster1">
<!--
Pose: x y z in metres, then roll pitch yaw in radians. Values use the parent frame
unless relative_to specifies another frame.
-->
<pose>0.14 -0.092 0.0 -1.571 1.571 -0.785</pose>
<!--
Visible surface for rendering and cameras. Changing a visual does not automatically
resize the collision shape or change mass.
-->
<visual name="thruster_prop_visual">
<!--
Pose: x y z in metres, then roll pitch yaw in radians. Values use the parent frame
unless relative_to specifies another frame.
-->
<pose>0 0 0 -1.571 0 0</pose>
<geometry>
<!--
Mesh resource and optional axis scale. Keep the exported asset path and bundle
together; scale multiplies the mesh coordinates.
-->
<mesh>
<uri>assets/4c4ae10284584339de36be62165caca9464a8df8ec1e81567d08180b3531d643.dae</uri>
</mesh>
</geometry>
</visual>
<!--
Mass properties: mass is in kg; pose locates and orients the centre-of-mass frame
relative to the link. Use measured or CAD-derived values.
-->
<inertial>
<mass>0.002</mass>
<!--
Inertia tensor in kg*m^2 at the centre of mass. ixx/iyy/izz are diagonal terms;
ixy/ixz/iyz are cross terms. Keep the tensor physically consistent with mass and
shape.
-->
<inertia>
<ixx>0.001</ixx>
<ixy>0</ixy>
<ixz>0</ixz>
<iyy>0.001</iyy>
<iyz>0</iyz>
<izz>0.001</izz>
</inertia>
</inertial>
</link>
<!--
Rigid body and its local coordinate frame. Geometry, mass properties and sensors
inside this link move together.
-->
<link name="thruster2">
<!--
Pose: x y z in metres, then roll pitch yaw in radians. Values use the parent frame
unless relative_to specifies another frame.
-->
<pose>0.14 0.092 0.0 -1.571 1.571 -2.356</pose>
<!--
Visible surface for rendering and cameras. Changing a visual does not automatically
resize the collision shape or change mass.
-->
<visual name="thruster_prop_visual">
<!--
Pose: x y z in metres, then roll pitch yaw in radians. Values use the parent frame
unless relative_to specifies another frame.
-->
<pose>0 0 0 -1.571 0 0</pose>
<geometry>
<!--
Mesh resource and optional axis scale. Keep the exported asset path and bundle
together; scale multiplies the mesh coordinates.
-->
<mesh>
<uri>assets/4c4ae10284584339de36be62165caca9464a8df8ec1e81567d08180b3531d643.dae</uri>
</mesh>
</geometry>
</visual>
<!--
Mass properties: mass is in kg; pose locates and orients the centre-of-mass frame
relative to the link. Use measured or CAD-derived values.
-->
<inertial>
<mass>0.002</mass>
<!--
Inertia tensor in kg*m^2 at the centre of mass. ixx/iyy/izz are diagonal terms;
ixy/ixz/iyz are cross terms. Keep the tensor physically consistent with mass and
shape.
-->
<inertia>
<ixx>0.001</ixx>
<ixy>0</ixy>
<ixz>0</ixz>
<iyy>0.001</iyy>
<iyz>0</iyz>
<izz>0.001</izz>
</inertia>
</inertial>
</link>
<!--
Rigid body and its local coordinate frame. Geometry, mass properties and sensors
inside this link move together.
-->
<link name="thruster3">
<!--
Pose: x y z in metres, then roll pitch yaw in radians. Values use the parent frame
unless relative_to specifies another frame.
-->
<pose>-0.15 -0.092 0.0 -1.571 1.571 0.785</pose>
<!--
Visible surface for rendering and cameras. Changing a visual does not automatically
resize the collision shape or change mass.
-->
<visual name="thruster_prop_visual">
<!--
Pose: x y z in metres, then roll pitch yaw in radians. Values use the parent frame
unless relative_to specifies another frame.
-->
<pose>0 0 0 1.571 0 0</pose>
<geometry>
<!--
Mesh resource and optional axis scale. Keep the exported asset path and bundle
together; scale multiplies the mesh coordinates.
-->
<mesh>
<uri>assets/c4b609828a11b8387f2d49c1de4bd37e911767c38f948144f84a0fc9c29a9a54.dae</uri>
</mesh>
</geometry>
</visual>
<!--
Mass properties: mass is in kg; pose locates and orients the centre-of-mass frame
relative to the link. Use measured or CAD-derived values.
-->
<inertial>
<mass>0.002</mass>
<!--
Inertia tensor in kg*m^2 at the centre of mass. ixx/iyy/izz are diagonal terms;
ixy/ixz/iyz are cross terms. Keep the tensor physically consistent with mass and
shape.
-->
<inertia>
<ixx>0.001</ixx>
<ixy>0</ixy>
<ixz>0</ixz>
<iyy>0.001</iyy>
<iyz>0</iyz>
<izz>0.001</izz>
</inertia>
</inertial>
</link>
<!--
Rigid body and its local coordinate frame. Geometry, mass properties and sensors
inside this link move together.
-->
<link name="thruster4">
<!--
Pose: x y z in metres, then roll pitch yaw in radians. Values use the parent frame
unless relative_to specifies another frame.
-->
<pose>-0.15 0.092 0.0 -1.571 1.571 2.356</pose>
<!--
Visible surface for rendering and cameras. Changing a visual does not automatically
resize the collision shape or change mass.
-->
<visual name="thruster_prop_visual">
<!--
Pose: x y z in metres, then roll pitch yaw in radians. Values use the parent frame
unless relative_to specifies another frame.
-->
<pose>0 0 0 1.571 0 0</pose>
<geometry>
<!--
Mesh resource and optional axis scale. Keep the exported asset path and bundle
together; scale multiplies the mesh coordinates.
-->
<mesh>
<uri>assets/c4b609828a11b8387f2d49c1de4bd37e911767c38f948144f84a0fc9c29a9a54.dae</uri>
</mesh>
</geometry>
</visual>
<!--
Mass properties: mass is in kg; pose locates and orients the centre-of-mass frame
relative to the link. Use measured or CAD-derived values.
-->
<inertial>
<mass>0.002</mass>
<!--
Inertia tensor in kg*m^2 at the centre of mass. ixx/iyy/izz are diagonal terms;
ixy/ixz/iyz are cross terms. Keep the tensor physically consistent with mass and
shape.
-->
<inertia>
<ixx>0.001</ixx>
<ixy>0</ixy>
<ixz>0</ixz>
<iyy>0.001</iyy>
<iyz>0</iyz>
<izz>0.001</izz>
</inertia>
</inertial>
</link>
<!--
Rigid body and its local coordinate frame. Geometry, mass properties and sensors
inside this link move together.
-->
<link name="thruster5">
<!--
Pose: x y z in metres, then roll pitch yaw in radians. Values use the parent frame
unless relative_to specifies another frame.
-->
<pose>0.0 -0.109 0.077 0 0 0</pose>
<!--
Visible surface for rendering and cameras. Changing a visual does not automatically
resize the collision shape or change mass.
-->
<visual name="thruster_prop_visual">
<!--
Pose: x y z in metres, then roll pitch yaw in radians. Values use the parent frame
unless relative_to specifies another frame.
-->
<pose>0 0 0 -1.571 0 1.571</pose>
<geometry>
<!--
Mesh resource and optional axis scale. Keep the exported asset path and bundle
together; scale multiplies the mesh coordinates.
-->
<mesh>
<uri>assets/4c4ae10284584339de36be62165caca9464a8df8ec1e81567d08180b3531d643.dae</uri>
</mesh>
</geometry>
</visual>
<!--
Mass properties: mass is in kg; pose locates and orients the centre-of-mass frame
relative to the link. Use measured or CAD-derived values.
-->
<inertial>
<mass>0.002</mass>
<!--
Inertia tensor in kg*m^2 at the centre of mass. ixx/iyy/izz are diagonal terms;
ixy/ixz/iyz are cross terms. Keep the tensor physically consistent with mass and
shape.
-->
<inertia>
<ixx>0.001</ixx>
<ixy>0</ixy>
<ixz>0</ixz>
<iyy>0.001</iyy>
<iyz>0</iyz>
<izz>0.001</izz>
</inertia>
</inertial>
</link>
<!--
Rigid body and its local coordinate frame. Geometry, mass properties and sensors
inside this link move together.
-->
<link name="thruster6">
<!--
Pose: x y z in metres, then roll pitch yaw in radians. Values use the parent frame
unless relative_to specifies another frame.
-->
<pose>0.0 0.109 0.077 0 0 0</pose>
<!--
Visible surface for rendering and cameras. Changing a visual does not automatically
resize the collision shape or change mass.
-->
<visual name="thruster_prop_visual">
<!--
Pose: x y z in metres, then roll pitch yaw in radians. Values use the parent frame
unless relative_to specifies another frame.
-->
<pose>0 0 0 1.571 0 1.571</pose>
<geometry>
<!--
Mesh resource and optional axis scale. Keep the exported asset path and bundle
together; scale multiplies the mesh coordinates.
-->
<mesh>
<uri>assets/c4b609828a11b8387f2d49c1de4bd37e911767c38f948144f84a0fc9c29a9a54.dae</uri>
</mesh>
</geometry>
</visual>
<!--
Mass properties: mass is in kg; pose locates and orients the centre-of-mass frame
relative to the link. Use measured or CAD-derived values.
-->
<inertial>
<mass>0.002</mass>
<!--
Inertia tensor in kg*m^2 at the centre of mass. ixx/iyy/izz are diagonal terms;
ixy/ixz/iyz are cross terms. Keep the tensor physically consistent with mass and
shape.
-->
<inertia>
<ixx>0.001</ixx>
<ixy>0</ixy>
<ixz>0</ixz>
<iyy>0.001</iyy>
<iyz>0</iyz>
<izz>0.001</izz>
</inertia>
</inertial>
</link>
<!--
Joint connecting parent and child links. fixed locks their relative motion; revolute
permits rotation about axis/xyz. Preserve names used by thruster and controller
plugins.
-->
<joint name="thruster1_joint" type="revolute">
<parent>base_link</parent>
<child>thruster1</child>
<axis>
<xyz>0 0 -1</xyz>
</axis>
</joint>
<!--
Joint connecting parent and child links. fixed locks their relative motion; revolute
permits rotation about axis/xyz. Preserve names used by thruster and controller
plugins.
-->
<joint name="thruster2_joint" type="revolute">
<parent>base_link</parent>
<child>thruster2</child>
<axis>
<xyz>0 0 -1</xyz>
</axis>
</joint>
<!--
Joint connecting parent and child links. fixed locks their relative motion; revolute
permits rotation about axis/xyz. Preserve names used by thruster and controller
plugins.
-->
<joint name="thruster3_joint" type="revolute">
<parent>base_link</parent>
<child>thruster3</child>
<axis>
<xyz>0 0 -1</xyz>
</axis>
</joint>
<!--
Joint connecting parent and child links. fixed locks their relative motion; revolute
permits rotation about axis/xyz. Preserve names used by thruster and controller
plugins.
-->
<joint name="thruster4_joint" type="revolute">
<parent>base_link</parent>
<child>thruster4</child>
<axis>
<xyz>0 0 -1</xyz>
</axis>
</joint>
<!--
Joint connecting parent and child links. fixed locks their relative motion; revolute
permits rotation about axis/xyz. Preserve names used by thruster and controller
plugins.
-->
<joint name="thruster5_joint" type="revolute">
<parent>base_link</parent>
<child>thruster5</child>
<axis>
<xyz>0 0 -1</xyz>
</axis>
</joint>
<!--
Joint connecting parent and child links. fixed locks their relative motion; revolute
permits rotation about axis/xyz. Preserve names used by thruster and controller
plugins.
-->
<joint name="thruster6_joint" type="revolute">
<parent>base_link</parent>
<child>thruster6</child>
<axis>
<xyz>0 0 -1</xyz>
</axis>
</joint>
<!--
Loaded engine plugin. filename identifies an installed library and name selects its
implementation. Preserve both when uploading numeric edits; an SDF file does not
install plugins.
-->
<!--
Propeller thrust model: fluid_density is kg/m^3, propeller_diameter is metres, and
thrust_coefficient relates angular speed to thrust. use_angvel_cmd selects rad/s
commands when true, or force in N when false.
-->
<plugin filename="gz-sim-thruster-system" name="gz::sim::systems::Thruster">
<namespace>bluerov2</namespace>
<joint_name>thruster1_joint</joint_name>
<thrust_coefficient>0.02</thrust_coefficient>
<fluid_density>1025.0</fluid_density>
<propeller_diameter>0.1</propeller_diameter>
<velocity_control>true</velocity_control>
<use_angvel_cmd>False</use_angvel_cmd>
</plugin>
<!--
Loaded engine plugin. filename identifies an installed library and name selects its
implementation. Preserve both when uploading numeric edits; an SDF file does not
install plugins.
-->
<!--
Propeller thrust model: fluid_density is kg/m^3, propeller_diameter is metres, and
thrust_coefficient relates angular speed to thrust. use_angvel_cmd selects rad/s
commands when true, or force in N when false.
-->
<plugin filename="gz-sim-thruster-system" name="gz::sim::systems::Thruster">
<namespace>bluerov2</namespace>
<joint_name>thruster2_joint</joint_name>
<thrust_coefficient>0.02</thrust_coefficient>
<fluid_density>1025.0</fluid_density>
<propeller_diameter>0.1</propeller_diameter>
<velocity_control>true</velocity_control>
<use_angvel_cmd>False</use_angvel_cmd>
</plugin>
<!--
Loaded engine plugin. filename identifies an installed library and name selects its
implementation. Preserve both when uploading numeric edits; an SDF file does not
install plugins.
-->
<!--
Propeller thrust model: fluid_density is kg/m^3, propeller_diameter is metres, and
thrust_coefficient relates angular speed to thrust. use_angvel_cmd selects rad/s
commands when true, or force in N when false.
-->
<plugin filename="gz-sim-thruster-system" name="gz::sim::systems::Thruster">
<namespace>bluerov2</namespace>
<joint_name>thruster3_joint</joint_name>
<thrust_coefficient>-0.02</thrust_coefficient>
<fluid_density>1025.0</fluid_density>
<propeller_diameter>0.1</propeller_diameter>
<velocity_control>true</velocity_control>
<use_angvel_cmd>False</use_angvel_cmd>
</plugin>
<!--
Loaded engine plugin. filename identifies an installed library and name selects its
implementation. Preserve both when uploading numeric edits; an SDF file does not
install plugins.
-->
<!--
Propeller thrust model: fluid_density is kg/m^3, propeller_diameter is metres, and
thrust_coefficient relates angular speed to thrust. use_angvel_cmd selects rad/s
commands when true, or force in N when false.
-->
<plugin filename="gz-sim-thruster-system" name="gz::sim::systems::Thruster">
<namespace>bluerov2</namespace>
<joint_name>thruster4_joint</joint_name>
<thrust_coefficient>-0.02</thrust_coefficient>
<fluid_density>1025.0</fluid_density>
<propeller_diameter>0.1</propeller_diameter>
<velocity_control>true</velocity_control>
<use_angvel_cmd>False</use_angvel_cmd>
</plugin>
<!--
Loaded engine plugin. filename identifies an installed library and name selects its
implementation. Preserve both when uploading numeric edits; an SDF file does not
install plugins.
-->
<!--
Propeller thrust model: fluid_density is kg/m^3, propeller_diameter is metres, and
thrust_coefficient relates angular speed to thrust. use_angvel_cmd selects rad/s
commands when true, or force in N when false.
-->
<plugin filename="gz-sim-thruster-system" name="gz::sim::systems::Thruster">
<namespace>bluerov2</namespace>
<joint_name>thruster5_joint</joint_name>
<thrust_coefficient>0.02</thrust_coefficient>
<fluid_density>1025.0</fluid_density>
<propeller_diameter>0.1</propeller_diameter>
<velocity_control>true</velocity_control>
<use_angvel_cmd>False</use_angvel_cmd>
</plugin>
<!--
Loaded engine plugin. filename identifies an installed library and name selects its
implementation. Preserve both when uploading numeric edits; an SDF file does not
install plugins.
-->
<!--
Propeller thrust model: fluid_density is kg/m^3, propeller_diameter is metres, and
thrust_coefficient relates angular speed to thrust. use_angvel_cmd selects rad/s
commands when true, or force in N when false.
-->
<plugin filename="gz-sim-thruster-system" name="gz::sim::systems::Thruster">
<namespace>bluerov2</namespace>
<joint_name>thruster6_joint</joint_name>
<thrust_coefficient>-0.02</thrust_coefficient>
<fluid_density>1025.0</fluid_density>
<propeller_diameter>0.1</propeller_diameter>
<velocity_control>true</velocity_control>
<use_angvel_cmd>False</use_angvel_cmd>
</plugin>
<!--
Loaded engine plugin. filename identifies an installed library and name selects its
implementation. Preserve both when uploading numeric edits; an SDF file does not
install plugins.
-->
<!--
ArduPilot simulator connection: network endpoint, lock-step timing, coordinate
transforms and IMU name. Preserve these connections when adjusting the vehicle's
physical parameters.
-->
<plugin name="ArduPilotPlugin" filename="libArduPilotPlugin.so">
<fdm_addr>127.0.0.1</fdm_addr>
<fdm_port_in>9002</fdm_port_in>
<connectionTimeoutMaxCount>5</connectionTimeoutMaxCount>
<lock_step>1</lock_step>
<modelXYZToAirplaneXForwardZDown>0 0 0 3.142 0 0</modelXYZToAirplaneXForwardZDown>
<gazeboXYZToNED>0 0 0 3.142 0 1.571</gazeboXYZToNED>
<imuName>imu_sensor</imuName>
<!--
Maps one controller channel to a joint command topic. servo_min/max define its input
range; offset and multiplier set the output offset and scale. Retain the channel and
topic mapping.
-->
<control channel="0">
<jointName>thruster1_joint</jointName>
<servo_min>1100</servo_min>
<servo_max>1900</servo_max>
<type>COMMAND</type>
<cmd_topic>/model/bluerov2/joint/thruster1_joint/cmd_thrust</cmd_topic>
<offset>-0.5</offset>
<multiplier>100</multiplier>
</control>
<!--
Maps one controller channel to a joint command topic. servo_min/max define its input
range; offset and multiplier set the output offset and scale. Retain the channel and
topic mapping.
-->
<control channel="1">
<jointName>thruster2_joint</jointName>
<servo_min>1100</servo_min>
<servo_max>1900</servo_max>
<type>COMMAND</type>
<cmd_topic>/model/bluerov2/joint/thruster2_joint/cmd_thrust</cmd_topic>
<offset>-0.5</offset>
<multiplier>100</multiplier>
</control>
<!--
Maps one controller channel to a joint command topic. servo_min/max define its input
range; offset and multiplier set the output offset and scale. Retain the channel and
topic mapping.
-->
<control channel="2">
<jointName>thruster3_joint</jointName>
<servo_min>1100</servo_min>
<servo_max>1900</servo_max>
<type>COMMAND</type>
<cmd_topic>/model/bluerov2/joint/thruster3_joint/cmd_thrust</cmd_topic>
<offset>-0.5</offset>
<multiplier>100</multiplier>
</control>
<!--
Maps one controller channel to a joint command topic. servo_min/max define its input
range; offset and multiplier set the output offset and scale. Retain the channel and
topic mapping.
-->
<control channel="3">
<jointName>thruster4_joint</jointName>
<servo_min>1100</servo_min>
<servo_max>1900</servo_max>
<type>COMMAND</type>
<cmd_topic>/model/bluerov2/joint/thruster4_joint/cmd_thrust</cmd_topic>
<offset>-0.5</offset>
<multiplier>100</multiplier>
</control>
<!--
Maps one controller channel to a joint command topic. servo_min/max define its input
range; offset and multiplier set the output offset and scale. Retain the channel and
topic mapping.
-->
<control channel="4">
<jointName>thruster5_joint</jointName>
<servo_min>1100</servo_min>
<servo_max>1900</servo_max>
<type>COMMAND</type>
<cmd_topic>/model/bluerov2/joint/thruster5_joint/cmd_thrust</cmd_topic>
<offset>-0.5</offset>
<multiplier>100</multiplier>
</control>
<!--
Maps one controller channel to a joint command topic. servo_min/max define its input
range; offset and multiplier set the output offset and scale. Retain the channel and
topic mapping.
-->
<control channel="5">
<jointName>thruster6_joint</jointName>
<servo_min>1100</servo_min>
<servo_max>1900</servo_max>
<type>COMMAND</type>
<cmd_topic>/model/bluerov2/joint/thruster6_joint/cmd_thrust</cmd_topic>
<offset>-0.5</offset>
<multiplier>100</multiplier>
</control>
</plugin>
<!--
Loaded engine plugin. filename identifies an installed library and name selects its
implementation. Preserve both when uploading numeric edits; an SDF file does not
install plugins.
-->
<!--
Publishes simulated odometry with the configured frames and frequency in Hz. These
values describe simulator state; use the sensor topics for simulated measurements.
-->
<plugin filename="gz-sim-odometry-publisher-system" name="gz::sim::systems::OdometryPublisher">
<odom_frame>map</odom_frame>
<robot_base_frame>base_link</robot_base_frame>
<dimensions>3</dimensions>
<odom_publish_frequency>100</odom_publish_frequency>
</plugin>
<!--
Loaded engine plugin. filename identifies an installed library and name selects its
implementation. Preserve both when uploading numeric edits; an SDF file does not
install plugins.
-->
<plugin filename="gz-sim-joint-state-publisher-system" name="gz::sim::systems::JointStatePublisher">
</plugin>
<!--
Loaded engine plugin. filename identifies an installed library and name selects its
implementation. Preserve both when uploading numeric edits; an SDF file does not
install plugins.
-->
<plugin filename="gz-sim-imu-system" name="gz::sim::systems::Imu">
</plugin>
<!--
Loaded engine plugin. filename identifies an installed library and name selects its
implementation. Preserve both when uploading numeric edits; an SDF file does not
install plugins.
-->
<plugin filename="gz-waves1-hydrodynamics-system" name="gz::sim::systems::Hydrodynamics">
<enable>bluerov2::base_link</enable>
<!--
Water-force coefficients. damping_on, viscous_drag_on and pressure_drag_on enable
their respective terms. cDampL/R tune linear/angular damping; pressure-drag
coefficients use this plugin's model and are not interchangeable with other solvers.
-->
<hydrodynamics>
<damping_on>1</damping_on>
<viscous_drag_on>0</viscous_drag_on>
<pressure_drag_on>0</pressure_drag_on>
<cDampL1>.1</cDampL1>
<cDampL2>40</cDampL2>
<cDampR1>.1</cDampR1>
<cDampR2>4</cDampR2>
</hydrodynamics>
</plugin>
<!--
Rigid body and its local coordinate frame. Geometry, mass properties and sensors
inside this link move together.
-->
<link name="gnss_link">
<!--
Pose: x y z in metres, then roll pitch yaw in radians. Values use the parent frame
unless relative_to specifies another frame.
-->
<pose relative_to="base_link">0 0 0.3 0 0 0</pose>
<!--
Mass properties: mass is in kg; pose locates and orients the centre-of-mass frame
relative to the link. Use measured or CAD-derived values.
-->
<inertial>
<mass>.001</mass>
<!--
Inertia tensor in kg*m^2 at the centre of mass. ixx/iyy/izz are diagonal terms;
ixy/ixz/iyz are cross terms. Keep the tensor physically consistent with mass and
shape.
-->
<inertia>
<ixx>0.000001</ixx>
<iyy>0.000001</iyy>
<izz>0.000001</izz>
</inertia>
</inertial>
<!--
Sensor attached to this link. Its pose sets the mounting position; type selects the
measurement implementation. The builder also prepares topic routes and required world
systems.
-->
<sensor name="gnss" type="custom" gz:type="posim_gnss">
<always_on>true</always_on>
<!--
Requested sensor update frequency in Hz. Delivered rate also depends on simulation
speed and rendering load.
-->
<update_rate>5</update_rate>
<!--
Gazebo Transport output topic. Keep it aligned with the exported sensor manifest and
ROS bridge routes.
-->
<topic>/model/bluerov2/gnss</topic>
</sensor>
</link>
<!--
Joint connecting parent and child links. fixed locks their relative motion; revolute
permits rotation about axis/xyz. Preserve names used by thruster and controller
plugins.
-->
<joint name="gnss_joint" type="fixed">
<parent>base_link</parent>
<child>gnss_link</child>
</joint>
<!--
Loaded engine plugin. filename identifies an installed library and name selects its
implementation. Preserve both when uploading numeric edits; an SDF file does not
install plugins.
-->
<!--
GNSS receiver model. update_rate is Hz; latency and reacquire_seconds are seconds.
Position noise and dry_margin use metres; velocity_stddev uses m/s. link_name, topic
and wave_topic connect the antenna, output and water-surface input.
-->
<plugin name="posim::Gnss" filename="libposim_gnss.so">
<update_rate>5</update_rate>
<latency>0.2</latency>
<reacquire_seconds>3</reacquire_seconds>
<dry_margin>0.05</dry_margin>
<horizontal_stddev>0.7</horizontal_stddev>
<vertical_stddev>1.2</vertical_stddev>
<velocity_stddev>0.1</velocity_stddev>
<water_level>0</water_level>
<seed>42</seed>
<enabled>true</enabled>
<link_name>gnss_link</link_name>
<topic>/model/bluerov2/gnss</topic>
<wave_topic>/wwos/wave_surface</wave_topic>
</plugin>
</model>
</sdf>
Transfer the configuration
Export ZIP includes SDF, meshes, recipe and sensor manifest. Import vehicle rebuilds the installed template and validates the SDF edits against it, preserving supported numeric changes. Different engine versions or missing providers may require regeneration. Use Edit a copy and reapply your edits after exporting the compatible template.
For general mesh uploads, continue with the model-format reference below.
Model upload format
Upload a model
Upload an SDF file or a ZIP with SDF and meshes.
| Limit | Web | Desktop |
|---|---|---|
| File upload | 20 MB | 200 MB |
| Expanded contents | 50 MB | 500 MB |
| Root SDF | 1 MB | 1 MB |
Use relative mesh paths within the ZIP. Include links, collision geometry and inertia. Validation checks archive paths and supported plugins; external executables are rejected.
Choose the uploaded revision when starting a new world. Sensor/mount changes require restarting the world. Wait until queued or active sessions finish before archiving their model revision. Archiving hides the revision from the list and keeps its stored data.
Change mass and inertia
Edit the SDF in the robot editor. Check mass, center of mass, inertia tensor, collision shape and mesh scale together. Save a new revision, then test a short stationary and low-speed run before a longer route. An unrealistically small inertia tensor can cause rapid motion or instability even if the mesh looks correct.
<inertial>
<mass>12.0</mass>
<inertia>
<ixx>0.22</ixx><iyy>0.35</iyy><izz>0.40</izz>
<ixy>0</ixy><ixz>0</ixz><iyz>0</iyz>
</inertia>
</inertial>
These numbers are an illustrative syntax example, not a calibrated model. Use measured dimensions/mass or a CAD calculation. Validate inertia for positive definiteness and units in kg·m².
Add sensors or ROS packages
Define sensor placement and settings in SDF, then start a new session. The sensor tree displays generated topics. Configure Autopilot and thruster connections in the runtime profile.
Run autonomy code and ROS dependencies locally through the Control an installed workspace. Native plugins or server ROS nodes require a runtime profile with compatible dependencies.
Storage
Models, source ZIPs and revisions count towards account storage limits, including archived files. Remove duplicate meshes and unnecessary assets to fit the upload limit.
Use Archive / Restore in Manage saved terrain and vehicles to change visibility of account terrain and robot entries. Use export/import to move a vehicle to another host.
Autopilot parameters
Disarm before changing Autopilot values in ArduPilot parameters, then read them back. See Autopilot parameters.
Use your own STL
Export a closed, triangulated STL from CAD and place it next to model.sdf in a ZIP:
my-robot.zip
model.sdf
meshes/hull.stl
STL does not carry units. Export in metres, or set an explicit scale (for example 0.001 0.001 0.001 for millimetres). Reference the bundled file from a visual:
<visual name="hull_visual">
<geometry><mesh>
<uri>meshes/hull.stl</uri>
<scale>1 1 1</scale>
</mesh></geometry>
</visual>
Use boxes, cylinders or a reduced closed mesh for collision. Define mass and inertia in the link's <inertial>. Include sensors, actuators and hydrodynamics in SDF/runtime configuration, then connect the controller to command topics.
Upload in Workspace → Robots and check validation. Select the saved revision when starting a world.
- Browser: converts validated STL for display
- Gazebo: uses original geometry
- Format SDF: indents XML; preserves attributes, paths and comments
- Invalid XML: preserves editor contents
Multiple vehicles
A personal workspace runs one vehicle at a time. The WAM-V pair in LIVE world voyage uses a dedicated configuration; the workspace does not provide a general fleet editor.