Video & projection
Novastar MX40 Pro troubleshooting
The Novastar MX40 Pro problems live-event techs bring to Ask Roadie most (also called MX 40, MX40). Pick your symptom, or describe your own in plain words, and get the likeliest fix first, with the manual page when there is one.
Common MX40 Pro errors & problems
What techs run into most, and what's usually behind it. The step-by-step fix for your exact unit is in Ask Roadie.
- Step-by-step fixGet the fix →
Art-Net or SNMP control / central management not working
Likely cause: SNMP and Art-Net integration were added in V1.2.0; they must also be enabled in settings.
- Step-by-step fixGet the fix →
Cannot enable Low Latency and Genlock at the same time
Likely cause: The two features use incompatible timing paths in firmware, so only one can be active.
- Step-by-step fixGet the fix →
Device will not power on
Likely cause: Confirms the input is within the rated universal-mains range and rules out cable/switch before assuming a hardware fault.
- Step-by-step fixGet the fix →
Firmware upgrade to V1.4.0 fails or VMP will not connect after update
Likely cause: V1.4.0 has a minimum prior-version prerequisite and a matched-VMP requirement; skipping either causes the upgrade or the control link to fail.
- Step-by-step fixGet the fix →
Genlock sync unstable, jittering or dropping lock
Likely cause: NovaStar traced genlock instability to power-supply noise coupling into the Genlock input; isolating the power path removes the interference.
- Step-by-step fixGet the fix →
HDR not available on DP 1.2 or 12G-SDI input
Likely cause: HDR on those inputs was introduced in the V1.2.0 firmware; earlier versions lack the option.
- Step-by-step fixGet the fix →
Image flicker on the LED wall
Likely cause: Persistence-of-vision flicker on LED is reduced by higher refresh; NovaStar documents low frame rate as a flicker cause.
- Step-by-step fixGet the fix →
No signal / input not detected (HDMI, DP or SDI)
Likely cause: MX40 Pro only locks when the incoming timing is within a supported format; the front panel/VMP shows the detected signal so a mismatch is easy to spot.
- Step-by-step fixGet the fix →
One or more Ethernet output ports show dark cabinets / not loading
Likely cause: The MX40 Pro assigns cabinets to ports by the VMP layout; an unbalanced or wrong-mode map leaves ports unfed, showing dark sections.
- Step-by-step fixGet the fix →
Set up device / port backup (redundancy) correctly
Likely cause: COEX backup requires matched topology on both the controller and the receiving-card loop so the standby path can take over seamlessly.
Not on the list? Describe it your way, or paste the error code off the display. Ask Roadie works the problem with you until it's fixed or you have a clear next move.
How Ask Roadie helps with the MX40 Pro
- 1. Pick the Novastar MX40 Pro. It's already in the list.
- 2. Describe what you're seeing. In your own words, or the error code off the screen.
- 3. Get the likeliest fix first. Steps in order, the manual page when there is one, and a note when other techs have confirmed it.
- 4. Still broken? Tap 👎 and it keeps going from where you left off.