zrzk/zr-v4 - zr-v4 - Gitea: Brown's Gitea

Author	SHA1	Message	Date
Randy Mackay	6816262e3d	AP_RangeFinder: benewake tfmini always provide cm distances a misunderstanding of the datasheet led to the mistaken idea that while in short-range-mode the distances were returned in millimeters	6 years ago
Randy Mackay	f5a9fdaf42	RangeFinder: benewake buffer uses uint8_t	6 years ago
Randy Mackay	e9c1abfc3c	AP_RangeFinder: fix benewake checksum check	6 years ago
Randy Mackay	123e10c058	AP_RangeFinder: benewake returns at least 12m or 22m when out-of-range value logged and shown to the user will be at least 12m for TFmini or 22m for TF02 which ensure the user won't see the range drop even if they have configured a very short useable distance	6 years ago
Randy Mackay	35be68348d	AP_RangeFinder: benewake logic reordering this should be a non-functional change	6 years ago
Randy Mackay	a09cd8411d	AP_RangeFinder: benewake lidar returns max range + 1m when out-of-range also returns out-of-range when signal is weak	6 years ago
Randy Mackay	7fdd0bd996	AP_RangeFinder: Benewake driver discards distances over 327m	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
Patrick José Pereira	32fa7e2c2a	AP_RangeFilter: Fix equality comparison with extraneous parentheses Signed-off-by: Patrick José Pereira <patrickelectric@gmail.com>	7 years ago
Randy Mackay	e520d4fe42	AP_RangeFinder: Benewake TF02 and TFmini lidar driver	7 years ago