Bad data on daisy chained SRX1-PSU

[davidr236]

Hey guys, long time lurker here and have mostly been able to figure out all my issues with search. Coming to a dead end now and seeing if anyone can help me out.

My Setup:

I am running a Falcon F16v3 with 2 daisy chained SRx1-PSU off of the top RJ45 connector on the board. I also have a Holiday Coro Alpha Pix 16 connected to the ETH1 port. All of these are running off a Pi3b with FPP over wireless.

The SRx1's are using 1 and 2 on the dial, and the dip switches are correctly set for their position in the chain.

Issue: Port 1, (17a and 17b, both controllers) are very glitchy in the first handful of nodes. Operational, but colors are off and its just flashes weird. Port 2 (18a and 18b) are completely non operational. Just gives the shimmer effect to all props plugged into the second port on both controllers.

Under test mode via the controller button all nodes function as they should on all ports.

Things I have tested:
-Multiple network cables. Testing passed on cable tester. 
-pigtail attachments
-Using A-B on the dial and not 1-2
-Switching out SRX1-PSU's
-All firmware is up to date on the f16 and FPP

It seems like I am maybe getting some sort of bad data signal since all the nodes operate fine under manual testing. Maybe my DMX port is bad? I can get a new Falcon but would hate to throw money at something that won't fix the problem.

Any ideas? Thanks for the help!

[davidr236]

Well I got Port 1 back via a factory reset of the F16v3. Port 2 is still flashing on both remotes though. Seems like there is a problem with the #2 Serial Port. I have them all set to pixel data on the web interface. Looking into maybe problems with the FPP?

[allknowing2012]

cable or cable glands. The cable has a pair for each port - so a pair is bad or a pin in gland is bad.

[davidr236]

That's what I thought as well. Tested all cables and glands with a tester and everything was a pass. Even made a new cable 

[davidr236]

For anyone looking in the future. After troubleshooting every possible thing, I acquired an expansion board and everything works perfectly now. Looks like the serial port on the f16v3 is bad.