Conversation
marinauterion
force-pushed
the
driver-airspeed-sensor-dlvr
branch
5 times, most recently
from
bb6c335 to
33cb129
Compare
|
|
||
| #define M_DEG_TO_RAD 0.017453292519943295 | ||
| #define M_RAD_TO_DEG 57.295779513082323 | ||
| #define M_INH_TO_PA 249.089f |
There was a problem hiding this comment.
It looks like it isn't lining up the value with the values on the previous lines
| @@ -0,0 +1,44 @@ | |||
| ############################################################################ | |||
| # | |||
| # Copyright (c) 2015-2024 PX4 Development Team. All rights reserved. | |||
There was a problem hiding this comment.
Should copyright years be refined here? Just 2026, or maybe 2025 - 2026?
marinauterion
force-pushed
the
driver-airspeed-sensor-dlvr
branch
4 times, most recently
from
b8b4861 to
08885af
Compare
marinauterion
force-pushed
the
driver-airspeed-sensor-dlvr
branch
2 times, most recently
from
f9f2091 to
0602879
Compare
Signed-off-by: Marin Doetterer <marin@auterion.com>
marinauterion
force-pushed
the
driver-airspeed-sensor-dlvr
branch
from
0602879 to
1e8139d
Compare
There was a problem hiding this comment.
Can you also update https://docs.px4.io/main/en/sensor/airspeed#hardware-options and https://docs.px4.io/main/en/sensor/airspeed#enable-airspeed-sensors to mention this?
Can we enhance the docs with a description? While this is the kind of docs that airspeed drivers normally have, I think the model here is better https://docs.px4.io/main/en/modules/modules_driver_distance_sensor#leddar-one
Specifically, having a description section that includes what the part is (with a link) and minimally what parameter is used to enable it.
3 participants
This driver does support dlvr-sensors that are using continuous sampling
Tested:
Sensor: DLVR-L10D NI3N on
Hardware: Auterion Skynode-X (fmu-v6x)