From a11ef6be107035428a80b83b9ff66b15ee73f993 Mon Sep 17 00:00:00 2001 From: Mohammed Kabir Date: Tue, 23 May 2017 18:12:57 +0200 Subject: [PATCH] lis3mdl : fill device ID, scale and range into uORB topic properly --- src/drivers/lis3mdl/lis3mdl.cpp | 3 +++ 1 file changed, 3 insertions(+) diff --git a/src/drivers/lis3mdl/lis3mdl.cpp b/src/drivers/lis3mdl/lis3mdl.cpp index cdf4cbf698..32a3989282 100644 --- a/src/drivers/lis3mdl/lis3mdl.cpp +++ b/src/drivers/lis3mdl/lis3mdl.cpp @@ -911,6 +911,9 @@ LIS3MDL::collect() /* this should be fairly close to the end of the measurement, so the best approximation of the time */ new_report.timestamp = hrt_absolute_time(); new_report.error_count = perf_event_count(_comms_errors); + new_report.range_ga = _range_ga; + new_report.scaling = _range_scale; + new_report.device_id = _device_id.devid; /* * @note We could read the status register here, which could tell us that