Organize Confluence

Archive old documents

New organization: By project.

• Requirements

• Plan

• Documentation

Project Clarification

Scope of Jetson Infrastructure team is all of the Airside System except landing.

• Renamed to Airside System

Scope of Auto-Landing Research & Development is landing.

IMACS Tasks Overview

Interface:

• Physical: USB COM

• Protocol: MAVLink

  • Dart MAVLink library (USB bytes to MAVLink messages)

• Internal: Flutter streams (divide in some manner)

GUI

• Separate components

  • Testable subsets (that can use the simulator for testing)

• Information received as Flutter stream

Simulator

• Mission Planner Simulated Ardupilot

• For testing GUI

  • Ensure everything works correctly

  • Getting pilot opinion

Feedback

See #auto-leads

Action Items

Which subteam is responsible for sourcing the antenna that will connect the drone to the ground station?

Write documentation/direction for QR scanner and Mission Planner team. Include Suraj's documentation.

Should the Jetson's communication with the flight controller be compatible with COTS flight controllers (i.e. use estabished protocol (e.g. MAVLink) vs WARG in-house developed protocol (e.g. )?

• Discuss with EFS and/or Directors

Auto-landing kickoff meeting

IMACS requirements/introduction meeting