Jump to content
Light-O-Rama Forums

Recommended Posts

Im starting to plan for next year, I have one e682 and i am planning on adding another one. I want to change out the led's on my house with the ws2811 smart pixels but im not sure how far the pixels can be from the controller. Does anyone know the distance that the pixels can be from the controllers. Also what type of wire would I use to do this. Right now I believe im just using thin 22 gauge wire but the pixels are right next to the controller, does anyone have any suggestions.  

 thank you to anyone with any input

Edited by Steelers95

Share this post


Link to post
Share on other sites

The 2811s will generally do about 25 feet.  If you need longer than that, you can use null pixels.  Do some tests to see what works during the off-season.  If you're going very far or lots of pixels, I would use 18 or 16 gauge (I have both in stock).

Share this post


Link to post
Share on other sites

Go here and I have posted some results of my testing. There is a lot of useful information in the thread.

Quick answer, 25 ft not possible without changing the resistor packs. I can get 20ft then null, then 20 ft etc. but the resistor packs are easy to change.

http://forums.lightorama.com/index.php?/topic/32606-wire-type-does-matter/

Share this post


Link to post
Share on other sites

Thanks sax.  I remembered that thread, but could not make any real effort to find it on my phone....

 

Thanks for bringing it up...

Share this post


Link to post
Share on other sites

Alright thanks. I was also wondering how I would be able to max out a controller with 16 strings because each universe can only handle 170 pixels which means that I can really only use 12 strings if im using 50 count strings. would I need to cut each string down to 42 pixels? 

Share this post


Link to post
Share on other sites

Alright thanks. I was also wondering how I would be able to max out a controller with 16 strings because each universe can only handle 170 pixels which means that I can really only use 12 strings if im using 50 count strings. would I need to cut each string down to 42 pixels? 

 

Why would you need to cut them down to 42 pixels?

 

I have 12 strings of 72 on mine and will be adding more to it next year.

Edited by KStatefan

Share this post


Link to post
Share on other sites

If using the sandevice in unicast you can have up to 12 dmx universes. So 170 pixels per universe x 12= 2040 pixels.

Sorry have to edit the 6804 will do 12 universes. The e682 does 6. So you can still use 1020 pixels

Edited by Darryl Lambert

Share this post


Link to post
Share on other sites

If using the sandevice in unicast you can have up to 12 dmx universes. So 170 pixels per universe x 12= 2040 pixels.

Sorry have to edit the 6804 will do 12 universes. The e682 does 6. So you can still use 1020 pixels

 

The 682 will do 7 universes on multicast and 12 on unicast.

Share this post


Link to post
Share on other sites

If you put a string of lights on a sans connector, it does the max number of pixels you program for it. For example, if I put 50 lights on it it will be channels 1-150 of whatever universe I programmed. If I put another light on that string, I would have to program for 51 pixels. Now, if I put so many that the universe needs to change, the sans will do that. So pixel 171 would be the next universe channels 1,2,3. It knows that 2 channels needs to be skipped too. (Since RGB requires 3 channels per pixel and in the dmx universe of 512 max channels there are 2 extra channels, the sans cuts this off so there are no oddball channels)

The way this works is you just program the starting universe, starting channel and number of pixels and the sans assigns them properly. So it doesn't have to be channels 1-150 in my above example.

I personally like to have each element it's own universe. I am lucky not to have so many pixels per element I guess. Anyway, I have 2 50 pixel strips on my roof. To keep them separated, I tell the sans that each connector is 170 pixels even though they are only 50 so my next channel will be a new universe. Yes, there are wasted pixels or channels, but I don't need them.

This is just another way the sans works.

The manuals are free downloads. It has a wealth of information of course.

Share this post


Link to post
Share on other sites

The 682 will do 7 universes on multicast and 12 on unicast.

I thought that was the case but I checked the e682 product Page & it's states 6. That's why I edited my original post. I think KsStatefan is correct & Jim hasn't changed the page to reflect the added capacity. Sorry for the confusion. Edited by Darryl Lambert

Share this post


Link to post
Share on other sites

I just purchased a 682 for my 16 Strip tree (Like a CCR tree). I purchased the 682 because it has 16 outputs and I can plug 1 strip into each output and I was told this would eliminate any power injection. My question is how do I spread out the universes to cover all 16 outputs? How do I set it up in SE?

 

Read the manual but just not getting it....

Share this post


Link to post
Share on other sites

The page is quite outdated.  The E6804 and E682 both support 7 universes in multi-cast and 12 universes in uni-cast.  This does require version 4.xxx firmware.  I sent an E-Mail to Jim at SanDevices suggesting that he needs to update that page...

Edited by k6ccc
  • Like 1

Share this post


Link to post
Share on other sites

