Controller configuration

[Swedge]

I have a Kulp F8-B controller running FPP 6.3. It has Ethernet and WIFI interfaces. The Ethernet interface is on my show network at 192.168.131.130/24. I have other non-FPP devices on the show network which I communicate with via e1.31. The WIFI interface connects to my Windows Mobile Hotspot and has a static address of 192.168.137.130/24. I want to manage the F8-B via the Hotspot address. I prefer to not have the WIFI interface connect to my home network as it's much easier to sever connectivity by disabling the Hotspot.

I'd like to be able to load settings, sequences, outputs, etc. to the F8-B over the Hotspot. I've been unable to find much information about the controller IP Address, FPP Proxy IP/Hostname, or Force Local IP settings on the controller configuration page.

I'm looking for controller settings for:

• IP Address
• FPP Proxy IP/Hostname
• Force Local IP

Thanks in advance.

[Poporacer]

I have a Kulp F8-B controller

Are you sure it is an F8? Those were an early production several years ago and are quite different than the K8s

I'm looking for controller settings for:

• IP Address

Any valid IP address on your network that is not being used will work

I'm looking for controller settings for:

• FPP Proxy IP/Hostname

Do you need a Proxy? That is a specialized routing method.
Any valid unused Hostname will work
https://falconchristmas.github.io/FPP_Manual(6.0).pdf#page=166

I'm looking for controller settings for:

• Force Local IP

That is only used if your computer has more than one interface and isn't routing correctly.

[Swedge]

Thanks for responding. It's an F8-B according to the Cape/Hat Info page. I've had it a few years so I'm not surprised that it's an earlier version. I'm not getting crazy with the hardware features so it should be fine. My other controllers are an older 4 port Advatek, a Chinese DMX-to-e1.31 bridge, and a couple of LOR AC controllers. I also have a couple of smart receivers. I tend to chain my props together and power inject and use f-amps where necessary. I run my show at 20fps and it's relatively small so I haven't needed a lot of ports.

To achieve what I want and after reading your response, I'll set the controller's IP address in xLights to 192.168.137.130/24 (the wlan interface), leave the other controllers on the show network (192.168.131.0/24) and let the F8 talk to them via its Ethernet interface (192.168.131.130/24).

[Poporacer]

Thanks for responding. It's an F8-B according to the Cape/Hat Info page.

That can be wrong if the EEPROM was not programmed correctly or you pushed an incorrect configuration. I would look on the board to be sure. They are way different and won't work right if configured incorrectly.

I'll set the controller's IP address in xLights to 192.168.137.130/24

I assume that you know how to set the netmask correctly, even though you used the /24 notation for shorthand?

[Swedge]

The board says F8-B v3.1. I was a network engineer in a former life and I'm just used to the /## style notation. IP addressing, netmasks, gateways, and routing is familiar ground, I just needed some info on the xLights controller config.

[bloojoop]

I am presuming the f8-b is also being used as your "player".  If so then configure it in xlights with the wlan0 interface IP address that your computer can talk to it on.  Also configure the "active" property for that controller to be "xlights only".  The advatek and chinese dmx bridge may or may not work correctly directly from xlights using "Proxy mode". Are the LOR AC controllers controlled via the dmx output of the Advatek?  Anyway, there are two methods of access a separate show network, one is by using the FPP device as a proxy and the other is using it as a router.  For router operation, you would need to enable IP fowarding on the wlan0 interface.  If that option is not visible, set the UI to advanced mode in FPP settings.  Then you would need to configure a static route on your computer or home router to route the show network (192.168.131.0/24) via the wlan0 interface on the FPP device (192.168.137.130).