-
-
Notifications
You must be signed in to change notification settings - Fork 510
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
FollowMeImpl::set_config() returns immediately though Device didn't confirm #221
Labels
Comments
#217 addresses this. |
shakthi-prashanth-m
changed the title
FollowMeImpl::set_config() returns immediately though Device didn't confirm
Jan 10, 2018
FollowMeImpl::set_config
returns immediately though Device didn't confirm
Merged
Closing the issue, as #217 is merged. Thanks @julianoes. |
rt-2pm2
pushed a commit
to rt-2pm2/DronecodeSDK
that referenced
this issue
Nov 27, 2018
1. This commit address DroneCore issue mavlink#221. 2. Corresponding changes (from mavlink#1 above) in integration tests & example. 3. Replaces boost::bind by std::bind. 4. Adds important note about using Boost in the example. 5. Adds debug_str to distinguish FollowMe plugin debug messages.
dlech
pushed a commit
to dlech/MAVSDK
that referenced
this issue
Jan 14, 2022
action: add request for vehicle to hold position (loiter)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is a known issue as mentioned in the code as FIXME.
Issue:
When an application calls
FollowMe::set_config()
requesting for config change, the API returns early before device confirmation for the same. It is not a fatal issue as it is most likely successful. However,device confirmation may get delayed by few microseconds.
Solution:
Waiting for the device confirmation should happen from Follow Me plugin side.
The text was updated successfully, but these errors were encountered: