2023-2024 Houston update requirements
- Anthony Luo
Success metrics
Goal | Metric |
|---|---|
Houston has flight long enough to complete Auto Missions (20 mins) | |
Houston is able to carry sensors / boards from EFS/Autonomy |
|
Houston is able to carry a variety of sensor modules. |
|
Houston parts are available and can be replaced. |
|
Thrust - to - weight > 3:1 without payload (non-flight critical) incl. batteries. |
|
Houston has proper mounting locations for telemetry / control links |
|
Has proper mounting locations for forward & downward facing cameras |
|
|
|
Assumptions
Houston will fly using Ardupilot as the primary flight computer.
Houston continues the f450 frame (we have two.)
Houston will use either the TBS Crossfire with XBees OR the RFD900’s
Houston will use Caddx Baby Ratel sized FPV Cameras
Houston will use current CV camera (specs to be linked).
Assumption that we will be able to buy new motors/props.
Requirements
Requirements / Constraints | Context | Priority | Owner | Notes |
|---|---|---|---|---|
Must be able to mount:
in a safe way with space (some) for wiring | These are the boards we are using to test our software | HIGHMEDIUM LOW | ||
Must be able to have proper mounting (including antennas) for RFD900x’s OR tbs crossfire + xbees |
|
|
|
|
Must be able to accomodate 2 3s 4000mah batteries | Gives us 8000mah in parallel for long flights |
|
|
|
Must have flat surface for mounting devices on the top and the bottom of the drone (for various sensors) with mounting points |
|
|
| EG: screw grid |
Must be able to accomodate the minipix or the PX5/6 as primary flight computers. |
|
|
|
|
T:W ratio of 3:1 when no payload | Healthy T:W w/payload > 2:1 per ardupilot recommendation | high |
|
|
Swappable ESC’s |
|
|
|
|
Must be able to accommodate 360 Lidar |
|
|
|
|
Mounting pattern for motors 16x19 | that is the mounting pattern on the frame |
|
|
|
Must be able to accomodate VTX |
|
|
| Does not necessarily need a clear space for mounting - can use mounting grid for ex |
Must have easy way to track drone when/if we crash |
|
|
| eg: gps tracker / beeper / etc. |
Houston needs to be visible |
|
|
| EG: bright/Reflective colours |
Houston must have clear mounting for GPS (NEO M8 flat mount or NEO M9N on a post) |
|
|
| VN-300 as a separate option |
|
|
|
|
|
Houston Architecture
Air-Side hardware
Flight compute:
One of: Minipix/px5/px6
One of: L5 nucleo, ZP3
Command & Control
One of: RFD900 / XBee / ELRS RX
One of: TBS Tracer RX/TBS Crossfire RX/ELRS RX
One of: Caddx Baby Ratel 2 / RUNCam Micro Swift
Sensors:
(Potentially): Hereflow Optical Flow Sensor, Benewake TF-Mini Lidar
At least one: NEO M8 GPS or NEO M9 GPS
(Potentially): Second NEO M9 GPS
Payload:
Open for interpretation
Open Questions
Question | Answer | Date Answered |
|---|---|---|
Motor/Prop Selection? | Someone needs to do T:W analysis |
|
|
|
|