RC Control Link Requirements
- Anthony Luo
Success metrics
Goal | Metric |
|---|---|
Support multiple RC Control Protocols to the drone (crossfire, elrs, etc) | Hot-swappable demonstration. |
Low Latency | Latency low enough to control the drone over long distances. |
Long Range | Able to maintain link over long distances and high interference environments |
Have a safe failsafe action |
|
Reliable in all operating conditions (rain, heat, etc) |
|
Assumptions
Transmitters are TX16 MKii
EgeTX will be used on the controllers
ELRS will be used for wireless trainer
External battery power may be supplied to the transmitter.
Requirements
Requirements / Constraints | Context | Priority | Owner | Notes |
|---|---|---|---|---|
Must be able to run continuously for 1hr | This is the length of a flight window. | HIGH | ||
ELRS / RFD900 / Crossfire / Tracer Has to be supported | These are the control links that WARG commonly uses |
|
|
|
Control link must output SBUS | This is the control format that ZP and Ardupilot expects in WARG Context |
|
|
|
Control links must support at least 12 channels | This is the minimum number of channels WARG requires |
|
|
|
|
|
|
|
|
Open Questions
Question | Answer | Date Answered |
|---|---|---|
|
|
|