- Welcome to Falcon Christmas.
News:
LATEST RELEASE: FPP 9.5 - Download from here - https://github.com/FalconChristmas/fpp/releases/tag/9.5
User
Site Stats
Members
Total Members: 17225
Latest: mswenson
New This Month: 4
New This Week: 0
New Today: 0
Stats
Total Posts: 137009
Total Topics: 17316
Most Online Today: 1329
Most Online Ever: 7634
(January 21, 2020, 02:14:03 AM)
Users OnlineMembers: 0
Guests: 658
Total: 658
Recent posts
#11
Falcon Player Plugins / Re: LoRa plugin. Is it worth ...
Last post by csmith - February 10, 2026, 09:57:30 AMThis LoRa plugin actually works and has a great range!!!
I used 4 different EBYTE E22-900T22U LoRa modules. All plug into the USB 2.0 port. Each module includes a stubby 3" antenna.
I'm running FPP 9.5 on Raspberry Pi 4B's each with 4GB RAM
but...
After the FPP remotes are up and running, then you must start (or reboot) the FPP player before it establishes a reliable wireless data link. Start/restart a remote after the player is running and the remote never plays a sequence... even when the player starts another sequence. Odd.
What's the range? I went >1000 feet from my house... where no WiFi signal had ever penetrated and the remotes stayed in sync using LoRa.
At the beginning of a sequence, the remotes would be about 100msec behind the player but would catch up in a few seconds.
Bottom line: the LoRa technology works but the plugin needs some tweaking to be as bulletproof as the rest of FPP.
I used 4 different EBYTE E22-900T22U LoRa modules. All plug into the USB 2.0 port. Each module includes a stubby 3" antenna.
I'm running FPP 9.5 on Raspberry Pi 4B's each with 4GB RAM
but...
After the FPP remotes are up and running, then you must start (or reboot) the FPP player before it establishes a reliable wireless data link. Start/restart a remote after the player is running and the remote never plays a sequence... even when the player starts another sequence. Odd.
What's the range? I went >1000 feet from my house... where no WiFi signal had ever penetrated and the remotes stayed in sync using LoRa.
At the beginning of a sequence, the remotes would be about 100msec behind the player but would catch up in a few seconds.
Bottom line: the LoRa technology works but the plugin needs some tweaking to be as bulletproof as the rest of FPP.
#12
F16v3 Pixel Controller / Re: FPP won't connect with F16...
Last post by patdepri - February 10, 2026, 08:59:08 AMQuote from: JonD on February 04, 2026, 03:22:32 AMMight just need to add falcon controller to FPP proxy config, and then add fpp wifi IP as proxy to falcon controller settings in xlights.
Another alternative is to change FPP GUI Settings, place into advance or developer mode, then under network settings on FPP, change IP forwarding mode to "Forwarding".
Hello everyone, sorry for the delay.
First of all, thank you for your prompt response, which was crucial for the basic solution to the problem.
Thanks JonD, your suggestions were helpful.
The goal of communicating with the F16v3 controller was achieved brilliantly, and I'll explain below with a short guide for beginners like me.
For this project, I used a PI 4 and a Falcon F16v3 Controller.
Please note: All network values displayed refer to MY project. They most likely won't apply to yours.
Preparing FPP Software
- Download FPP-v9.5-Pi.img or newer
- Format 32GB SD card with —> - SD Formatter -
- Start - balenaEtcher -
- —> Flash from file
- —> Select Target
- —> Flash!
If necessary, also update F16v3.
- In this case, you will need two 32GB SD cards.
- One is for booting.
- The other updates the software.
- There are explanations online.
FPP 9.5
- Insert the SD card into the PI.
- Connect the PI to the modem with an Ethernet cable.
- Open Safari, Chrome, Firefox, or similar browsers.
- In the browser, open the page —> http://fpp.local.
- Fill in the opening page - FPP Initial Setup - and click Finish Setup.
- Go to: —> Status/Control —> FPP Setting --> UI.
User Interface Level: Developer.
- Go to: —> Status/Control —> Network Configuration —> Interface Settings —> wlan0.
(in my case)
Interface Mode: Static.
IP Address: 92.168.1.100.
Netmask: 255.255.255.0.
Gateway: 192.168.1.1
DNS Settings
DNS Server Mode: Manual
DNS Server 1: 192.168.1.1
DNS Server 2: 1.1.1.1
Wireless Settings
WPA SSID: - Enter your parameters -
WPA Pre Shared Key: - Enter your parameters -
- IMPORTANT -
Advanced Interface Settings
IP Forwarding: Forwarding
- Press Update NOT Reboot
Interface Settings —> eth0
(in my case)
Interface Mode: Static
IP Address: 92.168.2.100
Netmask: 255.255.255.0
Gateway: leave blank
DNS Settings
DNS Server Mode: Manual
DNS Server 1: 192.168.1.1
DNS Server 2: 1.1.1.1
- IMPORTANT -
Advanced Interface Settings
IP Forwarding: Forwarding
- Press Update AND Reboot
- Unplug the Ethernet cable from the modem and connect the PI to the Falcon Controller F16v3 (in my case)
- Go to: —> Status/Control —> Proxy Settings —> Proxied Host
- Click + Add to add the Proxied Hosts (Manually Maintained)
(in my case)
IP/HOSTNAME: 192.168.2.50
DESCRIPTION: Falcon Controller F16v3
Go to: —> Input/Output Setup —> Channel Inputs
E1.31 / ArtNet / DDP Inputs
Enable Input: √ (selected) (This will allow xLights to display the light show directly by clicking on the bulb).
The pages:
- Input/Output Setup —> Channel Outputs
and
- Input/Output Setup —> Pixel Overlay Models
They will be configured directly from xLights.
F16v3
- On the Falcon Controller's OLED screen, manually set the parameters for receiving data from the Pi using the small buttons (in my case, these are the ones).
Network type: Static
IP: 92.168.002.050
Mask: 255.255.255.000
GW: 192.168.002.100
DNS: 192.168.001.001
xLights
- Layout and Sequencer (created according to your own project, not explained here)
- Controllers —> Add Ethernet
- In the side window, select: Active
- Monitor: √ (selected)
- IP Address: 192.168.2.50 (<—this must be the address of the Falcon Controller)
- FPP Proxy IP: 192.168.1.100 (<—this must be the address of the FPP)
- Protocol: E131
- Click - Save -
- Clicking the - Open - and - Open Proxy - buttons opens the Falcon Controller and the FPP.
Please Note: When transferring sequences from xLights to FPP using the -FPP Connect- button, a new window opens where you must configure the type of data to transfer. At the top, we have Upload - HostName - IP Address - Description - Mode - Version - FSEQ Type - Media - Models - UDP Out - Add Proxies - Playlist - Pixel Hat/Cape. Below, you'll find the project sequences that xLights has detected.
I personally use these parameters:
FSEQ Type: V2 Sparse/zstd (this may NOT be your case)
Media: √ (selected to export music, etc.)
Models: All (to export data: Pixel Overlay Models)
UDP Out: All
Add Proxies: √ (selected)
In the window below, I select the sequences I want to send.
Finally, click Upload.
From Safari, Chrome, Firefox, or other browsers
- Enter the address http://fpp.local/proxy/192.168.2.50/config.htm (in my case). The Falcon F16v3 controller home page opens.
- Under the menu —> Network Configuration, if the settings are missing, configure them.
(In my case, these are the settings)
IP Address: 192.168.2.50
Gateway: 192.168.2.100
Subnet Mask: 255.255.255.0
Primary DNS: 192.168.1.1
Secondary DNS: 0.0.0.0
- Under the menu —> E131 Setup, if the settings are missing, you must configure them manually and save.
Something like this:
1 1 510 1 510 E131Artnet
2 2 510 511 1020 E131Artnet
3 3 510 1021 1530 E131Artnet
4 4 510 1531 2040 E131Artnet
5 5 510 2041 2550 E131Artnet
etc.
- Under the menu —> Output Settings —> Strings Port (Port Configuration) If the LED strip parameters are missing, as in my case, I had to enter them manually. They must match (i.e., align) with those set in xLights, otherwise no LEDs will light up.
Something similar to this:
1) WS2811 Mega Tree 1 960 1 2880 ForwardReversed RGB 0 0 100%
2) WS2811 Top 1 2881 80 1 3120 ForwardReversed RGB 0 0 100%
3) WS2811 Top 2 3121 80 1 3360 ForwardReversed RGB 0 0 100%
4) WS2811 Top 3 3361 80 1 3600 ForwardReversed RGB 0 0 100%
5) WS2811 Top 4 3601 80 1 3840 ForwardReversed RGB 0 0 100%
etc.
IMPORTANT TIPS
- Whenever you decide to end an FPP session, you must do so using the Shutdown button at the bottom of the FPP page and wait for no further data to be transmitted to the Falcon controller (usually about ten seconds is enough).
- Disconnect the power.
- If everything works as expected, I personally recommend CLONE the software on the PI's card.
How to do it?
1 - Disconnect the system power.
2 - Remove the SD card from the PI.
3 - Format a new card (also use the SD Card Formatter) with the same capacity as the SD card you want to clone.
4 - Start balenaEtcher.
5 - Click —> clone Drive.
6 - Click —> Select source —> insert the card you want to clone.
7 - Click —> Select target —> insert the newly formatted card.
8 - Click —> Flash!
9 - Once the operation is complete, you have a copy of all your work.
10 - Insert the new card into the PI and test it.
I can't answer any other questions. I just described how to make my simple project work.
Thanks again for everything, and I hope I've been clear about what I described in my mini-guide.
#13
Falcon Player (FPP) / Re: Explanation of ED (Extende...
Last post by dkulp - February 09, 2026, 05:58:08 PMDepends on the controller. xLights has separate classes that handle that for each of the controller types it supports. Falcons have their own code path. FPP has its own. ESPixelStick has its own, Experience, etc.... Basically, if the contoller has a decent REST api (json preferred, but not required) and the controller is publicly available, then xLights could be updated.
#14
Falcon Player (FPP) / Re: Explanation of ED (Extende...
Last post by Florida-Rob - February 09, 2026, 09:48:42 AMWhere may we find the protcol definition for the 'configuration that is needed', either via the "Upload Inputs/Output" buttons or via FPP connect ? i belive its here
#15
Falcon Player (FPP) / Re: Explanation of ED (Extende...
Last post by dkulp - February 07, 2026, 06:30:39 AMI would definitely NOT rely on anything in those or even rely on the existence of those. Those were just added in 2026.01 and there is some debate about making them optional or even removing them. Also don't rely on the format of them as they will be changing throughout this year.
xLights needs to push the configuration that is needed either via the "Upload Inputs/Output" buttons or via FPP connect.
#16
Falcon Player (FPP) / Re: Explanation of ED (Extende...
Last post by Florida-Rob - February 06, 2026, 05:07:17 PMThanks for the reply
I have found that the facebook ZSTD need > 150KB to run, no matter how to try and contain the workspace for the algorithm, either Block, Raw or Stream. So for small micros, its 'impossible' to use ZHSD.
So ZLIB works, typically 32KB, and works great.
BUT, BUT....
The ED section is ALWAYS encoded in ZSTD !
// XS - xLight xsq (zstd compressed binary)
// XN - xLight xlights_network.xml (zstd compressed binary)
// XR - xLight xlights_rgbeffects.xml (zstd compressed binary)
so...
How are we supposed to decode universes from the file? as the blocks with Frames of Channels are in ZLIB, but the ED data is in ZSTD !
Why does XLIghts not use ZLIB for the ED Data !!!
am I missing something ?
Of course we can separate the Sender from Receiver, and program the Receiver (with the FSEQ file) with mapped Universe(s) to strip(s), but how is that mapped ?
you can see from the data below how a simple 2 universe, 200 LED, 600 Pixel, FSEQ as ZLIB is output, and also the memory usage during Zlib:
Directory contents of /sdcard:
DIR: System Volume Information
FILE: seq-200LED.fseq
Inside process_fseq
-->MEM FREE 151552
======================
== Xlights FSEQ V2.0 Header
======================
Channel Data offset : 216
variable Data offset : 128
FSEQ Version: 2.2
Channel Count: 1020
Frame Count: 600
Step Time (ms): 50
Compression : ZLIB
Compression Blocks : 12
channel Range Count : 0
======================
-->MEM FREE 151552
== Variable Headers
ID: sp, Size: 34 Data: xLights Windows 2026.01 64bit
ID: ED, Size: 18, Code: XR, Offset: 47126, Ln: 1805xLights_rgbeffects.xml (zstd), Data[0-9]:28 B5 2F FD 60 CB 1E 1D 38 00
ID: ED, Size: 18, Code: XN, Offset: 48931, Ln: 460xLights_network.xml (zstd) , Data[0-9]:28 B5 2F FD 60 25 02 15 0E 00
ID: ED, Size: 18, Code: XS, Offset: 49391, Ln: 1415xLights xsq (zstd) , Data[0-9]:28 B5 2F FD 60 9F 18 ED 2B 00
======================
-->MEM FREE 151552
== Compression Blocks
Block 0: First Frame 0, Comp. Size 2594 bytes
Block 1: First Frame 10, Comp. Size 17946 bytes
Block 2: First Frame 76, Comp. Size 8241 bytes
Block 3: First Frame 142, Comp. Size 1934 bytes
Block 4: First Frame 208, Comp. Size 1375 bytes
Block 5: First Frame 274, Comp. Size 1834 bytes
Block 6: First Frame 340, Comp. Size 2672 bytes
Block 7: First Frame 406, Comp. Size 4011 bytes
Block 8: First Frame 472, Comp. Size 3420 bytes
Block 9: First Frame 538, Comp. Size 2883 bytes
Block 10: First Frame 0, Comp. Size 0 bytes
Block 11: First Frame 0, Comp. Size 0 bytes
======================
Block 0: MEM FREE 129024 SUCCESS 10200 bytes
Block 0: Decompressed 10200 bytes. Starting timed output...
Block 1: MEM FREE 56320 SUCCESS 67320 bytes
Block 1: Decompressed 67320 bytes. Starting timed output...
Block 2: MEM FREE 65536 SUCCESS 67320 bytes
Block 2: Decompressed 67320 bytes. Starting timed output...
Block 3: MEM FREE 71680 SUCCESS 67320 bytes
Block 3: Decompressed 67320 bytes. Starting timed output...
Block 4: MEM FREE 71680 SUCCESS 67320 bytes
Block 4: Decompressed 67320 bytes. Starting timed output...
Block 5: MEM FREE 71680 SUCCESS 67320 bytes
Block 5: Decompressed 67320 bytes. Starting timed output...
Block 6: MEM FREE 71680 SUCCESS 67320 bytes
Block 6: Decompressed 67320 bytes. Starting timed output...
Block 7: MEM FREE 69632 SUCCESS 67320 bytes
Block 7: Decompressed 67320 bytes. Starting timed output...
Block 8: MEM FREE 69632 SUCCESS 67320 bytes
Block 8: Decompressed 67320 bytes. Starting timed output...
-->MEM FREE 151552
======================
I have found that the facebook ZSTD need > 150KB to run, no matter how to try and contain the workspace for the algorithm, either Block, Raw or Stream. So for small micros, its 'impossible' to use ZHSD.
So ZLIB works, typically 32KB, and works great.
BUT, BUT....
The ED section is ALWAYS encoded in ZSTD !
// XS - xLight xsq (zstd compressed binary)
// XN - xLight xlights_network.xml (zstd compressed binary)
// XR - xLight xlights_rgbeffects.xml (zstd compressed binary)
so...
How are we supposed to decode universes from the file? as the blocks with Frames of Channels are in ZLIB, but the ED data is in ZSTD !
Why does XLIghts not use ZLIB for the ED Data !!!
am I missing something ?
Of course we can separate the Sender from Receiver, and program the Receiver (with the FSEQ file) with mapped Universe(s) to strip(s), but how is that mapped ?
you can see from the data below how a simple 2 universe, 200 LED, 600 Pixel, FSEQ as ZLIB is output, and also the memory usage during Zlib:
Directory contents of /sdcard:
DIR: System Volume Information
FILE: seq-200LED.fseq
Inside process_fseq
-->MEM FREE 151552
======================
== Xlights FSEQ V2.0 Header
======================
Channel Data offset : 216
variable Data offset : 128
FSEQ Version: 2.2
Channel Count: 1020
Frame Count: 600
Step Time (ms): 50
Compression : ZLIB
Compression Blocks : 12
channel Range Count : 0
======================
-->MEM FREE 151552
== Variable Headers
ID: sp, Size: 34 Data: xLights Windows 2026.01 64bit
ID: ED, Size: 18, Code: XR, Offset: 47126, Ln: 1805xLights_rgbeffects.xml (zstd), Data[0-9]:28 B5 2F FD 60 CB 1E 1D 38 00
ID: ED, Size: 18, Code: XN, Offset: 48931, Ln: 460xLights_network.xml (zstd) , Data[0-9]:28 B5 2F FD 60 25 02 15 0E 00
ID: ED, Size: 18, Code: XS, Offset: 49391, Ln: 1415xLights xsq (zstd) , Data[0-9]:28 B5 2F FD 60 9F 18 ED 2B 00
======================
-->MEM FREE 151552
== Compression Blocks
Block 0: First Frame 0, Comp. Size 2594 bytes
Block 1: First Frame 10, Comp. Size 17946 bytes
Block 2: First Frame 76, Comp. Size 8241 bytes
Block 3: First Frame 142, Comp. Size 1934 bytes
Block 4: First Frame 208, Comp. Size 1375 bytes
Block 5: First Frame 274, Comp. Size 1834 bytes
Block 6: First Frame 340, Comp. Size 2672 bytes
Block 7: First Frame 406, Comp. Size 4011 bytes
Block 8: First Frame 472, Comp. Size 3420 bytes
Block 9: First Frame 538, Comp. Size 2883 bytes
Block 10: First Frame 0, Comp. Size 0 bytes
Block 11: First Frame 0, Comp. Size 0 bytes
======================
Block 0: MEM FREE 129024 SUCCESS 10200 bytes
Block 0: Decompressed 10200 bytes. Starting timed output...
Block 1: MEM FREE 56320 SUCCESS 67320 bytes
Block 1: Decompressed 67320 bytes. Starting timed output...
Block 2: MEM FREE 65536 SUCCESS 67320 bytes
Block 2: Decompressed 67320 bytes. Starting timed output...
Block 3: MEM FREE 71680 SUCCESS 67320 bytes
Block 3: Decompressed 67320 bytes. Starting timed output...
Block 4: MEM FREE 71680 SUCCESS 67320 bytes
Block 4: Decompressed 67320 bytes. Starting timed output...
Block 5: MEM FREE 71680 SUCCESS 67320 bytes
Block 5: Decompressed 67320 bytes. Starting timed output...
Block 6: MEM FREE 71680 SUCCESS 67320 bytes
Block 6: Decompressed 67320 bytes. Starting timed output...
Block 7: MEM FREE 69632 SUCCESS 67320 bytes
Block 7: Decompressed 67320 bytes. Starting timed output...
Block 8: MEM FREE 69632 SUCCESS 67320 bytes
Block 8: Decompressed 67320 bytes. Starting timed output...
-->MEM FREE 151552
======================
#17
F16v3 Pixel Controller / Re: Issues with firmware updat...
Last post by darylc - February 05, 2026, 09:20:05 PMQuote from: 2Couyon on February 05, 2026, 10:06:47 AMSo you have to "hold the select button down" to install the Bootloader as well?You don't need the bootloader, it's already been done since you are on 2.56
Just do this bit:
Updating Firmware (These steps taken for each firmware update)
1) Place .fl2 file MicroSd card
2) Power Down/Up
3) The firmware will install
4) Remove card when finished and power down/up.
5) Controller will boot
#18
F16v3 Pixel Controller / Re: Issues with firmware updat...
Last post by 2Couyon - February 05, 2026, 10:06:47 AMQuote from: Todd on February 03, 2026, 04:48:20 PMSo you have to "hold the select button down" to install the Bootloader as well?Quote from: 2Couyon on February 02, 2026, 04:34:26 AMAre you holding the select button down while powering back up with the bootloader as card inserted?Quote from: Todd on January 31, 2026, 02:18:54 PMMine was a pain in the *** when I did it before Christmas. I put the boot loader on one so card 32gb or less sd card. And the firmware on another. 32gb or less. It won't work with a larger sd card. Be sure to follow the instructions on pixel controller.com exactly. Mine took multiple try's to get it to go. The same issue was on my F48. But it eventually went and all was good.Yeah I am following it exactly. Tried a 8GB & 16GB SD card. It is like I don't even put a card in there.
Sent from my iPad using Tapatalk
Sent from my iPhone using Tapatalk
#19
Falcon Player (FPP) / Re: Explanation of ED (Extende...
Last post by dkulp - February 05, 2026, 09:17:59 AMIt can be whatever the application that wrote the xseq wants it to be. In this case, the code is "XR" (0x58 and 0x52), which, again, can be whatever the application wants it to be. The only two that are really defined are "mf" and "sp". xLights has a few it uses, with the important ones being FC and FE which are the FPP command preset and effect timing tracks.
#20
F16v3 Pixel Controller / Re: FPP won't connect with F16...
Last post by JonD - February 04, 2026, 03:22:32 AM"I can't open the 192.168.2.50 page, which should allow me to directly open the PxelController, as was done in the past, where I had to enter the LED strip settings.
I don't know if this still needs to be done with the new updates.
- If I start a sequence from the FPP Player, nothing lights up."
IP and routing look okay to me. The fact you can get to Pi 192.168.2.100 is good sign. Might just need to add falcon controller to FPP proxy config, and then add fpp wifi IP as proxy to falcon controller settings in xlights.
Another alternative is to change FPP GUI Settings, place into advance or developer mode, then under network settings on FPP, change IP forwarding mode to "Forwarding".
I don't know if this still needs to be done with the new updates.
- If I start a sequence from the FPP Player, nothing lights up."
IP and routing look okay to me. The fact you can get to Pi 192.168.2.100 is good sign. Might just need to add falcon controller to FPP proxy config, and then add fpp wifi IP as proxy to falcon controller settings in xlights.
Another alternative is to change FPP GUI Settings, place into advance or developer mode, then under network settings on FPP, change IP forwarding mode to "Forwarding".
Support FPP
Recent Topics
|
FPP 9.5
by alman4511
Today at 09:53:32 AM |
|
F16V5 FW 37 Fan settings
by jnealand
February 14, 2026, 07:48:45 AM |
|
Issues with firmware update
by 2Couyon
February 11, 2026, 04:45:33 PM |
|
FPP won't connect with F16v3
by patdepri
February 11, 2026, 05:25:33 AM |
|
LoRa plugin. Is it worth pursuing in 2026
by csmith
February 10, 2026, 09:57:30 AM |
|
Explanation of ED (Extended Data)
by dkulp
February 09, 2026, 05:58:08 PM |
|
E682 San Devices doesn't power up
by ScaryJerry
February 03, 2026, 06:48:50 PM |
|
F16v3 v2.58
by JonD
February 02, 2026, 09:03:41 AM |
|
Retrofit and Simple Message Generation Software Recommendations
by skyblaster
February 01, 2026, 07:23:25 PM |
|
New Plugin
by sctwohig
January 29, 2026, 12:46:55 PM |
Powered by EzPortal