Falcon Controller connections in the middle of a matrix column

[laserman]

I have an ever-expanding show with five controllers now, but this is the first year I have added matrices.  I have a 34 high x 38 wide matrix that I am running off of three outputs from a Falcon F16 V3.  I wired it with 100 node strings in a vertical up-down pattern.  Obviously 100 node strings do not divide evenly with 34 node columns so each string ends somewhere in the middle of a column.  I had planned on having 400 nodes (4 strings) on the first and second outputs, which would leave 492 nodes for the third channel.  I didn?t realize there might be a software problem as a result of having a controller output feed a string in the middle of a column until I started trying to set it up in x-lights. I can?t seem to make it work because I keep getting a mess on the matrix and/or a red highlighted row in x-lights when I enter certain values for the Strands/String row.  Is there an x-lights/Falcon setup solution or do I have to rewire my matrix so each of the three outputs starts a string with even multiples of 34 (i.e., 1, 409, and 817)?  I sure hope there is a software fix.

[laserman]

I concluded that there was no software fix to my problem.  I should have done a little homework on how to set up matrices in Xlights before I started instead of assuming I could build whatever I wanted and then get the software to match it.  I reworked my lights so I had two strings of 646 nodes each.  That gives me 19 columns (strands/strings) for each each string and each string has its own Controller output.  I am still struggling to get it to display correctly but I assume I can get that figured out.  I will come back for help if I can't figure it out.

[Gilrock]

Usually its only a problem if you want to have xLights automatically upload the configuration to the controller.  Otherwise just lie to xlights to create the matrix and manually setup the outputs in the controller.  xLights doesn't need to really know the actual number of strings just make it 1 string.  That creates a block of data in the sequence and then you map that data to the controller outputs by setting up the controller to reality.

[jnealand]

I had problems with a matrix not exactly like your problem, but it takes a custom model to fix the issue.  I believe there is a video on this done in the PPD library.  This may be it, but I did not rewatch it to be sure - https://www.youtube.com/watch?v=BNGGXqgIkSg&t=1s

[allknowing2012]

Yep .. custom model and an excel spreadsheet to figure out where all the pixels are .. then cut n paste that back into the custom model. Zoom Room can help you on this .. (during less busy times - if that exists :-) )

[pennymoor]

in x-lights cant you make it 1 strand of 1292 pixels and set individual start nodes where the ports change in the prop settings that is what i do if  matrix is bigger than 1024 pixels in my falcons.

[allknowing2012]

For some models .. yes .. like custom models. Others you can only say how many strings/ports and it equally divides the pixel count by that number.

[laserman]

I had problems getting it to display correctly even when I changed to only use two ports.  The image coming from the second port was inverted.  The problem went away when I took Gilrock's advice and configured it as one string consisting of 1292 nodes.  Thanks for the help.