NovaStar MX40 Pro

NovaStar MX40 Pro: VMP, capacity and LED setup

Ask GLMedia about rental options for an LED screen system. We review availability, configuration, and alternatives for your event.

Model and platform

With the date, location, and intended use, we can review which equipment and combination can be offered. You can inquire before measurements, drawings, or the final schedule are ready.

MX40 Pro combines video processing and LED display control within COEX. VMP configures layers, scaling, mapping and screen parameters.

This guide covers MX40 Pro with Gigabit outputs. Do not confuse it with the 5G CX40 Pro or transfer MCTRL4K or VX settings just because a panel uses NovaStar.

Video, LED data and control

Inputs: Three HDMI 2.0 inputs with loop-through, one DP 1.2 and one 12G-SDI with loop-through. Supported resolution and frame rate depend on the input; an advertised maximum does not apply to every format, sampling and bit-depth combination.
LED outputs: Twenty Gigabit ports and four 10G optical ports. Documentation distinguishes optical modes with 20 and 40 logical ports: these are not four unrestricted additional banks or a guarantee of doubled device capacity.
Control and reference: Two Ethernet control ports, Genlock with loop-through and an auxiliary port. LED data and control ports serve different functions. Optical transport requires modules and converters compatible with the path.

System requirements

Mutually compatible VMP, controller firmware and receiving cards. The current table includes A5s Plus, A7s Plus and specified A8s/A10s families; A5s is not the same as A5s Plus. Identify the cabinet’s exact card.

Correct panel configuration file and revisions. For NCP-based functions, verify receiving card, driver IC and the file supplied for that cabinet; matching pixel pitch alone does not justify loading a file.

Pixel and cabling plan per port, output frame rate and bit depth. Published total capacity is up to 9 million pixels, while per-port limits and mapping capacity losses must also be met.

Basic preparation

Record VMP, controller and receiving card versions, cabinet file and cable map. Preserve configuration and coefficients before changing the system.
Check detected video under Input Settings > source > Infoframe: resolution, frame rate, bit depth and gamut. Then compare EDID, layers and scaling with the content.
Calculate each port’s load for the actual frame rate and bit depth. As a documented reference, 8 bit at 60 Hz has a nominal limit of 659722 pixels per port, subject to all other conditions and the total limit.
Assign cabinets and cabling direction in VMP. Check mapping with a suitable pattern and verify optical mode, converter and backup paths before relying on them.
Compare presets, correction and receiving card status. Validate preset recall and system recovery in a controlled test; a visible change alone does not prove persistence.

Three technical questions

Why is capacity insufficient even with spare connectors?
Can I move a NovaLCT panel to MX40 Pro without reviewing files?
Why does correction change after a preset recall or restart?

Why is capacity insufficient even with spare connectors?

Separate the controller’s total limit from per-port load. Load depends on frame rate, bit depth, receiving card and distribution; adding every port’s nominal maximum does not yield guaranteed device capacity.

Also review load-area and mapping losses in the current specifications. Optical mode changes distribution without removing those limits.

Can I move a NovaLCT panel to MX40 Pro without reviewing files?

Identify receiving card and driver IC first. COEX uses VMP and has its own requirements; compatibility with another NovaStar controller does not prove complete MX40 Pro compatibility.

The NCP guide allows .rcfgx use in certain migrations, but VMP cannot edit it. Advanced functions need a compatible combination and suitable NCP; check the file against cabinet documentation before updating.

Why does correction change after a preset recall or restart?

Record what changes, the recalled preset and VMP, controller and receiving card versions. Compare brightness, gamma, color temperature, parameters and coefficients as separate items.

Preserve a copy and test one variable at a time. If the change returns, compare the preset with the receiving cards’ effective parameters before recalibrating or changing firmware.

Checks by symptom

NovaStar MX40 Pro
Symptom	Check	What it separates
Input detected, incorrect image	Infoframe, EDID, layers and scaling.	Input and composition.
Port overloaded	Pixels, frame rate, bit depth and receiving card.	Per-port and total capacity.
Cabinet incompatible	Exact card, driver IC and file.	System brand and actual compatibility.
Change after preset	Parameters, coefficients and versions.	Preset and persistent correction.

Limits and precautions

Advanced functions do not work with every receiving card. The current table states that Low Latency cannot be enabled with Genlock, 3D or Frame Multiplication.

Do not work on energized fiber or improvise optical modules. Follow the manufacturer’s procedure and verify mode and port numbering before connection.

Preserve panel coefficients and verify the cabinet file before changing color or mapping. An update requires compatible versions and a recovery procedure.

Official documentation

Accessed October 22, 2026. Capacity and compatibility checked against official documentation; verify actual versions and cabinets.