Makuna/NeoPixelBus
1
0
Fork 1
mirror of https://github.com/Makuna/NeoPixelBus.git synced 2025-08-07 12:54:26 +02:00
Code Issues Packages Projects Releases Wiki Activity

Updated FAQ #5 (markdown)

Michael Miller
2018-12-23 20:47:54 -08:00
parent 6c6cdabdff
commit 6cc83d2414
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
FAQ-#5.md

@@ -2,11 +2,11 @@
There are two pieces to this question really. One is how much time does it take to send the data to the NeoPixels. And the other is how fast can your code provide the next set of changes so they can be sent.
#### How much time does it take to send the data to the NeoPixels?
The wire protocol takes 1.25us per bit. If you are using a 3 element Rgb LEDs, that's 30us per pixel. Add 50us latch between updates, and a little overhead of about 100us, and this should be what to expect.
The wire protocol takes 1.25us per bit. If you are using a 3 element Rgb LEDs, that's 30us per pixel. Add 300us latch between updates, and a little overhead of about 100us, and this should be what to expect.
For 4 element Rgbw LEDs, its 40us per pixel.
```
RGB microseconds = pixelcount x 30 + 50 + 100
RGBW microseconds = pixelcount x 40 + 50 + 100
RGB microseconds = pixelcount x 30 + 300 + 100
RGBW microseconds = pixelcount x 40 + 300 + 100
```
Depending on the "method" used to send this data, the actual time the CPU takes will vary greatly.
For most platforms, the CPU will be doing the work. So the cpu will consume time to do all the work except for the latching. So you end up with...