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

Updated DotStar Methods (markdown)

Michael Miller
2023-04-04 14:15:54 -07:00
parent b47870ba10
commit 47b62c0d9e
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
DotStar-Methods.md

@@ -10,7 +10,7 @@ Simply insert the model name of your LED before "Method" and more than likely yo
* **Lpd8806**Method - (LPD8806) Must use either Lpd8806BrgFeature or Lpd8806GrbFeature color feature.
* **Lpd6803**Method - (LPD6803) Must use one of the many Lpd6803*Feature.
Provide the Pins to use for Data and Clock using the `strip.Begin()`.
Provide the Pins to use for Data and Clock by setting them in the constructor `NeoPixelBus(uint16_t countPixels, uint8_t pinClock, uint8_t pinData)`.
### Hardware SPI named:
**"\<insert LED name\>SpiMethod"**
@@ -22,7 +22,7 @@ Simply insert the model name of your LED before "SpiMethod". It will use the av
* **Lpd8806Spi**Method - (LPD8806) Must use either Lpd8806BrgFeature or Lpd8806GrbFeature color feature.
* **Lpd6803Spi**Method - (LPD6803) Must use one of the many Lpd6803*Feature.
Generally, the clock and data pins are not changeable for hardware support and thus the Pins argument is omitted on the constructor. If the pins are changeable like on the ESP32, then provide the pins to `strip.Begin()`.
Generally, the clock and data pins are not changeable for hardware support and thus the Pins argument is omitted on the constructor. If the pins are changeable like on the ESP32, then provide the pins to `strip.Begin(int8_t sck, int8_t miso, int8_t mosi, int8_t ss)`.
NOTE: The hardware pins on the board are often labeled as MOSI for data, and MSCLK or CLK for the clock.
NOTE: The SPI clock speed will be 10MHz.
@@ -47,7 +47,7 @@ A few examples would be:
* Tlc5947**Spi15Mhz**Method - TLC5947 running at its low normal of 15Mhz.
* P9813**SpiHz**Method - P9813 running on hardware SPI with the speed set at run-time by latter calling `strip.SetMethodSettings()`.
Generally, the clock and data pins are not changeable for hardware support and thus the Pins argument is omitted on the constructor. If the pins are changeable like on the ESP32, then provide the pins to `Begin`.
Generally, the clock and data pins are not changeable for hardware support and thus the Pins argument is omitted on the constructor. If the pins are changeable like on the ESP32, then provide the pins to `strip.Begin(int8_t sck, int8_t miso, int8_t mosi, int8_t ss)`.
NOTE: The hardware pins on the board are often labeled as MOSI for data, and MSCLK or CLK for the clock.
### The platform specific named: