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

« Previous Version 3 Next »

Overview

This document contains a summary of different tests the Pathing team has conducted, how to run the tests, and the results of each test.

Summary of Tests

Mission Planner Simulator

Instructions on how to run

  1. Follow the steps to run the Mission Planner simulator which are explained in this document: https://uwarg-docs.atlassian.net/wiki/spaces/CV/pages/2240643073/Ardupilot+Simulation+with+Mission+Planner#MAVLink-Forwarding.

    1. Note: On step 2 you will be running another application so proceed to step 3.

  2. Once you finish step 3 in the document, you can run the pathing repository code with the command python -m path_2023.

  3. Scan the QR code. TODO: Link the QR code image here.

  4. The script should run successfully (The script should output “Done” to signify it has finished) and the waypoints should be loaded onto the simulator. The simulated drone will follow the route.

Testing Status

The code has been tested and the pathing repository works as expected.

Realflight Simulator

Instructions on how to run

Arunav Munjal to link documentation here.

Testing Status

The code has been tested and the pathing repository works as expected.

USB Communication

Instructions on how to run

  1. Find a USB-C to USB-A cable

  2. Connect the USB-C end to the Pixhawk. There is a USB-C port on the side of the Pixhawk.

  3. Connect the USB-A end to a USB port on the ground station computer.

  4. Power the Pixhawk.

  5. Determine the name of the COM port the Pixhawk is connected to on the ground station computer.

  6. Edit the CONNECTION_ADDRESS constant in the main_2023.py to be "comX" where X is the COM port number.

    1. For example, if the Pixhawk is connected to COM port 6 then the CONNECTION_ADDRESS would be "com6". The documentation for this can be found here: https://dronekit-python.readthedocs.io/en/latest/guide/connecting_vehicle.html#get-started-connecting under the “Connection string options” header.

  7. Run the pathing repository with the command python -m main_2023.

  8. Scan the QR Code.

  9. The script should run successfully (The script should output “Done” to signify it has finished).

  10. Remove the USB cable from the Pixhawk and place the UAV in position for takeoff.

  11. Open Mission Planner and connect Mission Planner to the drone.

  12. Press the “Plan” tab in the top left corner.

  13. Click on the “Read” button on the right-hand side.

  14. The waypoints from the script should appear on Mission Planner.

Testing Status

The code has been tested and the pathing repository works as expected.

LTE Communication

Instructions on how to run

  1. Find a USB-C to USB-A cable.

  2. Connect the USB-C end to the Pixhawk. There is a USB-C port on the side of the Pixhawk.

  3. Connect the USB-A end to a USB port on the Raspberry Pi.

  4. Power the Pixhawk.

  5. Power the Raspberry Pi using a USB-C charger that connects to the USB-C power port on the Raspberry Pi.

  6. Open Mission Planner and wait for around a minute to see if the UAV connects automatically to the ground station computer.

  7. If Mission Planner doesn’t connect after a minute, configure Mission Planner to connect to UDP port 14550 on the top right-hand corner and click connect.

  8. Run the pathing repository with the command python -m main_2023.

  9. Scan the QR code.

  10. The script should run successfully (The script should output “Done” to signify it has finished).

  11. Press the “Plan” tab in the top left corner.

  12. Click on the “Read” button on the right-hand side.

  13. The waypoints from the script should appear on Mission Planner.

Testing Status

The code has been tested and the pathing repository works as expected.

XBee’s Communication

Instructions on how to run

Testing Status

The code has not been tested yet.

RFD 900 Communication

Instructions on how to run

Testing Status

The code has not been tested yet.

  • No labels