Display or Controll...
 
Notifications
Clear all

Display or Controller Mapping Issue

11 Posts
6 Users
0 Reactions
4,174 Views
Posts: 83
Topic starter
(@tmarshal61)
Estimable Member
Joined: 13 years ago
[#33095]

Sorry for this really long post, but I want to get out all the information needed to help address this issue.

I am having a very difficult time getting my setup properly configured in Vixen. I am at a complete loss. Either I am doing something critically wrong or there is a serious bug in Vixen. If it is me, I, for the life of me, cannot figure out what I am doing wrong. Help!!!

My lights are not lighting up in the expected order or even in the expected place. The rightmost two 142px strings, (RoofLine4), is lighting up when I have the effect placed on the left most group RoofLine1. In addition, my effects seem to be starting at the first pixel of the left most string, (expected, if it were the right group), AND about the 28th pixel into the rightmost string, (not expected). This corresponds to about the 170th pixel on that controller output which, BTW corresponds to the 510th and last channel on Universe 5 as you will see below in the Vixen Controller configuration. My Floods are also lighting up when there are no effects on the elements corresponding to them.

To see exactly what I am talking about, here is a short video of the issue. In this example, I am using a simple chase sequence placed on the RoofLine1 Group. It is actually showing up on RoofLine3, (and my spot light channels). Notice also how it starts in two places at once. I also want to point out that in the Vixen Preview, everything shows up correctly. It is the real physical rendering that is not coming out correctly.

I have checked and double checked everything. I have even repeated my entire configuration three time and I always get the same results. If I duplicate my Controller configuration in XLights, everything works as expected.

Here is my setup. I have Vixen configured for 8 strings across my roof line. At this stage, I only have the two strings RoofLine4-1 and RoofLine4-2 installed but I have my controller and Vixen configured for all of them. Here is my Preview Setup with the controller output mapping shown in different colors where Green represents the roof line pixels I have physically installed and connected to output # 3 on my controller:

I am using a PixLite 16 controller running split bus 5V on side A, (outputs 1-8), for the pixels and 12 V on side B for the SpotLights. The PixLite 16 is configured like this:

The Vixen controller is configured like this:

Like I said, I had an identical configuration in XLights that worked correctly:

All of the stuff in green represents the RoofLine4 and Output # 3 that it is connected to. I have my controller Output #3 connected to the left side of RoofLine4-1 and the output of that goes into Roofline4-2 from the far left side.

Here is my test sequence. Notice the chase effect is placed on RoofLine 1 but the effects are showing up on RoofLine4 and my spot lights. There are no other effects on Roofline4 or any other element. The only effects are the chase effects shown below. If I put the effect on RoofLine 4, nothing happens. I don’t have RoofLines 1 through 3 hooked up yet so I can’t tell if they would be mixed up as well or not.

I would really appreciate any help anyone can provide. Or at least help confirm if it is a bug if it is not me.

Thanks,

Tom


10 Replies
Posts: 83
(@damo1271)
Estimable Member
Joined: 16 years ago

I could be way off with this, nor am I familiar with the pixlite, but I thought the universe numbers used in the controller needed to match the universe numbers set in Vixen. Again I may be wrong...


Reply
Posts: 83
Topic starter
(@tmarshal61)
Estimable Member
Joined: 13 years ago
damo1271 wrote:I could be way off with this, nor am I familiar with the pixlite, but I thought the universe numbers used in the controller needed to match the universe numbers set in Vixen. Again I may be wrong...

Actually, they do match. The PixLite 16 supports up to 340 pixels, or two Universes, per output. So For instance, Output 1 starts at Universe 1, Channel 1 and has 243 pixels. 243*3 = 729 channels which won't fit in one Universe so, the first 510 channels are from Universe 1 and the remaining 219 from Universe 2. This is exactly how I have the Vixen controller setup.

Thanks


Reply
Posts: 83
Topic starter
(@tmarshal61)
Estimable Member
Joined: 13 years ago

Original post edited to add that the Vixen preview shows up correctly. It is the only real physical output that is showing up incorrectly.


Reply
duramadmax
Posts: 904
(@duramadmax)
Noble Member
Joined: 16 years ago

I thought when using Unicast in vixen that the start channels for each universe could not all be one, they had to have total channel count added sequentially from previous universe..


Reply
adski
Posts: 164
(@adski)
Estimable Member
Joined: 15 years ago

Yes, the "starts" on the Vixen controller configuration should be:

1
511
730
1240
1630
2140
2482

Dave


Reply
Posts: 83
Topic starter
(@tmarshal61)
Estimable Member
Joined: 13 years ago
adski wrote:Yes, the "starts" on the Vixen controller configuration should be:

1
511
730
1240
1630
2140
2482

Dave

I'll give that a try. That was my original configuration, but I has some other weirdness going on that I was troubleshooting so, I changed it. Those issues ended up being due to moisture from the rain.

Thanks,
Tom


Reply
Elmo2resc
Posts: 265
(@elmo2resc)
Reputable Member
Joined: 19 years ago
adski wrote:Yes, the "starts" on the Vixen controller configuration should be:

1
511
730
1240
1630
2140
2482

Dave

I also was thinking that.


Reply
jchuchla
Posts: 8698
(@jchuchla)
Illustrious Member
Joined: 15 years ago

Yes. The start numbers should be different. The start column is where in the output controller that universe starts. With the config you have shown You're basically sending the same data to all of your universes. So whatever you have connected to your first 510 channels on the output controller module is what's going out (in varying sizes) to all of the universes you've defined. And nothing beyond the first 510 inputs is connected to any universe.

--Jon Chuchla--

Sent from my iPhone using Tapatalk


Reply
Posts: 83
Topic starter
(@tmarshal61)
Estimable Member
Joined: 13 years ago

You are all absolutely correct. That did it.

In the PixLight controller setup, the "Start Channel" is the starting channel within that universe. This made me think that "Start" in Vixen also meant the starting channel within the given universe. I did not understand that it was the starting number based on the cumulative channel count.

I wish there had been some documentation on this. I know I have seen something somewhere before, but for the life of me, I could not find anything when I needed it. When I get done with all of this, maybe I will write something up to help then next poor lost soul. Thanks for everyone's assistance.

Tom


Reply
Page 1 / 2
Share: