Does 3 e682 allow 3...
 
Notifications
Clear all

Does 3 e682 allow 3 x 2040 pixels?

26 Posts
9 Users
0 Reactions
7,756 Views
Posts: 3735
(@algerdes)
Famed Member
Joined: 15 years ago

No. The E682 (and most other controllers) does not lock you into universes 1 through 7. You set the universes you want that particular controller it to react to.

For example, with the 3 controllers that you have (according to this thread) and in multicast mode, you could choose universes 1 through 7 for controller A, universes 991 through 997 for controller B, and even mix up universes for controller C - say 86, 87, 88, 204, 207, 208, 209.

You can do the same thing under unicast (with more universes available), but you have to tell your show player what universes are on what controller. It takes longer to setup, but has its advantages.

One thing you can do with multicast that is not easy with unicast is use the same universes on two different controllers. Say you wanted two props to act the same way at all times. Simply set their universe on two (or more) multicast controllers and use the same channel range. Both props will react since they are watching all traffic and see the instructions to do something on that universe and those channels.

This does not work on unicast because the controllers are only listening for their particular activity stream for their particular IP address, and not the entire "broadcast".

In knowing this, you probably see that there are choices to be made. I prefer unicast because I have many receiving "controllers" and want direct communications between my show player(s) [FPPs - Falcon Players] and not have my controllers listen to a lot of things that don't belong to their job. There are many here that prefer the simplicity of multicast. A choice to be sure.


Reply
Posts: 3735
(@algerdes)
Famed Member
Joined: 15 years ago

Two things to be aware of that I didn't mention in the last post.

1) Some of the programs use a contiguous channel list to do their outputing. The DMX separations are not apparent. This is extremely easy to get confused with assignment of player to controller assignments. They are two different yet related items. I'll not get into it here, but refer you to the wiki entries on the different sites. LOTS of good information in all of them.

2) There are other types of universes. One that comes to mind is Pixelnet. It uses the equivalent of several DMX Universes to make 1 PN Universe.

As you are trying to figure this stuff out, knowledge of the existence of other standards can be quite helpful when you run across discussions that don't make sense on the surface. They all work to do the same thing. Make lights go on and off.

Happy Blinking!


Reply
Posts: 3735
(@algerdes)
Famed Member
Joined: 15 years ago

Please forgive my additional post, but I can see where your confusion may be coming from.

In the explanation for "multicast" in the wiki it states that all controllers would be sent information at the same IP. What is meant by this is there are specific IP addresses within each IP subnet that are considered "all-call" and everyone listens to it in addition to their own address. Multicast takes advantage of this "everyone listen to me" channel. One send, everyone hears it, everyone does whatever their firmware says to do with it.

Note that each Ethernet device listens to BOTH the "all-call" IP and their unique IP.


Reply
AuburnLights
Posts: 213
(@auburnlights)
Estimable Member
Joined: 12 years ago
MikeSD wrote:Thanks for the explanation. But being a bonehead, I still have a question.

First, I found this description for e1.31. And in it and in this thread, it suggests that multicast sends all info to every controller (i.e. to all 3 e682 boards in my example).

Exactly, multicast sends all packets to all devices on your network (wired or wireless). The device then has to interpret each packet to determine if any data in that packet was meant for it. So this is where your Universe numbers and channel numbering come into play. If the packet contains universes and channels that have been configured on that controller it will then execute those commands (turn on/off those lights, dim them, whatever). This is why some of the responses to your original question are pointing out that the larger your show (more universes and more channels) the less multicast is recommended. The reason being that every packet sent out has to be interpreted by every controller on your network (actually every device, but I digress). This can swamp a controller eventually as it has to process so many packets that may not have any commands that it needs to actually perform.

MikeSD wrote: So, if each board used universe 1 through 7, but had different IP, would any packet for universe 1 (for instance) turn on those lights on all 3 boards, or can lights on each board be controlled independently of the other boards. I'm thinking universe 1 lights would all be turned on at the same time, even if on 3 different boards (i.e. not independent of each other). That is a full universe 1 on board 1 and a full universe 1 on board 2 would come on at the same time. Right or wrong?

Right, a multicast packet that has commands to turn on channels 1-9 on Universe 1 would turn on the first 3 pixels (remember, each RGB Pixel takes 3 DMX channels) on all multicast controllers on you network that have Universe 1 Channels 1-9 configured.

MikeSD wrote:Update: I'm going to leave my questions above but I have another DUH! Question.

I've been assuming that the e682 controller uses channels 1-7 for Multicast. But is it specifically 1 to 7 or can they be any numbers. Can I have one controller with multicast and universes 1 to 7 and the 2nd controller in multicast with universes 8 to 14 and the third in multicast with 15 to 21? Or will all three be limited specifically to universes 1 to 7?

The short answer is no, it doesn't require you to use universe 1-7 for Multicast on all controllers. The E682 Manual here states Valid universe numbers are 1‐63998

Remember, Multicast and Unicast are network standards, not something specific to DMX.

The advantage of Multicast is that you don't have to know what the IP Address is of the device you are sending the commands to, it just has to be connected to the same network. All devices receive that packet and interpret whether that packet was destined for them. In the case of lighting controllers using SACN (E1.31) whether they have Universes and channels that are referenced in the packet. I explained the cons above, lots of universes and channels can swamp lighting controllers on your network as they have to interpret every packet that is sent to determine if it should be executed.

