FPP PB16 Pixel Cont...
 
Notifications
Clear all

FPP PB16 Pixel Controller

630 Posts
62 Users
6 Reactions
389.5 K Views
Posts: 79
(@bobsmith)
Trusted Member
Joined: 11 years ago

They did end up getting the boards delivered to me yesterday (they just made it onto the truck late in the afternoon after I wasn't looking for tracking updates anymore). The regulators work good on the PB16. I got the last few things I needed to get soldered on to the boards done, dug around in the garage for that box of old ribbon cables I knew would come in handy at some point (I threw a TON of old IDE ribbon cables out before I moved last time, but I did keep some - enough for this anyway).

Did a test with the PB16 connected to a diff expansion board, and one receiver connected to one of the diff ports with a long ethernet cable - things seem to be working well!

(excuse the messy desk)

pb16 diff expansion

If anyone needs some regulators, drop me a PM with your email. The regulators are $3 each, and it looks like the cheapest flat rate envelope is $9 in the US (but I wonder if I just put them in a small padded envelope if that would be cheaper). I buy a lot of stuff, but I don't really sell or ship anything, so I'm not familiar with what the cheapest shipping options are. Also they don't include pins between the regulator and the PB16 board. If you have some slightly stiff solid wire, you can just use that for pins and solder it both to the PB16 board and the regulator.

They're not exactly dainty, but they get the job done!

pb16 regulator

Reply
Posts: 113
(@cmndr-brain)
Estimable Member
Joined: 9 years ago
Cmndr Brain wrote:Well, per the norm, I'm late to the game. I have an extra E682 that I would like to experiment with. I'm assuming, even though the files are 2 years old, that the E684 gerber files v2 are correct. The bom in that github folder seems older and some of the stuff is out of stock or obsolete. Let's see what we can break.

Also, is the .bin file the same for the dedicated controller as it is for the E682 upgrade?

Last, does the speed of the EEProm make a difference? I see that Digikey is out of stock and the only ones I can seem to find are 400khz whereas the Digikey part number referenced in the bom is a 1Mhz

Another question I thought of, Will the hack work with a E6804?


Reply
Posts: 79
(@bobsmith)
Trusted Member
Joined: 11 years ago
Cmndr Brain wrote:
Last, does the speed of the EEProm make a difference? I see that Digikey is out of stock and the only ones I can seem to find are 400khz whereas the Digikey part number referenced in the bom is a 1Mhz

I used a 400khz eeprom - it's working fine. I used this:
Mouser #:579-24AA256UID-I/P
Mfr. #: 24AA256UID-I/P
Desc.: EEPROM EEPROM 256K I2C EE EUI-48 EUI-64 Unique ID

The eeprom isn't even strictly necessary - all it does is when you insert a brand new FPP sd card, it automatically selects PB16 as the board and automatically enables the OLED (if you have one) and sets up the GPIO assignments so the buttons work. If you don't have the eeprom, the first time you boot a new SD card, you have to manually select PB16 expansion board, and enable the OLED. Once it's selected, FPP remembers anyway - so it's only of slight convenience when starting with a fresh SD card image.

Of course the very first time you boot the board up, the eeprom does you no good as it's blank anyway. You have to follow the instructions in the PB16 manual to flash the eeprom bin file to the board.


Reply
Posts: 113
(@cmndr-brain)
Estimable Member
Joined: 9 years ago
bobsmith wrote:I used a 400khz eeprom - it's working fine. I used this:
Mouser #:579-24AA256UID-I/P
Mfr. #: 24AA256UID-I/P
Desc.: EEPROM EEPROM 256K I2C EE EUI-48 EUI-64 Unique ID

The eeprom isn't even strictly necessary - all it does is when you insert a brand new FPP sd card, it automatically selects PB16 as the board and automatically enables the OLED (if you have one) and sets up the GPIO assignments so the buttons work. If you don't have the eeprom, the first time you boot a new SD card, you have to manually select PB16 expansion board, and enable the OLED. Once it's selected, FPP remembers anyway - so it's only of slight convenience when starting with a fresh SD card image.

Of course the very first time you boot the board up, the eeprom does you no good as it's blank anyway. You have to follow the instructions in the PB16 manual to flash the eeprom bin file to the board.

Thanks. That's one question down. I can and have done circuit board repair, so burning the eeprom prior to install won't be a problem. I mainly work on older pcb's so some of this newer technology like the beaglebones, I just don't have the experience.


Reply
Posts: 79
(@bobsmith)
Trusted Member
Joined: 11 years ago

There's no need to burn the eeprom beforehand. You just won't get the oled display on the first boot. Check your DHCP log to see what IP address it gets and then you can do everything you need to from the web interface (including burning the eeprom file). After the second reboot, it shows the IP on the display, which is nice, but not necessary either - I assign fixed addresses to the controllers in my DHCP table (and internal DNS name as well) after they boot the first time and I get the MAC address. Just depends on how fancy you want to get with your network setup.

You can also use the "FPP Connect" feature in XLights to find it the first time it boots if you don't know how to check your DHCP logs.


Reply
Page 84 / 126
Share: