PIXELIGHT

NovaStar CA50E: keeping the COEX chain consistent

Pair the CA50E receiving card with a COEX controller (CX40 Pro, MX40 Pro, KU20): firmware, calibration, cabinet management and card-swap diagnostics.

Receiving cards — the COEX ecosystem

The CA50E is NovaStar's high-end COEX receiving card. Its value only shows up when it stays consistent with the controller, the firmware and the cabinets around it.

The NovaStar CA50E belongs to the new generation of receiving cards in the COEX control system. It handles up to 768 × 512 pixels at 60 Hz for an 8-bit or 10-bit video source, and 512 × 480 pixels at 60 Hz for a 12-bit source, alongside advanced features such as Thermal Compensation 2.0, Full Grayscale Calibration, LED Image Booster, HDR, Mapping 2.0 and hot backup across two cards.

These features only pay off inside a consistent chain. A CA50E mounted on a hub board only reaches its potential when paired with a compatible COEX controller — CX40 Pro, MX40 Pro or the KU20 video processor — and with firmware kept aligned across the card, the controller and the calibration software. A version mismatch, a wrong network pairing, or a poorly prepared card replacement produce symptoms that have nothing to do with a hardware fault.

This tutorial covers the CA50E from that angle: how to check compatibility with the installed controller, how to update firmware without breaking the chain, how calibration and cabinets are managed, and how to diagnose a compatibility issue when swapping a failed card. All figures come from the official CA50E specifications sheet, revision V1.1.1 dated December 30, 2023.

1. Where the CA50E sits in the COEX ecosystem

The CA50E is positioned as a high-end 5G receiving card for image-critical LED displays: production studios, xR sets, control rooms. It communicates through high-density connectors that limit dust and vibration effects, and supports up to 32 groups of parallel RGB data or 64 groups of serial data, expandable to 128 groups.

It remains, however, only one link in a larger chain. Upstream, a COEX controller drives the card over Ethernet; downstream, the card drives the LED modules through the cabinet's hub board. Keeping this chain consistent — firmware versions, load capacity, calibration workflow — is what determines the stability of the displayed image.

Before ordering CA50E cards for a project, confirm the intended controller is on NovaStar's COEX compatibility list: a card compatible with one controller is not automatically compatible with every model in the range.

2. Official technical specifications

The table below reproduces the figures published in the CA50E V1.1.1 datasheet. Use it as a reference to validate a wall's sizing and to diagnose electrical or thermal issues.

NovaStar CA50E — official specifications sheet V1.1.1
SpecificationValue
Maximum resolution (8/10-bit)768 × 512 pixels @ 60 Hz
Maximum resolution (12-bit)512 × 480 pixels @ 60 Hz
Input voltage3.8 V to 5.5 V (5.0 V recommended)
Rated current1.35 A
Rated power consumption6.8 W
Operating temperature-20°C to +70°C
Operating humidity10% to 90% RH, non-condensing
Storage temperature-25°C to +125°C
Dimensions80.0 × 45.0 × 8.6 mm
Net weight25.5 g (single card)
Packing40 cards per box, antistatic bag and anti-collision foam
CertificationRoHS

Measured current and power consumption vary with product settings, usage and environment: the table lists rated values, not guarantees for every installation.

3. Checking the hardware before integration

On receipt, check the original packaging: each CA50E card is protected by an antistatic bag and anti-collision foam, typically shipped 40 cards per box. Handle cards by the edges, avoid touching the high-density connectors, and work on a grounded surface to prevent electrostatic discharge.

Then confirm the exact reference of the COEX controller planned for the project and obtain its compatibility sheet from NovaStar or your distributor. Skipping this step is a common way to discover an incompatibility only after the cards are already mounted on the cabinets' hub boards.

4. Pairing with a COEX controller

The CA50E is designed to work in chains driven by a COEX controller: CX40 Pro and MX40 Pro for all-in-one setups with built-in video inputs, or the KU20 video processor for a split video-processing/sending configuration. In every case, pairing happens over the Ethernet network linking the controller's output ports to the hub board carrying the CA50E.

Pairing should be checked in three steps: is the card detected on the expected Ethernet port, does the pixel load assigned to it respect its 768 × 512 pixel capacity in 8/10-bit mode, and does the communication protocol (number of parallel RGB groups or serial data groups) match the cabinet's hub board configuration. A card that is not detected despite correct cabling almost always points to a firmware mismatch between controller and card rather than a hardware fault.

Document, cabinet by cabinet, the controller's Ethernet port, the card address and the associated hub board. This map saves considerable time the day a card needs an emergency replacement.

5. Firmware update

The CA50E keeps two copies of its application program from the factory, which prevents the card from getting stuck if an update is interrupted: on a failed load, the card automatically switches to the backup program. Configuration parameters follow the same dual-backup logic, split between an application area and a factory area.

Before any firmware update on a CA50E chain, check version consistency between the configuration software, the COEX controller and the installed receiving cards. A partial update — for instance a controller updated without the receiving cards — is the most common cause of compatibility issues seen in the field.

The one-click firmware learning feature copies a validated program and configuration file from one cabinet to others, which significantly speeds up deployment across a large fleet of identical CA50E cards.

Never update the firmware of a single card within a uniform wall without planning updates for the neighboring cards: a version mismatch between cards on the same wall can produce visibly different image rendering.

6. Calibration and cabinet management

The CA50E supports pixel-level brightness and chroma calibration as well as full grayscale calibration, working with NovaStar's high-precision calibration system and the C3200 scientific-grade camera. Calibration coefficients can be uploaded quickly, read back, and saved to the card's hardware.

