increase NUM_NO_REPLY_UNTIL_UNRESPONSIVE to 6 #24250
Draft
+1
−1
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.
Solved Problem
To make sure latency or other issues between the FMU and the mission computer do not cause a mode registration problem, number of no replies to raise the mode unresponsive flag is increased to 6. This change is added after observing mission computer latency issues due to overheating and increasing this value relatively increased the chance of successful mode registrations.
Fixes #{Github issue ID}
Solution
NUM_NO_REPLY_UNTIL_UNRESPONSIVE
is increased from 3 to 6.Changelog Entry
For release notes:
Alternatives
By enabling mode registration while armed, an unresponsive mode can be re-registered and any undesired mode unresponsive flag can be resolved. Please see, #24249
Test coverage
Context
Related links, screenshot before/after, video