You should maybe take a look at Stellascapes. With that sort of industrial-type need, you want appropriate gear. Andrew at Stellascapes has done SeaWorld, among others....
The most dense/most pixels would be the various BeagleBone based controllers. A BeagleBone can drive 48 strings, 750 PIXELS per string at 40fps. Drop to 20fps and you can double that.
The problem is actually getting the data to the controller. For the most part, with BBB's, we would run them in remote mode with the data stored locally. If they have to be 1.31, you will definitely have issues. It can handle the 210 universes for the 750*48. 420 is more than the ethernet it has can handle. If you grab one of the SanCloud BBE's with the Gigabit ethernet, it may allow more, but I honestly haven't tried it yet.
By shear coincidence, I was working on updating my F32-B design today. It has 32 ports local and another 16 via differential receivers. Haven't decided if I'll actually have any made or not.
dkulp wrote:The most dense/most pixels would be the various BeagleBone based controllers. A BeagleBone can drive 48 strings, 750 PIXELS per string at 40fps. Drop to 20fps and you can double that.The problem is actually getting the data to the controller. For the most part, with BBB's, we would run them in remote mode with the data stored locally. If they have to be 1.31, you will definitely have issues. It can handle the 210 universes for the 750*48. 420 is more than the ethernet it has can handle. If you grab one of the SanCloud BBE's with the Gigabit ethernet, it may allow more, but I honestly haven't tried it yet.
By shear coincidence, I was working on updating my F32-B design today. It has 32 ports local and another 16 via differential receivers. Haven't decided if I'll actually have any made or not.
Agreed with the amount of data to pass by E1.31, at least during show time, which is why I was leaning toward the F16v3 as I believe it can act as remote thereby reducing the amount of E1.31 traffic.
Regarding your F32-B, this might be the best of both worlds, near maximum channels per controller and still having remote mode - which the Advateks seem to lack.
Should you do decide to proceed with the F32-B's (or perhaps even a F48-B :P)I would certainly be interested further.
dkulp wrote:The most dense/most pixels would be the various BeagleBone based controllers. A BeagleBone can drive 48 strings, 750 PIXELS per string at 40fps. Drop to 20fps and you can double that.The problem is actually getting the data to the controller. For the most part, with BBB's, we would run them in remote mode with the data stored locally. If they have to be 1.31, you will definitely have issues. It can handle the 210 universes for the 750*48. 420 is more than the ethernet it has can handle. If you grab one of the SanCloud BBE's with the Gigabit ethernet, it may allow more, but I honestly haven't tried it yet.
By shear coincidence, I was working on updating my F32-B design today. It has 32 ports local and another 16 via differential receivers. Haven't decided if I'll actually have any made or not.
Oh and I was going to add, subsequent to my research on various controller options, I've also been looking into DDP in place of E1.31 - seems to have some marked efficiency/performance improvements. So my original requirement of an E1.31 input might change to DDP. But still TBD.
No idea what you are building but it sounds massive. Please post pictures!
Sent from my iPhone using Tapatalk

