Mega Tree with 1804...
 
Notifications
Clear all

Mega Tree with 1804 pixel issues

19 Posts
3 Users
0 Reactions
4,882 Views
Posts: 8517
(@angus40)
Illustrious Member
Joined: 15 years ago

@ Rokkett

Holy Cow Batman , You wrota a novel reply .

I knew that some how the config > 100 pixel physical connection had to be accounted for .

I would never have imagined how to do it in Vixen , but through this post I am clear on how to setup the e682 now

Cheers &
Thanks


Reply
rokkett
Posts: 441
(@rokkett)
Reputable Member
Joined: 17 years ago

Ok, so I just tried to do this in Vixen 3, but I immediately ran into the unicast requirement issue for pixel density per controller issue. Is there a way to do unicast with the Vixen 3 e131 controller? I may need to go back and see if we spread this out over all three controllers more evenly and see if that will allow us to do this.

Let's see, that's 28 strand over 3 controllers. Max multicast channels per controller is 7*510 = 3570. Currently, we are trying to put 1200 pixels on the first two controllers, so that's 3600 channels, which will not fit in a multicast only configuration. So one strand from the first two controllers would need to move to the third controller.

Let me do that math on that...

First e682:

First three groups configured for 3 strands, 100 pixels.
Fourth group configured for 2 strands, 100 pixels

Just assuming we are starting at Universe 1, This is your network socket configuration:

Socket 1 - Universe 1
Socket 2 - Universe 2
Socket 3 - Universe 3
Socket 5 - Universe 4
Socket 5 - Universe 5
Socket 6 - Universe 6
Socket 7 - Universe 7
Socket 8 - Universe 0 <-- not used
Socket 9 - Universe 0 <-- not used
Socket 10 - Universe 0 <-- not used
Socket 11 - Universe 0 <-- not used
Socket 12 - Universe 0 <-- not used

Group Start Address Configuration:

Group 1 - Universe 1, Channel 1 <-- Vixen start Channel 1, 300 pixels, consuming 900 DMX addresses
Group 2 - Universe 2, Channel 391 <-- Vixen start Channel 301, 300 pixels, consuming 900 DMX addresses
Group 3 - Universe 4, Channel 271 <-- Vixen start Channel 601, 300 pixels, consuming 900 DMX addresses
Group 4 - Universe 6, Channel 151 <-- Vixen start Channel 901, 200 pixels, consuming 600 DMX addresses

Second e682:

First three groups configured for 3 strands, 100 pixels.
Fourth group configured for 2 strands, 100 pixels

Socket 1 - Universe 7 <- Yes, really map this to both devices....
Socket 2 - Universe 8
Socket 3 - Universe 9
Socket 5 - Universe 10
Socket 5 - Universe 11
Socket 6 - Universe 12
Socket 7 - Universe 13
Socket 8 - Universe 0 <-- not used
Socket 9 - Universe 0 <-- not used
Socket 10 - Universe 0 <-- not used
Socket 11 - Universe 0 <-- not used
Socket 12 - Universe 0 <-- not used

Group Start Address Configuration:

Group 1 - Universe 7, Channel 241 <-- Vixen start Channel 1101, 300 pixels, consuming 900 DMX addresses
Group 2 - Universe 9, Channel 121 <-- Vixen start Channel 1401, 300 pixels, consuming 900 DMX addresses
Group 3 - Universe 11, Channel 1 <-- Vixen start Channel 1701, 300 pixels, consuming 900 DMX addresses
Group 4 - Universe 12, Channel 391 <-- Vixen start Channel 2001, 200 pixels, consuming 600 DMX addresses

Third e682:

Just use the first three groups, configured for 2 strands, 100 pixels

Socket 1 - Universe 13 <- Yes, really map this to both devices....
Socket 2 - Universe 14
Socket 3 - Universe 15
Socket 5 - Universe 16
Socket 5 - Universe 17
Socket 6 - Universe 0 <-- not used
Socket 7 - Universe 0 <-- not used
Socket 8 - Universe 0 <-- not used
Socket 9 - Universe 0 <-- not used
Socket 10 - Universe 0 <-- not used
Socket 11 - Universe 0 <-- not used
Socket 12 - Universe 0 <-- not used

Group Start Address Configuration:

Group 1 - Universe 13, Channel 481 <-- Vixen start Channel 2201, 200 pixels, consuming 600 DMX addresses
Group 2 - Universe 15, Channel 61 <-- Vixen start Channel 2401, 200 pixels, consuming 600 DMX addresses
Group 3 - Universe 16, Channel 151 <-- Vixen start Channel 2601, 200 pixels, consuming 600 DMX addresses
Group 4 <-- not used



The third group will have an end address of universe 17, channel 240, for a total of 16*510+240 = 8400. Which is equal to the 28 *100 *3, or 8400, channels we needed and we squeezed into a multicast addressable space on the e682.

Whew. Who said we would never use math after high school...? 🙂

Here is the vixen 3 config, which should not need to change. See attached images...

