dshot: check for bad pulses and handle wrap correctly #78
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.
new variant of #76
this ensures we handle timer wrap correctly, fixing bad dshot frames with ArduPilot, and also checks for much too narrow or wide pulses
by making variables static this also saves flash and ram. Using REF_F031 as the benchmark we get:
current REF_F031:
with this PR:
so we save 54 bytes of ram and 16 bytes of flash, while fixing the wrap issue and adding pulse width checks