Strange Model Light Behavior Skipping a Node

[popcorndog]

Issue:  I am having strange behavior out of one of my sequences where I apply lights to two lines in a snowflake model.  I have part of a sequence that is designed to create a sand island with a swaying palm tree.
 In xLights, all lights are displaying correctly when played back.  On FPP, four of the snowflakes (ports 1 & 5) in the show light the two lines correctly and four of the snowflakes (ports 2 & 3) skip the last node in the model line and light the next node which results in the lights forming an L shape verses a straight line.  All snowflake models have been created the same identical way, both in xLights model layout and in the actual model wiring.

I am running 3 universes for a total of 1200 channels.  I am using ports 1 and 2 on the F48.  I am using ports 1, 2, & 3 of one Falcon smart receiver and port 1 of the other falcon smart receiver.  I have attached the models in a pdf along with the Falcon 48 E131 and String Port settings. 

I have been banging my head up against a wall trying to correct this triple checking each model, wiring, and configuration.  I am at a loss, as it appears to me that all the ports and models are configured the same.  Open to all suggestions, as my sandy beaches look are distracting from the show. 

Lights:
50 x 8 WS2811 Pixel Nodes across 8 Boscoyo 3 prong and 2 prong snowflakes

Controllers: 
Falcon F48v3
2 x Falcon Smart Receivers
2 x Raspberry Pi 4 running FPP (One Main and One Remote for Audio which is Multi-synced)
3 x 12v Meanwell Power Supplies

Software:
Running the latest versions of xLights and FPP.

Also to note, this is only my second year programming and running a light show.  So new to xLights, controllers, nodes, and such.

Received an error when attempting to post, so posting again.

[Gilrock]

First I start swapping cables and see if the problem follows the prop or the port.

[popcorndog]

Ok, switched port 1 (represents line model correctly) with port 3 (lines form an L which is not correct), and the skipped node L issue moved to the snowflakes previously on port 1.  The snowflakes previously on port 3 displayed straight lines correctly.  I will check my model configuration for port 1 and port 3 comparing the two.  Will post what I find.

[popcorndog]

Comparison checked, a functioning snowflake with the exact model as a non-functioning snowflake, and the model parameters in xLights and they are identical.  Checked the FPP port configurations and they are a match to the port configurations in xLights.

Could there be an issue with Auto Layout Models?

Anything else I should check?

[Gilrock]

It sounds like the props/lights are fine and if everything in xLights looks correct in the preview then its a setup mismatch between xLights and the controllers.  Would be best to seek help in the xlights zoom room.

[popcorndog]

Happy to report the issue is resolved.

My previous experiences last year allowing xLights to control the lights and uploaded x-light configurations did not go very well.  I had numerous issues.

That said, tried the xLights autosize and full control setting again.  The lights are much worse than previously.  The lights on the first snowflake of each series (2 snowflakes total per port) display fine.  The nodes I left at the back end of the first snowflake are not lighting, exhibiting the proper null settings.  The second snowflake in the series is much worse.  The model is all out of wack, with lights a bit scrambled around.  The two null lights at the end of the second snowflake turn on with the sequence.

I then changed the Null string settings, deselecting the Set Start Null pixels.  Wala, I finally have everything working perfectly!  xLights Start null pixel settings skips nodes before starting the node with your light settings, hence it was throwing everything off past the first snowflake.

Dealing with null pixels is very confusing.

Someone in another forum suggested I cut my last nodes off the strings and reattach the pigtail.  I use full 50 count strings for a couple of reasons.  First, if a line goes bad, it is a lot more effort to replace as I have ordered standard 50 node strands.  Second, even though I would do a fairly decent job soldering the tail on and would shrink sleeve them, it would not be water proof.  Hence the path I chose.  Agree, it is a little more confusing on the programming end.  Now that I understand what xLights does with Null settings, should not be a problem moving forward.

[Gilrock]

I always cut to size.  And unless you plan to have the cables underwater they will last many years without being waterproof.  My whole display is full of heat shrink butt connectors and sometimes I get busy and don?t even do the shrink step.  It?s raining on them right now. Some of my cables are 10 years old.