Before you buy another adapter, figure out what kind of connection your controller needs. LOR, serial DMX and E1.31 can all be part of a light show, but the software settings and physical connections are different.
We want you to be able to look at a cable and explain where it goes, what data it carries and which prop it controls. That is a much better starting point than guessing from the shape of the socket.
Start with the path from the computer
| Connection | Typical path | Settings to match |
|---|---|---|
| LOR or Enhanced LOR | USB to a suitable LOR RS485 adapter, then the controller network | Network name, Unit ID and circuit |
| Serial DMX | Supported USB-DMX interface to a DMX device | DMX universe and channel |
| E1.31 / sACN | Ethernet to an E1.31-capable controller | Destination, universe and channel |
Check the LOR Networks guide for your release. Current documentation also lists Art-Net, but your receiving controller still has to support the protocol you choose.
Our MD1500 Baldrick8 xConnect controller is an example of an Ethernet pixel controller with E1.31 support. Its pixel pigtails and its network connection do different jobs. Follow the exact unit's instructions for both.
Label serial and Ethernet connections clearly. The Aurora Core manual, for example, distinguishes its Ethernet port from serial outputs and warns against connecting that Ethernet port to a USB-RS485 adapter. Similar-looking plugs are not permission to interchange them.
Know when Enhanced LOR is required
Enhanced LOR, or ELOR, supports Motion Effects and larger channel counts. Standard LOR does not carry Motion Effects. The adapter, controllers and other equipment on that network must support the selected mode and speed.
Use the manufacturer's network compatibility table before changing speed or mixing equipment generations. In the LOR Adapter settings, record which COM port belongs to Regular, Aux A or another named network. Matching the Unit ID is not enough when the prop is assigned to the wrong network.
Count channels according to the lights
An RGB pixel uses three intensity channels. One hundred individually controlled RGB nodes therefore need 300 channels. RGBW adds a separate white channel. A traditional AC string controlled as one output uses one intensity channel for that output; each bulb is not an RGB node. The Channels reference explains the addressing.
This also helps when comparing EVO with EVO+. EVO+ uses four wires for its dual-data design. That does not make it RGBW. Check light type and protocol separately from conductor count.
Make 510 or 512 agree at both ends
A DMX universe has up to 512 channels. A 510-channel RGB mapping puts 170 complete RGB nodes in each universe. With that arrangement, a 200-node prop starting at universe 1, channel 1 uses universe 1's 510 channels plus channels 1–90 of universe 2.
That is a data example, not a port power rating. One physical output does not always equal one universe. Check pixel capacity, current limits and wiring separately.
Inspect existing props rather than relying on defaults. The S6 release notes say version 6.6.2 changed the default for new DMX props to 510 channels without changing existing props.
Set up both sides of E1.31
Add the E1.31 controller in the Control Panel with its intended universe range and destination. For unicast, use that controller's actual IP address. The E1.31 settings guide describes the destination modes.
Then open the controller's own configuration and check which incoming data feeds each output. Use unique device addresses and the appropriate subnet for your network. Being able to open a controller's web page proves you can reach the settings; you still need a light test to prove the output mapping. See LOR's TCP/IP examples.
Keep license limits separate from equipment limits
The official chart reviewed October 29, 2026 lists one E1.31 universe for Basic, 999 for Advanced and 3,000 for Pro. Basic includes limited pixel Motion Effects; Advanced lacks Motion Effect sequencing; Pro supports larger pixel shows. Check the current feature chart for your installed release.
A software allowance does not establish what your computer, controller or power system can run. Plan for the actual display rather than treating the license maximum as a target.
Switching between xLights and LOR takes another check
A model, editable sequence and rendered playback file are different things. S6 can import supported .xmodel shapes, but you must verify count, wiring and assignments; consult the model-import documentation. Importing the shape does not import a song's effects.
LOR Pro's FSEQ export includes DMX props and reserves 512 channel slots for every universe from 1 through the highest used universe, even when prop numbering uses 510. Its legacy LMS/LAS export excludes Motion Effect rows. Read the export limitations before planning the handoff.
Back up the working show and prove one prop through the intended player before switching everything. Need a second look? Send Mattos support your software version, controller, pixels and a simple connection sketch.
