DMX Addressing Higher than 128
Posted: Tue Jun 09, 2020 4:22 pm
Good morning, I am having an issue setting up my lights with more than 128 addresses. Of course, I'm expecting a maximum per universe of 512. I am using a single "ENTTEC Open DMX USB" (https://www.amazon.ca/ENTTEC-Open-DMX-USB/dp/B00O9RY664) interface and I have it configured in QLC as a "DMX USB" Output device using the only mode that does anything, "Open TX".
The behavior I'm seeing when I use the Simple Desk is that attempting to control lights that are addressed at channel 128 or above does nothing, instead, they appear to respond to signals to their address minus 128. So if I turn on channel 128 nothing happens (presumably because there is no channel 0). If I turn on channel 129, the light at address 1 turns red (they are all RGB LED lights). This is consistent with everything above 128.
I initially thought it was the controller, but I tried two other models of controller and they all exhibit the same behavior. I am using a 5-pin to 3-pin adapter then XLR cable until the controllers. I have also attempted this with several other DMX lighting control programs, but they all show the same issue. Is there potentially a driver issue here?
Any help would be greatly appreciated. My only next option would be to buy a second controller.
Thanks,
Ben
The behavior I'm seeing when I use the Simple Desk is that attempting to control lights that are addressed at channel 128 or above does nothing, instead, they appear to respond to signals to their address minus 128. So if I turn on channel 128 nothing happens (presumably because there is no channel 0). If I turn on channel 129, the light at address 1 turns red (they are all RGB LED lights). This is consistent with everything above 128.
I initially thought it was the controller, but I tried two other models of controller and they all exhibit the same behavior. I am using a 5-pin to 3-pin adapter then XLR cable until the controllers. I have also attempted this with several other DMX lighting control programs, but they all show the same issue. Is there potentially a driver issue here?
Any help would be greatly appreciated. My only next option would be to buy a second controller.
Thanks,
Ben