Peter Barker
7e5808a97b
AP_RangeFinder: add prearm for analogue/pwm pin conflicts
3 years ago
Peter Barker
50fc43b2d2
AP_RangeFinder: tidy includes
3 years ago
Peter Barker
f6aeb01994
AP_RangeFinder: signal quality reporting
3 years ago
Sebastian Quilter
0f7c3e3964
AP_RangeFinder: make rangefinder ranges m rather than cm
3 years ago
Shiv Tyagi
9729377bb3
AP_Rangefinder : make get_temp const
...
This makes backend get_temp methods const
Co-Authored-By: Josh Henderson <69225461+hendjoshsr71@users.noreply.github.com>
3 years ago
Pierre Kancir
bcfb07b39f
AP_Rangefinder: fix override in constructor
4 years ago
Randy Mackay
fee30b4447
AP_RangeFinder: add get_temp and implement for NMEA driver
4 years ago
Peter Barker
cba5f142a7
AP_RangeFinder: correct MAVLink backend's out-of-range checks
4 years ago
yaapu
bc21e505e3
AP_RangeFinder: aligned msp message data struct name to gps,baro and mag
4 years ago
Andrew Tridgell
34430e9d6c
AP_RangeFinder: allow separate enable of MSP rangefinder
4 years ago
Andrew Tridgell
17173871a4
AP_RangeFinder: fixed non-MSP build
4 years ago
yaapu
699ffcbcd2
AP_RangeFinder: added support for MSP based range finders
4 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
82db4383d4
AP_RangeFinder: use enum-class for Status
5 years ago
Peter Barker
ea26e94f66
AP_RangeFinder: use enum-class for RangeFinder type
5 years ago
Pierre Kancir
c4ec373b20
AP_RangeFinder: pass mavlink_message_t by const reference
6 years ago
Siddharth Purohit
479c238177
RangeFinder: add support for rangefinder sensor over can
6 years ago
Michael du Breuil
b31cd1adb5
AP_RangeFinder: Remove pre arm distance check
6 years ago
Randy Mackay
a72477590f
AP_RangeFinder: format fixes
6 years ago
Dmitri Ranfft
5eff01a86f
RangeFinder: allow up to 10 range finders to be used at once
6 years ago
Andrew Tridgell
b1e4434332
AP_RangeFinder: use WITH_SEMAPHORE()
...
and removed usage of hal.util->new_semaphore()
6 years ago
Randy Mackay
3e8d9f4131
RangeFinder: shorten comment
7 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
Randy Mackay
9e27b93538
AP_RangeFinder: move some backend implementations to cpp file
7 years ago
Michael du Breuil
9e551350a4
AP_RangeFinder: Remove unneeded state member
7 years ago
Peter Barker
30c4ea8123
AP_RangeFinder: stop storing sensor type as a variable
...
And change method name
8 years ago
Peter Barker
c0aa10d84b
AP_RangeFinder: move rangefinder backend data accessors to backend
8 years ago
Peter Barker
127edce39e
AP_RangeFinder: move prearm checks into backend
8 years ago
Peter Barker
0b1c67d170
AP_RangeFinder: remove unused parameters from detect and constructors
8 years ago
Pierre Kancir
8b38bd2e33
AP_RangeFinder: add sensor type to backend
8 years ago
Andrew Tridgell
e88519364f
AP_RangeFinder: fixed maxbotix I2C semaphore and bus usage
8 years ago
Mathieu OTHACEHE
152edf7189
Global: remove mode line from headers
...
Using a global .dir-locals.el file is a better alternative than
reincluding the same emacs header in every file of the project.
8 years ago
Andrew Tridgell
50958bc026
AP_RangeFinder: fixed typo
9 years ago
Allan Matthew
d3831e4a5d
RangeFinder: add MAVLink rangefinder
9 years ago
Lucas De Marchi
f6712c8bc4
AP_RangeFinder: replace header guard with pragma once
9 years ago
Gustavo Jose de Sousa
5d39587469
AP_RangeFinder: standardize inclusion of libaries headers
...
This commit changes the way libraries headers are included in source files:
- If the header is in the same directory the source belongs to, so the
notation '#include ""' is used with the path relative to the directory
containing the source.
- If the header is outside the directory containing the source, then we use
the notation '#include <>' with the path relative to libraries folder.
Some of the advantages of such approach:
- Only one search path for libraries headers.
- OSs like Windows may have a better lookup time.
10 years ago
Randy Mackay
7663b8eade
RangeFinder: replace healthy with status and no_data methods
10 years ago
Andrew Tridgell
a6d76b4e03
AP_RangeFinder: added PX4-PWM rangefinder
...
uses PWM input driver to read a rangefinder
10 years ago
Andrew Tridgell
cb037f3416
AP_RangeFinder: new rangefinder API ready for its first backend
...
the backends are setup to have just the minimum functionality needed
for a rangefinder, with all of the higher level logic in the
frontend. This should make writing a new backend easier
11 years ago
akdslr
d759a9dd9b
AP_RangeFinder: Seperated the Backend driver functionality into a separate class
11 years ago