Help with Mega Tree Null Pixels

[HDhomer]

Hey All, Wondering if there are any wizards here that can see if i have set things up correctly in my Falcon Controller to handle Null pixels in the middle of a string on my Mega tree.

I am using a SRx2 smart receiver so the tree is split over the 8 ports between A & B on the smart receiver.

I have the tree setup it up as 8 strings(8 ports) with 192 pixels per String and 3 strands per string.

I am using 5cm spaced seed pixels to go from:
1. Bottom of the mega tree to the top (63 pixels)
2. Back down (63 pixels)
3. Then across the bottom there are 3 pixels that i want to Null
4. Then it goes back up to the top (63 Pixels)

Step 3 is the bit i'm asking about. In order to not have to cut and solder the pixel wire when the string comes back down from the top on the second strand to then reach the 3rd strand going back up i need to leave 3 pixels along the bottom to space the strings apart properly.

Edit: I should state what ive done. On each port i have created a virtual string. On the first part i go 63x2 so 126 pixels + 3 Null pixels so call it 129 pixels and then i null 3 pixels at the end. Then on the Virtual string i say another 63 pixels.

See the two images below. The first is how i've setup the controller and the second image you can see the full String. It goes from left to right:
Up 63 Pixels
Down 63 Pixels
3 NULL pixels along the bottom
Up again 63 pixels then that string ends and i repeat the same patter on the next string for all 8 strings.

Hope this makes sense! Thanks for your help in advance!

 

[brother fergy]

Hey All, Wondering if there are any wizards here that can see if i have set things up correctly in my Falcon Controller to handle Null pixels in the middle of a string on my Mega tree.

I am using a SRx2 smart receiver so the tree is split over the 8 ports between A & B on the smart receiver.

I have the tree setup it up as 8 strings(8 ports) with 192 pixels per String and 3 strands per string.

I am using 5cm spaced seed pixels to go from:
1. Bottom of the mega tree to the top (63 pixels)
2. Back down (63 pixels)
3. Then across the bottom there are 3 pixels that i want to Null
4. Then it goes back up to the top (63 Pixels)

Step 3 is the bit i'm asking about. In order to not have to cut and solder the pixel wire when the string comes back down from the top on the second strand to then reach the 3rd strand going back up i need to leave 3 pixels along the bottom to space the strings apart properly.

See the two images below. The first is how i've setup the controller and the second image you can see the full String. It goes from left to right:
Up 63 Pixels
Down 63 Pixels
3 NULL pixels along the bottom
Up again 63 pixels then that string ends and i repeat the same patter on the next string for all 8 strings.

Hope this makes sense! Thanks for your help in advance!

You need to configure the port for each string to include the three null pixels as a "virtual string" section, ensuring those specific pixels are designated as "null" on the controller side.

1. Navigate to your Port Configuration page on the Falcon Controller's web interface.
2. Find the port corresponding to the first string.
3. Click the + icon next to the port configuration entry to add a new "virtual string" section within that same physical port.
4. Define the sections as follows for each of the 8 strings:
   • Section 1: Pixels 63 (up)
   • Section 2: Pixels 63 (down)
   • Section 3: Pixels 3 (null) - In the settings for this section, you will specify it as having 3 null pixels.
   • Section 4: Pixels 63 (up)
5. The total count for the controller port will be 63 + 63 + 3 + 63 = 192 pixels, matching your current total pixel count per string.

This tells the controller that the data signal must pass through all 192 pixels, but the 3 specified in the middle section should be treated as non-lighting pixels.

In xLights
You need to ensure your xLights model for the mega tree accounts for these 3 unlit pixels to correctly map effects.

1. In your xLights Layout tab, your mega tree model definition should also account for all 192 pixels, but the software needs to know which channels to ignore.
2. You can model this in xLights by treating the null pixels as part of a separate, unlit model or, more simply, ensure your main mega tree model is set up as a custom model or polyline that skips the specific pixel numbers corresponding to the 3 nulls when mapping the display.
3. Alternatively, a common method is to create a small, separate, single-line "Null" model for the 3 pixels in xLights and ensure it is placed at the bottom of the sequence timeline and assigned an "Off" effect to guarantee they never light up.
4. When you map your main mega tree model to the controller ports in xLights, it will send data for all 192 pixels, and the controller's internal configuration will prevent the specific 3 "null" pixels from illuminating.

Your approach of running the string up, down, across the bottom (3 null), and up again works physically, and using the virtual strings feature in the Falcon controller is the correct way to configure it.

 

[HDhomer]

You need to configure the port for each string to include the three null pixels as a "virtual string" section, ensuring those specific pixels are designated as "null" on the controller side.

1. Navigate to your Port Configuration page on the Falcon Controller's web interface.
2. Find the port corresponding to the first string.
3. Click the + icon next to the port configuration entry to add a new "virtual string" section within that same physical port.
4. Define the sections as follows for each of the 8 strings:
   • Section 1: Pixels 63 (up)
   • Section 2: Pixels 63 (down)
   • Section 3: Pixels 3 (null) - In the settings for this section, you will specify it as having 3 null pixels.
   • Section 4: Pixels 63 (up)
5. The total count for the controller port will be 63 + 63 + 3 + 63 = 192 pixels, matching your current total pixel count per string.

This tells the controller that the data signal must pass through all 192 pixels, but the 3 specified in the middle section should be treated as non-lighting pixels.

In xLights
You need to ensure your xLights model for the mega tree accounts for these 3 unlit pixels to correctly map effects.

1. In your xLights Layout tab, your mega tree model definition should also account for all 192 pixels, but the software needs to know which channels to ignore.
2. You can model this in xLights by treating the null pixels as part of a separate, unlit model or, more simply, ensure your main mega tree model is set up as a custom model or polyline that skips the specific pixel numbers corresponding to the 3 nulls when mapping the display.
3. Alternatively, a common method is to create a small, separate, single-line "Null" model for the 3 pixels in xLights and ensure it is placed at the bottom of the sequence timeline and assigned an "Off" effect to guarantee they never light up.
4. When you map your main mega tree model to the controller ports in xLights, it will send data for all 192 pixels, and the controller's internal configuration will prevent the specific 3 "null" pixels from illuminating.

Your approach of running the string up, down, across the bottom (3 null), and up again works physically, and using the virtual strings feature in the Falcon controller is the correct way to configure it.

Amazing thank you so much for the detailed reply!

Honestly that sounds pretty complex and the easiest solution sounds like I should just not be lazy and try and fix it in software and just cut those pixels out and solder in a wire join.

I’ve already had to do it 99 times with my pixel stakes, so what’s another 8 times on the megatree.

Appreciate you taking the time to write up a solution though!