Do we need information about performance?
hamishwillee opened this issue · 0 comments
hamishwillee commented
The following performance below was copied from mavlink.org - I don't think it is at all useful.
What sorts of performance information might be useful?
- I guess something comparative - ie using MAVLink vs some other protocol
- Something that shows range/data loss limits for working with common autopilot systems
- Kind of data rates you can get over USB say for companion computer control, and what sort of specific things this allows vs what you can't do.
Not really sure. Maybe it isn't useful.
===== Performance =====
This protocol was totally geared towards two properties: Transmission speed and safety. It allows to check the message content, it also allows to detect lost messages but still only needs six bytes overhead for each packet.
=== Transmission examples ===
^ Link speed ^ Hardware ^ Update rate ^ Payload ^ Float values ^
| 115200 baud | XBee Pro 2.4 GHz | 50 Hz | 224 bytes | 56 |
| 115200 baud | XBee Pro 2.4 GHz | 100 Hz | 109 bytes | 27 |
| 57600 baud | XBee Pro 2.4 GHz | 100 Hz | 51 bytes | 12 |
| 9600 baud | XBee Pro XSC 900 | 50 Hz | 13 bytes | 3 |
| 9600 baud | XBee Pro XSC 900 | 20 Hz | 42 bytes | 10 |