../../libraries/AP_Proximity/AP_Proximity_LightWareSF40C.cpp: In member
function ‘void AP_Proximity_LightWareSF40C::request_new_data()’:
../../libraries/AP_Proximity/AP_Proximity_LightWareSF40C.cpp:235:6:
warning:
‘__builtin___snprintf_chk’ output may be truncated before the last
format
character [-Wformat-truncation=]
void AP_Proximity_LightWareSF40C::request_new_data()
^~~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from /usr/include/stdio.h:862:0,
from ../../libraries/AP_Common/AP_Common.h:179,
from ../../libraries/AP_HAL/UARTDriver.h:5,
from ../../libraries/AP_HAL/HAL.h:11,
from ../../libraries/AP_HAL/AP_HAL_Main.h:19,
from ../../libraries/AP_HAL/AP_HAL.h:8,
from
../../libraries/AP_Proximity/AP_Proximity_LightWareSF40C.cpp:16:
/usr/include/x86_64-linux-gnu/bits/stdio2.h:65:44: note:
‘__builtin___snprintf_chk’ output between 10 and 16 bytes into a
destination
of size 15
__bos (__s), __fmt, __va_arg_pack ());
^
../../libraries/AP_Proximity/AP_Proximity_LightWareSF40C.cpp: In member
function ‘bool
AP_Proximity_LightWareSF40C::send_request_for_distance()’:
../../libraries/AP_Proximity/AP_Proximity_LightWareSF40C.cpp:275:6:
warning:
‘__builtin___snprintf_chk’ output may be truncated before the last
format
character [-Wformat-truncation=]
bool AP_Proximity_LightWareSF40C::send_request_for_distance()
^~~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from /usr/include/stdio.h:862:0,
from ../../libraries/AP_Common/AP_Common.h:179,
from ../../libraries/AP_HAL/UARTDriver.h:5,
from ../../libraries/AP_HAL/HAL.h:11,
from ../../libraries/AP_HAL/AP_HAL_Main.h:19,
from ../../libraries/AP_HAL/AP_HAL.h:8,
from
../../libraries/AP_Proximity/AP_Proximity_LightWareSF40C.cpp:16:
/usr/include/x86_64-linux-gnu/bits/stdio2.h:65:44: note:
In file included from
../../libraries/AP_Proximity/AP_Proximity_RPLidarA2.cpp:30:
../../libraries/AP_Proximity/AP_Proximity_RPLidarA2.h:88:10: warning:
private field '_payload_data' is not used [-Wunused-private-field]
bool _payload_data;
^
../../libraries/AP_Proximity/AP_Proximity_RPLidarA2.h:91:10: warning:
private field '_skip' is not used [-Wunused-private-field]
bool _skip;
^
../../libraries/AP_Proximity/AP_Proximity_RPLidarA2.h:92:10: warning:
private field '_rp_reset' is not used [-Wunused-private-field]
bool _rp_reset;
^
../../libraries/AP_Proximity/AP_Proximity_RPLidarA2.h:95:13: warning:
private field '_element_len' is not used [-Wunused-private-field]
uint8_t _element_len[2];
^
../../libraries/AP_Proximity/AP_Proximity_RPLidarA2.h:96:13: warning:
private field '_element_num' is not used [-Wunused-private-field]
uint8_t _element_num;
^
5 warnings generated.
Object avoidance is possible with just one valid distance
Boundary is initialised in new init_boundary function to be 100m from
vehicle
If sectors do not have valid distance measurements, we use the distance
from adjacent sectors. This conveniently leads to a concave shaped
boundary that keeps the vehicle from travelling into the dataless sector.
AC_Avoidance will not stop if it thinks the vehicle is on or outside the polygon. Setting a minimum distance ensures the vehicle is always within the polygon.
Only SF40c uses these ignore areas for now at least.
It is safe to increase the eeprom locations for the 2nd proximity instance because we only define a single instance.
Randy Mackay
pierre-louis.k
Mateusz Sadowski
Peter Barker
Patrick José Pereira
Michael du Breuil
Holger Steinhaus
Steven Josefs
khancyr
Dr.-Ing. Amilcar Do Carmo Lucas
Luis Rodrigues
murata
Andrew Tridgell