Fix incorrect ws2811 high speed timing & tolerance #3
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
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 high speed timing for WS2811 1 bit low was not correctly half of the low speed timing.
After addressing this issue, the analyser still failed to correctly interpret my captured data due to the tolerances. The datasheet or the original ws2811 drivers is ambiguous on whether the tolerances should also be divided for high speed mode. The behavior of the driver as well as the datasheet of the similar 2812 part (800mhz, +-150ns tolerance) seem to indicate that the tolerance should remain +- 150ns.
Changing the tolerances as suggested in #2 results in correct analysis.
I've attached a sample capture taken using an ESP32 controller running the FastLED library on WS2811 800MHz mode #LEDs
ws2811_on_esp32_fastled.zip