DMX Universe Strangeness

The road house on campus is exactly like that and they run an Eos. Pretty sure they just patch in absolute numbers rather than universe numbers. This particular house uses net2 nodes outputting to Sensor dimmers using DMX, so the universe numbers are predefined by the node.

If you use lightwright and you use the x/y (x=universe, y=address) format for your paperwork, you can define what the numbers are for the universe in the program. Then, when you export and ASCII softpatch, it will only tell it the absolute numbers, not universe numbers. 

The road house on campus is exactly like that and they run an Eos. Pretty sure they just patch in absolute numbers rather than universe numbers. This particular house uses net2 nodes outputting to Sensor dimmers using DMX, so the universe numbers are predefined by the node.

If you use lightwright and you use the x/y (x=universe, y=address) format for your paperwork, you can define what the numbers are for the universe in the program. Then, when you export and ASCII softpatch, it will only tell it the absolute numbers, not universe numbers. 

I agree with Brian that I would simply patch the Eos as you would a normal system, letting the nodes and racks figure what to do with the DMX, which they are already doing.

But to get my head wrapped around this,  the only way I can these systems functioning with pure DMX runs to the racks, is for those racks that have dimmers configured to have addresses that are across 2 universes (512 & 513, 1024 &1025), is for the nodes to be sending 2 DMX cables to the A & B ports on the particular racks that span 2 universes.  The actual assigments of what slot listens to what address is then configured in the CEM. 

Unless there's another way to do this ? (outside of EDMX), and this is mostly a rhetorical question.

Steve B.

Brooklyn College