Andrew Tridgell
5f604ff012
AP_RangeFinder: fixed legacy parsing of 65436 for lightware i2c
...
some lidars will probe as legacy protocol and return 65436 as range
2020-07-30 08:44:36 +09:00
Henry Wurzburg
df5ab0c148
AP_RangeFinder: rename Benewake types for easier identification
2020-06-13 08:21:13 +09:00
Andrew Tridgell
fb1bd4b47f
AP_RangeFinder: cope with beyond max range with LightwareI2C
2020-06-12 16:50:46 +09:00
Andrew Tridgell
8e0124f383
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
2020-02-05 11:13:30 +09:00
Randy Mackay
06f9c6a210
AP_RangeFinder: fix offset param for PWM driver
2020-02-03 19:38:59 +09:00
Randy Mackay
fc0f6297a7
AP_RangeFinder: update OFFSET param description to clarify only for analog and pwm
2020-01-31 19:50:19 +09:00
Randy Mackay
a2fdc5b428
AP_RangeFinder: PWM driver adds offset param value
2020-01-31 19:50:16 +09:00
Michael du Breuil
2c0eee390d
AP_Rangefinder: Fix bad subgroup pointer for drivers
2020-01-19 10:44:01 +09:00
Randy Mackay
d2e6df570c
AP_RangeFinder: TYPE param desc clarification for Benewake lidar
...
This renames some of the TYPE parameter's driver options:
19 :BenewakeTF02 is unchanged
20: BenewakeTFMini becomes BenewakeTFMini/Plus-Serial
25: BenewakeTFMiniPlus becomes BenewakeTFMini/Plus-I2C
27: BenewakeTF03 is unchanged
2019-12-16 14:55:07 +09:00
Randy Mackay
19f3060439
AP_RangeFinder: update Type and Pin parameter values
...
The _TYPE change is to remove the "v2" from the LidarLite description because both v2 and v3 are supported
The _PIN change is to make it more clear that any of the auxiliary pwm pins can be used for PWM input
2019-12-16 14:54:55 +09:00
Randy Mackay
f28f376f20
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-16 14:09:17 +09:00
Randy Mackay
eab638cfab
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-16 14:09:14 +09:00
Andrew Tridgell
2818151a39
AP_RangeFinder: disable some incompatible drivers for AP_Periph
2019-10-25 09:35:27 +11:00
Andrew Tridgell
ca1bd8be3c
AP_RangeFinder: disable logging for AP_Periph
2019-10-21 19:12:01 +11:00
Andrew Tridgell
282936eab2
AP_RangeFinder: allow for less rangefinder instances
...
for AP_Periph
2019-10-21 19:12:01 +11:00
murata
000aa4f515
AP_RangeFinder: Add TF03-180
2019-10-15 10:07:53 +09:00
Lucas De Marchi
7520cdef2f
AP_RangeFinder: update minimum fw version of TFMiniPlus
...
Version 2.0.3 has important fixes to avoid having the sensor to lock up.
Let's make sure we check for it and warn on console.
2019-09-23 12:56:13 +09:00
Lucas De Marchi
5f65033511
AP_RangeFinder: add missing overrides
2019-09-21 08:01:08 +10:00
Lucas De Marchi
ce877ba40a
AP_RangeFinder: fix build
2019-09-21 08:01:08 +10:00
Andrew Tridgell
54b9524c0b
AP_RangeFinder: make LightWare I2C native work with more hw versions
...
this allows the native i2c lightware driver to work with a wide range
of lidars from LightWare, removing the specific version check, and the
version specific config commands
2019-09-12 07:40:32 +10:00
Michael du Breuil
c12652b325
AP_Rangefinder: Remove stop pin usage
2019-09-04 09:54:50 +10:00
Andrew Tridgell
9c900c7176
AP_RangeFinder: added driver for Lanbao CM8JL65
2019-09-03 09:10:48 +10:00
Andrew Tridgell
172c802ffa
AP_RangeFinder: support native I2C protocol on LightWare Lidars
...
this supports both the native and the legacy I2C protocol for
LightWare Lidars. The native protocol is a string based protocol that
is enabled by default on new Lidars. By supporting both protocols we
avoid the need for users to re-configure their new lidar using a
serial cable before using it on I2C.
This driver was originally written by Mitch Koch and Jonathan
Challinger, and ported to master by me (it required only minor
changes)
2019-09-02 07:20:22 +10:00
murata
4754710e60
RangeFinder: Change to coding style (NFC)
...
RangeFinder: RangeFinder: Change to coding style (NFC)
2019-08-23 10:11:30 +09:00
murata
851ee24c99
AP_RangeFinder: Clarify the purpose of input registers
2019-08-20 14:36:29 +01:00
murata
0b1987ae36
AP_RangeFinder: Use common hexadecimal to character number conversion method
2019-08-06 10:14:12 +10:00
Randy Mackay
01a713a812
AP_RangeFinder: param desc rename from PX4-PWM to just PWM
...
the PWM driver is available for many boards
2019-08-04 21:15:49 +10:00
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
2019-07-30 13:32:36 +10:00
Michael du Breuil
3202a2e0a6
AP_Rangefinder: Add arming checks
2019-07-30 10:42:16 +10:00
Randy Mackay
84b502b0c4
AP_RangeFinder: resolve gcs::send_text compiler warning
2019-07-30 09:02:39 +09:00
Randy Mackay
480a3ebb03
AP_RangeFinder: LightwareSerial driver handles invalid distances
...
reports the longer of 100m or RNGFNDx_MAX_CM+1m
2019-07-30 08:05:35 +09:00
Pierre Kancir
c4ec373b20
AP_RangeFinder: pass mavlink_message_t by const reference
2019-07-16 20:51:42 +10:00
Peter Barker
ac96461c6c
AP_RangeFinder: use AP_SerialManager singleton
2019-07-16 09:29:48 +10:00
murata
d7b2271197
AP_RangeFinder: Common modbus crc method
2019-07-12 15:33:21 +10:00
Pierre Kancir
209b0300a5
AP_Rangefinder: fix compilation for Bebop
2019-06-14 18:56:05 -07:00
Peter Barker
68d7e0c22f
AP_RangeFinder: correct macro being used for parameter definition
2019-06-11 12:47:56 +10:00
Peter Barker
8cd5e3103f
AP_RangeFinder: remove use of removed AP_PARAM_FLAG_IGNORE_ENABLE
2019-06-11 11:38:10 +09:00
Peter Barker
4c88a1e9de
AP_RangeFinder: remove dangling update_instance declaration
2019-06-04 19:36:57 +09:00
Tatsuya Yamaguchi
18a43601cd
RangeFinder: Add up to 10 RangeFinder logs
2019-06-04 19:11:11 +10:00
Lucas De Marchi
4f73881c4b
AP_RangeFinder: TFMiniPlus: enforce minimum version 1.7.6
...
On this version of the firmware the command changed - support the new
command and only that one: it's not expected to have devices with the
older versions.
2019-05-24 01:47:04 -07:00
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.
2019-05-24 01:47:04 -07:00
alancaro2013
a1557184d5
AP_RangeFinder: Modified uLanding parse to check device version.
...
US-D1 version ID was changed to 2 from 0. This alteration will prevent
past US-D1s, with version ID 0, from being 3-byte parsed.
2019-05-22 08:20:42 +10:00
Peter Barker
93c33fda1d
RangeFinder: correct bad include of old semaphore library
2019-05-15 19:34:31 +09:00
Siddharth Purohit
479c238177
RangeFinder: add support for rangefinder sensor over can
2019-05-15 16:01:53 +09:00
Andrew Tridgell
09792d3056
AP_RangeFinder: removed unusued AP_Common/Semaphore.h
2019-05-15 15:33:48 +10:00
Michael du Breuil
85da4955b6
AP_Rangefinder: Enforce checking I2C status on VL53L1X
2019-05-05 12:12:05 -07:00
Michael du Breuil
b31cd1adb5
AP_RangeFinder: Remove pre arm distance check
2019-04-16 11:00:32 +09:00
Michael du Breuil
6dd05db3b7
AP_Rangefinder: Fix VL53L1X ignoring return status
2019-04-12 17:23:19 +10:00
murata
49b0a00182
AP_RangeFinder: Delete unnecessary judgment
2019-04-11 06:11:47 -07:00
Peter Barker
dd567ad18a
AP_RangeFinder: handle RFND logging
2019-04-09 22:17:58 +10:00