From 8ce48931809bffd1f2773384764a40204c40111a Mon Sep 17 00:00:00 2001 From: Randy Mackay Date: Thu, 2 Oct 2014 16:49:15 +0900 Subject: [PATCH] RangeFinder: TYPE param description to PX4-MaxbotixI2C This hopefully reduces confusion for PX4/Pixhawk users with MaxBotix I2C sonar --- libraries/AP_RangeFinder/RangeFinder.cpp | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/libraries/AP_RangeFinder/RangeFinder.cpp b/libraries/AP_RangeFinder/RangeFinder.cpp index 2ea265b59a..218eb04e6d 100644 --- a/libraries/AP_RangeFinder/RangeFinder.cpp +++ b/libraries/AP_RangeFinder/RangeFinder.cpp @@ -25,7 +25,7 @@ const AP_Param::GroupInfo RangeFinder::var_info[] PROGMEM = { // @Param: _TYPE // @DisplayName: Rangefinder type // @Description: What type of rangefinder device that is connected - // @Values: 0:None,1:Analog,2:APM2-MaxbotixI2C,3:APM2-PulsedLightI2C,4:PX4 + // @Values: 0:None,1:Analog,2:APM2-MaxbotixI2C,3:APM2-PulsedLightI2C,4:PX4-MaxbotixI2C AP_GROUPINFO("_TYPE", 0, RangeFinder, _type[0], 0), // @Param: _PIN @@ -91,7 +91,7 @@ const AP_Param::GroupInfo RangeFinder::var_info[] PROGMEM = { // @Param: 2_TYPE // @DisplayName: Second Rangefinder type // @Description: What type of rangefinder device that is connected - // @Values: 0:None,1:Analog,2:APM2-MaxbotixI2C,3:APM2-PulsedLightI2C,4:PX4 + // @Values: 0:None,1:Analog,2:APM2-MaxbotixI2C,3:APM2-PulsedLightI2C,4:PX4-MaxbotixI2C AP_GROUPINFO("2_TYPE", 12, RangeFinder, _type[1], 0), // @Param: 2_PIN