From 29e4e2f1342bb7dab3cba2afde681cdce09b02c7 Mon Sep 17 00:00:00 2001 From: Michael Miller Date: Mon, 14 May 2018 00:23:42 -0700 Subject: [PATCH] Updated NeoPixelBus object (markdown) --- NeoPixelBus-object.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/NeoPixelBus-object.md b/NeoPixelBus-object.md index 1446f90..8e2a41a 100644 --- a/NeoPixelBus-object.md +++ b/NeoPixelBus-object.md @@ -45,6 +45,12 @@ A three element color in the order of Blue, Red, and then Green. ## NeoRbgFeature A three element color in the order of Red, Blue, and then Green. +# DotStar Features +These "feature" objects will be used to define what color order is used for the pixels and what color size (rgb, or rgbw). +Currently there are only a few sizes and color formats. Used only with DotStar methods. + +If you do not see what you require, request it by creating an issue on GitHub. + ## DotStarBgrFeature A three element color in the order of Blue, Green, and then Red. Used only with DotStar methods. @@ -74,6 +80,9 @@ Same as Neo800KbpsMethod but running at the older and slower data rate. The NeoWs2813Method primarily expands the delay time to support these new chips. It is fully compatible with Ws2812 and some newer Ws2812b chips may require this method. On the Esp8266 using this Method has a Pin restriction. Please review [NeoEsp8266DmaWs2813Method](https://github.com/Makuna/NeoPixelBus/wiki/NeoPixelBus-object#neoesp8266dmaws2813method) below for details. +# DotStar Methods +These platform methods will define "how" the pixels are updated. + ## DotStarSpiMethod This method should only be used with DotStar color features. It will use the available hardware SPI support for the board you build with. The clock and data pins are not changeable for hardware support and thus the Pins argument is omitted.