Hi,

I found that the splitty4 is not really an RGBpx splitter, it is a fan splitter for other vendor fans. I expect many people know that, but it was not clear to me when I purchased one; I thought that it was a splitter for RGBpx that also supported other vendor RGB fans. It does not split the RGBpx itself. I don't have any RGB fans from any vendor; I only have RGB on farbwerk and RGBpx strips for the Quadro.

The limitations with the wiring and lack of options for the RGBpx adds unexpected challenges. I did not expect to have to connect them all in series, or be constrained in the cable lenghts due to their tiny header/connectors due to their being a unique size compared to all other AQ parts I own.

I wanted to purchase some kind of RGBpx splitter to allow for ideal strip placement and cable management; I did not realize each RGBpx strip must connect to each other in sequence as the only available method for the Quadro to control them, nor that the RGBpx addressing is based on the order of sequence rather than actually being individually addressed (like an aquabus selectable address, for example). The farbwerk physical wiring is what I expected, and I also expected they could not be mixed--but I did not anticipate that the design options were limited to one giant string of LEDs for the RGBpx.

I expected the Quadro would have four different RGBpx headers for direct control; much like how the Farbwerk does for RGB, however, I understand now that is not how the connection works, there is a single connection, and all must connect to it. The splitty 4 seemed like it would be the solution, but it is not. It sounded like it would be an RGBpx splitter and was the way to connect RGBpx strips back to the Quadro for custom placement requirements- It does not allow for that--there are no RGBpx connections at all except for the one to receive data from other vendor hardware. That was not expected and I cannot find an AQ solution that allows for this.

Can someone suggest what the RGBpx cable/Quadro header/pin part numbers are, so that I may try to create my own "T" and "L" junctions or to create a true splitter/hub for the RGBpx strips? I'm just looking to make it fit my case properly and I didn't expect this to be so hard compared to what is available for Farbwerk compatible RGB LEDs.
Are the RGBpx/Quadro pinouts using JST mini of some kind? what type are they? Can this info be placed in the manual in the future as part of the technical specifications? (I can crimp the cables or make a breadboard to do what I want, that's fine... I just need to know what the header/plug JST size is so I can order the parts....but it'd be great if a ready made solution was available for purchase to split RGBpx LED strips. Maybe call it Splitty RGBpx...)

I recognize I cannot use more than the limit of addressable RGBpx LEDs in any combination of strips and to exceed 60 would mean I require a second Quadro.. I would like to connect the strips in a manner besides end-to-end and the splitty4 for rgbx doesn't work at all for that purpose; it is for systems that are not rgbpx. it might be best if that splitty 4 is called an adapter for other vendor hardware to work with the quadro than to call it a perfect a splitter for rgbpx.

I misunderstood or mistranslated that the description of "Splitter for fan power supply and RGBpx lighting control." did not actually control or allow one to split the connections of RGBpx LED strips. It even says "The mixed connection of lighting systems from different manufacturers is not possible!" which meant great, I am not using anything except Aquacomputer RGBpx, this should work great. But it is not for someone without lighting systems from a different manufacturer. It is my fault for not understanding that--I am hoping someone can help with how to connect the RGBpx without them being physically in series, even if they logically must be (as long as they can be addressed that is fine with me...)

Thank you for your help. I expect other people have been more creative than me, and in the near future other people will too, and perhaps this thread can be used to help those that might have encountered similar problems and might share some of their ideas for solutions.