Shiv Tyagi
e1a528213d
AP_Rangefinder: Use default address for TFMiniPlus I2C unless configured
...
This fixes the issue #13419 . If RNGFNDx_ADDR is not configured, it uses default address for TFmini i2c
3 years ago
Andrew Tridgell
4f6da39bb7
AP_CANManager: support Benewake CAN
3 years ago
Andrew Tridgell
3f85eab272
AP_RangeFinder: added Benewake CAN Lidars
...
includes support for setting CAN ID and min SNR
3 years ago
Peter Barker
f6aeb01994
AP_RangeFinder: signal quality reporting
3 years ago
Wynn, Jesse Stewart
a7321cbae1
AP_RangeFinder_LightWareSerial: check dist for lost signal flags
...
consider messages valid only if they are non-negative AND if the value is not a known lost-signal reading
3 years ago
TunaLobster
ba9381f40c
AP_RangeFinder: fix ADC scaling on IOMCU
3 years ago
Shiv Tyagi
516eafa45b
AP_Rangefinder: fail RF prearm checks for NoData/NotConnected statuses
...
Earlier we only failed RF checks if we could not detect an RF instance but we should also fail it if the RF is not connected or we receive no data.
3 years ago
divyateja04
001f6a29ee
AP_RangeFinder: removed empty constructors
3 years ago
Andrew Tridgell
4f2bec72b6
AP_RangeFinder: rename uLanding to USD1_Serial
...
this was rebranded by the vendor Ainstein a long time ago
3 years ago
Andrew Tridgell
c1b9585926
AP_RangeFinder: average over 100Hz frames in USD1 CAN driver
...
this reduces noise
3 years ago
Andy Piper
a2bb0b01e8
AP_RangeFinder: convert APM_BUILD_COPTER_OR_HELI() to APM_BUILD_COPTER_OR_HELI
3 years ago
Sebastian Quilter
0f7c3e3964
AP_RangeFinder: make rangefinder ranges m rather than cm
3 years ago
Randy Mackay
85dbb70df5
AP_RangeFinder_NMEA: add hondex custom message support
3 years ago
Iampete1
f667c098a2
AP_RangeFinder: analog: check for valid pin
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
Gone4Dirt
e0af10886b
AP_RangeFinder: Add APM_BUILD_Heli
3 years ago
Iampete1
17e8ea0136
AP_RangeFinder_Params: update PIN discription
3 years ago
Iampete1
0d3c00cb96
AP_Rangefinder: MAVLink: accept data only from configured orentation
3 years ago
Pierre Kancir
bcfb07b39f
AP_Rangefinder: fix override in constructor
4 years ago
bugobliterator
e51d358552
AP_RangeFinder: use typename SIM instead of SITL as it conflicts with namespace name
4 years ago
bugobliterator
4312213e18
AP_RangeFinder: change class name from SITL::SITL to SITL::SIM
4 years ago
bugobliterator
98f5eb28db
AP_RangeFinder: use separate register_driver method while contructing CAN Driver
4 years ago
Andrew Tridgell
a0ef4f76e2
AP_RangeFinder: replaced Pixhawk with more appropriate wording in docs
4 years ago
Siddharth Purohit
0795225475
AP_RangeFinder: Use HAL_CANMANAGER_ENABLED instead of HAL_ENABLE_LIBUAVCAN_DRIVERS
4 years ago
Michael du Breuil
b3a1e6a1ce
AP_RangeFinder: Rearrange parameters to reduce memory usage
...
Saves 4 bytes per instance, and with 10 instances this gives us an extra
40 bytes of RAM
4 years ago
Pierre Kancir
117ca8a6ef
AP_Rangefinder: make backend get_reading() pure virtual
4 years ago
Pierre Kancir
88b5ff8c6f
AP_Rangefinder: make get_temp const
4 years ago
Siddharth Purohit
2e41077347
AP_RangeFinder: fix using labs on unsigned value subtraction
4 years ago
Randy Mackay
fee30b4447
AP_RangeFinder: add get_temp and implement for NMEA driver
4 years ago
PYBrulin
240bfeb6bd
AP_RangeFinder: TeraRangerI2C added case of out of range measurement
4 years ago
PYBrulin
afe9573900
AP_RangeFinder: TeraRangerI2C redefining the output distance logic with OutOfRange cases
4 years ago
Randy Mackay
5912052a39
AP_RangeFinder: lightware legacy I2C retry count to 20
...
This is consistent with the non-legacy I2C protocol
4 years ago
murata
09f04e8a5a
AP_RangeFinder: Devices are enabled and disabled by type
...
AP_RangeFinder: Devices are enabled and disabled by type
AP_RangeFinder: Delete some description of I2C function address.
4 years ago
Patrick José Pereira
efffed0510
AP_RangeFinder: Add missing const in member functions
...
Signed-off-by: Patrick José Pereira <patrickelectric@gmail.com>
4 years ago
Peter Barker
78b49a2c35
AP_RangeFinder: maxbotix: use i2c-address parameter
4 years ago
Peter Barker
496267115c
AP_RangeFinder: MAVLink: use larger of min ranges / smaller of max ranges
4 years ago
Peter Barker
cba5f142a7
AP_RangeFinder: correct MAVLink backend's out-of-range checks
4 years ago
Peter Barker
223e775a3c
AP_RangeFinder_MAVLink: only set sensor type if we accept a reading
4 years ago
Peter Barker
40eb9a8b99
AP_RangeFinder: do not start the mavlink rangefinder as healthy
...
Also takes the opportunity to clean things up a little
4 years ago
Andrew Tridgell
66c05bef76
AP_RangeFinder: added USD1 CAN driver
...
also known as uLanding CAN
4 years ago
murata
282590668d
AP_RangeFinder: Make measurement time and call back time static constant
...
Co-authored-by: Pierre Kancir <pierre.kancir.emn@gmail.com>
4 years ago
Tatsuya Yamaguchi
4dc5162d0a
AP_RangeFinder: change i2c reading frequency to 50Hz
4 years ago
ashvath
54708d916b
AP_RangeFinder: TFminiPlus driver outputs init failure to ground station
4 years ago
Tatsuya Yamaguchi
b0ee6393ae
AP_RangeFinder: TFminiPlus: set frame rate to 250hz
4 years ago
Peter Barker
1c57eed66c
AP_RangeFinder: remove unused voltage_mv_orient method
...
This is really backend-specific data and shouldn't be exposed
4 years ago
Andrew Tridgell
0c05e9a2e7
AP_RangeFinder: fixed handling of instance numbers
...
if a backend allocation failed then we could end up with the backend
being assigned to the wrong instance number. Switch to using
_add_backend() everywhere, and pass the instance number to
_add_backend() to ensure that it always uses the correct slot.
Also added comment explaining how num_sensors() works when we have a
sparse set of rangefinders configured
4 years ago
Brent McLaughlin
e241433c89
AP_Rangefinder: change lightware lost signal timer to 20
...
The LightWare lost signal timer is set to 20 by the manufacturer.
4 years ago
murata
bbc673c668
AP_RangeFinder: Change rangefinder number 10 to A
4 years ago
Lucas De Marchi
4be9b4171b
AP_RangeFinder: TFMiniPlus: respect max configured via param
...
Do like other drivers do and cap the maximum reported value with what is
configured in the parameter.
4 years ago
Lucas De Marchi
0e63a833e9
AP_RangeFinder: TFMiniPlus: fix out-of-range returned a no-data
...
Other drivers consider that they received data even if the value is
reported as "out of range" by sensor. On the I2C driver for TFMiniPlus
we considered this case, too. However when the signal strength is very
low (and thus the distance would likely be out of range), we would end up
ignoring the new sample. With enough samples without any value this
would lead the status to turn to "NoData".
4 years ago