How to configure model to use F48 DMX channels

[dm9991966]

I have several LOR controllers that will be daisy chained off one of the F48 DMX ports.  Using 2019.36, what is the correct way to configure the setup and models to use those devices?  I can't seem to find anything in the manual or videos that cover that type of setup.

Thanks,
Trace Wilson
Jacksonville, FL

[Ebuechner]

You use an E1.31 universe that you send to the f48.
The f48 converts that Universe to the DMX output for your Lor controllers.
With Lor controllers make absolutely sure you have the jumper set correctly and only use one of the two bottom RJ45 connectors on the right hand side of the board and not the top connector.

[Ebuechner]

The model would depend on what you're doing with those controllers but you would just set up whatever model you make with the universe and start Channel the matches the universe you used for the DMX output and the start channel of the controller.

[keithsw1111]

If you are looking to upload set protocol to dmx and the port to the dmx port number. If getting problems with the upload we would need to see the logs.

[dm9991966]

Ok.  In the model Controller Connect section, Port = the DMX port on the F48, Protocol = "DMX", and "dmx Channel" = the LOR channel, using the LOR to DMX mapping (LOR ID 1 = DMX channels 1-16, LOR ID 2 = DMX channels 17-32, etc), correct?

For the Setup tab, lets assume I'm using Universes 1-96 for the pixel ports, and Universe 500 for the LOR stuff.  Can I put 2 controller entries the point to the same IP address, or do I need switch up to use port 97 for the DMX stuff and only have a single entry for that IP address?

[keithsw1111]

First of all dont define 96 universes unless you are actually using them.

Yes dmx channel works as you describe.

The rest of your question is largely confusing.

[dm9991966]

Hmmm, ok.  If I want universes 1-4 to be pixels, and universe 100 to be my LOR stuff, all running off the same F48, what would be the best way to define that on the Setup tab? 

Can I define 1 E131 unicast network for universes 1-4 on IP address 192.168.2.32, then a second E131 unicast network for universe 100 also on IP address 192.168.2.32, or will xLights not like have 2 separate definitions pointed to the same IP address?

[keithsw1111]

You can have 2 if you like.

[dm9991966]

Very good.  Another question (sorry):  When I update the FPP via FPP Connect, I am expecting to see 2 entries in the Channel Inputs/E1.31 Bridge page, one for universes 1-4 going to 192.168.2.32, and a second for universe 100 also going to 192.168.2.32.  Instead, that page is empty, and all of my models are defined on the Pixel Overlay Models page.  Is that expected?  If not, where would be the best place to start looking to figure out how I misconfigured things?

FWIW, FPP is running on a Raspberry Pi 3B+, FPP v2.7.2.