Telemetry Link Requirements
- Anthony Luo
Success metrics
Goal | Metric |
|---|---|
Be able to use different Telemetry Links (I.e. LTE/RFD900/etc) with the drone & groundstation | Ability to swap out different telemetry links. |
Maintain link over long distances and high interference environments | Link Quality maintained during testing? |
Low Latency | Latency low enough to receive critical information from the drone. |
Have a safe failsafe action |
|
Reliable in all operating conditions (rain, heat, etc) |
|
Low Weight & compact size | Needs to be put onto the drone. |
Assumptions
MAVlink will be used between drone and GCS
LTE or 5g Available when flying
Weather resistance /protection provided by some sort of enclosure?
Groundstation will be a laptop.
Mains voltage won’t be supplied.
Telemetry system will not draw more current than the chosen power source can provide.
Requirements
Requirements / Constraints | Context | Priority | Owner | Notes |
|---|---|---|---|---|
Must run off of either 5v or 12v | These are the outputs supplied by our BEC | HIGH | ||
Must be able to run continuously for 1hr | This is the length of a flight window |
|
|
|
Telemetry link must support MAVLink | This is the communication format we use for telemetry |
|
|
|
Telemetry link must terminate in a telemetry port airside | This is the connector ardupilot uses. |
|
|
|
|
|
|
|
|
Open Questions
Question | Answer | Date Answered |
|---|---|---|
|
|
|