We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
@LorenzMeier why are we using MAV_CMD_PREFLIGHT_REBOOT_SHUTDOWN with param1 == 3 as link shutdown? https://github.com/PX4/Firmware/blob/7d7e40f59473ed538c61f8b76020ca505ee52487/src/modules/mavlink/mavlink_receiver.cpp#L353
MAV_CMD_PREFLIGHT_REBOOT_SHUTDOWN
param1 == 3
According to the specs that should do an FC reboot with forcing it to bootloader. Which is implemented but never happens because of the above logic.
Funnily this could have been the same issue: #5473 (although normal boot was ok for him I guess)
The text was updated successfully, but these errors were encountered:
This is indeed a case where we had a custom use and then the spec got extended.
Sorry, something went wrong.
Fix issue #5501. Link termination now requires param 2 = 10
d98bbd9
Closed in d98bbd9.
Thanks!
No branches or pull requests
@LorenzMeier why are we using
MAV_CMD_PREFLIGHT_REBOOT_SHUTDOWN
withparam1 == 3
as link shutdown? https://github.com/PX4/Firmware/blob/7d7e40f59473ed538c61f8b76020ca505ee52487/src/modules/mavlink/mavlink_receiver.cpp#L353According to the specs that should do an FC reboot with forcing it to bootloader. Which is implemented but never happens because of the above logic.
Funnily this could have been the same issue: #5473 (although normal boot was ok for him I guess)
The text was updated successfully, but these errors were encountered: