Simpler way to map LOR

[Jeffl]

I took a test drive playing with both a Lynx Express set at channel 1 and a LOR unit set to 11.  The Lynx Express worked as expected but the LOR unit was a bit more fun.

In my display I have about 32 LOR controllers and label all of them with decimal numbers, i.e 1-32 (it's easy even for technical people like me) and skip the hex values.  Network scans are also easy as you can scroll the list to see who missed roll call.

Where things got crazy is my LOR controller was set to 11.  So I setup XLights, clicked on xTester and tried to test controller 11, and nothing worked.

After playing a bit I set the controller ID to 0B and everything worked.

For DMX, xLights makes it very easy, 1-512 = 1-512.  For LOR, it seams difficult where OB (LOR) = 11 (xLights).

What are your thoughts?

[dowdybrown]

I'm thinking about having xTester require your exported LOR channel config for LOR networks. Then all of your LOR channels would be labelled with friendly names.

Would that work for you?

Matt

[Jeffl]

I think this would work.  This way you would see the channels you would expect.  The other way would be to populate the list with hex values from 01 - max specified by the network setup.

Either would work or maybe both.  Programming either way may be a challenge as counting in hex is confusing.

[memphislights]

Maybe this will help.

Code: You are not allowed to view links. Register or Login

LOR Start Channel LOR HEX DMX Start DMX End
1 01 1 16
2 02 17 32
3 03 33 48
4 04 49 64
5 05 65 80
6 06 81 96
7 07 97 112
8 08 113 128
9 09 129 144
10 0A 145 160
11 0B 161 176
12 0C 177 192
13 0D 193 208
14 0E 209 224
15 0F 225 240
16 10 241 256
17 11 257 272
18 12 273 288
19 13 289 304
20 14 305 320
21 15 321 336
22 16 337 352
23 17 353 368
24 18 369 384
25 19 385 400
26 1A 401 416
27 1B 417 432
28 1C 433 448
29 1D 449 464
30 1E 465 480
31 1F 481 496
32 20 497 512