I was helping work on a buddy's megatree tonight and can't figure out why it is doing this. Test patterns look great from #1 to 25. During a sequence, any sequence it just doesn't work right.
In this image the sequence was an effect with Vixen 3.
I cannot get all of the strings to work with a sequence but do in the test. See how the strings stop on a transition from white to blue and only one blue pixel is there?
So this tree is 28 strings of 100 pixels, 12v power is only injected at the bottom. Vixen is setup as each string is a universe with 12 strings per e682. Now in the e682 I had to tweak the pixel counts to make the universes work. Outputs 1-1 to 1-4 are configured with 4 outputs, 170 pixels per output to make the universes work out. If I make it 100 pixels it only uses 3 universes. On outputs 2-1 to 2-4 I only use 2 outputs, and they are 100 pixels each and the universes work out. Outputs 3 and 4 are the same as 1 and 2 with the exception on it using 150 pixels instead of 170 on the output 3's. So maybe that config is the issue. The e682's are running firmware 4.026.
Any thoughts would be great, especially since my MT is very similar to this one.
James
you have 2800 pixels , with 12 universes available on 1 x e682 using unicast ,that is 2040 pixels max
4080 max capacity for 2x e682 . 2800/32 = 90 pixels per < which exceeds the 510 limit you will need to be creative in your wiring ?
The tree uses a total of 3 e682's. Two of them drive 12 strings/universes and the third drives 4, sorry about that.
James
Is there a physical connection to 170 pixels on 1-1 ? Your issue may be assigning pixels that are not connected to the output ?
angus40 wrote:Is there a physical connection to 170 pixels on 1-1 ? Your issue may be assigning pixels that are not connected to the output ?
No, each output is a single universe with a 100 pixel string connected to it.
my last question cluster 1-1 to 1-4 what is the # of strings setting for each ?
angus40 wrote:my last question cluster 1-1 to 1-4 what is the # of strings setting for each ?
Not sure what you are asking, I don't see a "String setting"
But Here is what I have:
Outputs - 1-1 to 1-4
Outputs In Use - 4
Output Type- 1804/2811
Length Pixels- 170
Group Size- 1
Color Order- RGB
Start Address Universe - 11
Start Address Channel- 1
James
Ah I see what I am missing , the new firmware settings are a bit different .
The reason I have asked these questions is to get a better understanding of this before I update my own e682's .
I am stumped at the whole issue of 16 outputs having 12 universe ability and assigning 4 universes to 1 socket .
It would make some sense if each socket was divisible x 3 .
I hope you resolve this .
Best of luck .
If you have 28, 100 pixels strands, you will need to configure the groupings on the e682 to allow for 28 ports to plug in each strand. I think you already physically has this, now we just need to get the logical Vixen channel to physical pixel mappings correct. Each of the the output ports should be configured to support 100 pixels. If you configure the groupings to group to support more than 100 pixels, that is fine, but you need to leave these gaps where the logical addresses do not match up with physical pixels in your Vixen configuration, i.e - the channel to e131 address mappings. Where the sequence of strands cross over between the e682 groups, sure, you could overlap the universes and make a one up addressing mapping happen, but within the group, this will not happen unless you make the pixel counts match the physical pixel count.
Here is what I would do, assuming your three e682 controllers with 12/12/4 strands configuration:
(Because you are trying to address 8 universes on the first and second two e682s, you will need to use unicast, as the multicast configs will only allow for 7 universes to be addressed per device.)
First e682:
All four groups configured for 3 strands, 100 pixels.
Just assuming we are starting at Universe 1, This is your network socket configuration:
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 8
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 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, 300 pixels, consuming 900 DMX addresses
Second e682:
All four groups configured for 3 strands, 100 pixels.
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 15
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 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, 300 pixels, consuming 900 DMX addresses
Third e682:
Just use the first two groups, configured for 2 strands, 100 pixels
Socket 2 - Universe 16
Socket 3 - Universe 17
Socket 5 - Universe 0 <-- not used
Socket 5 - Universe 0 <-- not used
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 2 - Universe 16, Channel 151 <-- Vixen start Channel 2601, 200 pixels, consuming 600 DMX addresses
Group 3 <-- not used
Group 4 <-- not used
So now in Vixen, I should have 2800 pixels (8400 channels) defined, starting with universe 1, channel 1 and mapping each channel one address up in the e131 namespace, remembering not to use the e131 channels 511 and 512, which the e368 will ignore and not map to outputs.
Just adjust the numbers as needed if your start universe is not 1, channel 1.
Whew! Confusing enough?
I think this is around here other places, but here is an spreadsheet formula to calculate the starting e131 starting address of a RGB pixel. It assumes that you are starting your addressing at universe1, channel 1.
Paste this formula in any cell except for A1, and enter the pixel node number in A1. The input is the pixel node number, not the raw channel number:
=CONCATENATE("Universe: ", QUOTIENT(A1*3-1,510) + 1, " Address: ", MOD(A1*3-2,510))
Some sample answers:
Pixel Node Number Starting Address
1 ----------------->Universe: 1 Address: 1
85 ---------------->Universe: 1 Address: 253
170 --------------->Universe: 1 Address: 508
171 --------------->Universe: 2 Address: 1
1234567 ---------->Universe: 7263 Address: 79
Funny story, I actually stumbled onto the 85 pixel length string being exactly one-half of a universe by accident. I measured the length strand I physically needed, which turned out to be 85 pixels. Later, when I went to program the controller, I realized that was a very easy pixel length to use to calculate the next starting address....

