FPP v6 changes related to BeagleBone, PocketBeagle, & Raspberry Pi pixel outputs

[CaptainMurdoch]

Here you go.

Your co-pixelStrings.json config file thinks it should use the Beagle BBB48String channel output driver on the PiHat.  Can you reinstall the PiHat virtual EEPROM and see if that fixes it.  If it doesn't, switch to a different virtual EEPROM and then switch back, but you shouldn't have to resort to that.  The default co-pixelStrings.json should be overwritten when you reinstall the virtual EEPROM.

[Ebuechner]

That cleared it up, but the question is why did it do that in the first place. I didn't think I did anything unusual during the OS upgrade.
I did pull in updates just before I uninstalled and reinstalled the eeprom.
I was thinking of doing that with the virtual eeprom but I wanted to wait in case there was any Diagnostics that needed to be done to figure out why it did that.

[CaptainMurdoch]

That cleared it up, but the question is why did it do that in the first place. I didn't think I did anything unusual during the OS upgrade.

I'm not sure, I'm going to have to dive into the UI code to see if there is some case where it could write the wrong driver to the co-pixelStrings.json file.  That would have to come from the UI.

[CaptainMurdoch]

There has been some confusion surrounding whether Multi-String WS281x Pi capes purchased by July 31, 2022 are eligible for a free grandfathered-in key voucher.

This post is to clarify that the Multi-String WS281x Pi capes such as the M4-Pi, M16-Diff, etc. ARE eligible for free grandfathered-in vouchers if purchased by July 31, 2022.

We have had several users actually purchase a key instead of using a voucher and use the key to sign the EEPROM for one of these capes.  I will be reaching out to those users via email directly regarding refunds since they did not need to purchase a key and should have been able to use a voucher.

[deanathpc]

My DIY LED Express item, Scroller Assembled, that I purchased years ago.  Does this require a license then?

There are only 2 pixel output types that are affected, the enhanced DPIPixels for the Pis and the BBBStrings48 for the BB Based controllers. This is for Pixel Strings connected directly to the cape.

I tried a search and nothing but may have missed it so..

Did you read the original post in this thread that you are posting on?

This list of Outputs which are NOT affected includes but is not limited to... the LED Panels outputs including directly attached as well as the ColorLight/Linsn outputs

Several people have asked almost the exact same question.

If several people have asked the exact same question them maybe it's not as clear as all you thought it to be.  Hence why I asked what I did when I did.

And in regards to reading the original post and your snarky response, yes.  I needed clarification as I was not understanding it due to be over tired from working nights.

[Poporacer]

And in regards to reading the original post and your snarky response, yes.

It was not intended to be snarky, but usually when people post additional comments to an existing post, they would read the responses to see if their question had been answered, in this case several times.

If several people have asked the exact same question them maybe it's not as clear as all you thought it to be.

Or maybe they didn't read what had already been posted?

I was not understanding it due to be over tired from working nights.

That is understandable and people learn things in different manners.

[Woganaga]

Hi - sorry if this has already been covered. 
I just upgraded to V6
I have the license keys. 
I have homemade PB16 boards w/ EEPROM chip.
when i go to "about capes" it shows the following.  I do not get an option to put in a license key.
can someone point me to the steps sorry if i missed.

[Woganaga]

Hi - sorry if this has already been covered. 
I just upgraded to V6
I have the license keys. 
I have homemade PB16 boards w/ EEPROM chip.
when i go to "about capes" it shows the following.  I do not get an option to put in a license key.
can someone point me to the steps sorry if i missed.

i think i may have figured this out.  I had to re-download /install the EEPROM code and then it asked for license.
I guess my question is now, what is the difference between the eeprom that was already there vs. the new one (it said unlimited before, then i upgraded and it said limited, then i added key and it said unlimited...)

[bossier17]

First Question,
What the hell is DPI pixels?

I've have had BBB48 boards since FPP came out.

When you first started talking about the eeprom thing,
I reached out to get more info about it, but got told there was plenty of information and how easy it was to use it.

Since i got no support back then, i never saw the reason to add the eeprom to my boards

Now Im being told that since someone added "DPI Pixel" code into FPP, My Controllers will No Longer Work,
 and i now need to pay a license fee for my controllers to working or to sell them.

I call what you are doing is RIPPING off everyone,
(making a monopoly of 2 selected gods allowed to make controllers without license issues)

What about the original DIY RGB123 card that you based your original code on for controlling the 48 pins? (killed that in the process as well i see)

My DIY controller is only $50 (aud) and $15 (aud) soldered up.
But Now you think its fine to start demanding $50 (usd) = ($75aud) for some license for a chip, (until 2 months ago said no info on how to use it).


If you are honestly doing this for the better of the community,
-Why did you keep board designers in the dark about this eeprom an how to program it.?
-So what was your plan for using a eeprom? For board designers data? Or really a plan to add a license fee's?

You say there is a grace thing?
So how will this work?
My boards don't have the eeprom thing, due to lack of support and information from you's.

What about the customers that also have a version of my board? since no eeprom how is that possible for a license
(Also Who gave you permission to know how many controllers I sell?, This way your forcing business to give you that information to you.)

Im sorry your boards got copyed.
BUT there is no need to SCREW everyone else in this christmas hobby because of it.

