FPP PB16 Pixel Cont...
 
Notifications
Clear all

FPP PB16 Pixel Controller

630 Posts
62 Users
6 Reactions
389.8 K Views
Posts: 629
(@dkulp)
Honorable Member
Joined: 14 years ago
bobsmith wrote:On a somewhat related note to these boards, does anyone know how a "Smart Differential" receiver actually works? I can find info on how they're setup, but not anything on how the protocol actually works. Is the smart receiver programmed somehow to know what channel ranges it should take from the stream? Or is some switching signal sent in the datastream?

There are 4 different "smart receiver" protocols:

1) The Hinks/HC smart receivers use some protocol that I have no idea what it looks like. Never looked into it. They aren't really pin compatible with the FPP/BBB/Falcon based capes so they are pretty much irrelevant from my standpoint.

2) The original "V1" protocol. This only supports chains of 3. The protocol is very simple, but time consuming. Basically, the signal is pulled low for roughly 6 pixels worth of data, then it is toggled high/low for 6 pixels of data (the BBB's use "white" data for the toggle) for receiver A, and then pulled low for 6 more pixels, then the pixel data for A. For B, the middle toggle phase is 12 pixels. For C, it's 18 pixels. Thus, if you use all three, you basically consume 84 pixels of data time. (the lead in/low for "A" can be part of the normal reset).

3) The "new" V2 protocol that the Falcon v4's use. I don't know what this looks like. I don't have a v4 to scope it exactly. However, I know all the data is sent in a continuous stream, then the line if flipped over to a serial mode of some sort (start/stop bits, etc...) to send some sort of config packet, and then put back to pixel mode. Again, I don't know all the details. HOWEVER, I do know that the config packet is very timing dependent and the processing on the smart receiver itself is more intense and thus requires a much more powerful processor to handle splitting the pixel data at the right marks. Note: the processor on the v4's cannot (easily, or in a performant way) have a pin pulled low while other pins output pixel data which is why the v1 protocol cannot be supported.

4) The "new" v2/BBB protocol. This protocol is very very simple. There is a 5us pull low reset at the beginning (normal for ws281x). Pixel data is sent out. When the stream should go to the next receiver, it's pulled low for 1.5us (or about 5 pixels of data). Thus, for 6 receivers, you lose 25 pixels of time (5 gaps). It's very simple (simpler than the original v1 protocol) and thus is doable on lower end processors on the smart receivers. It's also very simple for the BBB's to output. However, the Falcon v4's cannot output it.

This then brings up the Smart receivers versions.... The original v1 smart receivers obviously support dumb mode and v1 protocol. There are two versions of the "v2" smart receivers:
1) The receivers Dave sells (blue) - the original batch (if you have one already) supports dumb mode (mode 0 on the dial) and #3 (modes A - F on dial). The MAY support #4 via 4-9 on the dial. Due to a bug, the v1 protocol (modes 1-3) isn't working. Newer versions will have an updated firmware that should allow it to support all 4 protocols.

2) The receivers Wired Watts and I sell (black) - these currently have a lower end processor on them (that are available, component shortage) that cannot support the #3 protocol. These are specifically designed for the BBB based boards and actually say "BBB Smart Receiver" on them. They support dumb mode (0 on dial), v1 modes (1-3 on dial), and BBBv2 protocol (modes A-F on dial). Dial modes 4-9 are ignored (or do something funky, no idea really). Again, they will NOT work with Falcon v4 boards, but will work v3 boards in v1 mode (chain of 3). With BBB capes, they can work in dumb mode, v1 mode (chain of 3), or BBBv2 mode (chain of 6, and lower overhead for chains of 2 or 3 than v1 mode).

That likely answers the question with way more details than you need. 🙂


Reply
Posts: 79
(@bobsmith)
Trusted Member
Joined: 11 years ago
dkulp wrote:
That likely answers the question with way more details than you need. 🙂

I don't think you can ever have too many details. Thank you for filling me in. I'm not using any smart receivers yet, but I might in future years.

Seems like all "standards", the best thing is how many of them there are!


Reply
Posts: 113
(@cmndr-brain)
Estimable Member
Joined: 9 years ago

So, riddle me this. What is the benefit of converting my SanDevices E682 to a Pocket Beagle/PB16 controller? I've built and converted my E682. Don't get me wrong, it was well worth the learning experience. I'm actually starting to understand FPP and the options within. But, what makes the Pocket Beagle/FPP better than the stock E682?


Reply
DrNeutron
Posts: 2017
(@drneutron)
Noble Member
Joined: 14 years ago
Cmndr Brain wrote:So, riddle me this. What is the benefit of converting my SanDevices E682 to a Pocket Beagle/PB16 controller? I've built and converted my E682. Don't get me wrong, it was well worth the learning experience. I'm actually starting to understand FPP and the options within. But, what makes the Pocket Beagle/FPP better than the stock E682?

An E682 on its own is just a pixel controller which requires E1.31 data from a show computer/Pi/BBB.
A PB controller IS the show computer with FPP loaded onto it and a copy of the sequences you want to play.
If you had all FPP controllers you could sync them all via wifi and have them run the sequences locally on each.
There would be no lag as each FPP controller would only send sync packets over wifi and not E1.31 data to keep the sequences in sync.
This would eliminate cat5 cable to each controller....


Reply
ukewarrior
Posts: 4674
(@ukewarrior)
Illustrious Member
Joined: 18 years ago

Great point !

No need for a show computer or a Separate Falcon Player.

N I C E !

DrNeutron wrote:An E682 on its own is just a pixel controller which requires E1.31 data from a show computer/Pi/BBB.
A PB controller IS the show computer with FPP loaded onto it and a copy of the sequences you want to play.
If you had all FPP controllers you could sync them all via wifi and have them run the sequences locally on each.
There would be no lag as each FPP controller would only send sync packets over wifi and not E1.31 data to keep the sequences in sync.
This would eliminate cat5 cable to each controller....

Reply
Page 86 / 126
Share: