aepko/Ardupilot2
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

AP_RangeFinder: define 3_ADDR when we have three rangefinders

Browse Source 
Without this patch this field would only be defined when 4 rangefinders
were specified
This commit is contained in:
Peter Barker 2016-07-26 15:47:25 +10:00 committed by Lucas De Marchi
parent d5c18dc987
commit d5ffc8a863
1 changed files with 7 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
libraries/AP_RangeFinder/RangeFinder.cpp
View File

@ -227,6 +227,7 @@ const AP_Param::GroupInfo RangeFinder::var_info[] = {
#endif
#if RANGEFINDER_MAX_INSTANCES > 2
// @Param: 3_TYPE
// @DisplayName: Second Rangefinder type
// @Description: What type of rangefinder device that is connected
@ -300,17 +301,19 @@ const AP_Param::GroupInfo RangeFinder::var_info[] = {
// @Increment: 1
// @User: Advanced
AP_GROUPINFO("3_GNDCLEAR", 35, RangeFinder, _ground_clearance_cm[2], RANGEFINDER_GROUND_CLEARANCE_CM_DEFAULT),
#endif
#if RANGEFINDER_MAX_INSTANCES > 3
// @Param: 3_ADDR
// @DisplayName: Bus address of 2nd rangefinder
// @DisplayName: Bus address of third rangefinder
// @Description: This sets the bus address of the sensor, where applicable. Used for the LightWare I2C sensor to allow for multiple sensors on different addresses. A value of 0 disables the sensor.
// @Range: 0 127
// @Increment: 1
// @User: Advanced
AP_GROUPINFO("3_ADDR", 36, RangeFinder, _address[2], 0),
#endif
#if RANGEFINDER_MAX_INSTANCES > 3
// @Param: 4_TYPE
// @DisplayName: Second Rangefinder type
// @Description: What type of rangefinder device that is connected