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

Mavlink Client #4

Closed
1 of 6 tasks
atar13 opened this issue Oct 2, 2023 · 0 comments · Fixed by #107
Closed
1 of 6 tasks

Mavlink Client #4

atar13 opened this issue Oct 2, 2023 · 0 comments · Fixed by #107
Assignees

Comments

@atar13
Copy link
Member

atar13 commented Oct 2, 2023

🚀 Feature

Need a way to to communicate with the flight controller.

  • Find a library to communicate with the Pixhawk over Serial and UDP/TCP

Create a C++ class to contain all the mavlink functionality we need and to abstract away the details.

  • Connect to Pixhawk over Serial (verify heartbeat)
  • Connect to SITL over UDP/TCP (verify heartbeat)
  • Query positional telemetry in the form of mavlink message from the plane. Should return a struct that has this info:
    • latitude
    • longitude
    • altitude
    • relative_alt (from ground)
    • heading
    • airspeed
    • groundspeed
  • Function that queries wind information based on this message https://mavlink.io/en/messages/common.html#WIND_COV
  • Utilize library to create a function to send a mission

This declaration should go in the include/network/mavlink.hpp.
This definition should go in the src/network/mavlink.cpp.

Documentation

Add a page to the wiki under obc where you outline the functions of the interface. For the messages that get data from the flight controller, mention which mavlink messages they use.

Tests

Create a Mock plane that this client can interface with during testing. This is rather complicated so see Tyler or Anthony when you get to this step.

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

Successfully merging a pull request may close this issue.

2 participants