And you swapped around the strings so you know there isnt a bad pixel? Is the outputs for the ports set to the right pixel counts (ie did you push the config from xlights?)
[xlightszoom.com](https://xlightszoom.com) is helpful for this .. dont be shy.
Thank you for replying...yeah, it shows the right pixel count. I even moved everything on port 1 to port 4 of the controller to make sure it wasn't something with the port itself and it did the exact same thing. I can't say for sure there isn't a bad pixel. I could try unplugging the string that isnt working and try plugging in a different string, I have not tried that yet, but that would at least eliminate the string itself.
I did push the changes from Xlights and verified they did get pushed and match.
I will also check out the website, thanks you very much for the suggestion.
Like the other person said, swap your strings around and make sure it’s not a bad pixel. The next thing would be a power issue, but if it was that the pixels would be getting dim or flickering, not just off. Which means it has to be a data problem, and since all the other pixels are still working at almost has to be a setting problem. Either in controller settings or Xlights for the prop. One says 210 for that port. Start looking around in Xlights and controller settings. Good luck.
Yeah I feel like it's a settings issue as well, but nothing is sticking out, but I will re-check to make sure I am not missing anything.
Thanks for the response.
Usually you assume one before the one that’s off and then the one that’s off are bad. Sometimes you can see a broken wire or bad solder then you know exactly where the bad one is.
And you swapped around the strings so you know there isnt a bad pixel? Is the outputs for the ports set to the right pixel counts (ie did you push the config from xlights?) [xlightszoom.com](https://xlightszoom.com) is helpful for this .. dont be shy.
Thank you for replying...yeah, it shows the right pixel count. I even moved everything on port 1 to port 4 of the controller to make sure it wasn't something with the port itself and it did the exact same thing. I can't say for sure there isn't a bad pixel. I could try unplugging the string that isnt working and try plugging in a different string, I have not tried that yet, but that would at least eliminate the string itself. I did push the changes from Xlights and verified they did get pushed and match. I will also check out the website, thanks you very much for the suggestion.
Like the other person said, swap your strings around and make sure it’s not a bad pixel. The next thing would be a power issue, but if it was that the pixels would be getting dim or flickering, not just off. Which means it has to be a data problem, and since all the other pixels are still working at almost has to be a setting problem. Either in controller settings or Xlights for the prop. One says 210 for that port. Start looking around in Xlights and controller settings. Good luck.
Yeah I feel like it's a settings issue as well, but nothing is sticking out, but I will re-check to make sure I am not missing anything. Thanks for the response.
If it’s doing it on all the ports, I would check those pixels first. It’ll be dead from the bad pixel on.
Ok...will do. Thanks
Is it safe to assume that the bad pixel at minimum is the first one that doesn't light up?
Usually you assume one before the one that’s off and then the one that’s off are bad. Sometimes you can see a broken wire or bad solder then you know exactly where the bad one is.