Branch: zr-v5.1

c415-sdk

celiu-4.0

celiu-4.0.17-rc8

master

mission-4.1.18

zr-sdk-4.1.16

zr-sdk-4.3.1

zr-v4.1.17

zr-v5.0

zr-v5.1

Branches Tags

${ item.name }

Create tag ${ searchTerm }

Create branch ${ searchTerm }

from 'zr-v5.1'

${ noResults }

Commit Graph

508 Commits (zr-v5.1)

Author	SHA1	Message	Date
Randy Mackay	85c4db6896	AP_RangeFinder: LightwareSerial driver loses unnecessary initialisation	5 years ago
Randy Mackay	cdbc0c782b	AP_RangeFinder: add sf30d binary protocol support ... Co-authored-by: Tatsuya Yamaguchi <susumu-336@hotmail.co.jp>	5 years ago
Tatsuya Yamaguchi	ed14518634	AP_RangeFinder: TYPE param becomes enable flag	5 years ago
Henry Wurzburg	f9b02a6814	AP_RangeFinder: HC-SR04: Add glitch filter	5 years ago
Peter Barker	fc1ea612b1	AP_RangeFinder: add support for HC-SR04 rangefinder	5 years ago
Andrew Tridgell	2dcf8a3b08	AP_RangeFinder: cope with beyond max range with LightwareI2C	5 years ago
Peter Barker	af80c4a29f	AP_RangeFinder: remove move-to-error-state for LeddarOne driver ... Just because there's a lot in your input buffer doesn't necessarily mean the rangefinder is faulty.	5 years ago
Peter Barker	95f9769041	AP_RangeFinder: use new UARTDriver discard_input method	5 years ago
Henry Wurzburg	23e7e2d193	AP_RangeFinder: rename Benewake types for easier identification	5 years ago
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	5 years ago
Andrew Tridgell	603e5c4b55	AP_RangeFinder: added get_address() ... allows AP_Periph to supply sensor_id for multiple CAN rangefinders	5 years ago
Andrew Tridgell	ffe9fa22a1	AP_RangeFinder: invalidate param count when changing param tree structure	5 years ago
Andrew Tridgell	b102fd6b59	AP_RangeFinder: use GCS_SEND_TEXT()	5 years ago
Peter Barker	b7a03ae5ad	AP_RangeFinder: rename APMrover2 to Rover	5 years ago
Peter Barker	adcfb60850	AP_RangeFinder: comment out no-loner-used PX4 enum entry	5 years ago
Peter Barker	6febbcdc13	AP_RangeFinder: remove incorrect and misleading comment ... Wrong on several counts. detect calls this method. The constructor doesn't initialise the rangefinder. detect doesn't return boolean.	5 years ago
Patrick José Pereira	a183d00b7e	AP_RangeFinder: BLPing: Rework class to work with new firmware version 3.28 ... - Uses the continuous message request Signed-off-by: Patrick José Pereira <patrickelectric@gmail.com>	5 years ago
Randy Mackay	7d8952a48a	AP_RangeFinder: fix offset param for PWM driver	5 years ago
Randy Mackay	52ca1e016e	AP_RangeFinder: minor fix in POS param description	5 years ago
Randy Mackay	9f3154372d	AP_RangeFinder: POS param range of 5m and 1cm increment	5 years ago
Michael du Breuil	7bc1f4ff9b	AP_RangeFinder: a to close reading is not the minimum distance	5 years ago
Andrew Tridgell	2fa6f534ab	AP_RangeFinder: added get_type() API	5 years ago
murata	b0af48745e	AP_RangeFinder: VL53L1X LONG can be specified ... AP_RangeFinder: VL53L1X LONG can be specified AP_RangeFinder: Add VL53L1X to device number 16 AP_RangeFinder: Add VL53L1X to device number 16	5 years ago
Randy Mackay	141099078c	AP_RangeFinder: increase leddarvu8 timeout to 0.5sec	5 years ago
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
Randy Mackay	e5c3a7f7b5	AP_RangeFinder: typo fix for LeddarOne	5 years ago
Randy Mackay	266a908b83	AP_RangeFinder: serial backend get_reading returns false	5 years ago
Randy Mackay	9ac10c3af9	AP_RangeFinder: remove virtual from _get_mav_distance_sensor_type	5 years ago
Andrew Tridgell	7dcb5c60b0	AP_RangeFinder: use take_blocking instead of HAL_SEMAPHORE_BLOCK_FOREVER ... this makes for cleaner and smaller code as the failure case is not needed	5 years ago
Randy Mackay	bcef478eab	AP_RangeFinder: update OFFSET param description to clarify only for analog and pwm	5 years ago
Randy Mackay	2bdb2f67ab	AP_RangeFinder: PWM driver adds offset param value	5 years ago
Michael du Breuil	d92c4dc892	AP_Rangefinder: Fix bad subgroup pointer for drivers	5 years ago
Rishabh	fd2c6baf5d	AP_RangeFinder: added RNGFNDx_TYPE parameter description for the Lanbao lidar	5 years ago
Michael du Breuil	8bd4f2b097	AP_RangeFinder: Allow the VL53L1X to be put into short range mode	5 years ago
Michael du Breuil	224ea744e3	AP_Rangefinder: Reset the VL53L1X before setup ... A number of the config steps make the assumption they are running from the sensors default power on state. If you do a soft reset of the vehicle without killing power to the sensor this means the second time you configure the sensor you will start from a state which didn't match the base assumptions and can lead to the sensor preforming signficantly differently then it was intended to. This issues a soft reset, and waits for it to reboot before proceeding with configuration. If it's a watchdog reset we don't want to spend long enough to have ensured the sensor reset, so we say the sensor setup completely failed and don't use it, as not using it will be less erroneous then using a misconfigured sensor.	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
Randy Mackay	0844077df8	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	5 years ago
Randy Mackay	ae8f9a70d0	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	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	b1f8982292	AP_RangeFinder: remove old AP_RangeFinder.h ... Making way to move the actual header into place	5 years ago
Peter Barker	d0e62b0e0b	AP_RangeFinder: serial subclasses rely on base class for update()	5 years ago
Peter Barker	60cbefc1ae	AP_RangeFinder: move update function to serial base class	5 years ago
Peter Barker	b18f1a8e22	AP_RangeFinder: move uLanding to using common serial backend	5 years ago
Peter Barker	9829a1d08b	AP_RangeFinder: move wasp to using common serial backend	5 years ago
Peter Barker	62f2f3e19e	AP_RangeFinder: factor constructor, use to move Lanbao to serial baseclass	5 years ago
Peter Barker	acc1f955ef	AP_RangeFinder: make Benewake backend use new intermediate class	5 years ago
Peter Barker	0246dd990e	AP_RangeFinder: make MaxsonarSerialLV backend use new intermediate class	5 years ago