Multiple Bridge Con...
 
Notifications
Clear all

Multiple Bridge Configuration

7 Posts
5 Users
0 Reactions
1,919 Views
mikeh65
Posts: 794
Topic starter
(@mikeh65)
Prominent Member
Joined: 19 years ago
[#43250]

A couple of things I'm not sure of for my setup this year. I have added a second E1.31 bridge to my show. I will be using a total of nine ports, 4 on one bridge and 5 on the other. Each bridge will have one Renard output and the rest are DMX/Pixel. I am using Vixen 3 from a computer to run the show. Vixen has been set up to have two outputs, each E1.31 controllers. They have been configured with two separate IP address and outputs mapped to each. My question comes down to Universes and numbering. Bridge 206 will have four ports used, one universe to each port. The same for bridge 207, five ports, one universe assigned to each port. If I number the first bridge 1,2,3,4 do I number the second as 1,2,3,4,5 or 5,6,7,8,9? Also, where does the numbering need to happen? In Vixen, the bridge configuration, both, and do they need to match each other? i.e. 1 to 1, 2 to 2, and so on? Does anyone out there have more than one bridge config setup? Looking for some clarification as I move on to show setup.

Thanks.


6 Replies
mikeh65
Posts: 794
Topic starter
(@mikeh65)
Prominent Member
Joined: 19 years ago

Bump, seeing if anyone has an answer.


Reply
DrNeutron
Posts: 2016
(@drneutron)
Noble Member
Joined: 14 years ago

I don't use Vixen so I can't help with configuration from that standpoint.
As for Universe numbering, I would not have multiples of the same universe number as it will only confuse you as your show grows.
I use 2 bridges in my show and I keep things separate and have multiple universe numbers. I then keep things in a spreadsheet so I know at a glance how thing are supposed to be connected.
In theory you could have the same universe number since each bridge has its own IP on the network and the software will be told which IP the packets are destined but with a limit of somewhere around 64000 universes why re-use universe numbers. I have one output on my bridge just for a LOR controller that uses 16 channels all in one universe, nothing else on it.
As for your other question, the universe setting must be the same on the bridge as it would be in software otherwise packets would arrive at wrong destination.
One small point on using pixels with bridge....If you have over 170 on a single output the bridge will automatically span the universes, all you do is set starting universe/channel and bridge will show ending channel/universe. You don't have to think too hard on it, bridge does it for you.


Reply
mikeh65
Posts: 794
Topic starter
(@mikeh65)
Prominent Member
Joined: 19 years ago

So my thinking was not wrong either way, it's just a matter of keeping things straight. I think I will continue to count universes from one bridge to the other.
i.e. 1,2,3,4,5,6,7,8,9 And make sure I set my software to match. So far, I have not exceeded more than 170 pixels per port on either bridge. It just happened that's how the elements were built.

Thanks for the information and clarity Phil!


Reply
Wolfie
Posts: 2225
(@wolfie)
Noble Member
Joined: 11 years ago

The answer lies in your communications methods. You have two basic choices. Multicast and Unicast.

If you choose Multicast method of broadcasting show data, then NO you can't have the same universe on multiple bridges/IPs. Well, you can, but the same data will go both places. Not likely your intention. In a multicast system you need unique universe numbers across the whole network. Each device "subscribes" to the data it wishes to listen to. As the data is pumped onto the network, your switches route the data to the devices subsribed to that content. Therefore you should only have unique universes for each to subscribe to.

If you choose Unicast, your show player (either Vixen/xLights or FPP) sends show data to specific IP addresses. There isn't the subscription type scenario to contend with. So, yes, you can have Universe 1 on multiple devices with completely different data going to different props.

Personally I do not find it confusing having universe 1 on multiple devices. I ran Unicast last year playing my show in Vixen scheduler on my PC. I had 2 controllers and an DMX bridge. Each one having universe 1,2,3 etc. I didn't find it confusing at all. Mainly because you don't sequence on universes or ports or bridges. Not in Vixen. Not in xLights. You sequence on models. Once you set up your controllers and the mapping (vixen) or layout (xlights), you can totally forget what universe goes where because it doesn't freaking matter anymore. Not for sequencing anyway. You drop an effect on your tree. You put an effect on your arches. Neither sequencer gives a darn that both of them are on Universe 1 on different addresses and neither do you. At first, yes, it matters to you when configuring the software based on what you have (or plan to have) hooked up where.

I keep a small spiral notebook with all prop layouts (node counts), pigtail wiring diagrams, and controller port assignments (IP and universe/channel numbers). If everything crashes, my PC is wiped out. I still have my written notes and know where everything goes. I don't do spreadsheets. Some do. I just find it clutters up the process in my world. I can take the little book out into the yard and refer to it when I plug stuff in.

I named my controllers (in Vixen and xLights) using the last quad of its IP address. Armed with that info and whats in my little black book (no,not really black), I can find out what goes where. If I need to. But after I set up the controller and xLights for Halloween, all I needed to know is what prop plugs into what port. I couldn't tell you what channel number or universe my floods are on. I have no clue the universe my arches run on. The info it not pertinent to anything I do now. As long as xLights knows and my controller knows, the info is useless. I can find out simply looking at the controller page in my book or looking on the controller's string page (falcon). If I needed to know again for some reason.


Reply
Page 1 / 2
Share: