FPP PB16 Pixel Cont...
 
Notifications
Clear all

FPP PB16 Pixel Controller

630 Posts
62 Users
6 Reactions
389.5 K Views
wilmar
Posts: 2115
(@wilmar)
Noble Member
Joined: 8 years ago
pmiller wrote:I did. Then I switched to a 682 to hande the snowflakes and wheel. My thinking is the less injection I do the better it is to trouble shoot when a problem occurs. I could have run everything from one 682 which I originally did positioning the 682 between the 2 major props. Ended up being more touble than it was worth adding power injection and null pixels.

Sent from my SM-T710 using Tapatalk

You know more than me ,lol I was just asking as my plan to add on going forward had the a few e6804 involved at some point. Unless I was thinking wrong

Sent from my iPhone using Tapatalk


Reply
Posts: 87
Topic starter
(@scooter-seh)
Trusted Member
Joined: 12 years ago

The upgrade E682 board had to be small to fit the space on the controller so I couldn't add an expansion port. It does have a separate PCB for 2 DMX ports. I could probably add an expansion port if I made the PCB cover the network jack area or switched to a flex cable design. I mostly did the design for "fun". I don't plan on using it ever. I would recommend just building a full PB-16 controller.

pmiller wrote:I'm interested in the 682 upgrade but not sure how to apply it to my layout. Currently I have a 682 running a 16 string pixel tree and a Renard SS, both in the same enclosure. Using 8 outputs on the 682 to run 2 strings, 55 up and 55 down at 25%. Unfortunately running Renard I now have 3 outputs I can't use. Works like a charm but if a pixel goes out I have to take down 2 strings to repair it. I would like to use all 16 outputs for the tree only, that way I only need to take down one string. However, 20 feet away I have another 682 running a wheel and 8 snowflakes. Each snowflake is on its own output. Having 2 682's in the same approximate location I have 2 network cables going to each. Would be nice to eliminate the one 682 and be able to use communication from one 682 to supply data to a small, for the lack of a better word, controller", to run something 20 feet away. I do realize the "controller" 20 feet away would need its own power supply. Is this making any sense or am I explaining it wrong? I suppose you could say I want to increase my 682 outputs from 16 to 20 or 24 outputs but at a longer distance.

Sent from my SM-T710 using Tapatalk


Reply
pmiller
Posts: 2795
(@pmiller)
Famed Member
Joined: 12 years ago
scooter_seh wrote:The upgrade E682 board had to be small to fit the space on the controller so I couldn't add an expansion port. It does have a separate PCB for 2 DMX ports. I could probably add an expansion port if I made the PCB cover the network jack area or switched to a flex cable design. I mostly did the design for "fun". I don't plan on using it ever. I would recommend just building a full PB-16 controller.

If I went with the full PB-16 could I then use something to drive pixels 30 feet away from the PB-16 without using another full size controller? Sorta like adding another 4 or 8 outputs but 20-30 feet away.

Sent from my SM-T710 using Tapatalk


Reply
pmiller
Posts: 2795
(@pmiller)
Famed Member
Joined: 12 years ago

I guess what I'm thinking is like the F16V3 and 4-string differential SmartReceiver Board that allows 4 outputs 250 feet away. A couple of those SmartReceiver boards are a heck of a lot cheaper than an whole new controller but its the cost of the F16V3 that I don't care for.

Sent from my SM-T710 using Tapatalk


Reply
Posts: 36
(@supergumby)
Eminent Member
Joined: 17 years ago

It's been a busy first day of the year - looks like Santa showed up twice this season!

Scott has given us several new board designs, rounding out the PB16 family into a pretty comprehensive ecosystem of build-it-yourself Pixel Controllers. I hope I'm not stealing his thunder, but as of yesterday, the GitHub PB16 site has been updated with the following toys:

Receiver_Out - This is the differential receiver board that allows up to four pixel outputs of 700 pixels each to be located a long way from the PB16 controller using standard CAT cables. I believe this board can receive data from the following expansions: Quad_Diff_Out, Multi_Expansion, and the new Diff_Expansion.

Diff_Expansion - This board has four ports that can each drive a single differential receiver_out board.

PB_16_Expansion - This is my personal favorite for what I believe it does. The Pocket Beagle controller core only with two 16 output expansion headers. I'm hoping this board turns the PB16 into a Swiss army knife by allowing maximum flexibility in building a display layout using whatever outputs are needed.

Questions:

Let's say I need 32 pixel ports, in groups of four, located all over the house and the yard. Can I just connect two Diff_Expansion boards to a PB16_Expansion, and run 8 CAT cables to 8 Receiver_Out boards? I notice that the BBB Strings section of the FPP has selections for Standard/Differential on the Expansion strings but not the first sixteen, does this prevent using differential boards on these outputs?

If I still need DMX for AC controllers on a PB16_expansion, can I just add a USB hub and connect my USB to DMX dongle?

Also looks like many other boards received makeovers, including 'copper pours'. I've seen this done for thermal integrity as well as ground plane for signal stability/isolation. Same here, or was this for a different reason?

Looks like I'm going to be busy with the soldering iron.

Thanks Scott!

/Don


Reply
Page 16 / 126
Share: