Randy Mackay
f269004610
AP_RangeFinder: fix detect for LeddarVu8
...
Co-Authored-By: Peter Barker <pb-gh@barker.dropbear.id.au>
5 years ago
Randy Mackay
b068f15932
AP_RangeFinder: LeddarVu8 driver
5 years ago
Michael du Breuil
d92c4dc892
AP_Rangefinder: Fix bad subgroup pointer for drivers
5 years ago
Michael du Breuil
8bd4f2b097
AP_RangeFinder: Allow the VL53L1X to be put into short range mode
5 years ago
Randy Mackay
e12e0d95ae
AP_RangeFinder: remove param conversion for 3rd and 4th
...
3rd and 4th instances were not available to users unless they used their own builds which is rare
this reduces the firmware's flash size a small amount
5 years ago
Randy Mackay
1b84c8132e
AP_RangeFinder: param conversion fix
...
This resolves an issue with the parameter conversion when moving from Copter-3.6.x to 4.0 (and similar moves for other vehicle types)
5 years ago
Peter Barker
35e987c663
AP_RangeFinder: adjust for renaming of RangeFinder files
5 years ago
Peter Barker
7c9ab0203d
AP_RangeFinder: rename source files to include AP_ prefix
...
This makes them look like most of our libraries
5 years ago
Peter Barker
acc1f955ef
AP_RangeFinder: make Benewake backend use new intermediate class
5 years ago
Peter Barker
3538fe360b
AP_RangeFinder: add intermediate serial backend class to share common code
5 years ago
Peter Barker
82db4383d4
AP_RangeFinder: use enum-class for Status
5 years ago
Peter Barker
db36ef3433
Sub: use enum-class for RangeFinder type
5 years ago
Peter Barker
ea26e94f66
AP_RangeFinder: use enum-class for RangeFinder type
5 years ago
Andrew Tridgell
76dd2f0838
AP_RangeFinder: fixed failover between rangefinders
...
this fixes the case where we have one rangefinder that can handle
short range and another that is good for long range but no good for
short range (quite common, eg radar and lidar)
If possible we want to use the first rangefinder that is in range for
the right orientation. If none are in range then use the first for the
orientation
5 years ago
Andrew Tridgell
2818151a39
AP_RangeFinder: disable some incompatible drivers for AP_Periph
5 years ago
Andrew Tridgell
ca1bd8be3c
AP_RangeFinder: disable logging for AP_Periph
5 years ago
murata
000aa4f515
AP_RangeFinder: Add TF03-180
5 years ago
Andrew Tridgell
9c900c7176
AP_RangeFinder: added driver for Lanbao CM8JL65
6 years ago
Andrew Tridgell
0f6b8375bb
AP_RangeFinder: added a 1.5 delay to probe of LW20 I2C
...
the LW20 takes a long time to boot and be ready to probe
6 years ago
Michael du Breuil
3202a2e0a6
AP_Rangefinder: Add arming checks
6 years ago
Pierre Kancir
c4ec373b20
AP_RangeFinder: pass mavlink_message_t by const reference
6 years ago
Peter Barker
ac96461c6c
AP_RangeFinder: use AP_SerialManager singleton
6 years ago
Pierre Kancir
209b0300a5
AP_Rangefinder: fix compilation for Bebop
6 years ago
Peter Barker
68d7e0c22f
AP_RangeFinder: correct macro being used for parameter definition
6 years ago
Peter Barker
8cd5e3103f
AP_RangeFinder: remove use of removed AP_PARAM_FLAG_IGNORE_ENABLE
6 years ago
Tatsuya Yamaguchi
18a43601cd
RangeFinder: Add up to 10 RangeFinder logs
6 years ago
Lucas De Marchi
b3a8496613
AP_RangeFinder: add support for Benewake TFMini Plus on I2C
...
This was tested with firmware 1.7.0 on the sensor.
6 years ago
Siddharth Purohit
479c238177
RangeFinder: add support for rangefinder sensor over can
6 years ago
Michael du Breuil
b31cd1adb5
AP_RangeFinder: Remove pre arm distance check
6 years ago
Peter Barker
dd567ad18a
AP_RangeFinder: handle RFND logging
6 years ago
Randy Mackay
5e9aebd678
AP_RangeFinder: BlueRobotics Ping driver
6 years ago
Michael du Breuil
21b64ad19b
AP_Rangefinder: Remove parameter manipulation from initializer
6 years ago
Andrew Tridgell
bf4dc2d3b7
AP_RangeFinder: probe all I2C buses for rangefinders
...
we now have flight boards with up to 4 I2C buses, and probing only 2
of them causes user confusion
6 years ago
Randy Mackay
a72477590f
AP_RangeFinder: format fixes
6 years ago
Dmitri Ranfft
5eff01a86f
RangeFinder: allow up to 10 range finders to be used at once
6 years ago
Peter Barker
d71244dd23
APM_RangeFinder: remove PX4 backend type
6 years ago
Peter Barker
f037629fc3
RangeFinder: understand stop pin for AP_RangeFinder_PWM backend
6 years ago
Nghia Nguyen
60250e4c49
AP_Rangefinder: Add support for ST VL53L1X
6 years ago
Randy Mackay
fbf072d84b
AP_RangeFinder: add range to POS param description
6 years ago
Peter Barker
6e84a31613
AP_RangeFinder: use new ChibiOS driver if user attempts to use PX4 PWM driver
6 years ago
Peter Barker
186ce80827
AP_RangeFinder: add pwm backend
6 years ago
Nghia Nguyen
513eb1f5db
AP_Rangefinder: Add support for Garmin LidarLite-V3HP
6 years ago
Randy Mackay
1b0f0a7559
AP_RangeFinder: support last_reading_ms
...
Benewake, LeddarOne, LightWareSerial, MAVLink, MaxsonarI2CXL, MaxsonarSerialLV, NMEA, PX4_PWM, uLanding and Wasp already stored the last read time so for these drivers, this change just moves that storage to the state structure
analog, BBB_PRU, Bebop, LightWareI2C, PulsedLightLRF, TeraRangerI2C, VL53L0X did not store the last read time so this was added
7 years ago
Michael du Breuil
f0a4059d73
AP_Rangefinder: Remove APM doc references
7 years ago
Michael du Breuil
fb99ea0446
AP_Rangefinder: Update WASP defaults
7 years ago
Randy Mackay
e520d4fe42
AP_RangeFinder: Benewake TF02 and TFmini lidar driver
7 years ago
Michael du Breuil
b2d8f6e788
AP_Rangefinder: Fix bad fallthrough from NMEA driver
7 years ago
Andrew Tridgell
08228efc72
AP_Rangefinder: fixed param docs for Wasp backend
7 years ago
Andrew Tridgell
3b8d5ea4cf
AP_Rangefinder: fixed param handling for Wasp backends
7 years ago
Michael du Breuil
b678302aed
AP_Rangefinder: Add WASP 200 LRF backend
7 years ago