The advantage of Unicast is that every device (Lighting Controller) has a specific IP address and packets are sent only to that Address. In that case it doesn't matter if universes on different controllers overlap, as they will only be addressed to one specific controller (although it can get confusing, especially when you are doing layout or sequencing, if you use the same universe numbers on different controllers even using Unicast. Do yourself a favor and use different universe numbers on each controller and use a spreadsheet so you know what elements are associated with which controller. Like every home improvement project, a little time spent on Prep will save a lot of time in the end.) If you want to use the same lighting sequence for elements on different controllers, just assign the same sequence commands to the elements and make sure they are patched to the correct controller in the setup. I am not sure what sequencer you plan on using, I use Vixen 3.2 and it's easy peasy to do this type of operation.

The disadvantage of Unicast is that you have to know the IP Address for every controller (or device), so you have to assign Static IP Address and not use DCHP (otherwise the device IP Address can change and you will have no Blinky Flashy). If I am not mistaken, Sandevices requires all E682s to have a Static IP address anyway, regardless of whether you are doing Unicast or Multicast.

I hope that helps


Reply
Posts: 82
Topic starter
(@mikesd)
Estimable Member
Joined: 12 years ago

It's beginning to make sense now. I'll have to look tonight but I think in Vixen, when I specify Multicast for my controller type, I can or should be able to also select select the IP for the controller and map up my RGB elements to specific controller by IP. Currently, I just have one controller at the default IP and it just says Multicast. But somewhere I'm sure I get to specify the IP to select a particular controller, by IP.

Now, the question of unicast vs multicast (actual wiring).

I have a PC (PI computer), with a single Ethernet port. I planned to run that to a hub (switch) and then run 3 individual cables from hub to e682 controller. Can that still be multicast, or does that force me to unicast?

If the latter, what does the physical wiring example look like for multicast. The graphic in the wiki doesn't explain that specifically. It only explains it logically.


Reply
budude
Posts: 10400
(@budude)
Illustrious Member
Joined: 18 years ago
AuburnLights wrote:
The disadvantage of Unicast is that you have to know the IP Address for every controller (or device), so you have to assign Static IP Address and not use DCHP (otherwise the device IP Address can change and you will have no Blinky Flashy). If I am not mistaken, Sandevices requires all E682s to have a Static IP address anyway, regardless of whether you are doing Unicast or Multicast.

I hope that helps

I've seen this mentioned multiple times as a 'disadvantage' but when you have a half dozen or more controllers you *want* to know the IP of it so that you can configure it. Depending on DHCP or Automatic Private IPs (the 169.x address) is really not a good way to go for management purposes whether you use multicast or unicast it's good to know how to reach a particular controller at any time. You should set the static IP on every controller if you can - yes - it can work without it but I'd hardly call that a good practice...


Reply
Posts: 3735
(@algerdes)
Famed Member
Joined: 15 years ago
MikeSD wrote:Now, the question of unicast vs multicast (actual wiring).I have a PC (PI computer), with a single Ethernet port. I planned to run that to a hub (switch) and then run 3 individual cables from hub to e682 controller. Can that still be multicast, or does that force me to unicast?

It can be either one. Multicast and Unicast have nothing to do with the wiring. They are at the communications level.

MikeSD wrote:
If the latter, what does the physical wiring example look like for multicast. The graphic in the wiki doesn't explain that specifically. It only explains it logically.

The diagram that was shown (entry #8) is a great example of the logical connections involved when you use the different methods. Not wiring.
The wiring of the Ethernet side of any light system is the same as any other Ethernet setup. Each device connects to others through a switch (or older hubs), or several switches.


Reply
Posts: 82
Topic starter
(@mikesd)
Estimable Member
Joined: 12 years ago

Ok, I think I have it now. 😉 I was reading the wiki and it gave an example. Each controller has a unique IP but that's for configuration, with multicast. But in unicast, the data is sent to it also.

In multicast, it's sent to something like: 239.255.0.1 where 1 is universe 1. 239.255. seem to be what is for multicast. Is it always 239.255 for the first two?, for multicast?

So, if I have this right, I can have three e682, set to unique IP, for configuration purposes. If everything is configured for multicast, then the data goes to specific 239.255.x.y based on what universes I use, for each board. If two board have the same universe specified, those elements would behave the same. If different, then they would be controlled independently.


Reply
AuburnLights
Posts: 213
(@auburnlights)
Estimable Member
Joined: 12 years ago
budude wrote:I've seen this mentioned multiple times as a 'disadvantage' but when you have a half dozen or more controllers you *want* to know the IP of it so that you can configure it. Depending on DHCP or Automatic Private IPs (the 169.x address) is really not a good way to go for management purposes whether you use multicast or unicast it's good to know how to reach a particular controller at any time. You should set the static IP on every controller if you can - yes - it can work without it but I'd hardly call that a good practice...

I completely agree with you. I just wanted to lay out the pros and cons of each type of networking option, I wasn't making a recommendation. Personally, I use Unicast with Static IP addresses. It just makes everything much easier to understand, visualize and troubleshoot.


Reply
dpitts
Posts: 1020
(@dpitts)
Noble Member
Joined: 16 years ago

Wrong thread


Reply
Page 2 / 3
Share: