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 debugging topic #63

Open
hamishwillee opened this issue Nov 9, 2017 · 0 comments
Open

Add debugging topic #63

hamishwillee opened this issue Nov 9, 2017 · 0 comments

Comments

@hamishwillee
Copy link
Collaborator

hamishwillee commented Nov 9, 2017

Seed with information here: mavlink/MAVSDK#150 (comment)

Add info on developer logging - ie both messages you can add to plugins, and the message logging for all MAVLink comms: https://docs.dronecore.io/v/develop/en/contributing/dev_logging.html#message_logging

Perhaps start a FAQ on how to deal with particular types of issues - e.g. "What do to if you get a timeout" - with "ways to check that message is actually sent".

For this, from Julian - to solve this problem (timeout)

  • You need to know that a mavlink command gets published as a uORB vehicle_command
  • And that a vehicle_command_ack as a mavlink command ack again
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

1 participant