0f7c3e3964
AP_RangeFinder: make rangefinder ranges m rather than cm
3 years ago
cba5f142a7
AP_RangeFinder: correct MAVLink backend's out-of-range checks
4 years ago
35e987c663
AP_RangeFinder: adjust for renaming of RangeFinder files
5 years ago
7c9ab0203d
AP_RangeFinder: rename source files to include AP_ prefix
...
This makes them look like most of our libraries
5 years ago
82db4383d4
AP_RangeFinder: use enum-class for Status
5 years ago
ea26e94f66
AP_RangeFinder: use enum-class for RangeFinder type
5 years ago
479c238177
RangeFinder: add support for rangefinder sensor over can
6 years ago
b31cd1adb5
AP_RangeFinder: Remove pre arm distance check
6 years ago
5eff01a86f
RangeFinder: allow up to 10 range finders to be used at once
6 years ago
b1e4434332
AP_RangeFinder: use WITH_SEMAPHORE()
...
and removed usage of hal.util->new_semaphore()
6 years ago
3be9f35264
AP_RangeFinder: remove rangefinder prearm requirements for SITL
...
Getting the virtual rangefinder to move in prearm would be better, much
much more involved.
6 years ago
9e27b93538
AP_RangeFinder: move some backend implementations to cpp file
7 years ago
30c4ea8123
AP_RangeFinder: stop storing sensor type as a variable
...
And change method name
8 years ago
c0aa10d84b
AP_RangeFinder: move rangefinder backend data accessors to backend
8 years ago
127edce39e
AP_RangeFinder: move prearm checks into backend
8 years ago
0b1c67d170
AP_RangeFinder: remove unused parameters from detect and constructors
8 years ago
08cd3f4a77
AP_RangeFinder: move instance parameters into instance state
8 years ago
8b38bd2e33
AP_RangeFinder: add sensor type to backend
8 years ago
e88519364f
AP_RangeFinder: fixed maxbotix I2C semaphore and bus usage
8 years ago
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
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
6acd92be1e
AP_RangeFinder: compiler warnings: compare signed to unsigned
10 years ago
7663b8eade
RangeFinder: replace healthy with status and no_data methods
10 years ago
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
879eb5936b
AP_MATH: Adding WGS GPS conversions, CRC16 checks, and double-precision Vectors and Matrices
11 years ago
d67ad2c7ee
AP_Notify: added missing files
12 years ago
495c4bbbbe
AP_Notify: simplify interface to avoid timers and external calls
...
this changes AP_Notify to use updates via notify.update() at 50Hz,
avoiding the need for the 1kHz timer. It also creates a parent class
for ToshibaLED so that the I2C and PX4 ToshibaLED drivers can be
abstracted out.
Pair-Programmed-With: Randy Mackay <rmackay9@yahoo.com>
12 years ago
2658cda4bc
Toshiba_LED_PX4: local #defines for led brightness
12 years ago
0c1db12538
AP_Notify: add ToshibaLED_PX4
12 years ago
a52b1831ca
AP_Notify: make flags static variable
12 years ago
54007854a9
Notify: add ToshibaLED
12 years ago
Sebastian Quilter
Peter Barker
Siddharth Purohit
Michael du Breuil
Dmitri Ranfft
Andrew Tridgell
Randy Mackay
Pierre Kancir
Mathieu OTHACEHE
Gustavo Jose de Sousa
Tom Pittenger
Andrew Tridgell
Niels Joubert