Sean Meighan
Software => Xlights Setup => Topic started by: tktplz on July 11, 2021, 08:10:47 PM
-
I've searched all over, yet I cannot find the "best practices" for controller setup.
Background: I have 6 main controllers around my yard and house (all Kulp, either K8 or K16) and 4 matrices (all BBB with octoscrollers). I also have about 16 other AC boards around the yard as well... running DMX on universe 1.
Right now, I have everything sequentially ordered in xLights, based on my current prop channel needs. If a set of props on each controller needs, for example 750 pixels, that controller is set for 750 pixels, even though it may be a Kulp K8, with the capacity of (8*800) or 6,400 pixels.
My question: If I build new props or just want to change where props are plugged into, this would require a controller layout change, and it also would affect the other props down the line... So if I changed the channel count on the first controller, and added for example another 12 universes, this would shift all props by 12 universes... Causing me to have to reprogram the other controllers downstream.
My solution - Does this sound right... Can I setup my controller layout for the MAX PIXELS per port on each controller, even though I may not be using those channels right away? I'm not sure if it would grow the .fseq file too much, as the channels are mostly unused.
Any pros out there knowing the best practice? I'd appreciate any help!
-
In general, I wouldn't set it to the "max" the controller supports. If you try to do the test from xLights type of thing, it will be sending a LOT of extra data thats not needed.
I generally shoot for some happy medium.
My general suggestions:
1) put controllers that wont likely ever change size at the top of the list. The P5 panels, for example, will likely not change much or at all so having them set to the size they need and stick them at the top likely will allow them to never have to be reconfigured.
2) Size the remainder to a bit more than they need, usually enough extra to handle 2-3 extra "average props" at a minimum. In general, I add about a thousand channels which allows moving 3 100pixel props onto it if needed. For me, that's what happens the most. When I go setup in the yard, my carefully laid plans don't always work and I need to move a prop from one controller to another or similar so having a bit of a buffer helps. If the controller is mostly empty (lots of unused ports), I may add even more. If the controller is fairly full, maybe not as much.
3) When doing #2 round each UP to some multiple of 3 so each "first channel" is on a "3+1" boundary (like channel 3001). This just helps keep the "R" of the RGB in the right place. Kind of irrelevant, but helps for testings. :)
4) Once a year as we get close to show setup, I'll adjust the amount of extra channels for each controller based on estimates for this years show. That's usually enough. If the gaps are big enough, I can move things around a bit and really just need to reconfigure the outputs of that one controller.
THAT said, if you use FPP Connect and have everything setup, reconfiguring the controllers if you have to completely adjust everything takes almost no time at all. I can setup entirely new FPP SD cards in the controllers, make sure the hostnames/ip addresses are what I need, hit FPP connect, and all the controllers are ready to go. The largest amount of time will likely be spent on the "Batch Render" phase to re-render everything.
-
Thank you, Dan!! You make a REALLY nice controller and I love using them. I've upgraded from 8 - e682s to a myriad of K8s, K16s and K32s. I really like the batch upgrade options, like you mentioned. Thank you again for taking time to address my concerns.
I have had a show since 2010, and I started with AC - That was one universe of DMX for my 17 A/C controllers. Then I added in some RGB floods, then the e682s, then matrices... And I kept putting everything after the original controllers so I didn't have to reprogram their DMX addresses. And, when I started with Vixen 1, then Vixen 2, then Vixen 3, and now XLights, I HAD to keep the channels in the proper spots, as the data layer couldn't be moved in XLights. I've since gotten rid of all my data layers and replaced them with proper effects so I could move props/controllers around if needed.
I guess I will just invert my controller setup - I'll leave my 1 universe of DMX A/C props, but then I'll move the matrices up, then the rest of my pixel stuff after that. Thank you again for the insight.
Lastly - I have one more question for you... I have Kulp boards in each of my Pelican cases, receiving E131 data. I then use one of the serial outputs to generate the DMX signal I need to run my DMX controllers for A/C and my flood lights within each box. That worked AWESOME last year - I only need one data line to each box, then the Kulp board generates the DMX needed for that box. But... I tried to change over to DDP for efficiency's sake, but it won't allow it - I assume because I use the DMX out. Is this the case, or am I missing something?
Thank you again!!