Having issues with "Set End Null Pixel"

[iarann]

Not sure if I'm misunderstanding something or just getting weird results. I have three models that are closely spaced so when I wired them I just continued the physical string through all three giving me null pixels between the models. When I set them up in xLights, I added the null pixels in the "Set End Null Pixel" field. However, the null pixels still light. I've tried various combinations of pixel count and Start and Stop End Null Pixel settings. No matter what combination I try, the pixels are lit, it just changes what model they light with. Tried it with two separate controllers.

Is there a way to do this using the "Set End Null Pixel" or do I just create dummy models for the nulls?

Model1 has 69 pixels and 2 nulls
Model2 has 45 pixels and 3 nulls
Model3 has 73 pixels and 8 nulls

xLights 2021.39
JBoards ESPixel Stick running firmware 4.0-beta4
JBoards Pixel String Pihat Zero
FPP 5.3.1

[Rudy B.]

https://www.youtube.com/watch?v=ilO3qvFyCRI

[iarann]

Slightly different situation here. That video describes null pixels internal to the model. These are between the models. So they are on different model strings.

[Gilrock]

I haven't messed with that end null feature yet but technically any null you claim is at the end of a model can be considered the beginning of the next model.

[allknowing2012]

Null pixels at the end is only for controllers that allow this feature - I thought that was just the newer falcons and perhaps kulps. Otherwise put them as start nulls on the following prop.

[iarann]

I tried using the Start Null as well with basically the same results. I plan on starting over from scratch post-holidays from controllers up. Too many changes tweaks and feature additions to the original layout.

Also, I thought the ESPixel was supported but mine is an original version so it may just be too old for that.