Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Do we need information about performance? #73

Open
hamishwillee opened this issue Jul 5, 2018 · 0 comments
Open

Do we need information about performance? #73

hamishwillee opened this issue Jul 5, 2018 · 0 comments
Labels

Comments

@hamishwillee
Copy link
Collaborator

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 |
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant