SRx1 v5 slow to up date - lagging

[coyoteray]

I have a SRx1 v5 connect to the first expansion port (17-20) on a F16v5.  The SR channel is set to 0.  This powers a 1600 pixel mega tree with 4 connections (400 pixels each) - no power injection or balancing. The effects on the tree lag behind and a slow to update.  I have the latest (build 34) firmware installed and also upgraded the SR.  I have replaced the network cable (direct connect) between the F16 and the SR.  I joined the xLights zoom room to get advice, so far none of the recommendations have helped.   What am I doing wrong?  Any pointers would be highly appreciated.   The tree on the right should match what the tree on the left is doing.  Tree on the left is connected to a DigQuad WLED controller.

[JonD]

No suggestions other than make sure your F16v5 and SRv5 are at the latest firmware.
https://github.com/Pixelcontroller/f16v5_issues/tree/main/F16V5

[coyoteray]

Yep, done.  Issue persists 

[JonD]

Not many forum members have the F16v5, and a lot of questions go unanswered.  Hopefully someone will respond, but I would reach out to Falcon support as well if you have not already.

https://pixelcontroller.com/store/content/13-support2

[coyoteray]

Fixed sort of, maybe not sure.   I removed the mega tree from the controller, removed all values from the control/channel on the tree and readded to the controller. Cleared render cache, rendered and saved.  Works from the PC however it does not from FPP even though I uploaded new sequence to FPP.  Looks like I will be using xSchedule again this year ... I bought a Pi4 for this very thing

Maybe I'll reflash the Pi ... 

EDIT: A reflash of the Pi did not help, I was hoping .... xSchedule here I come

[Poporacer]

Works from the PC however it does not from FPP even though I uploaded new sequence to FPP

There are some output settings that you need to configure in FPP to tell it what controllers you have and what kind of data to send it.
Are you using FPP Connect to configure your Pi?
Drop in the Zoom Room and we can get you set up in no time. Or post a screenshot of your Controllers page in xLights so we have a little more information to point you in the right direction.

If you are not familiar with the Zoom Room, it is the best and quickest way to get help, here is a video that explains it.

EDIT: A reflash of the Pi did not help, I was hoping

Like I mentioned, you probably didn't configure your FPP to output data to your controller. If you can access your FPP then there is usually no need to re-flash it, it will typically be a configuration issue

[coyoteray]

100% I use xLights to configure FPP and use it to test the models.  I know (99% sure) it is something I am doing wrong, just not sure what.  The zoom room is great.

[dkulp]

Two thoughts:

1) Are you using DDP or e1.31?  If you are using e1.31, flip to DDP.   

2) If you can, try flipping the FPP over to the master branch.   I just did some updates to the UDP output to try and slow it down a bit.    When sending a ton of universes to some of the slower controllers (ex: Hinks), we tend to send them faster then the controller can handle and since they are UDP, the networks and such is free to drop them.   

[coyoteray]

Thank you all for your replies.  I joined the zoom room and Travis (from down under) was able to get me going.  DDP was not working for me thus the reason for E1.31.  He was able to get DDP working and WOW - everything works!!  He made it look so simple.

Boom, holiday stress reduced