-
Notifications
You must be signed in to change notification settings - Fork 119
New Robot: Preflight check
Xu Liu edited this page Dec 24, 2024
·
7 revisions
Credit: Steven Chen, Guilherme Nardari, Vaibhav Arcot
Follow These Steps Before Every Flight
These are lessons learned from crashes
- Everyone should always stay behind and keep a safe distance (>3m) from the safety pilot, to leave space for emergency take-over and avoid collision with the safety pilot.
- No person / car except for the safety pilot should be directly below the UAV.
- (Safety Pilot) Familiarize yourself with how to take over, land, and disarm the drone.
- (Computer Pilot) (Automated) Familiarize yourself with the software commands and GUI (Manual) Monitor QGC for Warnings
- (Scout/Videographer) Optional Take videos, follow drone, shout out strange behaviors
- Check loose cabling. These can catch in the propellers and make the drone crash.
- Check that wires are tightly plugged in and hot-glued into ESC. These can fall out during flight and make the drone crash.
- Check the battery levels/balance. Getting too low can cause the Pixhawk to restart and make the drone crash. Battery cell should always be above 3.4V.
- Check that the battery monitor will beep a warning when battery levels get below threshold. The battery level getting too low during a flight will make the Pixhawk restart and the drone crash.
- Perform a manual flight. This is important every time you start a new flight to make sure the trims on the RC are correct, there is nothing loose on the drone, the drone is behaving normally, the safety pilot can anticipate drone behavior.
- Reboot the Pixhawk before every automated flight. Not rebooting the Pixhawk will mess up state estimates and cause the drone to crash.
Check that everyone is ready Follow these commands every time before an automated flight (inspired by rock climbing). The purpose is to ensure everyone involved in the drone flight is ready
- Safety Pilot: get familiar with manually piloting the UAV in stabilized mode (attitude control mode). Make sure you know what throttle is needed for hovering the UAV (we will refer to this as Hover Throttle in the following instructions)
- Computer Operator: Check odometry and map are both available, turn off map visualization to avoid communication drop. Talk to safety pilot: Autonomy Ready!
- Safety Pilot: Disable kill switch, flip the mode into autonomous. Talk to the computer operator: Motors On!
- Computer Operator: click motors on. Talk to safety pilot: Motors On Confirmed!
- Safety Pilot: Now propellers should start spinning slowly, if yes, flip the arm switch to arm, push the throttle to the Hover Throttle position to prepare for taking over (propellers should be spinning at the same speed). Talk to computer opeator: Take off!
- Computer Operator: Click takeoff. Talk to the safety pilot: takeoff confirmed!
- Computer Operator: wait for takeoff to complete. After that, click / load waypoints, Publish Waypoints, and click Execute Mission. Talk to the pilot: Executing Mission!
- Computer Operator: if the mission is done, click Land Here.
- Safety Pilot: watch the UAV closely and be prepared to take over. If anything does not work as described, switch back to manual mode, land the UAV, and enable the kill switch to debug.
- Build and Install:
- Simulation Experiments:
- Real-world Experiments:
- Hardware requirements
- Install real robot code stack
- Safety protocol & preflight check
- Launch experiment and gain tuning
- Supported features:
- Integrate (semantic) SLAM for drift correction
- LIDAR-only autonomous flight
- Full coverage experiments
- Customize configurations: