From 57277ed37f3e028b1b7660e0904703261da89fb0 Mon Sep 17 00:00:00 2001 From: Juan Pablo Pino Bravo Date: Wed, 28 Oct 2026 14:11:48 +0100 Subject: [PATCH] Add the dive number and logfile name to DroneInfo Lets recordings that store DroneInfoTel (e.g. .mbez multibeam files) be tied back to the dive logfile they were recorded in. log_name stays unique when the dive counter restarts, e.g. after the storage is replaced. Co-Authored-By: Claude Opus 5.5 --- protobuf_definitions/message_formats.proto | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/protobuf_definitions/message_formats.proto b/protobuf_definitions/message_formats.proto index a1717b4c..e30431be 100644 --- a/protobuf_definitions/message_formats.proto +++ b/protobuf_definitions/message_formats.proto @@ -1045,6 +1045,10 @@ message DroneInfo { repeated CvModelInfo cv_models = 12; // Installed computer vision models, including models that are not running. PowerSource power_source = 13; // How the drone is powered. CameraCalibration main_camera_calibration = 14; // Intrinsic calibration of the main camera. Unset when unknown. + uint32 dive_number = 15; // Dive number, the counter at the end of the logfile name. 0 when unknown. + // Name of the dive logfile without extension (e.g. BYEDP070012_ea9ac92e040aa9d4_00231). + // Unlike dive_number it stays unique when the counter restarts, e.g. after the storage is replaced. + string log_name = 16; } // Known error states for the drone.