Preparing displays for conferences, stands and stages
Start with the content, display surfaces and who supplies each part of the system. A plan, label photos and the existing configuration help frame a video and display enquiry. Technical details help define the preparation, rehearsal and operation your project needs.
VX1000 and disabled RCFGX: identify the receiving card first
Check NCP loading, calibration, and backup recovery separately.
Request a photo of the label, cabinet model, and installed versions. If the PC also cannot see the controller, start with NovaStar USB and network connection. If it sees the controller and only a file operation fails, record that difference to narrow down the diagnosis.
We suggest gathering this information before choosing a procedure. Preserve received files exactly as delivered, with sender and date; work with copies. A filename resembling the cabinet’s name does not confirm a match.
| Missing information | Where to record it | What it is for |
|---|---|---|
| Controller and firmware | Label and unit screenshot | Distinguish VX1000 from MX40 Pro and document the version |
| Exact receiving card and firmware | Label and information available in the software | Avoid applying A10s Pro instructions to an assumed model |
| Cabinet and batch | Label, serial number, and manufacturer’s datasheet | Connect each file with the intended units |
| Software and received file | Version, extension, sender, and revision | Explain which operation is disabled and with which file |
A10s Pro in NovaLCT 5.8.0: documented NCP procedure
NovaLCT V5.8.0, §5.2.2 p. 10 directs A10s Pro to NCP; §5.2.2.2 pp. 21–22 requires a file compatible with the receiving card. Compare with the installed interface.
Documented path: Screen Configuration → Receiving Card → NCP Management → Load NCP. Select file and cabinet; Send NCP sends the file and Send Mode Parameters sends the mode. Select the destination receiving cards, send, and use Save to HW.
Restore NCP is documented for A8s Pro ≥V1.2.0.0, not A10s Pro. Reset the Starting Coordinate moves the origin to (0,0) and may repeat the image.
For the rehearsal, we suggest a spare unit identified with the LED lead. Do not select all units to check just one. Before sending, agree with the manufacturer on how to restore the initial state and keep the connection map. If a compatible file or confirmed restoration procedure is missing, leave sending pending. Record the exact software message: updating firmware by trial and error adds another variable.
MX40 Pro and A5s Plus: RCFGX available and functions to check
The COEX NCP V1.0.1 manual, table 1-2 p. 3 and §6.1.1 p. 19 supports RCFGX for A5s Plus: Tools → Maintain → Cabinet. To edit it, it documents NovaLCT with a non-COEX controller; VMP does not modify RCFGX.
An LED powering on does not verify all requested functions. Record which are missing and whether the selection applies to screen or cabinet. Request a response from the manufacturer for your exact combination before installing a different package.
There are differences between editions: NCP V1.0.1, §6.1.2 p. 19, mentions RCFGX for A10s Pro in certain scenarios; NovaLCT V5.8.0 directs that model to NCP. For COEX, we use the explicit restriction in VMP V1.5.0, §15.2 p. 102: A10s Pro is updated with NCP. We do not transfer the A5s Plus path to A10s Pro.
Requesting the correct NCP and preserving the library
The NCP V1.0.1 manual, §§2.1–2.4 and 3.5, pp. 4–5 and 12 includes configuration and firmware together with image parameters. Its generation depends on the receiving card and driver IC; the documented process delivers the file through NovaStar and the LED manufacturer. Changing an RCFGX extension does not create that data.
For the request, we suggest sending identification for both batches, label photos, original files, versions, and a description of the missing function. Request written confirmation of which cabinets the package covers, what changes, how to check it, and how to restore the initial state. A delivered file still needs testing in the setup.
In VMP V1.5.0, §15.2 pp. 101–102, Tools → Maintain → Cabinet lets you review manufacturer, cabinet, receiving card, and firmware. To update: select destinations, Update, Import, and file; then Update. The manufacturer recommends a wired network. Cabinet Painter copies configuration and firmware: we do not use it as a color test between batches.
In §16.2 pp. 104–107, Cabinet Library manages existing NCP files: Local pack stays on the PC; Device pack on the controller. Export preserves packages; Packaging reorganizes NCP files already available. It does not demonstrate generating optical parameters from RCFGX. Compare receiving card type, file version, and revision with the request before applying it.
Questions for preparing the system
Can I enquire before I have an NCP file or receiving-card model?
Yes. Tell us what you want to display and which parts your team already supplies. Label photos and available files can follow later; that identification frames the technical review and what must be requested from the manufacturer.
Can I swap RCFGX and NCP by renaming the file?
The formats have different scopes. NCP can contain configuration, firmware and cabinet parameters. Retain original extensions and provenance and request the file matched to receiving card, driver and batch; renaming RCFGX does not create an NCP package.
Does the A5s Plus procedure also apply to A10s Pro?
Choose the procedure by model and document edition. COEX NCP V1.0.1 permits RCFGX for A5s Plus; VMP V1.5.0 directs A10s Pro to NCP. Confirm installed versions and prepare the test and recovery procedure before sending files.
Preparing the enquiry and test
Gather what is available: event purpose and city, cabinet plan, video source, models and versions. The date or equipment may still be undecided. Identify who retains the originals and authorises changes. Agree a test unit and window, acceptance criteria and recovery procedure before making changes.
Editable identification and test worksheet
Continue with your system controller or files
Manuals and editions
Check the stated model, edition and language at the manufacturer’s source. Verify the document edition and installed software version separately.
MX40 Pro · User Manual V1.5.1
Open official documentation ↗COEX · NCP file · Manual V1.0.1
Open official documentation ↗
Documentation consulted
Document adaptation: October 29, 2026. Check your system model and version before applying changes.
