/
2022-09-18 Meeting Notes

2022-09-18 Meeting Notes

Owned by Anonymous
2022-09-18
3 min read

  • Meeting Attendees:

    • Aidan B (Team Lead)

  • Assignments:

    • Aidan: Setup asana for SysInt

  • Welcome to the SysInt team!

  • Important notes:

    • Get Onboarded

    • Make sure all requirements from CONOPS are met

    • Plan future sync meetings for CONOPS

    • Get prepped on Discord (nick, role)

    • Competition 2023

      • Question: what is the specific shape / dimensions of the landing pads?

      • Question: Max length for route (30km) for task 1 includes diversions?

      • Can batteries be replaced on aircraft if we are not on the original take-off point?

      • Prepping writing report for phase 1

  • Main things to look at if you’re getting onboarded / the bootcamp:

  • Follow iterative design process with our projects

    • Needs assessment (requirements, constraints, users)

    • Ideas to solve the problem

    • (Rough) Prototype

    • Test

    • Repeat

      • As you repeat more and more, slow down more as you get more familiar with the problem constraints and get real-world data

    •  

  • Make sure as a project manager, keep in mind that people are volunteers, and deadlines will most likely slip

  • Ensure and plan for redundancy with that information in mind

  • Future goal: running planning meetings for prepping for CONOPS as the SysInt subteam

  • ZeroPilot 3.0

    • Flight controller (inhouse built)

    • Design process underway

    • Tentative delivery (electrical): Mid October

  • iMacs

    • Command station for monitoring and telemetry for everything

    • Transmits and receives data from aircraft directly

    • Ground station

    • Timelines seem to be approximately followed

  • PHOENIX

    • Very little iteration, designed to be a beater drone

    • First provision by mech delivered

    • No further updates, needs more follow up and reviewing before mass manufacturing

  • PID Tuning Rig

    • PID: Calibrating the aircraft

    • Needs requirements develpments

    • No project timeline/deadlines so far

    • Compatibility with pheonix

    • Priority on firmware team

  • Drone Testing Protection

    • Protecting drones from peoples and themselves

    • Looking into sponsorships for potentially drone netting?

    • Robohub cage?

  • 2023 Competition Roadmap for next 8 months

    • Create timelines and capture team strategy

    • Consolidate summary document with competition tasks into confluence

    • First Major Deadline: Nov 28 (Registration for the team)

    • Phase 1 Design Proposal: Jan 15

      • Show how we are managing the project

      • Vehicle and algorithms selected

      • Design and passenger safety

      • Automated aspects/manual aspects

      • Path optimizations

      • Computer Vision algorithms / landing

      • Strategies and novel tech used

      • Risk management

      • Timeline timelines and deadlines and planning

      • Funding and budget planning

      • Create report from this information and send to UAS for judging

    • Our responsibility as SysInt to manage this report and submitting and coordinate meetings with subteams to generate this report

    • March 31 Deadline: Submit team list + $300 per participant

    • 11 April 2023: Proof of successful flight

    • 5-7 May: Attend Phase 2 of competition (actually participating)

    • Blimp?

    • Phase 2: The actual flights

      • Task 1

        • Design aircraft to emulate a fake air taxi

        • Respond to mid-air route change

        • 10-30km long range

        • Stay within 50m of route waypoints and the centerlines between the routes

        • Ability to reroute around restricted airspaces

        • Carry at least 2 doll passengers, extra points for upto 4 more dolls

        • Enclosed cabin with ramp

        • Passengers must be restrained to aircraft

        • Flight window: 30-45 minutes

        • Question: what is the specific shape / dimensions of the landing pads?

      • Task 2

        • Air taxi route, must be at least 50% of given routes

        • Automated algorithm to pick routes

        • Get money for each route

        • Some routes restrict weight to 5kg, or have obstacles nearbye

        • Must have green light visible during operation

        • BVLOS: pilot cannot directly see the aircraft during landing

        • All landing gears must be in pad, and rotors must be not moving

        • Batteries can be swapped if passengers are not on board

      • Important flight prep rules to keep note of, have plan of attack

    • Last deliverable: Post-flight report

      • Comments on the task

      • Performance

      • Must be submitted within 90 mins of the flight

Related content