NovaStar MX20
NovaStar MX20: COEX, receiving cards, and LED configuration
If panels and content are already available, identify the system and define signal, loading, and mapping before programming.
Model and application
MX20 combines LED processing and control in COEX with VMP. Documentation reference V1.5.0; check the event’s actual controller, software, and receiving-card versions. It is not equivalent to VX1000 or MX40 Pro.
Signal and optics
- Signal
- Two HDMI 1.3 and one 3G-SDI input with loop connections. Separate input format, canvas, and cabinet resolution.
- Output
- 6 Gigabit ports and two 10G optical ports; maximum total loading 3.9 million pixels, subject to mode and distribution. The second optical port is a copy, not additional capacity.
System preparation
- Collect panel model, cabinet resolution, receiving cards and versions, quantity, and wiring sketch.
- Keep original project/configuration and calibration data. Obtain the applicable cabinet file from its supplier; do not test another panel’s files.
- Check MX20 and VMP compatibility documentation; calculate port loading using actual frame rate, bit depth, and receiving cards.
- Prepare source and canvas; map off-show and check an internal pattern before content. Rehearse presets and recovery without an audience.
Planning questions
- Can I inquire without knowing the receiving-card model?
- Does maximum loading apply at every frame rate and bit depth?
- Do I need another scaler for a different screen aspect ratio?
- What if cabinets appear in the wrong order?
- Can NovaLCT replace VMP, or can any previous file be loaded?
- What can show support include?
Can I inquire without knowing the receiving-card model?
Yes: send the date, label photos, resolution, and approximate cabinet quantity. We can organize identification and compare controller/setup options; compatibility and final technical booking require the card and its files.
Does maximum loading apply at every frame rate and bit depth?
No. Port capacity depends on frame rate, bits, load width, and receiving-card model. Review the exact table and physical distribution rather than copying another processor’s cabinet count per port.
Do I need another scaler for a different screen aspect ratio?
All-In-One mode provides layers and scaling; Send-Only has a different scope. Compare content, crop, and readability with a sample. Assess external equipment when it adds show-required destinations or transitions, rather than automatically.
What if cabinets appear in the wrong order?
Compare physical wiring and mapping using an internal pattern and port/card identification. Separate position errors from signal problems. Save a working state before sending configuration and avoid live changes.
Can NovaLCT replace VMP, or can any previous file be loaded?
The documented COEX configuration uses VMP. Verify file and feature compatibility for the cabinet, receiving card, and version; opening a file does not establish RCFG/NCP conversion or calibration preservation.
What can show support include?
Assess controller, distribution, setup, rehearsal, and operation, or integration with your supplied panels. A sketch and tentative content help define specific tasks, files to preserve, and options around compatibility and availability.
Checks by symptom
| Cabinets out of order | Internal pattern, topology, and mapping. |
|---|---|
| Correct pattern, missing content | Input, source status, mode, and layers in VMP. |
Use and safety
Do not send cabinet files or update firmware without a backup and exact match. Rehearse restoration off-show.
Keep the controller dry, ventilated, and correctly powered. This control guide does not size panel rigging or power distribution.
Official documentation
Consulted October 23, 2026.