Stuck with my arduino MEGA 2650 ,

Archive FastLED Archive
,
1

Stuck with my arduino MEGA 2650 , WS2811 led strip and FastLED!! Can’t make it work, even library example code, but everything is OK with FastSPI2… In blink sketch if i put NUM_LEDS 1 it works, but if more than 1 not… And second, I’m using pin 13 for data with led light and it is blinking bright with FastSPI2 when data going to led strip and pretty dimly when whith FastLed

2

Try using a pin other than 13 for a quick start. Also - what version of FastLED are you using, and what platform (mac os x, windows, ubuntu, something else) are you building from and what version of the arduino software are you using to do the build?

3

I tried and I got the same(( FastLed 3.0 and Windows 7 arduino 1.0.6

4

Try the FastLED 3.1 branch (I’m not going to be able to test anything on my setup until tomorrow at the earliest)

5

I checked this with my logic analyzer and seems like I got different timings… For Fastspi2 T0H=437 ns and that accords datasheet for WS2811, but for FastLED T0H=250 ns… Total period for both is the same and = 1.3 ms

6

Yeah - the timings had been tweaked according to a set of leds that I have here (both ws2811 and ws2812).

If you look in chipsets.h, around line 378 - swap out the commented pair of lines and see if that helps - ws2811 timings varied wildly across batches :frowning:

7

how I can get back old timings from fastspi2??

8

in datasheet for WS2811 T0H=500 ns, for WS812 T0H=350 ns

9

Read my comment again - go into chipsets.h - around line 378 - there’s two lines of timing definitions for the WS2811 - one commented out, one not commented out - swap which line is commented out.

10

John and again - I have 3 WS2811 datasheets with different timings on them, and I also have two separate sets of WS2812 timings from different data sheets - and I had to adjust the timings based on the physical WS2811s and WS2812s that I had.

11

Thanks a lot!!! Now it works)))

12

I’ll see about coming up with a cleaner way to let people switch between the timings. I think you are only the second person I’ve run across that has benefited from those timings!

13

I think u need to add more option into #define CHIPSET… like WS2811(250) or WS2811(500)

14

That’s not how they’re defined anymore, but yes, something along those lines. The big thing is keeping the default WS2811 to what it is (since most people have no problems with that) but make the backup WS2811 timings easy to switch to if someone has a problem with them.

15

@Daniel_Garcia would these timing account for the difference in brightness i’m seeing between Fast_SPI and FastLed?
I see less flicker with FastLed, but they are noticeably dimmer (drawing about half the current).

16

No, but the FastLED hsv to rgb conversion attempts to do a more logarithmic scaling, so possibly that is what you are seeing in your code?

17

I will have to setup some tests. I notice there is a power management functionality in progress, that could be interesting.

I’ve just run Marks Xmas twinkle code on a string of 100 WS2811 12mm LEDs via the USB port on my laptop 0_o