I just purchased a 682 for my 16 Strip tree (Like a CCR tree). I purchased the 682 because it has 16 outputs and I can plug 1 strip into each output and I was told this would eliminate any power injection. My question is how do I spread out the universes to cover all 16 outputs? How do I set it up in SE?

 

Read the manual but just not getting it....

 

You need to know how many pixels are on each strip. If it's 50 ( like a CCR ) you will need 150 channels for each strip ( 3 channels per pixel x 50 pixels ) 

So for 16 strips you would need 2400 channels. If you used every channel in a DMX universe, 510 ( channels 511 &512 are not used because you cannot have a pixel addressed to 2 different universes ) you would need 4.7 universes or 4 full universes plus 360 channels in universe #5

Share this post


Link to post
Share on other sites

godman, give me a phone call this evening (I think you have my number).  I will walk you through all kinds of stuff with live examples.  I will have you connect to my controllers so you can see what's going on and explain what you are seeing...

 

I should be done with dinner by shortly after 7:00 PM and up until at least 11:00 PM.  Almost any time over the weekend if tonight does not work.

Share this post


Link to post
Share on other sites

This is how I have my pixels setup.  I like to keep each element in its own universe.  And I made it so that I didn't need to have power injection.  I have 3 30 long pixel strings, one for each part of the tree.  So it just worked out for me to make these breaks where I did.  As I get more elements I will have to redo how this is setup.  But for now, this works without power injection...and my trees are over 50 feet away from the controller.

 

One thing to notice....I use plugs 3-1 and 3-2 as 2 universes but the strips I have plugged in are not full universes.  Normally, plug 3-2 would start where 3-1 ends. 

 

So 3-1 ends at Universe 1, channel 141.  Plug 3-2 would normally start at Universe 1, channel 142.  I just tell the sans that they are full universes to allow me to keep each element on its own universe while minimizing the plugs used.

Share this post


Link to post
Share on other sites

Sax you have pixels that are 50 feet away from your controller without power injection?

Share this post


Link to post
Share on other sites

Sax is using 12V to get the 50ft without power injection which should be no problem with distance for this scenario....it's the data hence why he needed null pixel every 20ft. I've only personal gone 30ft without power injection but needed 1 null pixel between. Sax probably needed 2 nulls.

Just assuming....Sax would better answer your question of what method he is using.

Edited by CLD Kevin

Share this post


Link to post
Share on other sites

Kevin nailed it. But I am more like 60'. 12v and a null pixel every 25'. I have 2 nulls, 2 25' extensions and a 10' extension into the element.

However, I did have to change out the resistor packs on the e682 to use the standard 25' extensions Ray sells. Without changing the resistors every now and then the pixels would flicker. I initially corrected this with a third null and 15' extensions, but the resistor pack is a better and cheaper fix.

Share this post


Link to post
Share on other sites

A null pixel is just another pixel in between a long run for the data. In the SanDevices controllers you tell it that there is some number of null pixels. I assume the other controllers are similar. A null pixel does not exist as far as LOR software is concerned..

Share this post


Link to post
Share on other sites

A null pixel is just another rgb pixel. It is used to carry the data signal on.

The problem is, over great distances the data signal degrades. But with a null pixel, the data signal comes in degraded and is sent out whole again. This also takes some of the voltage at the pixel.

So pixels are good for data signal but bad for the power supply.

I can only get the data to go about 20 ft before it degrades on a standard E682. By changing the resistor packs on the E682 I can go further, currently I have only tested out to 25' as that is my longest extension cable. The power supply voltage, I use 12vdc, can go much further. But to allow me to get the data out further, I have to put those pixels in to boost that degraded signal.

If you don't classify the pixel as null in your controller, then it is just pixel one. In truth you can have your pixels spread apart as much as you want as long as you can get the data signal and power to it. But in most cases you want them grouped on your element.

By classifying the pixel as null it is simply ignored by the controller as a working pixel.

If you classify more pixels as null than you have, you just push pixel 1 further from the controller. It passes the data on, but the pixel doesn't light.

Your null pixel has to match the pixels you have on that output. So if I have 2811 pixels the null must be a 2811. It can be a different shape, say flat over bullet...but it must be the same type.

My null pixels are simply a bullet 2811 pixel with pigtails on both ends to allow me to insert it anywhere I need it.

Hope this helps anyone confused over nulls

Edited by sax

Share this post


Link to post
Share on other sites

what type of wire/ what gauge do you use to connect the pixels to the controller and the controller to the power supply?

Share this post


Link to post
Share on other sites

Most of mine are using 4 conductor 16 AWG speaker wire. Since 2811s only take 3 wires, I double up the ground.

Share this post


Link to post
Share on other sites

It Helped alot, Thank you Sax. Now does anyone know why my power supplies stop working 12vdc 350 watt 29 amp ran 16 strips, 50 12volt square pixels  works fine during testing about 20 minutes, shut it down and when I went back to use later no power ?   Bought on Amazon.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


×
×
  • Create New...