F16v5 - issue testing over 170 pixels per channel

[coyoteray]

What am I doing wrong?  If I run a fade to red (blue, or green) and have a port set to over 170 pixels the next channel's pixels either don't light up or don't light up the correct color.  I reset the FC16v5 to factory and get the same results.   See images for details. 

[tbone321]

I believe that there is a firmware bug causing this issue.  How exactly are you running this test?

[coyoteray72]

I am running the test through the Falcon controller UI, the test page and then selecting <color> ramp.   I suspected there is a firmware issue, not 100% sure.   Wanted other people opinion first to be sure. 

Thank you for the quick response. 

[k6ccc]

Usually when that issue crops up it is because of a mismatch between the controller and whatever is sending the data on the number of channels in use.  A full DMX universe is 512 pixels which is 170 pixels with two channels left over.  In most cases you can set the number of channels in use and if the sender and controller are not set the same, you will get exactly what you are seeing.  As long as the controller and the sending software can handle a pixel that crosses universes, you can set it to either 510 or 512 channels, but SOME controllers don't support having a pixel that is partially in one universe and partially in another.  If that's the case you must use 510 channels.  I assume the F16v5 does not have an issue with pixels crossing universes, so it's just a matter of making sure the controller and data sender are both set the same.

[tbone321]

This is why I asked and he is using the controllers self test so there is no mismatch between the controller and what is sending the data because the controller is in full control and is both creating the data and sending it to the nodes.  

[tbone321]

I am running the test through the Falcon controller UI, the test page and then selecting <color> ramp.  I suspected there is a firmware issue, not 100% sure.  Wanted other people opinion first to be sure.

Thank you for the quick response.

I believe that there is a firmware update for that controller.  You may also want to try testing thru FPP and see of there is any difference.  Some of the Falcon controllers have issues with the self test function but work just fine when playing a sequence.

[breese]

F16v5 firmware
https://github.com/Pixelcontroller/f16v5_issues/tree/main/F16V5

[coyoteray]

I just tried through xLights ... something is not right.  Using just the "on" affect with color set to white and I select sub-models:

• All: 260 LEDs the entire prop and the next channel light up
• Under carriage, under carriage no wheels and wheels the correct LEDs light up
• Candy canes 5 or 6 the correct ones light up
• Candy canes 1 - 4 are weird (these are all above the 170), for example if I select cane 1 all the LEDs are white except 1 which is blue, cane 2 same thing plus the blue light on cane 1 is now yellow.
• All candy canes: All the candy canes light up plus the LEDs on channel 2

For those with a FC16v5 what is your build number?  Mine is build 30, (edit: updated the firmware to 30 just incase ... same issue) there does not appear to be a newer firmware on the support page - Am I missing something?

When I have time I will test using my WLED based controller, the FC16v5 is my only non-WLED based controller.

[coyoteray]

k6ccc you may be on to something.  The addressing mode was set to "Absolute Addressing", when I changed that to "Universal/Start channel" the issue with the self test was fixed - yah.  Thank you.

Now to get it working in xLights ...

edit: Got it working correctly in xLights - double yah!!

k6ccc - I owe you a coffee