Skip to content

Commit bdba49a

Browse files
DavidsastresasDonLakeFlyer
authored andcommitted
Vehicle.cc: After latest mavlink version we can use CMDs in development.xml
1 parent 18e3ee4 commit bdba49a

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

src/Vehicle/Vehicle.cc

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4017,7 +4017,7 @@ void Vehicle::requestOperatorControl(bool allowOverride, int requestTimeoutSecs)
40174017
safeRequestTimeoutSecs = SettingsManager::instance()->flyViewSettings()->requestControlTimeout()->cookedDefaultValue().toInt();
40184018
}
40194019
sendMavCommand(_defaultComponentId,
4020-
MAV_CMD(32100), // MAV_CMD_REQUEST_OPERATOR_CONTROL
4020+
MAV_CMD_REQUEST_OPERATOR_CONTROL,
40214021
false, // Don't show errors, as per Mavlink control protocol Autopilot will report result failed prior to forwarding the request to the GCS in control.
40224022
0, // System ID of GCS requesting control, 0 if it is this GCS
40234023
1, // Action - 0: Release control, 1: Request control.
@@ -4097,7 +4097,7 @@ void Vehicle::_handleCommandLong(const mavlink_message_t& message)
40974097
if (commandLong.target_system != MAVLinkProtocol::instance()->getSystemId()) {
40984098
return;
40994099
}
4100-
if (commandLong.command == MAV_CMD(32100)) { // MAV_CMD_REQUEST_OPERATOR_CONTROL
4100+
if (commandLong.command == MAV_CMD_REQUEST_OPERATOR_CONTROL) {
41014101
_handleCommandRequestOperatorControl(commandLong);
41024102
}
41034103
}

0 commit comments

Comments
 (0)