LED Controller & Receiving Card Products: Hardware & Evolution Explained

LED Display Control System: Controllers & Receiving Cards — Hardware Evolution & COB Selection Guide
LED Display · Control System · Engineer's Notes

LED Display Control System: Controllers & Receiving Cards, Explained from Hardware to Evolution

From the video source to every single LED, the controller (sending card) and the receiving card decide how bright, how smooth, and how color-accurate your COB LED display actually is. This guide breaks down their hardware, key specs, and four generations of evolution — so you can select and troubleshoot with confidence.

For: LED display engineers · pre-sales / commissioning / after-sales · ~8 min read

1. A field failure that exposed the "last mile" of signal

2:00 AM at a project site. The wall was playing test content when rows of "bright lines" suddenly appeared along one edge. The module was suspected first — swapped. Then the power supply — tested. The culprit turned out to be a receiving card parameter: the grayscale level was set wrong.

Many engineers blame the display itself for image problems — the LEDs, the modules, the power supply, the flat cables. But what actually determines picture quality is often the overlooked control system. The controller and receiving card are the "last mile" of the signal — brightness, grayscale, refresh rate, loading capacity. Get any one of them wrong, and even the best COB LED display will underperform.

2. System architecture: controller up front, receiving card at the back

A complete LED display control system has two stages — a controller on the front end and a receiving card on the back end. Understanding this split is the prerequisite for everything that follows.

LED display control system signal chain The video source passes through the controller and receiving card to drive the LED module 1 Video Source PC / Player Camera / Signal 2 Controller Sending Card Decode·Split·Send 3 Transport Gigabit Ethernet Optical Fiber 4 Receiving Card Data Decode PWM Drive 5 LED Module Pixel Array Displays Image Front end · signal processing & distribution Back end · driving & display

Figure 1: LED display control system signal chain (source → controller → transport → receiving card → module)

In one line: the controller receives, decodes, and splits the video signal; the receiving card distributes it to every LED and controls brightness and grayscale via PWM. Let's unpack each.

3. Controller hardware: the signal entry point

The controller (also called a sending card or main control) is the system's signal entry point. It receives video from a PC, player, camera, or other source, then decodes, scales, and splits the image before distributing it to the receiving cards over gigabit Ethernet or optical fiber.

To judge whether a controller is "enough," look at these key specs:

  • Input interface: DVI / HDMI / DP / SDI — determines what sources you can connect and the maximum resolution and refresh rate.
  • Loading capacity: the total pixels a single card can drive (million-level, 4K-level), which defines how much screen area one card covers.
  • Output interface: number of gigabit ports / optical fiber support — determines transmission distance and cascading ability.
  • Built-in video processing: splicing, scaling, multi-window, multi-input switching — decides whether you still need a separate processor.

Common product lines in the industry: the classic MCTRL series sending cards (MCTRL300 / MCTRL660), the 4K main control MCTRL4K, the integrated-processing VX series (VX4S / VX6S), and the standalone main controls and splicers MX series / Taurus series.

4. Controller evolution: from sending card to smart cloud main control

The controller's evolution has been driven by one force: higher resolution and more integrated functions. It can be summarized in four generations:

LED controller evolution timeline The controller evolved from a standalone sending card to integrated processing, 4K loading, and finally cloud intelligence Gen 1 · Standalone Sending Card MCTRL300 / MCTRL660 — DVI input + gigabit port, pure "signal forwarding" Relies on PC graphics output; resolution and refresh limited by the GPU Gen 2 · Processing + Sending Combined VX series (VX4S / VX6S) — integrated splicing, scaling, multi-window Multiple switchable inputs, some support offline playback — no extra processor needed Gen 3 · 4K / 8K High-Loading Main Control MCTRL4K / MX series — 4K@60Hz, HDR, multi-channel optical output Meets the high-resolution, high-refresh demands of COB and fine-pitch walls Gen 4 · Smart & Cloud-Connected Cloud-based remote O&M, smart calibration, module-level monitoring From selling hardware to "hardware + operation services"

Figure 2: Four-generation evolution of the LED controller

5. Receiving card hardware: the executor that drives the LEDs

The receiving card sits inside the display — the true "last mile" of the signal chain. It receives data from the controller, decodes it, and drives the modules through the Hub interface (HUB75 / HUB320), using PWM to precisely control each LED's brightness and grayscale.

When selecting a receiving card, focus on these specs:

  • Loading capacity: the pixel range a single card supports (e.g. 256×256, 512×256) — how many modules one card can drive.
  • Grayscale: 8-bit / 10-bit / 14-bit / 16-bit — the higher, the finer the shadow detail and color transitions.
  • Refresh rate: 960Hz / 1920Hz / 3840Hz — higher avoids camera scan lines and reduces visual flicker.
  • Output interface: HUB75 is the universal standard; HUB320 targets higher-density module interfaces.
  • Point-by-point calibration: brightness / chroma correction support — directly determines screen uniformity.

