We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
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?
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 |
The text was updated successfully, but these errors were encountered:
No branches or pull requests
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?
Not really sure. Maybe it isn't useful.
The text was updated successfully, but these errors were encountered: