Siddharth Purohit
479c238177
RangeFinder: add support for rangefinder sensor over can
2019-05-15 16:01:53 +09:00
Michael du Breuil
b31cd1adb5
AP_RangeFinder: Remove pre arm distance check
2019-04-16 11:00:32 +09:00
Dmitri Ranfft
5eff01a86f
RangeFinder: allow up to 10 range finders to be used at once
2019-02-04 11:08:47 +09:00
Andrew Tridgell
b1e4434332
AP_RangeFinder: use WITH_SEMAPHORE()
...
and removed usage of hal.util->new_semaphore()
2018-10-17 12:54:22 +11:00
Peter Barker
3be9f35264
AP_RangeFinder: remove rangefinder prearm requirements for SITL
...
Getting the virtual rangefinder to move in prearm would be better, much
much more involved.
2018-10-09 10:47:38 +11:00
Randy Mackay
9e27b93538
AP_RangeFinder: move some backend implementations to cpp file
2018-08-28 09:23:38 +09:00
Peter Barker
30c4ea8123
AP_RangeFinder: stop storing sensor type as a variable
...
And change method name
2017-08-15 18:58:16 +01:00
Peter Barker
c0aa10d84b
AP_RangeFinder: move rangefinder backend data accessors to backend
2017-08-15 18:30:45 +01:00
Peter Barker
127edce39e
AP_RangeFinder: move prearm checks into backend
2017-08-09 13:58:53 +01:00
Peter Barker
0b1c67d170
AP_RangeFinder: remove unused parameters from detect and constructors
2017-08-09 13:58:53 +01:00
Peter Barker
08cd3f4a77
AP_RangeFinder: move instance parameters into instance state
2017-08-09 13:58:53 +01:00
Pierre Kancir
8b38bd2e33
AP_RangeFinder: add sensor type to backend
2017-06-08 01:22:07 +01:00
Andrew Tridgell
e88519364f
AP_RangeFinder: fixed maxbotix I2C semaphore and bus usage
2016-11-09 17:08:02 +11:00
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.
2016-10-24 09:42:01 -02:00
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.
2015-08-11 16:38:23 +10:00
Tom Pittenger
6acd92be1e
AP_RangeFinder: compiler warnings: compare signed to unsigned
2015-05-05 13:27:02 +10:00
Randy Mackay
7663b8eade
RangeFinder: replace healthy with status and no_data methods
2015-04-24 10:57:10 +09:00
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
2014-07-08 15:07:50 +10:00