Capes and FPP6 licence status Printable version

This page details how specific pixel output board capes/hats are impacted by FPP6 pixel output changes. It is a work in progress, best efforts, and may contain errors. Corrections welcome. Where details conflict with any official FPP communication or resource, those official definitions, interpretations, etc take precedence.

How specific capes are affected

The table below attempts to clarify whether individual capes retain existing functionality unlicenced, whether they include a licence and if not what functionality a licence can add.

Who needs a licence key for DPI or BBB pixel output

In very generalised terms, a cape is affected by FPP6 changes if it outputs to pixels and:

• It runs from a BeagleBone Black/BeagleBone Green/PocketBeagle; or
• It runs from a Raspberry Pi and:
  • you want to to use DPIPixel output features which will allow you to:
    • use Raspberry Pi onboard audio; or
    • connect more than two pixel strings;

An unlicensed FPP 6.0 instance driving pixels strings using either a BeagleBone or with DPIPixels on a Raspberry Pi, will be limited to 50 pixels per string. An unlicensed BeagleBone will not allow you to use smart receiver functionality at all.

From https://shop.falconplayer.com/2022/05/06/how-to-tell-if-you-actually-need-a-license-key/:

License Keys are only applicable to the FPP Pixel outputs which use the BBB48String and DPIPixels Channel Output drivers. The BBB48String driver is the only pixel output on the BeagleBone. The new DPIPixels output for the Pi is a new Channel Output driver which can drive up to 24 strings of directly attached pixels on a Raspberry Pi.

Click to expand...

From https://shop.falconplayer.com/ufaq/...ality-provided-by-the-license-key-activation/:

When using a cape with an unsigned EEPROM, the BBB48String and DPIPixels Channel Outputs are limited to 50 pixels max per string output and are not allowed to use differential smart receivers. If you apply a license key or keys to sign the EEPROM, these limits are removed for the number of outputs covered by the license key(s) applied. The covered outputs are ALWAYS applied starting at the first outputs on a board, you can not select which outputs to cover with a license key.

Click to expand...

Licence key exceptions

For DIY capes you personally built, from https://shop.falconplayer.com/ufaq/how-do-i-get-one-of-those-free-diy-vouchers/:

If you built a DIY cape for your own personal use, you can get a free License Key voucher by sending a picture of the cape to diy@falconplayer.com and we will send you a voucher.

Click to expand...

For Kulp capes, from https://shop.falconplayer.com/ufaq/i-purchased-a-kulp-cape-do-i-still-need-a-license-key/:

All current-version Kulp capes come with a pre-signed EEPROM. This includes capes purchased directly from KulpLights.com as well as capes purchased from other vendors which sell Kulp capes such as WiredWatts.com. If you have an older Kulp cape which pre-dates the inclusion of EEPROMs, you should be able to use the Virtual EEPROM for your cape which is included with FPP. The Virtual EEPROMs for the original Kulp capes are signed as well.

Click to expand...

Any capes from other FPP developers are also understood to be pre-signed hence do not need a licence.


For other cape brand purchases before 31 July 2022, from https://shop.falconplayer.com/ufaq/...iving-free-license-key-vouchers-is-this-true/:

If you purchased a cape with more than 2 string outputs from another vendor on or before July 31, 2022, your cape is “grandfathered in”. Email sales@falconplayer.com with a picture showing proof of when the cape was purchased and how many outputs it has and we will send you a free voucher.

Click to expand...