Versions Compared

Old Version 39

changes.mady.by.user Ashish Agrahari

Saved on

compared with

New Version Current

changes.mady.by.user Ashish Agrahari

Saved on

Key

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

...

IR Camera Test (HOUSTON)

Procedure

Goals/Objectives

Knockoff criteria

  1. Setup (prepare drone)

  • A good outcome is if rc.local succesfully runs and images are auto captured and stored in a designated folder

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

  1. Hover at 3-5.

  • Best outcome: Image output is desirable (high quality and emitter light is clear visible with no discernible issues in image quality) and are successfully stored in a logging folder.

  • Acceptable outcome: Images are successfully stored in a logging folder (we will see what why image quality is poor).

due to vibration on drone, images are very blurry.

Weather: cloudy

  1. Hover at 10m

Same as above

  1. Hover at 15m

Same as above

  1. Hover at 20m

Same as above

...

Obstacle Detection/Guided Mode (HOUSTON)

Procedure

Goals / Objectives

Knockoff criteria

  1. Setup drone:

  2. a) Ensure the guided-mode script has been uploaded to the drone

  3. b) Switch on drone

  4. c) Run the script (starts the mission, where drone navigates to waypoints in a square, switches from AUTO → GUIDED → AUTO, completes mission and returns to landing)

  • Good outcome if drone completes the auto-guided-auto mode switches seamlessly, drone continues its auto mission after diversion, and returns to land.

IMP: pls see photo before reading the description below!

  • The mission is setup as follows. connection initialisedinitialized, armed, takes off 10m altitude, flies 10m NW to the first vertex of the square, flies 10m E to the second vertex. When the drone is about to arrive at second vertex, it switches from AUTO to GUIDED to simulate a diversion and navigates to a waypoint 7.5 NE of current pos. After reaching this intermediate wp, drone switches to AUTO, continues to 3rd waypoint. Just before it reaches the third waypoint there is another auto-guided-auto switch, abrupt change in velocity component direction. Then we carry on naturally to 4th wp. halfway between, we auto-guided-auto (through ned_waypoint this time) to another intermediate wp (see photo), return to waypoint originally navigating too, and initiate landing procedure.

  • 10m S, 4th waypoint 10m W, signifying the completion of the auto-mission. The drone then returns to landing position and lands gracefully.

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

Pilot intervention is not necessary unless safety issues arise, or there are environmental disruptions, as the auto → guided → auto switch is handled by the script.

if at any point the pilot needs to take control: 1) kill the script, this forcefully changes drone mode to loiter (tested on MP), and then aborts the current mission. 2) Pilot has manual control over the drone

NOTE: on mp, simulating a mission-abort, ie. killing the script changes mode to loiter almost instantly, but drone altitude plummets to zero. (discussed with Andrew and it should just be a MissionPlanner default issue). However, just in case, pilot should be ready to control vertical throttle when aborting mission (when killing the script)

image-20241116-020108.pngImage Added

Flight Card 4 ~ Moved to next flight test

...

Vyomm Khanna

Ashish Agrahari

Andrew Shum

Key People Not Attending

If you’re directly involved in this stuff and cannot make this test please note it here. All onsite FTCs and subteam leads should fill this out please.

Debrief

Flight Card 1

Recap

Photos below are also in onedrive

Takeoff location

Landing pad to detectlocation Flights 1-3

Landing pad to detect location Flight 4

TakeoffLocation_pic1.pngImage Added

LandingPadToDetectLocation_Flight4_Pic1.pngImage Added

LandingPadToDetectLocation_Flight1_to_3_Pic1.pngImage Added

TakeoffLocation_pic2.pngImage Added

LandingPadToDetectLocation_Flight4_Pic2.pngImage Added

LandingPadToDetectLocation_Flight1_to_3_Pic2.pngImage Added

Flight 1 - 5 m altitude

West

Flight 2 - 10 m altitude

West

Flight 3 - 20 m altitude

West

Flight 4 - 20 m altitude

315 deg (i.e. in NW direction)

Good

  • Geolocation logs worked, will update with photos after checking them

  • Auto starts with Houston when powered up

Bad

  • Camera direction needs to be labeled for installing

    • Distance/offset for camera location needs to be known at some point

Flight Card 2

Recap

Cloudy weather

Grass in the background

IR emitter set on top of controller box

Flight 1 - 5 m

Flight 2 - 10 m

Flight 3 - 15-20 m

Good

  • Lots of images

  • Different altitudes

Bad

  • Not great images

    • Need a better camera with global shutter due to vibe and drifting of drone

  • IR camera broke before flight test, glued back on (Nathan glued it)

  • Took a while prior to leaving for flight to get set up on Pi

Flight Card 3

Recap

Flight 1 - completed script

Flight 2 - tested canceling script switching to loiter

Good

Bad

Flight Card 4

Recap

Good

Bad

  • Script completed well, armed and took off drone in auto and successfully switched from Auto to Guided at flags

Bad

  • Could not switch from Auto/Guided to Loiter in the middle of the script

    • Was able to switch to RTL though

  • RTL switch to Loiter cut thrust and drone fell, caught with RTL but switch to loiter caused same issue

    • Hard landing, nothing was damaged

    • Thrust on controller was at 50% during this too

    • Test script on drone with lower altitude to problem solve switching to loiter issue

      • Simulation successfully switched from auto/guided to loiter, but did not translate to real flight

Action Items

  • Check photos for IR and Geolocation

  • Check path from guided mode and compare to simulation

  • Check RTL to loiter transition issues