Skip to content
New issue

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

Add suport for MAV_CMD_DO_SET_ROI_LOCATION in AP_Mission #28505

Open
bytesByHarsh opened this issue Oct 30, 2024 · 2 comments
Open

Add suport for MAV_CMD_DO_SET_ROI_LOCATION in AP_Mission #28505

bytesByHarsh opened this issue Oct 30, 2024 · 2 comments

Comments

@bytesByHarsh
Copy link

Feature request

Currently only in GCS_Common.cpp file MAV_CMD_DO_SET_ROI_LOCATION support is added, the command sent via Command Long Packet is parsed properly but when MAV_CMD_DO_SET_ROI_LOCATION is sent as a mission item it returns MAV_RESULT_UNSUPPORTED to GCS.

Describe the solution you'd like
A possible solution can be adding a switch statement in the AP_mission.cpp file for MAV_CMD_DO_SET_ROI_LOCATION.

Platform
[ X ] All
[ ] AntennaTracker
[ ] Copter
[ ] Plane
[ ] Rover
[ ] Submarine

If required I can create a MR for adding these changes in the code.

@bytesByHarsh
Copy link
Author

Also if possible can we add the support for MAV_CMD_DO_SET_ROI_NONE as well.

@DonLakeFlyer
Copy link
Contributor

Related to QGC problems discussed here: mavlink/qgroundcontrol#11963

QGC also uses MAV_CMD_DO_SET_ROI_WPNEXT_OFFSET for structure scan missions

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants