You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+6Lines changed: 6 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -42,6 +42,12 @@ It provides two variants:
42
42
- Is everything white? This may stem from an spi peripheral that's too slow or
43
43
one that takes too much time in-between bytes
44
44
45
+
- Is your first LED the wrong brightness/color while the rest of your LED's do what you expect?
46
+
This is due to low voltage of data line, or too much of a voltage difference between Vin and Din
47
+
voltages, making some "high" bits read as "low" bits to the chip. Due to the chips circuitry, these
48
+
voltages are regulated as they are passed on to the next LED in the line, which is why the other LED's
49
+
perform as expected. (For more on exactly what is going on here, see [Hackaday | Cheating at 5V WS2812 Control to Use 3.3V Data](https://hackaday.com/2017/01/20/cheating-at-5v-ws2812-control-to-use-a-3-3v-data-line/))
50
+
45
51
- Are you using the `--release` compiler flag?
46
52
47
53
The timing of each byte passed over SPI is very sensitive, and running code compiled
0 commit comments