Add DVL and DVLBeam messages issue ros#116

sensor_msgs/CMakeLists.txt

@@ -15,6 +15,8 @@ add_message_files(
   CameraInfo.msg
   ChannelFloat32.msg
   CompressedImage.msg
+  DVL.msg
+  DVLBeam.msg
   FluidPressure.msg
   Illuminance.msg
   Image.msg

sensor_msgs/msg/DVL.msg

@@ -0,0 +1,33 @@
+# Based on UUV Simulator:
+#   https://github.com/uuvsimulator/uuv_simulator
+
+# This is a message to hold data from a DVL sensor (Doppler Velocity Log).
+#
+# Distances are in [m], velocities in [m/s]
+#
+# If the covariance is known, it should be filled.
+# If it is unknown, it should be set to all zeros.
+# If a measurement was invalid, its covariance should be set to -1 so it can be
+# disregarded.
+
+Header header
+
+# Measured velocity [m/s] in sensor frame
+geometry_msgs/Vector3 velocity
+
+# Row major, xyz axes
+float64[9] velocity_covariance
+
+# Bottom range
+float64 range
+
+# Instrument reference data
+uint8 VELOCITY_REFERENCE_UNKNOWN = 0
+uint8 VELOCITY_REFERENCE_WATER = 1
+uint8 VELOCITY_REFERENCE_BOTTOM = 2
+
+uint8 velocity_reference
+
+# DVLBeams are optional. If they are set they contain individual ranges and 1D
+# doppler velocity estimates orthogonal to the ray.
+DVLBeam[] beams

sensor_msgs/msg/DVLBeam.msg

@@ -0,0 +1,17 @@
+# Original from UUV Simulator:
+#   https://github.com/uuvsimulator/uuv_simulator
+
+string frame_id           # Beam frame (defined as a TF wrt DVL frame)
+
+float64 range             # measured range [m] or < 0 if invalid
+float64 range_covariance
+
+float64 velocity          # measured velocity [m/s] of corr. beam
+float64 velocity_covariance
+
+float32 field_of_view     # the size of the arc that the distance reading is
+                          # valid for [rad]
+                          # the object causing the range reading may have
+                          # been anywhere within -field_of_view/2 and
+                          # field_of_view/2 at the measured range.
+                          # 0 angle corresponds to the x-axis of the sensor.