setting channel counts on e1.31 controllers in XLights

[neil]

I see some confusion with the various controllers having either 510 or 512 channels and it becomes more confusing as more controllers are supporting more pixels per output port and allowing the ports to span Universes.


I understand that the San Devices controllers support a max of 510 channels per Universe (170 RGB nodes) and XL should be configured as 510 channel on each E1.31 entry for that Universe.

when spanning Universes in XL/NC for a model it becomes important to know how many channels and nodes the controller supports per Universe otherwise setting the incorrect will effect the colors on the pixels.


I did check the wiki on Seans's RGB controller comparison and it only talks about the max nodes per output and not how many channels per Universe.


Does anyone have a good number for their controller that they had to use for each Universe of E1.31 in XL setup?

E682 510
E6804 510







 



 

[flyinverted]

A universe has 512 channels and that is universal.

All controllers can use 512 channels per universe, HOWEVER 3 channels are needed to control a single RGB light.
If you do the math, pixel #171 would end up on channel 511 and 512. This is OK if you only need R and G. but there would be no way to get BLUE to this #171 pixel.  That is why there's soft limit of 510.

If you had a DMX fixture like a strobe that turned on GREEN when CH511 was activated and Purple when 512 was activated this would be OK too.


There should be no confusion. Only the FalconF16 can span universes.

[neil]

the E682 says it can support 500 nodes on each output, will it be using a value of 510 channels or 512 like the F16 does?


the Alphapix and pixlite support a max of 340 RGB nodes and I think they also require the max channels on each Universe in the XL E1.31 setup to be set to 510 so that they span correctly.

[Gilrock]

Just buy controllers that can't span universes on its outputs....problem solved.

[msiebri]

I have a question related to this.  I'm not sure if I should ask here or on FalconChristmas, so I will start here.

This will be my first year with a prop that spans multiple universes.  I am planning to use an F16V2 with the expansion card to drive a new megatree with 24 100-count strings of pixabulbs.  Do I need to configure these universes in the setup tab as 510 or 512 channels?

- Martin

[neil]

I understand that the Falcon 16V2 is set to 512 channels in the XL and FPP E1.31 setup screens. This becomes more important that it is set right when spanning Universes with your models.

[flyinverted]

You can set the F16V2 up with 510 or 512 channel universes. Just set Nutcracker the same.   The folks watching your show won't care if they're 510/512.

[neil]

won't it effect any effects / colors that soon the Universes if it is wrong though.


I wish I could test this, but waiting on new controllers and power supplies to arrive

[flyinverted]

No it won't affect any effects.  The effects are placed on and rendered to models, not channels. NC does not care what channels the models are on.

You can have a megatree, with strands on different controllers. The only thing that matters is that the channels do not overlap. As long as you have the model defined correctly and controller config matches in NC, you're good to go.

[gerry]

Steve,

For the p10 panels on the BBB , what would you specify , 510 or 512 ?

For fseq execution , there is no such definition required, but for the e131 definition for bridge mode, and of course within xl, would it be 510 or 512  per universe ?

[neil]

for the P10 panels on the BBB you only need to define a range of Null channel in XL as it is not driven by E1.31


for my 8x4 panel layout (256x64 pixels) I defined 49,152 null channels

[gerry]

for the P10 panels on the BBB you only need to define a range of Null channel in XL as it is not driven by E1.31

Even in bridge mode, the xl setup definition is not used ?

The question still applies for the definition on the e131 screen on the BBB FP.

[Gilrock]

When driving lights from xLights you can't use NULL outputs.  Null outputs are only for situations where the output file will reside on something like a BBB that will have it's own definition of how to control the lights.

[gerry]

If I understand correctly,

To summarise then , if you consistently define/use 510 everywhere - you cant go wrong..

If you have the F16v2 , you could define/use 512, but one should know what one is doing ..

In the past , I had no need on any controller output to reach the boundary - but the panels now have to be paid attention to.


 

[pixelpuppy]

Not to muddy the waters, but for the sake of full disclosure, all universes do not have to be the same size.
Each universe can be a different size from 1 to a max of 512.  But everywhere that particular universe is defined needs to be set to the same size for that particular universe.  (xLights setup, Controller setup, FPP setup, etc.)

Its probably easiest to keep it all straight in our heads if we set every universe fixed at 510 channels but its not required to be that way.  F16V2 is not fixed at 512 or 510.  It uses whatever you set it to.  Likewise, SanDevices is not fixed at 510.  That is just the maximum it will take for each universe