Thanks for the replies, Yep, had both those ideas in mind, and already using the custom model. F-amps are being considered, but a lot more expensive than nodes...and I need lots (and don't really want to do more soldering).
At the moment, the model is just 2 matrices for a special project. One for each Falcon. Simple as that. Nothing fancy. The only hard part is each matrix occupies a whole controller (with about 1000 pixels per port), so there are heaps of extension cables.
I have 2 model build choices:
1. xLights Matrix, and add some unnecessary nodes on some ports to keep the pixels level, where the number of nodes is dictated by my max cable length, or:
2. build 16 strings in xLights, one string per port, with custom nodes on each port/string.
Building a custom matrix via separate strings with the GUI is a bit painful - so I would probably just manually modify the xml file.
My thought was that in the field for "number of nodes", it currently allows say "1".
Since I already define the matrix across 16 ports on the Falcon for example, it would be nice to define it as [1,1,1,0,0,0,0,0,0,0,0,0,0,1,1,1] - just like I would in Matlab. After all it is just basic addition on the address reference (from the previous string end address).
Cheers,
Trev
