FPP won't connect with F16v3

[patdepri]

My system yesterday and today:
Computer --> Modem --> Pi -- F16v3.

No other peripherals connected.

After switching to a fiber modem, the light show stopped working (FPP 4.6 installed).

So I decided to use the new FPP version 9 and begin this new adventure.

1 - I installed the new FPP 9.5 on the Pi.
2 - F16v3 (reset and updated b022).

3 - Via Ethernet, I performed the various FPP configurations, which I summarize here:

Static wlan0
IP Address 192.168.1.100
Netmask 255.255.255.0
Gateway 192.168.1.1

DNS 1 - 192.168.1.1
DNS 2 - 1.1.1.1

Static eth0
IP Address 192.168.2.100
Netmask 255.255.255.0
Empty Gateway

DNS 1 - 192.168.1.1
DNS 2 - 1.1.1.1

4 - I disconnect the Ethernet from the modem and connect the PI to the F16v3 with the same cable.

5 - From my Mac terminal, I created:

sudo route -n add -net 192.168.2.0/24 192.168.1.100.

6 - I can access the two IPs

192.168.2.100 and 192.168.1.100

They load the FPP 9.5 page.

So far, so good.

7 - Over the internet, I get this:

From x-Lights - I can send all the .fseq files.
Pixel Overlay Models - Loading correctly
E1.31 / ArtNet / DDP / KiNet - Loading correctly

8 - I set the following on F16v3:

IP address - 192.168.2.50
Mask - 255.255.255.0
GW - 192.168.2.100
DNS - 192.168.1.1

This is where the problems begin.

- 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.

Where did I go wrong?

Is there some configuration missing?

I'd like to highlight some of my other efforts to resolve the issue:

- I've reinstalled the software several times with no success.
- The same goes for F16v3 b022.
- I've changed several Ethernet cables.
- When I run the test on F16v3, the LEDs light up.
- I've consulted several discussions on the issue.

I'd like to know how FPP communicates with F16 today?
That is, what data does it send compared to the past?

Thanks in advance

[jnealand]

There are a number of things you did not mention such as channel outputs and ip forwarding.  The fastest way forward is for you to connect up to the zoom room and get live help.

[JonD]

"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".

[patdepri]

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".

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.

[Poporacer]

I'll explain below with a short guide for beginners like me

Thanks for the info, but just a FYI this is covered in the FPP Manual.

- Go to: —> Status/Control —> FPP Setting --> UI.

User Interface Level: Developer.

This is NOT a good idea, ESPECIALLY for someone that is not an expert. The setting the UI to Developer level will allow a user to make configuration changes that are NOT compatible with their device or even make it useless. 

[patdepri]

This is NOT a good idea, ESPECIALLY for someone that is not an expert. The setting the UI to Developer level will allow a user to make configuration changes that are NOT compatible with their device or even make it useless.

Thanks for the advice and clarifications. Have a nice day.