Browse Source

Sub: move handling of MAV_CMD_DO_SET_FENCE_ENABLED up

mission-4.1.18
Peter Barker 6 years ago committed by Randy Mackay
parent
commit
5002fa2081
  1. 15
      ArduSub/GCS_Mavlink.cpp

15
ArduSub/GCS_Mavlink.cpp

@ -763,21 +763,6 @@ MAV_RESULT GCS_MAVLINK_Sub::handle_command_long_packet(const mavlink_command_lon @@ -763,21 +763,6 @@ MAV_RESULT GCS_MAVLINK_Sub::handle_command_long_packet(const mavlink_command_lon
}
return MAV_RESULT_FAILED;
#if AC_FENCE == ENABLED
case MAV_CMD_DO_FENCE_ENABLE:
switch ((uint16_t)packet.param1) {
case 0:
sub.fence.enable(false);
return MAV_RESULT_ACCEPTED;
case 1:
sub.fence.enable(true);
return MAV_RESULT_ACCEPTED;
default:
break;
}
return MAV_RESULT_FAILED;
#endif
case MAV_CMD_DO_MOTOR_TEST:
// param1 : motor sequence number (a number from 1 to max number of motors on the vehicle)
// param2 : throttle type (0=throttle percentage, 1=PWM, 2=pilot throttle channel pass-through. See MOTOR_TEST_THROTTLE_TYPE enum)

Loading…
Cancel
Save