LED Display Loading Capacity: How to Size Network Ports and Controllers Correctly
A screen that powers on halfway, shows black bands, or flickers at high grayscale is rarely a lamp problem — it's usually a loading capacity miscalculation. This guide walks through the two calculations every LED screen project needs before procurement: gigabit network port loading and controller sizing — with practical notes for fine-pitch COB LED display projects.
- Why loading capacity is where projects go wrong
- Step zero: from pixel pitch to total screen resolution
- Network port loading: principle and a 3-step method
- Controller sizing: capacity and width/height checks
- Why COB fine-pitch projects demand early calculations
- Key takeaways · FAQ
1. Why Loading Capacity Is Where Projects Go Wrong
Familiar scenario: cabinets installed, each one tested OK individually — then the full screen powers on and only part of it lights up. Or the image shows regular black bands. Or refresh rate collapses into visible flicker at high grayscale. Power supplies, flat cables, modules all check out fine, and the culprit turns out to be sending equipment and network port allocation.
The root cause is always the same: every link in the signal chain — network port, receiver card, controller — has a hard ceiling on the pixels it can carry, while the screen's demand is fixed. If demand and capacity don't match, the failure surfaces the moment the screen is powered on. That's why both calculations below belong in the quotation and detailed-design phase, not on installation day.
2. Step Zero: From Pixel Pitch to Total Screen Resolution
Every loading calculation starts with one number: total screen resolution (total pixel count), derived through a fixed chain:
Worked example using the most common 640×480 mm cabinet at P2.5: a 320×160 mm module carries 128×64 pixels; a cabinet holding 2 modules across and 3 down gives 256×192 = 49,152 px. A screen built from 8×8 = 64 cabinets (6.4 m × 3.84 m) therefore totals 2560×1536 ≈ 3.93 million pixels — the input for everything that follows.
3. Network Port Loading: Principle and a 3-Step Method
3.1 The principle: two gates on every link
After the controller generates the image, data travels over gigabit Ethernet to the receiver card inside each cabinet, which then drives the modules. So "network port loading" is limited by two gates in series:
Gate one — receiver card processing capacity. Every receiver card has a maximum pixel budget (commonly 650,000 or 1.3 million px per card). This is a hard limit on what it can decode, buffer, and output.
Gate two — gigabit port bandwidth. Data per second = pixels × frame rate × bits per pixel. Bandwidth is fixed, so the higher your refresh rate and grayscale requirements, the fewer pixels one port can carry. That's why the same receiver card can run at full load in a standard application but must be de-rated in high-refresh, high-grayscale fine-pitch projects.
3.2 The 3-step method
3.3 Worked example
Continuing from Section 2: the screen totals 2560×1536 ≈ 3.93M px; ports are rated at 650,000 px each. 3.93 ÷ 0.65 = 6.05, so 7 ports are required. A 4-port controller would need two units — or one 8-port unit. Allocate ports by whole cabinet columns where possible: clean regions, shorter cable runs, and easier calibration zone management later.
4. Controller Sizing: Capacity and Width/Height Checks
The sending controller is the source of the entire screen's signal. Its loading capability is judged by two specs:
Spec one — total pixel capacity. A 4-million-pixel-class controller can only drive screens up to that budget. Our 3.93M-px example against a 4M controller leaves just ~2% headroom — technically workable, but fully maxed out. Once you enable high refresh, HDR, or 3D features, capacity tightens further, so spec 10–20% headroom into any controller selection.
Spec two — maximum loading width. Many controllers have ample total capacity but a per-axis width cap. Ultra-wide screens (a 16:1 storefront ribbon) and ultra-tall totems are where this bites: both screen width ≤ max width and screen height ≤ max height must hold.
Align the port count from Section 3 with the controller's port configuration and the whole chain closes: screen pixels → controller capacity/W-H checks → port count and allocation → per-port receiver loading. Pass all four, and the screen lights up first try.
5. Why COB Fine-Pitch Projects Demand Early Calculations
For COB LED display technology, loading calculations matter even more. COB packaging mounts LED chips directly onto the PCB, delivering superior protection and reliability — the mainstream route for fine-pitch and micro-pitch displays. But as pitch shrinks, pixel density grows quadratically:
| Pixel pitch | Pixels per m² | Area one gigabit port (650K px) can carry |
|---|---|---|
| P2.5 | 160,000 px | ≈ 4.1 m² |
| P1.5 | 444,444 px | ≈ 1.5 m² |
| P1.2 (typical COB) | 694,444 px | under 1 m² |
| P0.9 (COB micro-pitch) | 1,234,568 px | ≈ 0.5 m² |
Translation: a 20 m² screen at P2.5 needs 5–6 ports, while the same screen at P1.2 COB needs 30+ ports and multiple cascaded controllers. Add the stricter high-refresh and high-grayscale expectations of fine-pitch buyers, and per-port loading shrinks further. In COB fine-pitch projects, loading calculation isn't just a "will it light up" question — it directly determines controller count, cable routing, rack space, and total project cost.
Key Takeaways
| Item | Formula / Check | Engineering note |
|---|---|---|
| Screen resolution | Pixels = dimension ÷ pitch, level by level | Compute W and H separately; input to all loading math |
| Port loading | Total px ÷ per-port rating (e.g. 650K), round up | Limited by receiver card + port bandwidth; de-rate for high refresh/grayscale |
| Port allocation | Split load by whole cabinet columns | Verify each port's horizontal width against the device limit |
| Controller sizing | Total px ≤ capacity; W, H ≤ axis limits | Keep 10–20% headroom for HDR / high-refresh features |
| COB fine pitch | Density grows quadratically as pitch shrinks | Far more ports and controllers — calculate before you buy |
Frequently Asked Questions
There is no fixed number — it depends on the receiver card spec and the screen's refresh/grayscale settings. Use the datasheet's recommended loading (commonly ~650,000 px), and always keep headroom rather than designing to the limit.
Always round up. 3.93M ÷ 0.65M = 6.05 → use 7 ports, then distribute the cabinet regions sensibly across them.
You've most likely exceeded the maximum width or height. Controllers carry both a total capacity limit and per-axis limits; ultra-wide ribbons and ultra-tall totems hit this first.
Yes — pixel density. COB fine-pitch screens consume ports and controller capacity far faster than standard-pitch displays, and high-refresh settings reduce loading further. Complete the full loading calculation at the design stage, before equipment is ordered.
Need a complete COB LED display loading plan?
Send us your screen dimensions, pixel pitch, and application — our engineers will deliver a full calculation sheet covering resolution, port allocation, and controller selection.
Get a Free Loading Calculation
