New to QLC+, Issue communicating to universe 2. I have a service tomorrow, please help!!
Posted: Sat Dec 19, 2015 7:05 pm
So, I've been using QLC for a few months now with now issues. Last week, our HDD crashed, and I had to re-install Windows. Now, no matter what I do, I cannot communicate to Universe 2.
My setup is:
two eDMX1s, one for each universe. Universe 1 is using ArtNet 0, IP address 192.168.0.80. Universe 2 is using ArtNet 1, IP address 192.168.0.90. The computer is IP address 192.168.0.100.
We have 4 dimmer packs with generic par cans for universe 1. For Universe 2, we have 4 Chauvet SlimPar 56's, and 4 American DJ LED megabar 50 LEDs.
Troubleshooting I've tried:
- reset the DMX nodes.
- Switched the IP addresses on the nodes
- Switched which nodes were on universes 1 and 2
- Switched which fixtures went to each universe
- Ran all fixtures on Universe 1
- Ran all fixtures on Universe 2
Every test I run results in the same thing. I can talk to whichever node is Universe 1, no matter what fixture I'm talking to, but I cannot talk to Universe 2, no matter what fixture I'm talking to. I'm at a loss as to how to fix this, and I have a service to run tomorrow at 10:30 AM.
Thank you in advance!!!
My setup is:
two eDMX1s, one for each universe. Universe 1 is using ArtNet 0, IP address 192.168.0.80. Universe 2 is using ArtNet 1, IP address 192.168.0.90. The computer is IP address 192.168.0.100.
We have 4 dimmer packs with generic par cans for universe 1. For Universe 2, we have 4 Chauvet SlimPar 56's, and 4 American DJ LED megabar 50 LEDs.
Troubleshooting I've tried:
- reset the DMX nodes.
- Switched the IP addresses on the nodes
- Switched which nodes were on universes 1 and 2
- Switched which fixtures went to each universe
- Ran all fixtures on Universe 1
- Ran all fixtures on Universe 2
Every test I run results in the same thing. I can talk to whichever node is Universe 1, no matter what fixture I'm talking to, but I cannot talk to Universe 2, no matter what fixture I'm talking to. I'm at a loss as to how to fix this, and I have a service to run tomorrow at 10:30 AM.
Thank you in advance!!!