Introduction

• some thoughts thinking about https://discord.com/channels/776618956638388305/776618957138034690/1245803821863538769

• wifi stuff? ← some overlap with https://uwarg-docs.atlassian.net/wiki/spaces/ARCHS22/pages/2555707425

• Also add an IMACS groundstation hardware project to this

• this is meant to be the hardware thing we have that runs mission planner or the software autonomy has plz add details @Tong Zhang

Initial hardware requirements

• Built into Nanuk 930 case

• GMKTec G3 computer?

• Minimum one display in top of case. This can be a monitor that is disassembled or a laptop display

  • Could have multiple monitors that fold out

• Keyboard

• Trackball and mouse buttons

• RCA inputs for video with RCA to USB adapters

• Ethernet port(s)

• USB-C port(s)

• Arm switch (covered)

• Flight mode buttons with lights

• IMACS is an extension of https://uwarg-docs.atlassian.net/wiki/spaces/ARCHS22/pages/2060451847 and is intended to be used as a part of this ground control station

Software Requirements

• I believe we need to use MavProxy to forward MAVLink to Tracking Antenna as well as Pathing for Autonomy code

• Since EFS will use a network port to tracking antenna and Autonomy pathing software will use a network port to forward pathing commands we should be able to integrate both but this should be tested

• Maybe we store a script to run the MavProxy command in Autonomy pathing repository

Concept System Diagram

@Nathan Green can you add in a diagram for what the” ground station router and windows PC” portion of the above diagram will look like with all of it’s devices here?

Hardware Considerations

• https://www.expresslrs.org/software/airport/#required-hardware

  • running multiple ELRS devices in the same band is not a good idea

• minimizing weight on the airside is a priority

• minimizing system complexity is a priority

• debuggability is nice for autonomy people