6. Receiving card evolution: from 8-bit to point-by-point calibration

The receiving card's evolution follows one thread: bigger loading, higher grayscale and refresh, stronger intelligence:

LED receiving card evolution timeline The receiving card evolved from basic 8-bit driving to universal HUB75, high-grayscale high-refresh, and finally large-loading intelligence Early · Basic Driving MRV210 and similar — single module, low grayscale (8-bit), low refresh Good enough for basic display; limited shadow detail and camera performance Universal Standard MRV300 / MRV320 — HUB75 interface, larger loading capacity Became the industry mainstream; greatly improved compatibility and stability High Grayscale · High Refresh MRV366 / MRV336 — 16-bit grayscale, 3840Hz refresh rate Supports point-by-point calibration; meets rental and fine-pitch / COB needs Large Loading · Intelligent MRV416 / A8s and others — bigger loading, HUB320, automatic module calibration Supports smart modules and status feedback; simplifies on-site commissioning

Figure 3: Four-generation evolution of the LED receiving card

7. What COB LED display demands from the control system

If you work with COB LED display, pay extra attention to these points when choosing a control system. COB (Chip on Board) packages the LED chips directly onto the PCB, eliminating brackets and masks — bringing high protection, high contrast, wide viewing angles, low moiré, and good heat dissipation. But it also raises the bar for the control system.

Why is a COB display more "picky" about its control system? COB has higher chip density, higher contrast, and richer shadow detail. The better the panel, the more a weak control system will amplify grayscale banding and brightness non-uniformity.
  • Low-brightness high-grayscale: COB's high contrast and rich shadow detail demand that the receiving card keep enough grayscale at low brightness — no muddy darks, no crushed blacks.
  • Point-by-point calibration: COB's large chip count makes consistency challenging; per-pixel correction is the key to whole-screen uniformity.
  • High refresh: camera, live-broadcast, and surveillance scenarios need no scan lines — typically 1920Hz to 3840Hz support.
  • Stable transport: COB walls have high resolution and long cascading distance; the controller's loading and fiber stability are critical.

A practical selection approach: first pin down panel resolution + refresh requirement + grayscale requirement + whether point-by-point calibration is needed, then work backward to the controller's loading capacity and the receiving card spec — instead of judging by unit price alone. Get the parameters right, and the COB panel's picture-quality advantage is fully unlocked.

8. Key takeaways

ComponentRoleKey specsRepresentative products / evolution
Controller
(sending card)
Signal entry: decode, split, distributeInput interface · loading capacity · output ports/fiber · video processingMCTRL series → VX integrated → 4K/8K main control → smart cloud
Receiving cardSignal end: decode + PWM-drive the LEDsLoading capacity · grayscale · refresh rate · Hub interface · calibration8-bit basic → universal HUB75 → high-gray high-refresh → large-loading smart
COB adaptationBetter panels are more "picky" about the systemLow-brightness high-gray · calibration · high refresh · stable transportDerive specs from "resolution + refresh + grayscale + calibration"

9. FAQ

1. What's the difference between a sending card (controller) and a receiving card?

The controller is the front-end signal entry — it receives, decodes, and splits the video signal. The receiving card is the back-end executor — it drives the data to each LED and controls brightness and grayscale via PWM. They sit at opposite ends of the chain; both are essential.

2. Do COB LED displays and standard SMD screens have the same control system requirements?

No. COB has higher contrast, richer shadow detail, and greater chip-consistency challenges, so it demands more from low-brightness high-grayscale, point-by-point calibration, and high refresh — these take higher priority when choosing a control system.

3. How do I determine the loading capacity of the controller and receiving cards?

First calculate total pixels = horizontal × vertical, then divide by each receiving card's loading to get the card count. The controller's loading must cover the total pixels with headroom, and confirm the resolution and refresh-rate ceiling.

4. Which matters more — grayscale or refresh rate?

They serve different purposes: grayscale governs color and shadow detail, while refresh rate governs camera-friendliness and visual stability. Indoor COB and rental/broadcast scenarios need both to be high — don't sacrifice one for the other.

5. If the screen shows scan lines or moiré, is it always a panel problem?

Not necessarily. Scan lines often come from insufficient refresh rate, and moiré relates to module layout and calibration — both can be control-system or parameter issues. Always include receiving-card parameters and refresh settings in your troubleshooting.

Need a COB LED display control-system selection recommendation?

Tell us your panel resolution, pixel pitch, and application — we'll match the right controller and receiving card setup.

Get a Selection Proposal →

Note: the technical content references Chapter 2 of the NovaStar NCE certification textbook "LED Display Application — Beginner", reorganized and rewritten for this article. Product models and parameters are subject to the latest official datasheets.

Let's start a wonderful cooperation

Get A Quote

We will contact you within 1 working day, please pay attention to the email with the suffix “@xingshiled.com”