Ok this has me stumped. I just built a BBB16v2 (through hole board). I only installed 2 outputs to test (2 phoenix connectors). I put 50 pixels on output one and select test Port Number and all 50 light up with the 1st pixel white (Perfect!). I then add 50 pixels to output 2 but do not put anything in output 2 field (so shows 0 pixels), click test Port Number again and all 100 light up. The 50 on output 2 light up and only the 1st pixel is white. If I change output 1 to only 30 pixels, only 30 pixels light up on output 1 and 30 light up on output 2 (both with 1st pixel white). What the heck?? I checked and there are no pixel overlay models and this is a fresh copy of FPP off master branch (to fix outputs issue with BBB16 board). I have also tested this with several previous versions of FPP and same result.
joeytx wrote:
Just completed the "Pi Zero 16 SMD" board. I had previously made the BBB16 , 24 pin 16 Port Expansion and the 4 port Receiver Out .I wanted to see how the Pi Zero would work compared to the more expensive BBB version. The board is SMD and I ordered the bare board and hand soldered it. The board goes together rather quickly, the parts are fairly cheap, and works well.
The only issue I had was with FPP. On the BBB boards I was able to use FPP 5.5, and the EEPROM worked well without signing. I did purchase two licenses for it and a larger setup (one 24 and one 48), so I could upgrade to FPP 7.4 and use with X-Light Connect. On the Pi Zero I could not get the unsigned EEPROM to work right, every time I would make changes to the outputs, it would revert back to the defaults. I even made the changes directly to "co-pixelStrings.json" file, and rebooted. Then if I made a change it would revert back. This was on FPP 4.6, 5.3 and 5.5. I then tried 7.4 with the unsigned EEPROM and it worked perfectly (only limited by 50 pixels per output). I purchased a license for the Pi Zero (24 outputs), signed the EEPROM and it works perfectly.
Don't be afraid of signing the EEPROMs, they have made it very easy and straight forward. I know I could have asked for a voucher for the boards, but I really try to do my part with moving FPP and these projects forward.
Included are the 3D bases I did for the Pi Zero and the 24 pin 16 port expansion.
What are you referring to when you say signing the EEProms? I have the PB16 version built with 3 different boards, it would be fantastic to get all 3 going this year but my last attempt with one of the boards was a failure, I could only ever get pixel outputs on 1 of the 16 outputs. Is perhaps the trick signing the EEProm? I will likely go to version 7.5 FPP now as this was 2 years ago already that I was in the mist of trying this and unfortunately the boards have sat collecting dust ever since.
After FPP v6, you need a key to enable full functionality of any DIY FPP based board.
From FPP board "If you own a DIY cape which you assembled yourself, write your email address on a piece of paper and take a picture of the cape and paper and email it to diy@falconplayer.com and we will send you a voucher for a free license key."
Once you have the license key you can apply it to your board.
DrNeutron wrote:
After FPP v6, you need a key to enable full functionality of any DIY FPP based board.
From FPP board "If you own a DIY cape which you assembled yourself, write your email address on a piece of paper and take a picture of the cape and paper and email it to diy@falconplayer.com and we will send you a voucher for a free license key."
Once you have the license key you can apply it to your board.
Mine aren't a custom cape.. It is simply the PB16 that Scott designed, do they still consider this a custom cape? As I thought I had an EEProm already but believe it might be on my old laptop now.. AND.. I thought this was in order to do more than 50 pixels per output that you needed this license key? Is that no longer the case and you need the key regardless of pixel output ?
jllracer55 wrote:
Mine aren't a custom cape.. It is simply the PB16 that Scott designed, do they still consider this a custom cape? As I thought I had an EEProm already but believe it might be on my old laptop now.. AND.. I thought this was in order to do more than 50 pixels per output that you needed this license key? Is that no longer the case and you need the key regardless of pixel output ?
They consider these DIY as they were not purchased. I have sent pictures and received keys in the past
Thanks,
Shawn

