Copter: Suppress multiple anomaly alerts #27803
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Emitting multiple failures is actually a deliberate - requested! - feature. These tests are independent, too - one failure doesn't mean the others will. Sorry, but this isn't how things are desired. |
|
@peterbarker san. I believe it is necessary to be aware of the telemetry transmission rate. I am customizing QGC and MP to be mindful of the telemetry communication rate. I want telemetry transmissions to be reliably notified to the GCS. I do not think it is acceptable for them to be missed due to overflow. I use ArduPilot for business and am working to improve it. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The telemetry transmitter uses UART at 57600 BPS or 38400 BPS.
The signal lines are only TX and RX for the telemetry transmitter.
Sending many messages in a short time is prone to overflow.
If an error is detected in the order, I don't think other processing is necessary.
If it gets better, execute the next process.