Hello Everyone,
Next year I'm switching to pixels. After researching I've ran into a question I can't find the answer to: On the e682, what is the maximum number of pixels per port? I know dmx is 170 pixels, but i see in the documentation, that they put 2 universes on one port.
I was planning on keeping the pixels/port to 170; but If I don't need to do that because I can do more; I may switch to the e6804. I know input to both devices are limited to the refresh rate of dmx (20hz I believe) so If I keep the refresh rate per port under this, I should be fine - correct? I'm planning on doing a 12 strand (50 pixels/strand) mega tree this year, and expand out in the future. I'm also going to use one port to control my Renards via dmx.
At half the price for the kit, is it really worth getting the bigger controller now, or get it later when I outgrow the e6804? if I opt for the smaller controller, I can get pixels and replace the mini trees this year - for the same budget.
Thanks,
Trevor
It is my understanding that if you wanted to you could put all 2040 pixels on one port. The reason for keeping it under 170 is to avoid power injection from voltage drop. Maybe I am wrong though...
Matt Johnson
johnsonlightshow.com
marx1 wrote:Hello Everyone,Next year I'm switching to pixels. After researching I've ran into a question I can't find the answer to: On the e682, what is the maximum number of pixels per port? I know dmx is 170 pixels, but i see in the documentation, that they put 2 universes on one port.
I was planning on keeping the pixels/port to 170; but If I don't need to do that because I can do more; I may switch to the e6804. I know input to both devices are limited to the refresh rate of dmx (20hz I believe) so If I keep the refresh rate per port under this, I should be fine - correct? I'm planning on doing a 12 strand (50 pixels/strand) mega tree this year, and expand out in the future. I'm also going to use one port to control my Renards via dmx.
At half the price for the kit, is it really worth getting the bigger controller now, or get it later when I outgrow the e6804? if I opt for the smaller controller, I can get pixels and replace the mini trees this year - for the same budget.
Thanks,
Trevor
The only limit is that you can only enter 3 digits for pixel length so the max is 999. In practice, that would produce a refresh rate that was too slow for many applications. I have run 512 pixels on a port (16x32 matrix) with good results.
Doesn't the stock 5 amp resistor on each port limit the pixel count to no more than 80+ pixels when all white??
on my tree i am using 128 pixel per conection/port ,,, no problem at all and yes if u inject power you could run 2000 pixel on 1 port ,,,
I've read of people who tried several hundred pixels on a port (E6804 not that it matters) and noticed the delay at the end. They invested in the E682 for more ports.
I had 104 12v 2811 pixels on two ports (for a total of 208) for my roof line with all stock e682. Ran fine for all of October and December.
---Steve---
I'm running 340 per port on my E6804 on a matrix with no issues at all. It should be the same for the E682.
Then what is the purpose of the 5amp resistor on each port? Like duramadmax, I thought this would be the limiting factor. As in, I should not exceed this resistors rating or risk damage. Several boards have these resistors on their ports.
Just keep in mind that there are two separate constraints - data and power. They've kinda have been jumbled together in this thread.
For data, you can run many hundreds or even thousands of pixels per port. If you get more than a few hundred pixels, you'll have lower refresh rates. And you must account for data loss over long wire runs with null pixels (or some other mechanism).
For power, the limit will likely be between 100-200 pixels over a short wire run if powered only off the port on the E682. Any more than that (or for long wire runs) and you'll need to start injecting power (see http://www.doityourselfchristmas.com/wiki/index.php?title=Power_Injection )
There are some distinct advantages to going with the E682 and utilizing more ports. Primarily, it will decrease the need for power injection unless you have a very long wire run. And it's likely your display will grow in the future. 16 ports can control a LOT of lights. It will also make setting up the controller and programming lights a bit easier - just map one string (can be any number of pixels) per port. A disadvantage is that everything must be wired from the central controller location, so you might have more wire if your lights are further away.
Just remember that you can use pixel strings as wire. For example, if your controller is on your front porch, instead of running the house trim at the far edges of your house as distinct strings with a LONG wire run to them (with power injection and null pixels required), just attach them to the end of your roof trim strings to create one long string that contains two components. This will likely remove the need for null pixels, though with more pixels on the string, you may still need power injection along the way (something you'd need anyway, so no biggie).
For your 12 strand mega tree, you'll probably want to put one string of 100 pixels (50 pixels up and 50 pixels down) off of each of 6 ports. If your controller is located nearby, you likely won't need power injection (though adding it to the end of the 'down' string would be trivial).
Regarding refresh rates. You don't need to worry about setting anything. The E682 controls this. Just know that (more or less) as your string length increases, your refresh rate decreases (but only for that port). If you set a bank to DMX or Renard, it will send the data appropriately regardless of what on the other banks.
