I had a problem yesterday, while doing some testing, where my lights were no longer being controlled after unpatching and repatching. Something went haywire.
So, I decided to just create another controller instance and repatch everything. I kept getting a Vixen error that said a "universe was already assigned to another controller" and wouldn't let me use it again and instructed me to pick another. Why?
Why would that be a problem, since multiple controllers can have the same universe, so I've been told. Which is actually a way to have one program running two different elements, on different boards, by assigning them the same universe.
Was that must so glitch or is it a fact that Vixen can't have 2 or 3 controllers that use the same universe number?
And if it is a normal error BUT boards can actually have the same universe, what is the workaround? I guess one way would be to just not define the duplicate.
Thanks.
I thought it was that you could define a universe multiple times on a single controller... which I did when I first got started.
Roger
When you created the new instance did you delete the old one? I had that issue once and closed out the setup and went back in and it worked. I have 2 E6804's and to avoid any conflicts or confusion I use different universes.
Sent from my Nexus 7 using Tapatalk
The warning is there to promote proper network design. The reality is that there's a lot of hardware in common use that doesn't completely follow the standards and we can't predict the behavior. So we promote the best practice.
The sACN standard requires that each unique set of channel data be its own unique universe. So even if you're using unicast, you should be using different universes for each destination unless of course you are sending the same universe(containing the same data) to both destinations. There's many devices out there with very simple Ethernet stacks that simply check universe number to verify the data stream. That's especially true in the DIY community where we're always trying to use the cheapest and simplest hardware to get the job done. There are multiple ways that a device can get data that you think should be going elsewhere. And if there's more than one set of data using the same universe number it becomes ambiguous.
Some people around here will say that you can reuse universe numbers for each controller if you're using unicast. In theory that will work in many cases. But not in all cases. So we disallow it (as per the spec)
After deleting a controller or even just a universe on a controller, you may need to exit display setup and come back in it for it to be available for reuse.
--Jon Chuchla--
Sent from my iPhone using Tapatalk
Jon, you taught me well 🙂
Sent from my Nexus 7 using Tapatalk