Ohh i forgot,
Its Now just a money grabbing thing for you. (The Christmas spirit has left you, and you's became the Grinch stealing people's xmas shows)
Since you's want to stop all other board designers, or make it that hard for there customers.
Just so you can force them to buy your product, because its easyer to use without the license issue's

The Way you's have gone about this is totally SUS.
Also it is In moral for a business (that FPP now is due to licensing) to demand product sales information from other vendors that use this product.

Also where are my Grace Codes?
I have 8 BBB with my capes on them. So where is this illegal license your forcing on people?

Honestly there is going to be alot of abuse in zoom, When people say to upgrade FPP and it destroys people's shows cause of your license crap.

Unless your able to provide more information into what this license thing can do for my product.
eg.
- So i design a board to use a eeprom, for your new license.
- What are you offering the board designers for that license fee?
- You talk about special DPI pixel code, What is it? , What does it do?
- How can i integrate these new things on my boards

Does the License Fee cover any or all of the above questions?
(Or does the license only cover you's 2 and products you buy for research & future additions to your boards.)

What does the License really cover? (Some code that once worked? but you re-coded it to so you can charge money for it?)

Until you can be more Clear,
I will stick to FPP v5, and recommend everyone does the same,
Due to your money making grab, now using the license thing to back it up

Alec
SmartAlec Lights.

This is the ugliest, most ungrateful post I've read in a long time.  

Captain Murdoch, dkulp, poporacer, and everyone else who donates their time and talent to this forum and hobby - thank you.   I don't have to get a license, but I'll be donating what I would have spent this year if I did need to buy one.   I can't count the number of times you guys have personally helped me on these forums, and the support I have received on a free(!!!)FPP player is greater than any support I've received from paid products.  Thanks for all you do!!

[ninjinja]

Hi all,

I emailed a picture of my DIY cape to diy@falconplayer.com as per the FAQ on the website, but on this post is says to add my email address to a piece of paper in the photo.  Is that why I haven't heard back yet?  Also if I need to make changes to my EEPROM, can I sign it again with the same code, or is it a one time deal?  Thank you all for your hard work, this has made show work better than ever.

[dreiman]

I can understand why this was done. And I pary agree, however this means I partly do not agree. On one side of the coin, I wand fpp to be developed and to keep getting better.

On the other side, it seems messed up that you can download something open source yet have to buy a license fee to use its functionality.

Also... for me, this is a hobby, and I am not exactly rolling in money to spend. I have to squeeze every penny and look for ways to save money on my display.  I don't have a lot of money I can spend on this.

That being said, I am surely not the only one in the same boat boat. I'd love to be able to afford the best quality products from the source for everything but I can't afford it. So if I can buy a "knock off" for less that will work, that's great for me. 

It feels like a smack in the face to me that now if go to add to my show, and a 3rd party controller exists that could save me money, I now have to pay the (open source developers)

I did buy kulp with my first pixel controller. But in the future it sucks for a guy in my position.

Also... what about when you sell out of all your products??? What if I wanted to get a kulp or a falcon but can't and the only thing I can find is 3rd party???

You sell out a lot come close to Xmas. You don't exactly have an issue selling your boards...

[lrhorer]

I have a number of simple systems that use Pin 12 on the Raspberry Pi to drive a single string of WS28xx pixels.  If I upgrade these systems to V6, will I encounter any issues?  These systems have no intelligence whatsoever.  They are purely passive with the exception of a level shifter to allow the 3.3V GPIO pin to reliably drive various RGB pixels.

[breese]

While I have a Pi running pixels off 2 GPIO ports and upgrading to 6.2 did not change anything.
Personally, if your show is running I would wait until the season is over so as to not break anything.

[lrhorer]

Oh, absolutely.  I was just looking toward the horizon.

[Bwinter]

I can understand why this was done. And I pary agree, however this means I partly do not agree. On one side of the coin, I wand fpp to be developed and to keep getting better.

On the other side, it seems messed up that you can download something open source yet have to buy a license fee to use its functionality.

Also... for me, this is a hobby, and I am not exactly rolling in money to spend. I have to squeeze every penny and look for ways to save money on my display.  I don't have a lot of money I can spend on this.

That being said, I am surely not the only one in the same boat boat. I'd love to be able to afford the best quality products from the source for everything but I can't afford it. So if I can buy a "knock off" for less that will work, that's great for me.

It feels like a smack in the face to me that now if go to add to my show, and a 3rd party controller exists that could save me money, I now have to pay the (open source developers)

I did buy kulp with my first pixel controller. But in the future it sucks for a guy in my position.

Also... what about when you sell out of all your products??? What if I wanted to get a kulp or a falcon but can't and the only thing I can find is 3rd party???

You sell out a lot come close to Xmas. You don't exactly have an issue selling your boards...

One thing I'm not looking forward to, is when I need to do a complete/fresh install of FPP (which is common):

Will my prior licenses work?  If so, do I need to remember which license is attached to each Pi?

Also, since each uSD (and license) is attached to a discrete Pi, I can't keep a generic spare/backup uSD card handy to quickly swap-in mid-show.  Even though DIY licenses are free—I've learned that I need to get them well in advance (5+ days).