Commit Graph

49 Commits

Author SHA1 Message Date
Iampete1 8fe120b3d7 AP_RangeFinder: skip GPIO arming check on analog backend 2023-01-10 10:14:11 +09:00
Henry Wurzburg a46c774698 AP_RangeFinder: add TeraRange Neo Rangefinder 2022-08-09 09:01:34 +10:00
Peter Barker 7e5808a97b AP_RangeFinder: add prearm for analogue/pwm pin conflicts 2022-07-22 09:09:25 +10:00
Peter Barker ffc4910c7e AP_RangeFinder: reduce verbiage when detecting serial rangefinders 2022-07-13 18:39:06 +10:00
Peter Barker deba0b712b AP_RangeFinder: correct creation/use of TFMINI_ADDR_DEFAULT
Named incorrectly and defined in wrong file...
2022-06-21 09:15:20 +10:00
Peter Barker 3a347d32ca AP_RangeFinder: allow rangefinder backends to be individually compiled in 2022-06-21 09:15:20 +10:00
Andrew Tridgell 5413893c91 AP_RangeFinder: fixed use of configured() vs configured_in_storage() 2022-06-06 13:11:50 +10:00
Peter Barker 51246fda45 AP_RangeFinder: enable SITL rangefinder for sim-on-hardware 2022-05-24 10:38:57 +10:00
Peter Barker cef436b272 AP_RangeFinder: implement distance_cm_orient in terms of distance_orient 2022-05-03 09:23:37 +10:00
Peter Barker 414d3d27db AP_RangeFinder: add PARAMETER CONVERSION comments 2022-04-28 10:17:11 +10:00
Henry Wurzburg 8ab92f42cd AP_RangeFinder: add build option for Rangefinders 2022-03-08 14:33:38 -08:00
Peter Barker 8973dfa8e0 AP_RangeFinder: use HAL_LOGGING_ENABLED in place of HAL_BUILD_AP_PERIPH 2021-12-14 10:34:06 +11:00
Shiv Tyagi e1a528213d AP_Rangefinder: Use default address for TFMiniPlus I2C unless configured
This fixes the issue #13419. If RNGFNDx_ADDR is not configured, it uses default address for TFmini i2c
2021-11-30 10:09:24 +11:00
Andrew Tridgell 3f85eab272 AP_RangeFinder: added Benewake CAN Lidars
includes support for setting CAN ID and min SNR
2021-11-30 09:49:20 +11:00
Shiv Tyagi 516eafa45b AP_Rangefinder: fail RF prearm checks for NoData/NotConnected statuses
Earlier we only failed RF checks if we could not detect an RF instance but we should also fail it if the RF is not connected or we receive no data.
2021-11-13 09:47:39 +09:00
Andrew Tridgell 4f2bec72b6 AP_RangeFinder: rename uLanding to USD1_Serial
this was rebranded by the vendor Ainstein a long time ago
2021-10-26 15:31:12 +11:00
Andy Piper a2bb0b01e8 AP_RangeFinder: convert APM_BUILD_COPTER_OR_HELI() to APM_BUILD_COPTER_OR_HELI 2021-10-26 11:42:12 +11:00
Sebastian Quilter 0f7c3e3964 AP_RangeFinder: make rangefinder ranges m rather than cm 2021-10-21 21:28:53 +11:00
Gone4Dirt e0af10886b AP_RangeFinder: Add APM_BUILD_Heli 2021-09-29 19:55:48 +10:00
Pierre Kancir bcfb07b39f AP_Rangefinder: fix override in constructor 2021-08-26 21:48:19 +10:00
bugobliterator e51d358552 AP_RangeFinder: use typename SIM instead of SITL as it conflicts with namespace name 2021-08-05 07:25:31 +10:00
Siddharth Purohit 0795225475 AP_RangeFinder: Use HAL_CANMANAGER_ENABLED instead of HAL_ENABLE_LIBUAVCAN_DRIVERS 2021-06-24 09:02:42 +10:00
Pierre Kancir 88b5ff8c6f AP_Rangefinder: make get_temp const 2021-06-09 10:52:00 +09:00
Randy Mackay fee30b4447 AP_RangeFinder: add get_temp and implement for NMEA driver 2021-04-20 09:17:48 +10:00
Patrick José Pereira efffed0510 AP_RangeFinder: Add missing const in member functions
Signed-off-by: Patrick José Pereira <patrickelectric@gmail.com>
2021-02-03 18:45:14 +11:00
Peter Barker 78b49a2c35 AP_RangeFinder: maxbotix: use i2c-address parameter 2021-01-19 11:20:47 +11:00
Andrew Tridgell 66c05bef76 AP_RangeFinder: added USD1 CAN driver
also known as uLanding CAN
2021-01-01 17:29:54 +11:00
Peter Barker 1c57eed66c AP_RangeFinder: remove unused voltage_mv_orient method
This is really backend-specific data and shouldn't be exposed
2020-12-06 16:49:43 +11:00
Andrew Tridgell 0c05e9a2e7 AP_RangeFinder: fixed handling of instance numbers
if a backend allocation failed then we could end up with the backend
being assigned to the wrong instance number. Switch to using
_add_backend() everywhere, and pass the instance number to
_add_backend() to ensure that it always uses the correct slot.

