Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Meeting overview

Meeting to discuss all aspects of the command & control system for AEAC 2024

  • Tracking Antenna (hardware)

  • ELRS Configuration (including gemini, airport, etc)

  • Ground-station software & scripting

Table of Contents

📝 Meeting minutes & decision log

< to be filled out during the meeting >

📡 Tracking Antenna Updates

Mechanical

Item

Notes

Introduction

Arjun Mandair

Topics of Discussions

Current Design Photos & Videos

Arjun Mandair

Picture of the Current Design For Patch Antenna Tracker

  • ***NOTE*** current Antenna Tracker is designed only for Patch Antenna. Currently not compatible with Yagi Antennas.

Potential Changes

  • Move the battery and receiver mounting positions from their current positions to the side panels.

    • Pros: Less material needed. More space for other electrical components.

    • Cons: Not balanced around center of mass.

    • Any thoughts?

Previous Design of Antenna Tracker for Yagi Antennas

Questions

Arjun Mandair

  • Am I essentially making two separate Antenna Trackers for the Yagi antennas and the Patch antenna? Or am I making one Antenna tracker compatible with both?

  • Anthony Luo suggested a “crossbow” like configuration where there's a flat plate above the drive servo so that the antenna can be centered . Are you referring to a flat plate similar to the one below?

  • Anthony Luo asked if the current antenna tracker is compatible with HS311 servos. Should the designs be compatible with HS311 servos?

  • Are the current servo positions ideal knowing new constraints? (Considering HS311 Servos, Torque, Wiring, Yagi Antennas, etc.)

New Constraints / Conclusions / Rough Notes

going for 2-3 weeks for a prototype that can rotate

Software

Yuchen Lin to fill out

mavlink passthrough in progress

planning to port neo m8 and bmx 160 driver to f401, and develop the motor control algorithm

create an integration test code and ready for test flight

Electrical

@nolan haines or Hardy Yu to fill out

  • Yuchen solders the perf board for integrating the Nucleo and all the peripheral connections.

📶 Gemini Updates

Electrical

Michael Botros

  • Schematic phase

  • Deadlines assigned in Asana

If mech needs to design anything/ provide anything, please get that to mech leads within 1~2 weeks

đź’» Command Software Updates

Autonomy

IMACS:

  • working with DART MAVLink library. working on getting data telemetry setup.

    • two parts: reading from serial (get data from drone → in actual flight test), also reading from TCP so you can read mavlink from mock mission planner. → test gui without testing on actual drone

  • when GUI starts up → need to request data to listen to and then you’ll get that stream of messages.

    • need to test and confirm.

    • Xierumeng able to use mock missions & wireshark to read mavlink messages? → did not make a request to receive those messages.

      • Mission Planner itself is requesting certain information && that info is forwarded blindly to GUI.

QR Code → Auto Mission

  • Possible to not work with MP?

    • MP uses python2.7 (old).

  • At end of comp → script generates a file, and then you manually add the file into mission planner. (does not count as autonomy)

Embedded Flight Software

  • No labels