Pixel Controller Th...
 
Notifications
Clear all

Pixel Controller Thread

23 Posts
11 Users
0 Reactions
7,998 Views
MartinMueller2003
Posts: 7614
(@martinmueller2003)
Illustrious Member
Joined: 14 years ago

I topped out at about 4000 pixels on my F16v2. This year I will have close to 5K on one of them.


Reply
Posts: 114
(@wilkija)
Estimable Member
Joined: 12 years ago

Do you see any latency on the F16v2 with higher numbers of pixels per output? I'm doing at megatree with 27 strands of 100 pixels. So I'm trying to figure out how many outputs I need to use.

Sent from my Nexus 5X using Tapatalk


Reply
dpitts
Posts: 1020
(@dpitts)
Noble Member
Joined: 16 years ago

The refresh rate is not affected by pixel count.


Reply
Posts: 114
(@wilkija)
Estimable Member
Joined: 12 years ago

Thanks. So with power injection every 100 pixels what, if any, is the downside of running 600 pixels on a single output?

Sent from my Nexus 5X using Tapatalk


Reply
MartinMueller2003
Posts: 7614
(@martinmueller2003)
Illustrious Member
Joined: 14 years ago

I am using 400 pixels per output on the F16v2 and it seems to be working nicely.


Reply
Posts: 672
(@pixelpuppy)
Honorable Member
Joined: 12 years ago

The downside with long strings is when you have a pixel failure. When a pixel stops passing data, all the downstream pixels stop working too. Keeping strings shorter helps minimize the outage impact *when* you have a pixel failure (and you will).


Reply
Posts: 383
(@aesl1982)
Reputable Member
Joined: 12 years ago
AussieDoug wrote:Sorry, but the f16 V2 board was the “winner” in what way exactly? Just because the user ended up choosing it for his particular application? Do you really think that the Falcon controller is always the best fit in all cases?

I don’t think you can say that one controller is perfect for every person and use to the exclusion of all others. Many of the reasons you may think the Falcon controller is better may not even actually be relevant to Kevin.

For example, do you need to control multiple different types of pixels off the one controller (E.G. WS2811 and LPD6803 simultaneously)? Do you need to use virtual strings (E.G. add null pixels mid string or change RGB order in the middle)? If not, then why is the Falcon a better fit for that purpose? Well…it’s probably not. The PixLite controller is cheaper and drives more pixels, so I think it would be better – for that particular case.

Do you need to control a very complex array of different types of pixels all connected together in series? Such as using strings of pixels from different manufacturers where the RGB order is different and you need to change color mid string? Then maybe the Falcon is a better fit for that application because you can’t change RGB order mid string on the PixLite.

That being said, you can change RGB order on each output separately on a PixLite controller. So that is really an incredibly specific scenario where you need to change RGB order in the middle of the output. How often does that happen? P.S. You can easily change the RGB order of an element mid string in any good sequencing software too, so even then it’s certainly not a reason to discount any of the other pixel controllers. Never-the-less, points to Falcon for being able to do it at the controller level, if you want to do it that way instead.

From my point of view, the only 2 deal breaking differences between the 2 controllers are number of pixels (PixLite winner) or being able to control different types of pixels off the same controller (Falcon winner). Beyond that the main consideration is price (PixLite winner at least while the pre-sale is on). The other features are nice to have but you don’t actually NEED them in the majority of circumstances.

So all I’m saying is I don’t think it’s as cut and dry as you make it out to be in terms of which controller is the “winner”. Falcon users love the Falcon products and that’s great, so do PixLite users (like me)! But I think it’s important to consider what your application is and what your budget is when choosing a controller.

Distance to first pixel. expansion, differential expansion, receivers, ease of the user interface, ability to save configs in the user interface and import and export them, being able to have team viewer sessions with the designer anytime with no complaints unlimited chat service with usually immediate response time. Besides all that not much difference I guess.

Sent from my iPhone using Tapatalk


Reply
Posts: 3650
(@jhinkle)
Famed Member
Joined: 15 years ago
dpitts wrote:The refresh rate is not affected by pixel count.

David - please explain your statement - I disagree.

A specific type of pixel string has a timing protocol that must be adhered to. So it takes X amount of time to talk to 1 pixel and NX amount of time to talk to N pixels (all on the same string).

Depending on the amount of time it takes to transmit all N pixels -- that is directly related to refresh rate.

I've seen boards that say they can support 6 universes per port --- true -- but the sequence timing has to be 100 msec --- any thing slower and you get lag.

So depending on the pixel's communication frequency and the number of pixels per string --- THAT --- directly defines the minimum refresh rate.

Just my 2 cents.

Joe


Reply
dpitts
Posts: 1020
(@dpitts)
Noble Member
Joined: 16 years ago

The question was specifically asked about the F16V2. I have fixed the timing to 40Hz for all string types no matter how many pixels is configured. On another board it may not be the case. I can output 680 pixels of WS2811 which is the slowest pixels I support 40 times per second.


Reply
Posts: 3650
(@jhinkle)
Famed Member
Joined: 15 years ago

Thanks David -- what the fastest pixel type you support?

Joe


Reply
Page 2 / 3
Share: