Increase the maximum number of addressable LEDs 7.1 #9717
Merged
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.
INAV 7.1 based version of #9701
Rebasing at this stage is a nightmare.
This is a non-breaking change. So should not be a problem for 7.1
-- Original info from #9701
Increase the number of addressable LEDs from 32 to 128.
The extra 96 LEDs adds only 10560 B (5.37% on an F722) of RAM usage, and an extra 64 B (0.01% on F722) of Flash. If necessary, this could be changed so that it is only available on processors with > 512 KB flash.
Why so many LEDs? Why not? On larger aircraft, a single LED strip along a wing will have many chips. Here, for example is the tail boom extensions for a Drak.
Here's the CPU usage with the LEDs switched off.
Here's the CPU usage with 96 LEDs with a Larson scanner running.