I have a strange problem.

Jaroslaw_Pendowski · May 11, 2018, 4:35pm

I have a strange problem. I bought a couple of strips of what was advertised as WS2811 strips but I can’t make it work.

A simple code which should light each pixel red in 1-second intervals produces an effect of 3 blue pixels. (code: https://pastebin.com/7mu0p2UZ)

Here’s a video of that effect:

The strip chips have no markings on them - just a standard looking 8 pin chip for every 3 LEDs. I tried setting other chips in the code in case the seller didn’t know what he was selling/sent the wrong strips library but none of that helped.

marmil · May 11, 2018, 5:12pm

Your addLeds line in setup looks strange to me. Have a look at some of the FastLED examples.

github.com

FastLED/FastLED/blob/master/examples/Cylon/Cylon.ino

#include <FastLED.h>

// How many leds in your strip?
#define NUM_LEDS 64 

// For led chips like Neopixels, which have a data line, ground, and power, you just
// need to define DATA_PIN.  For led chipsets that are SPI based (four wires - data, clock,
// ground, and power), like the LPD8806, define both DATA_PIN and CLOCK_PIN
#define DATA_PIN 2
#define CLOCK_PIN 13

// Define the array of leds
CRGB leds[NUM_LEDS];

void setup() { 
	Serial.begin(57600);
	Serial.println("resetting");
	LEDS.addLeds<WS2812,DATA_PIN,RGB>(leds,NUM_LEDS);
	LEDS.setBrightness(84);
}

This file has been truncated. show original

And if it’s lighting up blue when it should be red you can try switching the RGB color order. Actually not a bad idea to test that with

github.com

FastLED/FastLED/blob/master/examples/RGBCalibrate/RGBCalibrate.ino

#include "FastLED.h"


////////////////////////////////////////////////////////////////////////////////////////////////////
//
// RGB Calibration code
//
// Use this sketch to determine what the RGB ordering for your chipset should be.  Steps for setting up to use:

// * Uncomment the line in setup that corresponds to the LED chipset that you are using.  (Note that they
//   all explicitly specify the RGB order as RGB)
// * Define DATA_PIN to the pin that data is connected to.
// * (Optional) if using software SPI for chipsets that are SPI based, define CLOCK_PIN to the clock pin
// * Compile/upload/run the sketch

// You should see six leds on.  If the RGB ordering is correct, you should see 1 red led, 2 green
// leds, and 3 blue leds.  If you see different colors, the count of each color tells you what the
// position for that color in the rgb orering should be.  So, for example, if you see 1 Blue, and 2
// Red, and 3 Green leds then the rgb ordering should be BRG (Blue, Red, Green).

This file has been truncated. show original

Stefin_T · May 11, 2018, 5:15pm

Review this format perhaps, https://pastebin.com/UWD5zxxK

Tom_Schubert · May 11, 2018, 5:16pm

@Jaroslaw_Pendowski Have you tried changing your RGB order line 9? Still doesn’t fix your counting errors though. Are these 3 or 4 wire leds? Difficult to see in the video.

FastLED.addLeds<ws2812b, DATA_PIN, GRB>(leds, NUM_LEDS);

Tom_Schubert · May 11, 2018, 5:21pm

We must have all 3 been replying at the same time

Jaroslaw_Pendowski · May 11, 2018, 5:44pm

@Stefin_T @Tom_Schubert GRB helped with the color but it stills lights up 3 LEDs at a time (both with WS2811 and WS2812B).
Now when I think about it - since there are 3 LEDs per segment (+4 resistors, 2 capacitors), maybe that’s a hint of what is going on/what chip is it.
I guess there’s always a chance that the chip addresses all 3 LEDs not each individual one, even if it was advertised as one.

Will_Tatam · May 11, 2018, 6:25pm

WS2811 is a control chip rather than an LED, so it’s entirely possible you have bought a strip of WS2811 where each chip drives more than one LED.

If you are buying strips, you should look for WS2812 or WS2813

Chris_Rees · May 11, 2018, 7:08pm

I agree looking at the cut lines you have a 3 pixels per IC setup. Is this 12v? I see this setup use 12v often

Jaroslaw_Pendowski · May 11, 2018, 7:12pm

Yes it’s 12V. I guess it’s probably 3 LEDs per IC. Thanks for the help guys!