Vixen 3 e131 config 1 9
Vixen 3 e131 config 10 17

Extra credit time, who can come up with the configuration that would just require moving two cables, instead of the massive shift every port by one or two positions solution I just did? That would be the smartest thing to do, if the display was already all set up and plugged up....


Reply
rokkett
Posts: 441
(@rokkett)
Reputable Member
Joined: 17 years ago

The solution to the "we only want to move two cables" puzzler is:

First e682:

First three groups configured for 3 strands, 100 pixels.
Fourth group configured for 2 strands, 100 pixels

Just assuming we are starting at Universe 1, This is your network socket configuration:

Socket 1 - Universe 1
Socket 2 - Universe 2
Socket 3 - Universe 3
Socket 5 - Universe 4
Socket 5 - Universe 5
Socket 6 - Universe 6
Socket 7 - Universe 7
Socket 8 - Universe 0 <-- not used
Socket 9 - Universe 0 <-- not used
Socket 10 - Universe 0 <-- not used
Socket 11 - Universe 0 <-- not used
Socket 12 - Universe 0 <-- not used

Group Start Address Configuration:

Group 1 - Universe 1, Channel 1 <-- Vixen start Channel 1, 300 pixels, consuming 900 DMX addresses
Group 2 - Universe 2, Channel 391 <-- Vixen start Channel 301, 300 pixels, consuming 900 DMX addresses
Group 3 - Universe 4, Channel 271 <-- Vixen start Channel 601, 300 pixels, consuming 900 DMX addresses
Group 4 - Universe 6, Channel 151 <-- Vixen start Channel 901, 200 pixels, consuming 600 DMX addresses

Second e682:

First three groups configured for 3 strands, 100 pixels.
Fourth group configured for 2 strands, 100 pixels

Socket 1 - Universe 8
Socket 2 - Universe 9
Socket 3 - Universe 10
Socket 5 - Universe 11
Socket 5 - Universe 12
Socket 6 - Universe 13
Socket 7 - Universe 14
Socket 8 - Universe 0 <-- not used
Socket 9 - Universe 0 <-- not used
Socket 10 - Universe 0 <-- not used
Socket 11 - Universe 0 <-- not used
Socket 12 - Universe 0 <-- not used

Group Start Address Configuration:

Group 1 - Universe 8, Channel 31 <-- Vixen start Channel 1201, 300 pixels, consuming 900 DMX addresses
Group 2 - Universe 9, Channel 421 <-- Vixen start Channel 1501, 300 pixels, consuming 900 DMX addresses
Group 3 - Universe 11, Channel 301 <-- Vixen start Channel 1801, 300 pixels, consuming 900 DMX addresses
Group 4 - Universe 13, Channel 181 <-- Vixen start Channel 2101, 200 pixels, consuming 600 DMX addresses

Third e682:

Just use the first two groups, configured for 2 strands, 100 pixels
The last two groups are configured for 1 (one) 100 pixel strand each

Socket 1 - Universe 15
Socket 2 - Universe 16
Socket 3 - Universe 17
Socket 4 - Universe 7
Socket 5 - Universe 13
Socket 6 - Universe 0 <-- not used
Socket 7 - Universe 0 <-- not used
Socket 8 - Universe 0 <-- not used
Socket 9 - Universe 0 <-- not used
Socket 10 - Universe 0 <-- not used
Socket 11 - Universe 0 <-- not used
Socket 12 - Universe 0 <-- not used

Group Start Address Configuration:

Group 1 - Universe 15, Channel 61 <-- Vixen start Channel 2401, 200 pixels, consuming 600 DMX addresses
Group 2 - Universe 16, Channel 151 <-- Vixen start Channel 2601, 200 pixels, consuming 600 DMX addresses
Group 3 - Universe 7, Channel 241 <-- Vixen start Channel 1101, 100 pixels, consuming 300 DMX addresses
Group 4 - Universe 13, Channel 481 <-- Vixen start Channel 2201, 100 pixels, consuming 300 DMX addresses

And pull the cable from controller 1, 4-3 and plug it into controller 3, 3-1.
Also pull the cable from controller 2, 4-3 and plug it into controller 3, 4-1.

Math. Who knew it would come in handy....? 🙂


Reply
james70818
Posts: 2045
Topic starter
(@james70818)
Noble Member
Joined: 19 years ago

Thanks Rokkett. I will make the changes tomorrow and see what happens. Well actually it looks like the weather will cooperate tomorrow so I should have my tree up and running! and can test on it.

James


Reply
rokkett
Posts: 441
(@rokkett)
Reputable Member
Joined: 17 years ago

James,

I was just shown how to do the unicast configuration in Vixen 3 - Right Click on the Destination option and enter the IP address of the controller. If you configure the unicast in vixen, then my first answer is the easiest choice, because would not need to move any wires...

...sorry for making it harder than it should have been....

🙁

In Vixen, you would need to send universes 8 and 15 to two devices, sample configuration images:

Vixen 3 e131 config 1 9
Vixen 3 e131 config 10 17

Reply
Page 3 / 4
Share: