Timeline for Common/standard library and/or protocol for Arduino to be I2C slave for driving NeoPixel
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 7, 2016 at 21:23 | vote | accept | jose can u c | ||
| Nov 7, 2016 at 21:09 | answer | added | Nick Gammon ♦ | timeline score: 0 | |
| Nov 7, 2016 at 19:06 | comment | added | Edgar Bonet | @Paul wrote: "NeoPixel's timing constraints are so bad that you can't even generate the pixels on the go". No, they aren't so bad. See: NeoPixels Revealed: How to (not need to) generate precisely timed signals. | |
| Nov 7, 2016 at 18:09 | answer | added | aaa | timeline score: 0 | |
| Nov 7, 2016 at 17:57 | comment | added | aaa | Plus, NeoPixel's timing constraints are so bad that you can't even generate the pixels on the go. You need to put the whole strip in memory, before writing it. The APA102 led strips can be "streamed", pixel by pixel. So you can "calculate-send, calculate-send, calculate-send" to theoretically drive limitless strips witouth using limitless memory ;) | |
| Nov 7, 2016 at 17:54 | comment | added | aaa | You could use APA102 led strips, they use an "spi-like" protocol (see datasheet) which is much less time-restrictive. Using the right parts is IMHO a better solution than adding more parts to get something working. | |
| Nov 7, 2016 at 17:09 | history | asked | jose can u c | CC BY-SA 3.0 |