Versions Compared

Old Version 4

changes.mady.by.user Amy Hu

Saved on

compared with

New Version 5

changes.mady.by.user Tong Zhang

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Expand
titleCard 1: Pegasus VTX testing

Video muxing w/ at least 2 cameras. Ideally 3: 1 front, 1 bottom (monster mount), 1 bottom (cabin)

Test #1: Pegasus VTX, LOS low speed & hover performance

Procedure

Goals / Objectives

Failure criteria

  1. Takeoff manually in Loiter, verify that video is stable during takeoff.

  • Ensure that video signal is maintained during close-range takeoffs.

  • Ensure hover doesn’t negatively impact video switching

  • Ensure OSD elements are correct

Loss of Video Transmission

  • Stop drone movement, attempt to re-establish video link.

Loss of Control

  • Land the drone as soon as possible

Loss of Orientation

  • RTL

Battery

  • Land, RTL if possible.

  1. Attempt switching video sources

  1. IF CONFIGURED: attempt switching OSD screens.

  1. Fly slow passes at varying altitudes / distances (pilot discretion) from the ground station

  • Ensure that video signal is maintained during different maneuvers

  • Ensure that different video sources are functional during different passes

  1. Land normally

Expand
titleCard 3: Houston obstacle avoidance2: Pegasus pathing

Test #2: Auto Pathing Mission

Procedure

Goals / Objectives

Failure criteria

  1. Connect pegasus to Mission Planner

  • Verify connection

  • Mavlink doesn't connect

  1. Run pathing code

  • Go to pathing repository

  • Activate the venv with source venv/bin/activate

  • Run pathing code with python -m path_2024

  • Failed sending waypoints

  1. Check waypoints

  • Verify waypoints added by pathing code are correct in Mission Planner

  1. Takeoff

  • Verify drone flies to correct waypoints

  • Pitch/Roll/Yaw incorrect

    • land, flip in mission planner, re-start test

  • Drone de-stabilizes.

    • Land, evaluate tune, re-start test

Expand
titleCard 3: Houston auto landing

Test #1: Auto Mission

Procedure

Goals / Objectives

Failure criteria

  1. Connect Houston to Mission Planner

  • Verify Connection

  • Mavlink doesn't connect

  1. Verify auto-landing script is running

  • Check that images are being logged

  • Script isn’t running

    • Start it manually by navigating to the auto landing repository and running python blue_only.py

    • Make note so this can be fixed

  1. Add waypoints in Mission Planner

  • Add a LAND waypoint at the intended landing pad

  • Offset the waypoint by ~5m to test if the auto landing script corrects it

  1. Takeoff

  • Verify drone lands on landing pad

  • Drone misses landing pad

Necessary Preparation

Explain what capacity you need, what needs to be mounted, etc.

...