RGB_Mixer
Supporting Member
This is real weird.
FOUR different controllers, multiple sets of WS2811 pixels, some new, tested, and never used. Some older working strings, working props, and even some WS2815 strips ? NO IDEA WHY THIS DOES NOT WORK.
WS2811 pixels are 50 node strings as noted above. NEVER had anything like this happen in the past.
Controllers:
SanDevices (1) 6804 & (2) 682 and
Advatek (1) PixLite 16 MkII Long Range AND (2) PixLite MkI controller.
The 6804 gives me grief from time to time so it is my bench controller. I tried three more controllers that HAVE always worked in the past with these pixels ? this is what makes everything really strange.
NONE of the controllers can control any of the old or new strings. Does not matter which end the data feeds, although it was fed into the -DI- and operating at 12v as checked by the power supply and benchtop meters.
Can access BOTH PixLite controllers via their app program, verified settings and none of the test modes work.
Swapped out and went to SanDevices. 6804, setup for ws2811. Using DA_e131 v2200, chase, 6804 showed data IN and NO LIGHTS. Same for the 682 controller. It showed data IN and NO LIGHTS. CRAZY, RIGHT?!
Tried swapping out known good strings, new and previously tested strings, even tried a few WS2815 strips. NOTHING WORKED. Okay, this is strange.
I have not used the Oscope to see if there is signal reaching but since ONE pixel always lights, something is trying to work. I cannot see having to resort to that since it is FOUR controllers that are acting up with these WS2811 pixels.
Anyone else ever encounter this?
FOUR different controllers, multiple sets of WS2811 pixels, some new, tested, and never used. Some older working strings, working props, and even some WS2815 strips ? NO IDEA WHY THIS DOES NOT WORK.
WS2811 pixels are 50 node strings as noted above. NEVER had anything like this happen in the past.
Controllers:
SanDevices (1) 6804 & (2) 682 and
Advatek (1) PixLite 16 MkII Long Range AND (2) PixLite MkI controller.
The 6804 gives me grief from time to time so it is my bench controller. I tried three more controllers that HAVE always worked in the past with these pixels ? this is what makes everything really strange.
NONE of the controllers can control any of the old or new strings. Does not matter which end the data feeds, although it was fed into the -DI- and operating at 12v as checked by the power supply and benchtop meters.
Can access BOTH PixLite controllers via their app program, verified settings and none of the test modes work.
Swapped out and went to SanDevices. 6804, setup for ws2811. Using DA_e131 v2200, chase, 6804 showed data IN and NO LIGHTS. Same for the 682 controller. It showed data IN and NO LIGHTS. CRAZY, RIGHT?!
Tried swapping out known good strings, new and previously tested strings, even tried a few WS2815 strips. NOTHING WORKED. Okay, this is strange.
I have not used the Oscope to see if there is signal reaching but since ONE pixel always lights, something is trying to work. I cannot see having to resort to that since it is FOUR controllers that are acting up with these WS2811 pixels.
Anyone else ever encounter this?