Also added comment explaining how num_sensors() works when we have a
sparse set of rangefinders configured
2020-12-01 10:53:08 +11:00
murata bbc673c668 AP_RangeFinder: Change rangefinder number 10 to A 2020-11-17 11:46:25 +11:00
Peter Barker dd8361ba33 AP_RangeFinder: remove default case from Rangefinder init switch
Allows the compiler to help the programmer fill in required code
2020-09-10 20:52:06 +10:00
yaapu bc21e505e3 AP_RangeFinder: aligned msp message data struct name to gps,baro and mag 2020-09-09 06:35:50 +10:00
Andrew Tridgell 84f7589f2d AP_RangeFinder: allow separate enable of MSP rangefinder 2020-09-02 05:56:46 +10:00
yaapu 699ffcbcd2 AP_RangeFinder: added support for MSP based range finders 2020-09-02 05:56:46 +10:00
Siddharth Purohit 6ef85dd7eb AP_RangeFinder: use AP_CANManager library 2020-08-19 17:31:09 +10:00
Iampete1 e18c195df4 AP_RangeFinder: add SITL backend 2020-08-05 18:24:36 +10:00
Peter Barker 6ec497229b AP_RangeFinder: add serial support for GY-US42v2 rangefinder 2020-07-04 13:40:10 +10:00
Peter Barker fc1ea612b1 AP_RangeFinder: add support for HC-SR04 rangefinder 2020-06-02 09:58:53 +10:00
Andrew Tridgell d16f31711e AP_RangeFinder: fixed mixing UAVCAN and non-UAVCAN rangefinders
UAVCAN rangefinders add themselves to the frontend drivers as the
devices appear. If they turn up before RangeFinder::init() is run then
this prevented init() from scanning for the other rangefinders as
num_instances is non-zero

This also fixes a race condition in updating num_instances in the
UAVCAN backend
2020-05-12 09:45:15 +10:00
Andrew Tridgell ffe9fa22a1 AP_RangeFinder: invalidate param count when changing param tree structure 2020-04-29 07:36:55 +10:00
Peter Barker b7a03ae5ad AP_RangeFinder: rename APMrover2 to Rover 2020-04-14 09:50:34 +09:00
Randy Mackay f269004610 AP_RangeFinder: fix detect for LeddarVu8
Co-Authored-By: Peter Barker <pb-gh@barker.dropbear.id.au>
2020-01-23 16:24:33 +11:00
Randy Mackay b068f15932 AP_RangeFinder: LeddarVu8 driver 2020-01-23 16:24:33 +11:00
Michael du Breuil d92c4dc892 AP_Rangefinder: Fix bad subgroup pointer for drivers 2020-01-15 12:13:44 +11:00
Michael du Breuil 8bd4f2b097 AP_RangeFinder: Allow the VL53L1X to be put into short range mode 2019-12-24 11:40:47 +11:00
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
2019-12-03 13:06:10 +08:00
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)
2019-12-03 13:06:10 +08:00
Peter Barker 35e987c663 AP_RangeFinder: adjust for renaming of RangeFinder files 2019-11-12 07:14:37 +08:00
Peter Barker 7c9ab0203d AP_RangeFinder: rename source files to include AP_ prefix
This makes them look like most of our libraries
2019-11-12 07:14:37 +08:00