NovaStar MRV vs DH vs AT Receiving Cards: Which One Does Your LED Wall Need?
Choosing between NovaStar’s MRV vs DH vs AT receiving cards decides two things at once: how many cards your wall needs, and how clean the picture will look after calibration. We build LED cabinets around all three series, and the question buyers actually need answered is rarely “which card is best” — it is “which card matches my module and my budget without overpaying”. This guide compares the three series model by model, with every specification taken from the official NovaStar sheets.
What Does an LED Receiving Card Do? (Quick Answer)
It receives pixel data from the sending controller over Ethernet and drives the LED modules row by row. One card feeds a fixed number of module connectors (HUB75E on most models) and therefore a fixed number of pixels — 256×256 on the compact cards, up to 512×512 on the high-capacity ones. For the deeper background, see the LED receiving card guide and the LED control system architecture article. Every figure in this comparison comes from the official NovaStar specification sheets, which you can verify at the NovaStar receiving card download center.
NovaStar Receiving Card Lineup Explained: MRV, DH and AT Series
| Series | Positioning | Connectors | EMC | Signature Features |
|---|---|---|---|---|
| MRV | General-purpose line, fullest feature set | HUB75 / HUB75E, 8–16 | Class A (MRV336 Class B) | Color Management, 18bit+, low latency, multi-batch on top models |
| DH | Cost-optimized line, same core reliability | HUB75 / HUB75E, 8–16 | Class A | Calibration and 3D; DH7516 drops chroma calibration to cut cost |
| AT | Compact cards for slim and custom cabinets | High-density connectors | Class B | LVDS, smart-module support, dual-card backup |
MRV Series vs DH Series: What Is the Actual Difference?
The MRV and DH lines share the same architecture, the same NovaLCT workflow and the same loop-backup reliability — the difference is feature depth per dollar. The MRV208 set the baseline: 256×256 pixels, eight HUB75 ports, 12-bit precision calibration, 3D, Mapping, and dual program/config backup. The DH line takes that formula and strips toward price: the DH7508 receiving card keeps calibration, 3D and backup but positions as the cost-effective pick, and the DH7516 saves further by supporting brightness calibration only — no chroma calibration, a detail worth knowing if you sell color-uniform walls to finicky clients. Top MRV models add what DH never has: Color Management (Rec.709 / DCI-P3 / Rec.2020), 18bit+ grayscale, low latency down to one frame and multi-batch adjustment.
Standard HUB75 Cards Compared: MRV208 vs MRV328 vs DH7508
The 256×256 tier is where most fixed-install walls live. All three cards load 256×256@60Hz and carry eight HUB75E ports with 16 groups of parallel RGB data, so cabinet wiring is interchangeable between them. The differences: the MRV328 is the current general card with RoHS and EMC Class A certifications and up to 1/32 scan support; the MRV208 is its predecessor (HUB75, firmware V4.5.1.0) with the same pixel count; the DH7508 undercuts both on price with the same 8-port/256² spec, slightly reduced 3D loading (192×256 PWM / 176×256 common IC) and EMC Class A. For plain P3–P6 indoor and outdoor modules this tier is the default choice — no reason to pay for 512² capacity a 2-million-pixel wall will never use.
High-Capacity Cards Compared: MRV412-N vs MRV416 vs DH7512 vs DH7516
Above 256², four cards split into two philosophies. The MRV pair is the premium route: the MRV412-N (12 HUB75E ports, 24 groups) and the MRV416 (16 ports, 32 groups) both load 512×512@60Hz with PWM driver ICs and 512×384@60Hz with common ICs at 8-bit, and both carry Color Management, 18bit+, multi-batch adjustment, low latency and 90° image rotation. The DH pair is the value route: the DH7512 (12 HUB75, 24 groups) matches 512×512 loading and even keeps color management and 18bit+; the DH7516 (16 HUB75E, 32 groups) loads 512×384 and cuts chroma calibration. NovaLCT V5.3.0 or later is required for the full resolutions on both DH models — an old software install is the most common reason a 512² wall shows a load error on site.
| Model | Ports | RGB Groups | Max Loading (8-bit) | EMC | Standout Features |
|---|---|---|---|---|---|
| MRV208 | 8× HUB75 | 16 | 256×256@60Hz | — | 12-bit calibration, 3D, Mapping |
| MRV328 | 8× HUB75E | 16 | 256×256@60Hz (PWM IC) | Class A | 1/32 scan, RoHS |
| MRV336 | 12× HUB75E | 24 | 256×256@60Hz | Class B | Denser cabinets, 24 groups |
| MRV412-N | 12× HUB75E | 24 | 512×512 (PWM) / 512×384 (common) | Class A | Color Management, 18bit+, low latency, 90° |
| MRV416 | 16× HUB75E | 32 | 512×512 (PWM) / 512×384 (common) | Class A | Color Management, 18bit+, 1-frame latency, multi-batch |
| DH7508 | 8× HUB75E | 16 | 256×256@60Hz | Class A | Cost-effective, 3D |
| DH7512 | 12× HUB75 | 24 | 512×512 (NovaLCT V5.3.1+) | Class A | Color Management, 18bit+, 90° |
| DH7516 | 16× HUB75E | 32 | 512×384 (NovaLCT V5.3.0+) | Class A | Brightness-only calibration, 3D |
| AT20 | High-density | 24 parallel / 64 serial | 256×256 | Class B | LVDS, smart module, dual-card backup |
| AT30 | High-density | 32 parallel / 64 serial | 512×256 | Class B | LVDS, smart module, dual-card backup |
AT Series Explained: What the High-Density Connector Changes
The AT20 (256×256, 24 parallel groups or 64 serial groups, expandable to 128) and the AT30 (512×256, 32 parallel or 64 serial groups) replace the classic HUB75E header with a high-density connector, and everything else follows from that swap: dust and vibration resistance for slim cabinets, LVDS transmission from hub board to module, and a smaller card that fits thin and curved designs. Both carry EMC Class B — the stricter emission class required for residential and office-adjacent installations — plus smart-module support (module ID, calibration coefficients stored in module Flash, automatic recalibration after module replacement) and dual-card backup: two cards on one hub board, with automatic failover and status monitoring in NovaLCT. If your cabinet is 70 mm thin or thinner, AT is usually the only series that physically fits.
How to Match a Receiving Card to Your LED Module: Ports, Groups and Pixel Math
Match the card to the module in two steps. First, ports and groups: each HUB75E port drives one ribbon run to the module, and each group handles one color data lane — a 1/32-scan module with a standard pinout typically needs 16 groups, which an 8-port card provides; fine-pitch or high-refresh modules often demand 24–32 groups, which is exactly what the 12-port and 16-port cards exist for. Second, pixel math: a 1920×1080 wall is 2.07 million pixels — that is 32 cards at 256×256 (65,536 px) but only 8 cards at 512×512 (262,144 px). Fewer cards means fewer ribbon runs, fewer failure points and less cabinet wiring, which is why high-capacity cards pay for themselves on fine-pitch walls even before image quality enters the conversation.
A concrete example from a recent build: a P2.5 wall of 1920×1080 using 320×160 mm modules with 1/32 scan. Each module holds 128×64 pixels, and four modules per cabinet mean 256×256 per cabinet — a textbook MRV328 job. Switching the same wall to a 512² card would change nothing visually, because the module scan rate, not the card capacity, is what limits the ribbon plan. The card choice follows the module, not the other way around, which is why we ask for the module datasheet before quoting a card. All ten models configure identically in NovaLCT, so the choice never locks you into a different workflow.
NovaLCT Receiving Card Configuration and Replacement
Configuration is the same across all three series: load the cabinet .rcfgx file in NovaLCT, map the screen, send the parameters, and the card stores them with a backup copy in its factory area — a firmware update that fails will not brick a card. Replacement is equally routine, and the two maintenance habits from our service team are worth copying: always read back the old card’s parameters before removing it (NovaLCT saves the firmware and configuration to your PC), and test the new card with a test pattern from the self-test button before hanging the module back on the wall.
Which Receiving Card Should You Choose? Decision Guide
| Your Cabinet / Wall | Recommended Card | Why |
|---|---|---|
| Standard P3–P6 modules, budget-led builds | DH7508 | 256², 8 ports, cost-effective with full reliability |
| General builds, denser cabinets, 1/32 scan | MRV328 / MRV336 | 256², 8/12 ports; MRV336 adds EMC Class B and 24 groups |
| Fine-pitch or color-critical walls, multi-batch stock | MRV412-N / MRV416 | 512², Color Management, 18bit+, low latency |
| 512² capacity on a tighter budget | DH7512 | 512² with color management and 18bit+ at DH pricing |
| 16-port value builds, brightness-only calibration acceptable | DH7516 | 512×384, 32 groups, lowest cost in the 16-port tier |
| Slim, curved or dust-prone cabinets; office environments | AT20 / AT30 | High-density connectors, LVDS, EMC Class B, dual-card backup |
Frequently Asked Questions About NovaStar Receiving Cards
What is the difference between MRV and DH series receiving cards?
Same architecture and NovaLCT workflow, different feature depth: DH is the cost-optimized line (DH7516 drops chroma calibration entirely), while MRV keeps the full feature set and adds Color Management, 18bit+, low latency and multi-batch adjustment on the MRV412-N and MRV416.
How do I choose a NovaStar receiving card for my LED module?
Check the module’s scan rate and pinout to size the ports and RGB groups, then check the wall’s total pixels to size the capacity. Most standard P3–P6 modules run on an 8-port 256² card; fine-pitch and high-refresh modules usually need a 12- or 16-port card.
Which NovaStar receiving card supports 512×512 pixels?
The MRV412-N and MRV416 load 512×512@60Hz with PWM driver ICs (512×384 with common ICs) at 8-bit, and the DH7512 loads 512×512 as well. The DH7512 requires NovaLCT V5.3.1 or later.
Can a DH7508 replace an MRV328?
Electrically yes — both are 8-port HUB75E cards loading 256×256. The MRV328 has a newer firmware line and slightly higher 3D loading; the DH7508 is the cost-effective pick. In a fixed-install non-3D wall they are interchangeable in practice.
What does EMC Class A vs Class B mean on a receiving card?
Class B is the stricter electromagnetic emission standard, required for equipment used near residential or office environments. The MRV336, AT20 and AT30 carry Class B; most other models carry Class A, which suits commercial and industrial venues.
What is the difference between HUB75E and high-density connectors?
HUB75E is the industry-standard 16-pin ribbon header used across module brands. The AT series replaces it with high-density connectors that resist dust and vibration, enable LVDS transmission, and shrink the card footprint for slim and curved cabinets.
Why is my receiving card not detected in NovaLCT?
In order of likelihood: Ethernet cable or port fault, wrong network segment between PC and controller, a card firmware mismatch after an interrupted update, or the card is configured on a different port map. Read back the card parameters first, then check cabling before touching firmware.
How many receiving cards does my LED wall need?
Divide the wall’s total pixels by the card capacity: a 1920×1080 wall (2.07M px) needs 32 cards at 256×256, or 8 cards at 512×512. Fewer high-capacity cards means less cabling and fewer failure points.
Bottom Line: MRV vs DH vs AT — Which Receiving Card Fits Your Build?
Standard modules on a budget: DH7508. Denser standard builds: MRV328 / MRV336. Fine-pitch, color-critical or multi-batch walls: MRV412-N / MRV416. 512² value builds: DH7512. Slim, curved or office-adjacent cabinets: AT20 / AT30. We stock all ten models and pair them with the right VX controller or MCTRL sending box — send us your module specs and wall size and we will return a complete card-and-controller specification with a factory-direct quote.
