That sounds very good.
Don't get me wrong, I think xlights is absolutely wonderful. It could easily be I'm doing something wrong here.
I noticed in xlights, the single network mode uses this formula:
xlights channel# = ((LOR_Unit_# - 1) * 16) + LOR_circuit_number
....
In the Multi-Network mode is seems to allow multiple networks to be mapped ... but again, I think the problem seems to be that Aux A= second xlights network, but 1-512 don't translate to 513-1024 for pixelnet.
The problem I had for mult-network mode was that I could assign the same come port more than one, so this might have worked for multiple DMX dongles, but when using a pixelnet flashed dongle, I'm thinking it has to be all 4096 channels assigned right there? ... and then translates into correct PN ch# by xlights??
It seems that for pixelnet, you could use networks for each pixelnet universe and multiply by (network-1) * 4096 ... so for regular network, add zero, for Aux 1 network, (pixelnet Univ#2), add 4096.
And then perhaps use unit# as the dmx multiplier (for PN sub universes (1->
).
So pixelnet ch# = ((network#-1)*4096) + ((unit#-1)*512) + circuit# ... and you could roughly translate as follows:
LOR Network Name: network#
----------------------- ------------
Regular 1
Aux A 2
Aux B 3
Aux C 4
Aux D 5
Aux E 6
Aux F 7
Aux F 8
or for DMX types from LOR S3
Universe 1 1
Universe 2 2
...
Universe 8 8
I'm just thinking that maybe this hasn't been used with pixelnet over 512 channels yet??