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

Connections Page #86

Open
5 tasks
Tyler-Lentz opened this issue Oct 17, 2023 · 0 comments
Open
5 tasks

Connections Page #86

Tyler-Lentz opened this issue Oct 17, 2023 · 0 comments
Assignees
Labels
feature New feature or request

Comments

@Tyler-Lentz
Copy link
Contributor

Tyler-Lentz commented Oct 17, 2023

🚀 Feature

The Connections page need to allow us to monitor all of the connections in our system. There are three main categories of connections:

  1. Antenna Tracker
  2. Onboard Computer
  3. Radio Mavlink

Each of these should be able to be clicked, bringing up a page with extra information about that connection type. For each connection type, here is a list of things that need to be available.

  1. Antenna Tracker
    • map with:
      • current plane position, angled at current heading
      • current antenna tracker position, angled to match the current angle in the real world
    • flowing log of all UDP packets being sent over the wire. (Think a terminal just constantly scrolling text)
  2. Onboard Computer
    • Status of imaging camera connection
    • Most recently taken camera image, where each image is stored in a gallery that you can view as they come in
    • form to update camera parameters
    • Status of onboard serial mavlink connection. (Include heartbeat time)
    • Either:
      • iframe to ubiquiti web interface to see nano station configuration and status
      • or just link to the right port in another tab if we can't get the iframes working
  3. Radio Mavlink
    • iframe to influx db database, or just link to the web interface if the iframe doesn't work

And these are all of the subtasks that need to be completed to finish this page:

  • Integrate Protobuf for Connection Status message from Hub
    • we need to standardize the typing of the /connections message from Hub so that Houston can request it. We will do this by creating a protobuf file and importing the compiled go code in the backend and ts code in the backend. This protobuf should only contain the high level information for each topic. For more specific connection information, other routes and protobufs should be used when they make sense.
  • Make actual HTTP request for Connection status message to Hub from Houston code. Link this to the displayed Statuses.
  • Antenna Tracker subpage with all relevant routes/protobufs/setup
  • Onboard Computer subpage with all relevant routes/protobufs/setup
  • Radio Mavlink subpage with all relevant routes/protobufs/setup
@Tyler-Lentz Tyler-Lentz added the feature New feature or request label Oct 17, 2023
@Tyler-Lentz Tyler-Lentz self-assigned this Oct 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant