I may be trying to do the impossible, again!
I have a pixel tree, 32 strings w/ 63 pixels each = 2,016 pixels = 6,048 channels = 11.859 universes
Each odd string goes up and is connected to the next string which comes back down.
So I am using 16 inputs.
I am trying to use an E682 w/ 16 outputs.
E682 can have 12 universes
I am setting up my controller
which seems fine.
How do I set up xLights to match this?
I don't know anything about using that controller, but wouldn't you just add an e1.31 unicast device to xlights with a starting universe of 59, #universes set to 12, maybe(?) check the one output box and that's it?
Sent from my Moto G (4) using Tapatalk
I don't understand use of the checkbox for one output. I'll try that.
First off you'll need to tell the E682 that every other string is zig-zag, put in 63 for that field on all your outputs in the E682 config page.
To add these in xlights:
In setup Click Add E1.31
Select unicast, put in your IP
Put in start universe, 59 in your case
Leave # of universes at 1
Leave one output UNCHECKED
Put in last channel #, 510 for the E682
Hit OK
Repeat for universe 60 - 69.
Universe 70 last channel will be 438 according to your config page.
That is as far as I can get you, I only use xLights for testing individual channels / elements. I don't actually sequence or map elements in xLights though.
As far as I can tell, it causes xlights to create only one line item. I don't know what that does beyond making it easy to enable/disable it as a whole. I'm not too keen on universe/channel number stuff as I use the absolute channel number mode in my Falcon controller and the absolute numbers that show up in xlights. I might be missing something important, but so far it works for me. I'm sure I'll be in for a rude education in the future though when I expand upon things.
By adding a fake device similar to yours, I can see that the box for last channel number applies to all the universes added. I don't know if you need to be concerned about the 510/512 split pixel issues that some controllers/firmware have. If you do, I don't know how you'll handle that on your controller end.
I have 32 universes defined in xlights and I noticed that when I added the fake device starting at universe 59, for 12 universes, that the absolute channel numbers picked up at 16384 right after the end of what I had defined. It didn't skip a bunch of channel numbers. I don't know if that's something you have to worry about or not. I really need to educate myself on the whole E1.31 thing and how things are addressed in the packets transmitted. I'm guessing that the packets have universe/channel info in them and not the absolute numbers that I see in xlights, then again... maybe they do? Maybe someone could chime in here and educate both of us on it. 🙂
EDIT: Looks like someone already responded that surely knows more than I do. I am curious about the "One Output" box and why you shouldn't use it. It does look like you need to keep things bounded to 510 channels per universe. I did a little digging and I think that my rude education will start just as soon as I try to add a second Falcon controller to my setup. It appears that by making my Falcon and xlights setups match, I've been able to avoid having to worry about universe/channel to absolute channel mapping. I apologize if I'm just confusing the issue for you, or if I'm steering you in the wrong direction by making assumptions that I shouldn't.

