Coming from LOR

Running LOR Controller in DMX Mode

LOR to DMX Channel conversion

The following table describes the conversion of a LOR Unit id to a DMX address. As an example, if you have a controller with a Unit id of 03, then when converted to run under DMX, the channel ranges will be 33 to 48.


DMX Address


DMX Address

































































Running LOR in DMX mode

The following diagram shows an example of how LOR controllers can be connected in DMX mode. Refer to the table above of Unit IDs to DMX channel conversions.

You must use the LOR hardware utility to set the DMX start address on a LOR controller if the controller doesn’t have on board channel selection. The next diagram shows an example of how LOR controller addresses are set in a DMX universe. The controllers do not need to be physically connected in order of the controllers start address. The controllers can be put in any order.

Converting a LOR sequence and importing into xLights

This section is based on a video created by Clyde Lindsey.

First ensure that within LOR, all the channels for the controller have been defined and are in sequence. Tools, Channel configuration will display an image similar to the following.

If there are any channels missing use the ‘Add Channels’ function to add the missing (unused) channel.

Note that in the image, the Unit id is 03 and the Channels (Circuit) values run from 1 to 16. However, referring to the LOR Unit Id to DMX channel mapping table Unit id 03 corresponds to Channel number 33. If Units prior to Unit 3 have not been defined, then you need to define them so as to ‘utilise’ the missing channels. Use the ‘Insert Device’ function to ‘Insert Device Above’ the current device (Unit 03) as a LOR 16 channel device – Unit id 01. Repeat this step and add another device - Unit id 02.

Therefore Channels 1-32 (Unit 1 and 2) have been defined – even if not required in LOR, and channels 33 – 48 belonging to Unit 03 are the ones that we are interested in.

On the xLights setup screen, the corresponding channels must be defined.

You can define it as a USB, with a network type of LOR, and set up the COM port (obtained from the LOR device manager) and you will need to try different baud rates.

However, there is sometimes a lag associated with the sequence when you use this option.

It is preferable to use a controller as an E131 to DMX bridge if possible and then define the channels as E131.

For the three devices were defined in LOR, only 48 channels need to be defined, but to preserve a buffer for future use, an extra 16 channels corresponding to an additional LOR device, (i.e. a total of 64 channels) will be defined in Universe 1 as E1.31.

Model definition

Next create a new Model definition that matches the LOR Channels of Unit 03.

Let’s say that this was 16 single channels Trees. In that case create a model ‘Small Tree 1’, with 1 channel. The start channel must be set to 33 (not 1) as this corresponds to the 1st channel of Unit 3.

Then you can copy the model, update the name (Small Tree 2) and change the starting channel to 34 and repeat this for all 16 channels, increasing the start channel by 1 each time until the last one is 48.

If within the LOR Unit 03 definition, there are unused channels, you do not have to create a model for that channel or channel range. For example, let’s say within Unit 03, channels 10-14 are not used. In which case, you would create 9 Trees (1 -9), and then another 2 trees (for 15-16). This is different to the setup tab where you must cover the entire range of channels from 1 onwards.

The next step is to use the Layout tab to align the models (the Trees) as required. Save the model definition.

Import sequence data

Create a new music sequence, add timing tracks and add the models you have defined to the sequencer tab.

Using the Import, Import Effects menu, change the ‘Import file’ file to LOR Music Sequence - LMS, navigate to where the LOR LMS file is and select the file to Import.

On the Map Channels dialog, all the xLights models will appear on the left hand side and all the LOR Channels on the right side.

Do not select the Map by Strand/CCR option in this case.

Highlight the 'Map To' Cell – in line with the model name. Double Click the LOR model name (as identified by the labels in LOR) in the right 'Available' list. You can also drag and drop channels from the 'Available' list to the 'Map To' column. Repeat this for all the channels.

When Done, Save the mapping first, so that you can re-use it later.

Click OK to start the process.

Double Click the model name and then double click the stand name to see the effects on the nodes.

Click on the Render All icon and play the sequence.

If you were importing data from a Singing face where your model has multiple channels, then you need to double click in the Channel column, but against the node row instead.

The Convert tab has an option to ‘convert a LOR sequence file with a ‘Show verbose Channel map’ setting that will provide details of the LOR to xLights channel mappings . You can simulate a conversion and review the mapping details first.

Instead of using the Import tab to import the data as an editable effect, you can also import the data as a Data Layer. The process is much more efficient, however you cannot directly edit the data after your have imported it. That option has also been described in this chapter.

Common Scenarios

Scenario 1

A user is still using LOR for 8 controllers this year. How should he set them up ? Should he run it in DMX if the controller support DMX?

The general rule is that you can do 96 channels of LOR with xLights if the LOR controllers are in LOR mode. In this case, put the LOR controllers in DMX mode and then xLights can do it all. The user can can import all the LOR sequences, schedule them play them, edit them, etc.

Scenario 2

A user has an E682 and an E6804 running pixels and 2 CMB16 and 1 CMB24 controllers. How should they be configured and connected ? Is a cross over cable required?

Plug in the USB, same com port that would be used, if running it from LOR. No crossover cable is required if running from a LOR network. On the setup screen, add LOR channels via USB device. Put in at least 48 channels. Set the com port as required. After the LOR USB row, add in universes of 510 for the E68x controllers.

Scenario 3

A user is using comm4 and the USB to ethernet dongle. How should they be configured?

Network Type – LOR, Port – COM4, Baud rate – 57600, Num channels (160 as example).

Note: Baud Rate of 250000 is for DMX only.

Scenario 4

A user is setup is a mixture of LOR and DMX Channels i.e. intermixed LOR -DMX-LOR-DMX.

LOR Controller 1, LOR Controller 2, LOR Controller 3, DMX Universe 1 ch. 1-126,

LOR Controller 4, LOR Controller 5, DMX Universe 1 ch. 127-183.

How should this be configured?

Option 1

Use Universe 1 for all the LOR and DMX channels.

Since the DMX is already set (channels 1-183), add an LOR entry with Universe 1 starting at 184 until the last channel for controller #5 (16 x 5 = 90), for a total of 274 total channels. You can 'reserve' additional channels should you need them later upto 510/512.

Option 2

Keep it simple with DMX - Universe 1, LOR - Universe 2 and then start with Universe 3 with the RGB controllers.

All the channels in LOR must be mapped exactly including blank ones in between. Setup your AC LOR channels first in XL4 and then start with your first prop in the same order as your LOR sequences. Otherwise the convert process will indicate that channels are unmapped.

LMS to xLights XML via Import Effects is done via model mapping so channel numbers don't matter. However, if using the LMS to xLights via Data Layer import option, channel numbers need to match models between LMS and xLights configurations.

When importing timing grids, xLights searches the LMS file for a section called <timingGrids> which needs to contain a subsection called <timingGrid> which must contain an attribute called "type=freeform". So, in case you can't import a LOR timing grid, you can open your LMS file in any editor that can view XML in a nice format like, Notepad++, and search for some of those terms to see why your timing grids aren't found inside the file.

Last updated