Has anyone experienced this problem?

[etterm]

I have a 16X50 Mega Tree , 23" Boscoyo 90 node star , (5) 50 node mini trees with (5) 20 node stars. I switched from a SanDevices E682 to a new Genius 16 port pixel controller.

Mega tree used ports 1-8 .
23" star uses port 9

Port 10 is (1) 50 node mini tree - (1) 20 node mini star to 6ft extension cable to (1) 50 node mini tree - (1) 20 mini star , then ends.

Port 11 is (1) 50 node mini tree - (1) 20 node mini star to 6ft extension cable to (1) 50 node mini tree - (1) 20 mini star , then ends.

Port 12 is (1) 50 node mini tree - (1) 20 node mini star , then ends.

All my pixel strings are 50 nodes.
The problem is with the 2 pairs of mini tree and stars (ports 10 & 11)

Port 10 Mini trees are connected to controller by Ray Wu pigtails to 4ft extension cable to (1st) 50 node mini tree then soldered to (1st) 20 node star , the 6ft extension to (2nd) 50 node mini tree to (2nd) mini star , then ends.

Port 11 mini trees and stars are connected the same as port 10 props.

** The problem I'm having is the last pixel of mini stars (before extension cable) will light up red and stays on. No test pattern on. All other pixels are off and happens as soon as power is applied to controller.
** When the extension cable between the mini tree/mini star props is removed the pixel does not light.
** I've factory reset controller and double checked all the wiring and controller setting and nothing has cleared that one pixel.
** Since all my pixel strings are 50 nodes , I've soldered 20 node for stars to the 50 nodes of mini trees. The extension cable is soldered to the end of 1st mini star and then soldered to start of 2nd mini tree and star.
** and it happens on all ports.

Any help or suggestions would be appreciated on why that pixel lights up red while on stand by.

[Aurbo99]

e682 uses 510 channels per universe as default
Genius 16 uses 512 channels as default

Carefully check your channel configurations on the controller as you may have overlapping channels that may be trimming each pixel string by 2 channels after the 510 old controller universe ends and the new controller 513 pixel channel begins

which will give you issues like you are describing

Also non-continuous channel counting routines like;
(based on 50 pixels per plug)
(DMX510)

plug1
start: Universe 1 channel 1
end: Universe 1 channel 300

plug2
start: Universe 2 channel 1
end: Universe 2 channel 300

Can also cause hardware test pattern problems.



I use continuous routine like:

plug1
start: Universe 1 channel 1
end: Universe 1 channel 300

plug2
start: Universe 1 channel 301
end: Universe 2 channel 90

And I do not have hardware test pattern problems.

[Aurbo99]

Also test your extension cables for proper pin out.

[etterm]

Thank you for your help.

Okay. I’ve removed all other props from Genius board. I only have one pair of mini trees and stars connected. It still lights the last star pixel red.

Then, I removed the extension wire and added a new string of 50 pixels to the end of star pixels (no extension) and all pixels act normal. No constant red pixel on.

So, I added the extension cable between one mini tree/star prop and new pixels and the last star pixel lights up.
It’s like it doesn’t like the extension cable.

Do you think it could be my pixels? I’ve noticed the gauge wire in my mini tree / star pixels is a bit thinner. (The pixels used for mega tree and 23” star are from a different manufacturer and wire is thicker gauge.) I’ve just ordered 3 strands of 50 from Wally’s to test if it may be pixels. I didn’t have this issue with my SanDevices board. It’s weird.

[Aurbo99]

The value of the SIP resistor networks on the e682 can be altered to account for wire resistance/wire length

Not sure if the same is possible on the G16

Try swapping the extension cable with another to rule out or confirm it's the issue

[MartinMueller2003]

Have you measured the voltage at the end of the string?

SIP only has an effect between the controller and the first pixel in the string. You would be seeing issues at the first pixel if the wire between controller and string was defective.

[MikeKrebs]

Post a picture of your genius config. Maybe we will see something in there.

If the same pixel and same brightness every time you cycle the power and it works on the Sans then you most likely have bad firmware or config on the genius.

Does it happen on every port of the genius?

You are saying that both strings on two different ports have exactly the same problem? It is pixel 70 on both strings?

Is the brightness 100% red or something below it?

Did you say the pixel works fine if you send a sequence or test pattern?

If you plug the same cables/props into the Sans Device, all is good?

There is a feature on the Genius board "Repair mode highlights where you need to splice to remove failed pixels*" Is it saying you need to fix me?

[etterm]

Thank you for all the suggestions. I’ll be trying them all in the next couple of days. The pixels I ordered from Wally’s should be here tomorrow.
I’m going to try my best to post a video and pictures to see if I’m doing something wrong.

[etterm]

Thank you for all the information. I've included a short video showing that the (1) red pixel is pulsing. Pixels are all WS2811

(1st batch of pixels (1000) for my Mega Tree & 23" Star are from William Lamp Store on AliExpress)
(2nd batch of pixels (500) for 5 X mini trees and stars are from China Light Store on AliExpress)
(3rd batch of pixels (159) for testing are from Wally's Lights (haven't tested these yet)

I changed out the extension cable and it still lights red. I noticed that when I removed postive wire from the extension cable, that runs between both trees, pixel stays lit red but when I remove to negative wire is goes off. Then with positive wire connected and negative wire not connected, pixel is off. I've tripled checked that no wires are crossed and everything is good.

My mini trees are 50 pixels with 20 pixels for stars (cut from a new 50 pixel string) then soldered to end of mini tree pixels.
50 + 20 + 50 + 20 = 140

So, controller powered on , no test pattern running at 50% power.
Voltage at 1st mini tree & star (before extension) is 11.98
Voltage at extension to 2nd mini tree & star is 11.97
Voltage at the solder point between 2nd mini tree & star is 11.94

With controller at 50% power and pixel marker test pattern on.
Voltage at 1st mini tree & star (before extension) is 9.64
Voltage at extension to 2nd mini tree & star is 9.51
Voltage at the solder point between 2nd mini tree & star is 8.85

I added power injection and tested same voltage points as above and the voltage didn't go below 11.30

Red pixel stayed on through all tests.

It happens on all 16 ports.



pixel trees.jpgsettings.jpg

[etterm]

Post a picture of your genius config. Maybe we will see something in there.

If the same pixel and same brightness every time you cycle the power and it works on the Sans then you most likely have bad firmware or config on the genius.

Does it happen on every port of the genius?

You are saying that both strings on two different ports have exactly the same problem? It is pixel 70 on both strings?

Is the brightness 100% red or something below it?

Did you say the pixel works fine if you send a sequence or test pattern?

If you plug the same cables/props into the Sans Device, all is good?

There is a feature on the Genius board "Repair mode highlights where you need to splice to remove failed pixels*" Is it saying you need to fix me?

Yes, it happens on every port of Genius.
I have 50 pixels then 20 soldered to mini tree - extension cable - 50 pixels then 20 pixels soldered to mini tree. 140 pixels on 1 port.
I've tested at 50,60,70,80,90 & 100 percent, stays red and it pulses.
On test pattern it acts more normal but I noticed the red is on as well.
I've sold the E682's , can't test on SanDevices.

Can you help me with the "repair mode" feature? Where is it located?

Thank you for your time.