First time user. As new as new can be.
First test PixLite 16, WS2811, lights 60/meter, 4 meters long. 16 strings but only 1 string connected to universe 1 at this time. Using e1.31 communication.
1) Factory Test works perfect. All 4 meters of RGB (GRB actually) work and cycle as expected.
2) Advatek-Assistant-V2.1.7 finds the controller without issue and I set it up for just a single string 240 pixels (tried a larger number, 300 no help)
3) XLights "test" mode runs fine except now the last meter of lights do not function at all. All of the test sequences seem to react as expected.
4) Don't know if it has any effect in test mode but I also played with the Model and # of pixel settings with the same result, the last meter not functioning.
5) Attempted to use Vixen to test lights but nary a blink from any light so I am obviously on the very left side of the learning curve.
6) In conclusion, right now the only mode which will activate all LEDs is the Factory Test mode of the PixLite 16 controller.
Can anyone give me the hand to forehead clue?
Am I correct that I can only only set 170 RGB nodes per string as that would equal 510 channels per universe or individual output on the PixLite 16? If so then it is actually working and I cannot have the full 4 meters in height. Hmmm.
I'm not familiar with that control board, but, looking on their website, it says that it can control up to 32 universes of data, and up to 340 nodes per individual output. So, that would mean that one output could handle 4x60=240 pixel nodes.
A universe will still be 170 pixels, or 510 channels (with two wasted). I'm not sure how that controller handles that, but you need to look at how xlights is configured along with how the controller is setup to take the data and output it.
I seem to be wrapped around the axle with pixels, elements, nodes. In all my engineering years I would treat an RGB element as 3 pixels or nodes. Now, every time I try to save an xLights sequence it is telling me "Increasing sequence channel count from 512 to 3300 Either your model is incorrect of the networks you have defined on the Setup Tab are Incorrect.
I went and set xLights to 110 RGB nodes per string and that seems to stop the error message. I am assuming 110 RGB = 330 physical LEDs / string.
Alright, if I break this down to what I actually know (or think I do) the math does not reflect what I am seeing.
My lights are 60 RGBs per meter and the strip is 4 meters long which should give me 720 physical LEDS or 240 Red, 240 Green, 240 Blue.
The PixLite manual states MAX 340 pixels/output.
Now if that is the case I should only be able to illuminate less than half or 2 meters of the light string [360 leds] HOWEVER I can always illuminate and control 3 meters which would be 540 individual LEDs via xLights by telling it I have 110 Pixels/string which I gather is 330.
The pixel count for your 4 meters is 240. The channel count for that same strip is 720. Your PixLite should be able to handle it with no problem.
Check to see if the lights are shutting down after 170 pixels/510 channels. If so, this is a sign that you are only able to send 1 universe to that port on the PixLight.
Thanks algerdes. I gather in this world of displays, a pixel consists of 3 LEDs. My previous world in electronics engineering a pixel was the smallest unit or just a red or a green or a blue element/image. Your explanation helps immensely.
510 channels or 170 pixels would make sense to what I am actually seeing as I get full control of 3 meters worth of this light strip.
As of right now, I am unsure as to how to force a 2nd universe to that output (assuming it is even possible) but PixLite claims to support 32 universes with 16 physical outputs. I'll read/reread and search for additional information.
Thanks again,
Mike
I think part of the problem here is terminology.
Pixel: 3 LEDs and a pixel control chip (WS2801/WS2811/ect...) in a single housing. One RED LED, one GREEN LED, one BLUE LED. NOTE: Not all pixel implementations take there inputs in this order.
Node: This is usually the same as Pixel.
Pixel String: Pixels connected by groups of wires with a typical spacing of about 4in.
Pixel Strip: A length of flexible PCB that has a pixel control chip + some number of pixel LED groups. Most typical configurations are
- 1 Chip plus one LED group
- 1 Chip plus three LED groups
NOTE: Many of the Pixel strips I have seen are actually set up as BRG and will not work as expected unless this is fixed in the sequence software or on the pixel controller.
Universe: A common term applied to a grouping of channels (NOTE: Channels, not pixels). It takes 3 channels to drive a pixel. In most implementations, a universe represents 512 channels (~170 pixels using 510 channels).
Now to get to your math.
For the most part, you are on the correct path. Your raw numbers:
- 60 pixels / Meter (I am assuming you have the 1 LED group per chip model)
- 4 Meters = 4 * 60 = 240 Pixels
- 240 Pixels = 3 * 240 channels = 720 channels. (240 Red, 240 Green, 240 Blue)
Based on this, Yes you should have no problem connecting all 240 Pixels to a single channel on a PixLite-16 board.
The next thing to look at is the number of pixels that can be controlled by a 'Universe'. Your 240 pixel configuration will need two universes (You have not mentioned how you set up your universes). 170 pixels plus two channels from pixel 171 on the first universe and one channel of pixel 171 plus 69 pixels on the second universe. Have you configured this?
While the above assumes you are using the universe concept, there are other ways to configure your system that make it independent of the universe concept. However, you have not indicated how you configured this so it is difficult to answer your question.
Martin
I have to agree with the caveat. It is actually the number of control chips that would be included in the "pixel count". I have some WS2811 strips that drive 3 LEDs as 1 "pixel". Others have a chip on each LED making them a "pixel" for each LED. Most wired lights would be a good example of one chip per LED. Your description got me to thinking it was the later (1 chip per LED).
Personally I refer to each changeable LED or group of LEDs working as one to be a "node". In the case of a "Universe", that would be 170 nodes.
Make note of the fact that a DMX universe is actually 512 channels. Unfortunately this does not divide by 3 without having a remainder (2). Some controllers use all 512 channels, others just 510, but this is getting off track.
In any case, it sounds like your strips are stopping at a universe break, but you need to make sure before troubleshooting any further. If it is more than a universe, then you may have a physical problem with the strips. If it stops at the universe break, then you can start looking at settings.
One thing you can try, if there is a test mode on the controller (the E1.31 Bridge from DIYLEDExpress has it now), turn it on. If all lights light, you have a settings problem for sure.
BTW, there are many more qualified than I to tell you about your particular controller.
Sorry about the ramble. In my defense, it is Sunday morning after all. 🙂
Thank you Martin for that detailed explanation!
The reason, I did not mention how I set up the universe is using the Advatek-Assistant-V2.1.7 which is the configuration software for the PixLite I have not seen how to assign more than one universe per physical output (which they also refer to as channels and as STRINGS ) The ADVANCED dialog only shows the 16 individual STRINGS which you can supply a universe # and manually set the Start Channel, Number of Nodes [& null pixels and zigzag]
I do know that it would never allow me to input a number larger than 340 in the Number of Nodes column. Again there are only 16 STRINGS and unless the PixLite automatically assigns a 2nd universe for a given STRING I am unsure as to how to address this.