For modules fitted with flash memory, cabinet management becomes automatic: when a faulty module is replaced with a new one, the calibration coefficients stored in its flash memory are automatically uploaded to the receiving card at power-on, preserving brightness and chroma uniformity without manual intervention. The Mapping 2.0 feature identifies each cabinet by color, Ethernet port number and receiving card number, which simplifies screen configuration and connection troubleshooting.

The Cabinet Finder feature lets users frame a cabinet on screen and change its indicator status to locate it physically — a valuable tool when diagnosing a wall made of many identical cabinets.

Before replacing a module without flash memory, back up its existing calibration coefficients manually: without onboard flash memory, automatic coefficient transfer does not apply.

7. Thermal compensation and chain reliability

Thermal Compensation 2.0 collects each cabinet's heat distribution data through the high-precision calibration system, then generates per-pixel compensation data to eliminate cross-shaped blue or red stripes caused by uneven heat dissipation. This also helps control power consumption and extends the display's service life.

On the reliability side, the CA50E supports hot backup across two cards mounted on the same hub board: if the primary card fails, the backup card takes over immediately without any display interruption. The status of both cards is actively reported to the control computer or controller if either fails. Loop backup between the card and the controller is also available, keeping the screen displaying normally even if a section of the cabling fails.

8. Compatibility diagnostics when swapping a card

The CA50E's running indicator gives a first diagnosis without any tool: a flash every second means normal operation, a flash every 3 seconds signals an abnormal Ethernet connection, three flashes every 0.5 seconds mean a correct connection with no video source, and a flash every 0.2 seconds means the card is running its backup program because it failed to load the application program.

When physically replacing a faulty card, follow this order: power off the cabinet, replace the card with an identical reference mounted on the same type of hub board, check that its firmware version matches the rest of the wall's cards, power back on, and check the running indicator. A problem persisting after replacement is most often caused by a firmware mismatch between the new card and the rest of the chain, or by a card meant for a different COEX controller model.

Quick diagnosis from the running indicator
Indicator behaviourMeaningAction
Flashes once per secondNormal operation, video source presentNo action needed
Flashes once every 3 secondsAbnormal Ethernet connectionCheck the cable and the network port
Flashes 3 times every 0.5 secondsCorrect connection, no video sourceCheck the upstream video source
Flashes once every 0.2 secondsApplication program failed, running backupReload the application firmware
Flashes 8 times every 0.5 secondsRedundancy switchover on the Ethernet portCheck the main line of the loop

Never replace a CA50E with a different reference card without first checking its compatibility with the installed COEX controller: two receiving cards may look physically interchangeable on a hub board while being incompatible at protocol or firmware level.

9. Troubleshooting common issues

Most incidents seen on a CA50E chain trace back to a firmware mismatch, a mis-sized pixel load, or confusion between compatible COEX controller models. The table below complements the indicator-based diagnosis above.

SymptomLikely causeAction
Card not detected by the controllerFirmware mismatch between card and controllerAlign versions, then re-check detection
Visible rendering gap between neighboring cardsPartial firmware update across the wallBring all cards' firmware to the same version
Calibration coefficients not carried over after module swapModule without onboard flash memoryReapply manually backed-up coefficients
Persistent cross-shaped color stripesThermal Compensation 2.0 not enabled or data missingRe-run the thermal data collection via the calibration system
No switchover on card failureHot backup not configured on the hub boardCheck the two-card mounting and enable the feature

Procedure

  1. Check the delivered hardware

    Inspect the antistatic packaging of the CA50E cards and identify the target COEX controller (CX40 Pro, MX40 Pro or KU20).

  2. Verify compatibility

    Confirm the card/controller pairing and the installed firmware version before integrating cards onto the hub boards.

  3. Wire and detect the cards

    Connect each card to its intended Ethernet port and check detection along with the assigned pixel load.

  4. Update firmware

    Align firmware versions across configuration software, COEX controller and CA50E cards, then duplicate the validated configuration with one-click learning.

  5. Calibrate the cabinets

    Upload pixel-level calibration coefficients and configure the Mapping 2.0 cabinet layout.

  6. Enable thermal compensation

    Run per-cabinet thermal data collection to remove color bands caused by uneven heat dissipation.

  7. Diagnose a card replacement

    On failure, replace the card with an identical reference, check firmware, and monitor the running indicator.

Frequently asked questions

What is the maximum resolution handled by a CA50E?

768 × 512 pixels at 60 Hz for an 8-bit or 10-bit source, and 512 × 480 pixels at 60 Hz for a 12-bit source, per the official V1.1.1 specifications sheet.

Which COEX controllers is the CA50E compatible with?

It works in chains driven by an all-in-one CX40 Pro or MX40 Pro controller, or by the KU20 video processor in a split configuration.

What if a new CA50E card is not detected after replacement?

First check that its firmware version matches the controller and the other cards on the wall: a firmware mismatch is the most common cause of non-detection.

Is calibration preserved when replacing an LED module?

Yes, if the module has flash memory: calibration coefficients are automatically uploaded to the receiving card at power-on. Without flash memory, a manual backup beforehand is required.

Does the CA50E support redundancy on failure?

Yes, through hot backup across two cards mounted on the same hub board, and through loop backup between the card and the controller.

Downloads

Related tutorials

Need help with your COEX chain?

PIXELIGHT's team validates compatibility between receiving cards, controllers and cabinets before integration.