9 Commits

Author	SHA1	Message	Date
Randy Mackay	6699a44b1b	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	2018-12-09 07:30:46 +11:00
Randy Mackay	dfe32e7496	RangeFinder: benewake buffer uses uint8_t	2018-12-09 07:30:44 +11:00
Randy Mackay	8969926765	AP_RangeFinder: fix benewake checksum check	2018-11-15 17:20:40 +11:00
Randy Mackay	07bbf75a8b	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	2018-11-15 17:20:30 +11:00
Randy Mackay	16c4776475	AP_RangeFinder: benewake logic reordering ... this should be a non-functional change	2018-11-15 17:20:27 +11:00
Randy Mackay	89f485f32e	AP_RangeFinder: benewake lidar returns max range + 1m when out-of-range ... also returns out-of-range when signal is weak	2018-11-15 17:20:23 +11:00
Randy Mackay	9485ab8eb8	AP_RangeFinder: Benewake driver discards distances over 327m	2018-11-10 14:04:07 +11:00
Patrick José Pereira	32fa7e2c2a	AP_RangeFilter: Fix equality comparison with extraneous parentheses ... Signed-off-by: Patrick José Pereira <patrickelectric@gmail.com>	2018-06-27 14:59:33 -07:00
Randy Mackay	e520d4fe42	AP_RangeFinder: Benewake TF02 and TFmini lidar driver	2018-05-30 11:16:35 +09:00