Skip to content

Commit

Permalink
Update top5_mistakes.md (#145)
Browse files Browse the repository at this point in the history
  • Loading branch information
wled-faq authored Aug 11, 2023
1 parent 14872f7 commit 16136af
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion docs/basics/top5_mistakes.md
Original file line number Diff line number Diff line change
Expand Up @@ -22,4 +22,4 @@ If you then still have troubles and are going to ask for help, provide as much i
![Brightness Limiter Settings](../assets/images/content/brightness_limiter.jpg)
4. Wrong LED type is set. The correct LED type and the correct color sequence (RGB, BGR, etc.) must be set in WLED LED preferences. Check that these settings are correct. You have to know the LED type, but you can simply try out the color sequence to see which is the right one. Special attention must be paid for example to the WS2814 LED strip, which must be set as SK6812 and not as WS281x in the LED preferences.
![Example LED type setup](../assets/images/content/example_led_type_setup.jpg)
5. Wiring is bad. Wiring must be done thoroughly. Loose contacts, cold solder joints etc. must be avoided. You also need to be careful about the correct sizing of the cables: too thin wires can not only cause high voltage drop but also lead to an overheating and fire! For wire sizing you may use this [LED power, wiring and fuse calculator](https://wled-calculator.github.io/).
5. Wiring is bad. Wiring must be done thoroughly. Loose contacts, cold solder joints etc. must be avoided. You also need to be careful about the correct sizing of the cables: too thin wires can not only cause high voltage drop but also lead to an overheating and fire! For wire sizing you may use this [LED power, wiring and fuse calculator](https://wled-calculator.github.io/). If many power sources are used (for example separate one for ESP and separate one for the LED strip), then all their grounds (GND, V-) must be connected together (but do not connect their V+ together!).

0 comments on commit 16136af

Please sign in to comment.