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

Created T_METHOD (markdown)

Michael Miller
2023-03-30 13:44:48 -07:00
parent a49c2991b3
commit ca81787631
1 changed files with 12 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
T_METHOD.md Normal file

@@ -0,0 +1,12 @@
The _T_METHOD_ is a template class specialization feature that defines the specifics of the method used to drive the signal output needed for various LEDs and LED driver chips like WS2813b, WS2811, or APA106. These definitions generally represent the signal form (timing/pulses), the hardware method to drive the signal (bitbang/SPI/UART/etc), and any specific settings needed for these. You as the sketch author do not need to write one of these as a large library of them is available for you to choose from.
**If you do not see a _method_ that matches your needs, you can make a request by creating an issue on the Github repo.**
In general, when the term _NeoPixel_ is used, it means either the specific smart LED like WS2812b or a combination of LED driver chips and LEDs like WS2811 driven by a single data wire.
Also, the term _DotStar_ is used to mean similar smart LEDs like APA106 or combinations of LED driver chips and LEDs driven by two wires, a data wire and a clock wire.
Either of which comes with variances of how the signal is generated on a pin(s), which can be very important on some platforms that a bitbang method is not reliable due to interrupts or other timing interactions.
### [Neo Methods List](https://github.com/Makuna/NeoPixelBus/wiki/Neo-Methods)
### [DotStar Methods List](https://github.com/Makuna/NeoPixelBus/wiki/DotStar-Methods)