NovaLCT: common errors and solutions

NovaLCT is the most widespread LED configuration software on the market — and the source of a good share of Lédia's calls. Nearly all « NovaLCT failures » fall into five families, all fixable without touching hardware.

Quick answerThe five NovaLCT classics: controller not detected (USB, driver, administrator rights, firewall); configuration lost after a power cut (Send without Save to Hardware); wrong read-back values (card firmware too old for the chip); a tint checkerboard (coefficients not reloaded); and plain wrong software — a COEX processor is driven by VMP, not NovaLCT.

The controller does not appear: the complete checklist

  1. USB cable plugged in directly, no hub, and tested with a second cable: cause number one by far.
  2. NovaLCT run as administrator (right-click the icon): without it, USB port access can fail silently.
  3. Controller USB driver visible in Windows Device Manager; reinstall it if needed.
  4. Firewall and antivirus: allow NovaLCT, especially over the network; put the PC in the controller's IP range.
  5. NovaLCT version: an old version ignores recent controllers. Also check the hardware is NovaLCT's job at all — a COEX (MX40 Pro family) is driven by VMP.
  6. Reboot the controller as a last resort: some stay mute after an incomplete power cycle.

Send is not Save: the trap that strikes weeks later

Sending a configuration to the cards (Send) applies it immediately but does not write it to memory: without Save to Hardware, everything vanishes at the first power cut — often weeks after commissioning, when nobody remembers the operation.

Systematic reflex: after every validated change, Save to Hardware, then export a dated configuration file (RCFG) stored off the control PC. Our « lost settings » guide covers full recovery.

Inconsistent read-back values: think firmware

If NovaLCT's displayed values do not match the module's reality (impossible scan, absurd frequencies), the receiving card firmware probably does not support the module's chip: read-backs are then unreliable.

Firmware updates happen with the wall out of operation, configuration and coefficients backed up first — never before an event.

Smart Settings and coefficients: powerful, therefore dangerous

Smart Settings rebuilds an unknown module's configuration by asking questions (how many modules light, in what order…). Useful for an inherited wall without files, but every wrong answer produces a wrong configuration: keep it for a wall out of operation and write down your answers.

Calibration coefficients live in Manage Coefficients: back up before any work, reload after any card or module replacement. A tint checkerboard after an intervention almost always means coefficients not reloaded — see our colour and calibration guide.

When to call an engineer

Controller still invisible after the full checklist, a configuration to rebuild without the original file, or inconsistent read-backs despite up-to-date firmware: get guided help before changing anything. Lédia knows NovaLCT's exact menus and when an operation must wait until the wall is out of service.

A failure right now? Lédia, our AI engineer, guides you step by step, 24/7, photos included.

Talk to LédiaSee pricing

Frequently asked questions

NovaLCT sees the controller but not the receiving cards — what to check?

Run Detect Communication Status: it shows where the chain stops. Then check the first mute link's network cable, then its card — the boundary method, as for a dark area.

Which NovaLCT version should I install?

The version validated by your wall's supplier, not necessarily the latest. On a fleet, standardize the version on every control PC and keep the installer offline.

Advanced mode asks for a password — is that normal?

Yes: NovaLCT's sensitive functions are password-protected (the default is in NovaStar's documentation). The protection exists because those menus can derail the wall: only enter with a backup done.

Can I drive an MX40 Pro with NovaLCT?

No. COEX processors (MX40 Pro, MX2000 Pro…) are driven by VMP. NovaLCT covers MCTRL, VX and classic receiving cards. The wrong tool makes healthy hardware look broken.

Read next