fix esp32 timer resolution #63
Open
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.
Set the timer frequency to 1MHz to match expected microsecond resolution for the alarm value.
The issue: the ESP32 library timerBegin(frequency) function uses a frequency in Hz to set the resolution of the timer and the alarm value (in timerAlarm()). Currently both the frequency and alarm value are set to the BPM in microseconds, so the interrupt will always be every second (or a ratio, if the tempo is later changed, changing the alarm value but keeping the default resolution).
Solution: set the timer frequency to 1MHz to match the expectation the alarm value is in microseconds.