Versions Compared

Key

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

...

Expand
titleCard 1: Pegasus OpFlow + Lidar Calibration

Test #1: Opflow calibration

Procedure

Goals / Objectives

Knockoff criteria

  1. Hover altitude <x>Inflow calibration setup

    1. Set RC6_OPTION = 158 (Optflow Calibration)

    2. Setup the EKF3 to use GPS (the default)
      • EK3_SRC1_POSXY = 3 (GPS)
      • EK3_SRC1_POSZ = 1 (Baro)
      EK3_SRC1_VELXY = 3 (GPS)
      EK3_SRC1_VELZ = 3 (GPS)
      • EK3_SRC1_YAW = 1 (Compass)
      • EK3_SRC_OPTIONS = 0 (Disable FuseAlIVelocities)

  • Obtain images of <x>

  • Verify colour calibration

  • < anything else you’re evaluating >

< list of reasons why you would want to stop the test >

  1. Setup GPS/Non-GPS transitions (to switch between GPS and Optical Flow inflight)

  1. Ensure

    1. EK3_ENABLE = 1
      EK2_ENABLE = 0
      AHRS_EKF_TYPE = 3

  1. Hover in Loiter mode (>10m)

< etc >

  1. Begin opflow

calibration
  • < Should get some message >

< etc >
  1. calibration

    1. Pull the auxiliary switch high to start the calibration

    2. Rock the vehicle back and forth in both roll and pitch

  • Check the GCS "Messages" tab for output confirming the calibration is complete

  • FLOW_FXSCALAR and FLOW_FYSCALAR values between -200 to +200 is good

    • Code Block
      FlowCal: Started
      FlowCal: x:0% y:0%
      FlowCal: x:66% y:6%
      FlowCal: x:100% y:74%
      FlowCal: samples collected
      FlowCal: scalarx:0.976 fit: 0.10   <-- lower "fit" values are better
      FlowCal: scalary:0.858 fit: 0.04
      FlowCal: FLOW_FXSCALER=30.00000, FLOW_FYSCALER=171.0000

  1. Check lidar calibration?

  1. Review test data?

Expand
titleCard 2: Tracking Antenna Validation

Test #1: straight passes

Procedure

Goals / Objectives

Knockoff criteria

  1. Hover altitude <x>

  • Verify antenna is able to point towards the drone

< list of reasons why you would want to stop the test >

  1. Translation motion:

Move in <pattern>

  • Ensure that the tracking antenna remains pointed at the drone

< etc >

Maintain desired movement towards
Expand
titleCard 3: Houston obstacle avoidance
< list of reasons why you would want to stop the test >

Test #1: ???Stab mode Lidar Verification

Procedure

Goals / Objectives

Knockoff criteria

  1. Hover altitude <x>

  1. Takeoff and hover in STAB 1.5-2m AGL. Verify controls.

  • Verify pitch/roll/yaw directions are correct.

  • Verify that Gemini functionality is retained.

  • Verify that flight modes & flight time is correct.

  • Pitch/Roll/Yaw incorrect

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

  • Drone de-stabilizes.

    • Land, evaluate tune, re-start test

  1. Translational movement @ slow speed towards vertical wall

  • Ensure that the proximity sensor is able to detect a wall.

  • contact with the wall

    • back-off and land. Evaluate prop health. Re-start if possible.

  • Loss of heading reference

    • back-off , re-establish, continue.

  1. Maintain desired distance from the wall while spinning heading vector 360

  • Ensure that proximity continues to track at all angles

  1. Approaches from front/side/rear ascending & descending.

  • Basic characterization of obstacle avoidance properties.

Test #2: Loit mode Obstacle Avoidance

Procedure

Goals / Objectives

Knockoff criteria

  1. Takeoff and hover in Loit mode 1.5-2m AGL. Verify controls.

  • Verify pitch/roll/yaw directions are correct.

  • Verify that Gemini functionality is retained.

  • Verify that flight modes & flight time is correct.

  • Pitch/Roll/Yaw incorrect

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

  • Drone de-stabilizes.

    • Land, evaluate tune, re-start test

  1. Translational movement @ slow speed towards vertical wall

  • Ensure that the proximity sensor is able to detect a wall.

  • Ensure that the drone

stops at specified distance before the wal

< etc >

  • does not move closer nearer to the wall.

  • contact with the wall

    • back-off and land. Evaluate prop health. Re-start if possible.

  • Loss of heading reference

    • back-off , re-establish, continue.

  • Obstacle avoidance malfunction

    • Back-off, re-attempt.

    • If same behaviour, land and evaluate settings.

    • Continue test if possible

  • Loss of drone handling?

    • land if possible , dis-arm, re-attempt & slower speed.

  1. Maintain desired distance from the wall while spinning heading vector 360

  • Ensure that obstacle avoidance continues to track and function at all expected angles.

  1. Approaches from front/side/rear ascending & descending

  • Basic characterization of obstacle avoidance properties.

  1. .

  • Ensure that obstacle avoidance continues to track & function at all expected angles.

Test #3: Auto Mission obstacle avoidance

Procedure

Goals / Objectives

Knockoff criteria

  1. Setup an auto mission which passes through an “obstacle”

  • Have a flight path.

  • Path doesn’t generate GG

  1. Set mission to AUTO, takeoff and fly!

  • Ensure obstacle avoidance continues to function!

  • drone does not avoid obstacle

    • Re-take control in stab. Back-away and attempt to re-start.

  • Drone de-stabilizes

    • Re-take control in stab. Back-away and attempt to re-start.

  1. Upon reaching end waypoint, RTL

  • Ensure obstacle avoidance functions in RTL

Necessary Preparation

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

...

Name

Phone # (opt)

Sub-team

Driving (question)

Role

Anthony Luo

Director

Y - 5pass SUV

Megan Spee

Director

5-person liftback

Nathan Green

Mechanical

3-277 Dodge Grand Caravan

Ryan Chan

Mechanical

Sam Zhang

EFS

Tim Gu

EFS

Georgia Vachon Westerlund

Ops

...