NovaStar: RCFGX and NCP with VX1000, MX40 Pro, and receiving cards

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.

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

No NCP obtained or final correction has been confirmed.

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.

Suggested test for a conference or stage with two batches

Use the receiving card and file worksheet before the technical test. Choose one representative unit from each batch and the same signal, content, and viewing conditions. Photos without recorded exposure and white balance are of little use for comparison. Also preserve naked-eye observations and avoid attributing the difference to wear without checking other causes.

We suggest recording one change at a time with the LED lead: initial state, selected file, destination, message, and result. Check borders, signal path, text, and grayscale. Repeat the observation under the event’s intended conditions. If a new difference appears, stop the test and follow the agreed restoration procedure; complete the result even if it remains unresolved.

Connect this worksheet with receiving card replacement and low latency, backups and continuity testing and video and screens. GLMedia can prepare video processing based on the identified equipment and files. These proposals do not record tests performed by GLMedia.

MX40 Pro: uneven brightness and calibration coefficients

These are different results, with incomplete equipment and version information.

Documentation for MX40 Pro: VMP V1.5.0, §§14.1 and 14.4, pp. 89 and 93–94. Tools → Coefficient Management displays Module Flash status. Brightness correction and brightness/chroma correction are mutually exclusive alternatives; available controls depend on the existing coefficients.

We suggest starting with screenshots of the current settings and a uniform pattern at the agreed test brightness. Identify the cabinets that differ and record batch, receiving card, firmware, file, and calibration state. Compare the same regions before and after a single reversible change. Reducing the difference by disabling a correction does not demonstrate its cause or establish that the screen has been calibrated.

Before making changes, prepare an export by cabinet: in §14.7, pp. 97–98, select the screen, Coefficient Management, and Cabinet; cabinets need IDs, and export is available only from Page 1. Export generates .db. Keep messages and the file.

We suggest naming each copy with cabinet, ID, batch, date, and the state it came from. Ask the manufacturer to confirm how to restore the initial state before applying coefficients from another unit. Do not treat “same brightness to the naked eye” as proof that the data is suitable for both cabinets. RCFGX/NCP files and Cabinet Painter are explained earlier in this guide.

MX40 Pro: saving coefficients and separating power cycles from preset changes

Separate saving parameters and coefficients from checking their retention after power cycling. Perform both tests using the documented procedure for the receiving card before concluding which data is lost.

The VMP V1.5.0 manual, §14.5 pp. 94–95 documents saving to prevent loss on power-off: screen → Coefficient Management → range → Save → OK. It fails if receiving cards go offline.

Without a current license, saving goes to the receiving card’s user area; with a license, it can go to the module. In §14.6 p. 96, Read applies coefficients: it reads Module Flash if present; otherwise, the user area. Record destination and source before confirming.

The read source may differ from the save destination. We suggest taking both screenshots to the manufacturer if the appearance changes again; we do not attribute that behavior to a missing license without reviewing the equipment. Do not erase factory data to try to match them.

Suggested test outside the event: with the LED lead, document content, cabinet, settings, preset, and save result. First check changing the preset and returning without powering off. Then, in a separate test with coordinated power, check power-off and power-on of the agreed assembly without changing the preset. Record when the appearance changes and which units were powered off; mixing both steps prevents identifying the trigger.

Use the coefficient and persistence worksheet for a conference or stage with cabinets from multiple batches. Results remain to be completed. Connect the test with continuity and backups and GLMedia’s video processing service. We do not record a calibration or physical test performed by GLMedia.

VX1000: a cabinet looks different after replacing a receiving card

Resending data with NovaLCT, copying it to the rest, and changing settings did not resolve it. Receiving card model, firmware, and NovaLCT version are missing.

Documented procedure: NovaStar NovaLCT V5.8.0, §6.1.3, pp. 50–53: Tools → Calibration → Single-Screen Mode → port and screen → Manage Coefficients. Module Flash lets you view status and coefficients and save them by address or topology. It requires modules with flash memory. The manual separates configuration and coefficient management; resending RCFGX does not establish that calibration data was recovered.

Before another send, we suggest identifying the repaired cabinet, old and new receiving cards, module, and original files. Request the corresponding review for that combination and the restoration procedure from the LED manufacturer. Keep a copy of current data and screenshots of scope, source, and destination. Work with one identified unit during the test; extending a change to the entire assembly may hide the original difference.

It does not demonstrate that its coefficients suit another screen. We suggest comparing white, grayscale, and uniform colors before and after the agreed procedure without changing signal, brightness, or gamma at the same time. Record appearance and messages; a visual improvement needs checking in our setup.

On another system, MX40 Pro with VMP, loading follows its own path: NovaStar VMP V1.5.0, §14.2, pp. 90–92. From Page 1: screen → Tools → Coefficient Management → Screen, Cabinet, or LDM range → .db file. Cabinet requires IDs. For Screen, the screen must be rectangular, start at (0,0), have no rotated cabinets, gaps, or overlaps, and match the resolution of a screen-type database. For cabinet/module, the ID is compared with the file; if Match: not matched appears and File ID is empty, manually select only the ID of a compatible file. OK loads and applies the coefficients. It fails if the controller or receiving card goes offline.

We suggest stopping the load if the relationship between file and ID is unclear and requesting the correct file and destination from the manufacturer. A file appearing in a list does not establish its origin. Keep the previous export and review saving and persistence before testing. ID matching is recorded in the worksheet; we did not perform any physical loading.

A5s Plus: the module still looks grainy after reading Module Flash

The problem continues. The image was not inspected.

For the exact receiving card model, NovaStar A5s Plus Specifications V1.3.0, Features / Improvements to Maintainability, p. 3 documents ID and coefficient management when the module has flash. Smart Module requires specific firmware. The datasheet does not identify the full Gloshine cabinet model or demonstrate that the noise in this case is a calibration fault.

In NovaLCT V5.8.0, §6.1.3, p. 53, flash messages guide the review: Hardware Fault points to a configuration/topology mismatch; Communication Error to the connection; Flash Topology Error to a module without flash or an unconfigured topology. The name Hardware Fault alone does not confirm a defective receiving card.

Suggested bench test with the responsible technician: photograph the module’s identification and position before intervening. Record the exact message and stage where it appears: reading, applying, or saving. Repeating “read Module Flash” without recording its response adds little information if it was already done and the symptom persists. Compare with a reference unit kept intact.

If the manufacturer confirms compatible spares and the handling procedure, we suggest one cross-swap at a time with the equipment de-energized: record whether the defect follows the module or stays at the position. Preserve the relationship between position, module, and files. The result guides the next inquiry to the manufacturer; it does not by itself identify a connector, voltage, board, or parameter as the cause. We provide no supply voltage values: the exact cabinet model is missing.

Common error: correcting the entire screen to disguise one module, or copying data from any spare because it has the same pixel pitch. Request confirmation of batch, revision, and driver IC. For a conference or stage LED screen, use the repair and coefficient worksheet, the guide on continuity and backups, and GLMedia’s video processing service. The worksheet contains proposed tests and results to be completed.